Hello,
My domoticz platform on RaspberryOS (Buster) and 1 wire Pi Plus shows every 10s messages like
Jul 7 22:11:10 domoticz kernel: [ 3025.890005] ds2482_wait_1wire_idle: timeout on channel 0
Jul 7 22:11:10 domoticz owserver[335]: DEFAULT: ow_reconnect.c:(69) Failed to reconnect DS2482-100 bus master!
Jul 7 22:11:21 domoticz kernel: [ 3036.650633] ds2482_wait_1wire_idle: timeout on channel 0
Jul 7 22:11:21 domoticz owserver[335]: DEFAULT: ow_reconnect.c:(69) Failed to reconnect DS2482-100 bus master!
Jul 7 22:11:32 domoticz kernel: [ 3047.530629] ds2482_wait_1wire_idle: timeout on channel 0
Jul 7 22:11:32 domoticz owserver[335]: DEFAULT: ow_reconnect.c:(69) Failed to reconnect DS2482-100 bus master!
More, htop shows an abnormal activity on owserver and owfs
I am obliged to use owfs for domoticz.
Any idea of what is the problem ?
Thank you
owserver[335]: DEFAULT: ow_reconnect.c:(69) Failed to reconnect DS2482-100 bus master!
1213 Views - Created 07/07/2021
07/07/2021
Posted by:
anthropo
07/07/2021
Posted by:
anthropo
cat /etc/owfs.conf
device = /dev/i2c-1
mountpoint = /mnt/1wire
allow_other
http: port = 2121
ftp: port = 2120
device = /dev/i2c-1
mountpoint = /mnt/1wire
allow_other
http: port = 2121
ftp: port = 2120
07/07/2021
Posted by:
anthropo
Other problem : I must reboot to restart owserver service
sudo service owserver restart
Job for owserver.service failed because the control process exited with error code.
See "systemctl status owserver.service" and "journalctl -xe" for details.
systemctl status owserver.service
* owserver.service - Backend server for 1-wire control
Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-07-07 22:16:54 CEST; 10s ago
Docs: man:owserver(1)
Process: 15558 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited, status=1/FAILURE)
Main PID: 15558 (code=exited, status=1/FAILURE)
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Failed with result 'exit-code'.
juil. 07 22:16:54 domoticz systemd[1]: Failed to start Backend server for 1-wire control.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Service RestartSec=100ms expired, scheduling restart.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
juil. 07 22:16:54 domoticz systemd[1]: Stopped Backend server for 1-wire control.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Start request repeated too quickly.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Failed with result 'exit-code'.
juil. 07 22:16:54 domoticz systemd[1]: Failed to start Backend server for 1-wire control.
sudo service owserver restart
Job for owserver.service failed because the control process exited with error code.
See "systemctl status owserver.service" and "journalctl -xe" for details.
systemctl status owserver.service
* owserver.service - Backend server for 1-wire control
Loaded: loaded (/lib/systemd/system/owserver.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-07-07 22:16:54 CEST; 10s ago
Docs: man:owserver(1)
Process: 15558 ExecStart=/usr/bin/owserver -c /etc/owfs.conf (code=exited, status=1/FAILURE)
Main PID: 15558 (code=exited, status=1/FAILURE)
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Failed with result 'exit-code'.
juil. 07 22:16:54 domoticz systemd[1]: Failed to start Backend server for 1-wire control.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Service RestartSec=100ms expired, scheduling restart.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Scheduled restart job, restart counter is at 5.
juil. 07 22:16:54 domoticz systemd[1]: Stopped Backend server for 1-wire control.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Start request repeated too quickly.
juil. 07 22:16:54 domoticz systemd[1]: owserver.service: Failed with result 'exit-code'.
juil. 07 22:16:54 domoticz systemd[1]: Failed to start Backend server for 1-wire control.
08/07/2021
Posted by:
anthropo
First problem solved disabling
sh -c "echo ds2482 0x18 > /sys/bus/i2c/devices/i2c-1/new_device "
in /etc/rc.local
But Cpu load is always high on owserver and owfs (about 10% each)
sh -c "echo ds2482 0x18 > /sys/bus/i2c/devices/i2c-1/new_device "
in /etc/rc.local
But Cpu load is always high on owserver and owfs (about 10% each)
08/07/2021
Posted by:
andrew
Location:
United Kingdom
Hello
I am glad you managed to solve your first problem. We do have a tutorial for setting up owfs on the Raspberry Pi. It may be worth reading through the tutorial to make sure your owfs setup is configured correctly.
OWFS does use a lot of CPU resources so if it is being accessed by other software like domoticz you may get a 10% CPU load on the processes.
With regards to restarting owserver, on my Linux server which uses owfs and home assistant I have found that stopping the owserver and owfs processes before starting owfs and then owserver sometimes works. You may have to wait a few seconds between starting the owfs and owserver services to allow owfs to finish loading.
Sometimes I have found that the only way to get owfs working again is to restart the server.
I am glad you managed to solve your first problem. We do have a tutorial for setting up owfs on the Raspberry Pi. It may be worth reading through the tutorial to make sure your owfs setup is configured correctly.
OWFS does use a lot of CPU resources so if it is being accessed by other software like domoticz you may get a 10% CPU load on the processes.
With regards to restarting owserver, on my Linux server which uses owfs and home assistant I have found that stopping the owserver and owfs processes before starting owfs and then owserver sometimes works. You may have to wait a few seconds between starting the owfs and owserver services to allow owfs to finish loading.
systemctl stop owserver.servicesystemctl stop owfs.servicesystemctl start owfs.servicesystemctl start owserver.serviceSometimes I have found that the only way to get owfs working again is to restart the server.
Note: documents in Portable Document Format (PDF) require Adobe Acrobat Reader 5.0 or higher to view, download Adobe Acrobat Reader or other PDF reading software for your computer or mobile device.