Web Interface Domoticz not available after enabling polling

[uschuga]

Hello,
The starting point of the total failure was the insufficient installation of Fibaro FGBS222, where none of the connected DS18B20 temperature sensors were registered in the device table. Changes of the configurations do not seem to be taken over by the device. To solve the problem I have activated polling on a trial basis. Since then Domoticz is no longer accessible via web interface. Probably the ZWave network is overloaded with polling tasks.

As Z-Wave controller I use the USB stick ZMEEUZB1, about 40 Z-Wave devices are in operation, some for years. Now I have no access anymore! Stupidly I did not create any current backups the last months.
Fortunately I still have access to the Raspberry via Putty. Unfortunately I have only limited knowledge of Linux. I think that in a configuration file of the ZWave stick an entry has to be set back to "Disable Polling". To do this I would also need to get to the configuration file - but how? Would this be the right way? Are there alternatives or I have not yet understood the problem properly?
I will try to get new access to the web interface without plugged ZWave stick in order to make an inital backup. But this will not solve the problem...
I am grateful for any hint!

[willemd]

I don't know anything about Z-wave but .... from your description it is not clear whether your conclusion that it is polling overload is correct.
Are you sure that Domoticz is still running? Check first.

To find out:
1) startup Putty and open a connection to your Raspberry IP number and login.
2) run the following command "ps -eaf | grep domoticz" at the command prompt.

It should show something like the following:

root 12751 1 4 11:31 ? 00:09:21 /home/pi/domoticz/domoticz -daemon -www 8080 -sslwww 443 -log /media/usbdisk/domoticz.log -loglevel normal,status,error
pi 27891 27620 0 14:51 pts/0 00:00:00 grep --color=auto domoticz

This shows the grep command you just typed yourself and on the other line the domoticz main process.

[uschuga]

Thank you for the fast reply.
First, I restartet the raspberry without the USB-ZWave stick and domoticz was reachable via web interface. This is an indication, that the ZWave stick and its inteaction with the Zwave network seems to be the reason of the problem. Than, as domoticz is available (check by putty not necessary anymore ), I did a backup (without stick) by domoticz. Currently, I take an image of the SD card.
My idea is to start the raspberry with stick OUTSIDE of the home installation, so that the stick is not able to find any device and the problematic polling does not occur - hopefully. Thats the plan - but first I take the images.

[uschuga]

After finishing the backups I come back to advice from willemd to check whether Domoticz is running with the Zwave Stick (without Stick web interface is reachable and domoticz is running!):

pi@Rasp3:~ $ ps -eaf | grep domoticz
pi 1563 985 0 17:38 pts/0 00:00:00 grep --color=auto domoticz

How to interprete these lines?

Above mentioned idea to run the system in a zwave free environment does not lead to wished result. I used alloy foil around the stick to separat it from the rest of zwave world. Domoticz ist still not reachable via web interface.

[willemd]

So you only get as a response the single line that shows that the grep process is running. The Domoticz process itself is not running since that would have been the second line.
Next step is to find out why it is not running....
What if you try a manual start by typing "sudo service domoticz start"? Any error messages? Any messages in the log file?

[uschuga]

Thank you for the analysis. This gives me a new view.
Here is the result to your proposed command line:

pi@Rasp3:~ $ ps -eaf | grep domoticz
pi 1670 1345 0 20:25 pts/0 00:00:00 grep --color=auto domoticz
pi@Rasp3:~ $ sudo service domoticz start
pi@Rasp3:~ $

What can you infer from this?

[uschuga]

Here further status info:

pi@Rasp3:~ $ sudo service domoticz status
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Sat 2022-09-17 18:04:25 CEST; 2h 56min ago
Docs: man:systemd-sysv-generator(8)
Process: 614 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SU

Sep 17 18:04:24 Rasp3 systemd[1]: Starting LSB: Home Automation System...
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: 2022-09-17 18:04:25.293 Status: Domotic
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: 2022-09-17 18:04:25.293 Status: Build H
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: 2022-09-17 18:04:25.293 Status: Startup
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: domoticz: Domoticz is starting up....
Sep 17 18:04:25 Rasp3 domoticz[623]: Domoticz is starting up....
Sep 17 18:04:25 Rasp3 domoticz[626]: Domoticz running...
Sep 17 18:04:25 Rasp3 systemd[1]: Started LSB: Home Automation System.
lines 1-14/14 (END)...skipping...
● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (exited) since Sat 2022-09-17 18:04:25 CEST; 2h 56min ago
Docs: man:systemd-sysv-generator(8)
Process: 614 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/SU

Sep 17 18:04:24 Rasp3 systemd[1]: Starting LSB: Home Automation System...
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: 2022-09-17 18:04:25.293 Status: Domotic
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: 2022-09-17 18:04:25.293 Status: Build H
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: 2022-09-17 18:04:25.293 Status: Startup
Sep 17 18:04:25 Rasp3 domoticz.sh[614]: domoticz: Domoticz is starting up....
Sep 17 18:04:25 Rasp3 domoticz[623]: Domoticz is starting up....
Sep 17 18:04:25 Rasp3 domoticz[626]: Domoticz running...
Sep 17 18:04:25 Rasp3 systemd[1]: Started LSB: Home Automation System.
~

Domoticz seems to run, but still no web interface...

[willemd]

Sorry, here is where my knowledge ends. Output on my system looks similar, although there seems to be some duplication in your post and there are two lines missing.

● domoticz.service - LSB: Home Automation System
Loaded: loaded (/etc/init.d/domoticz.sh; generated)
Active: active (running) since Sat 2022-09-17 11:31:20 CEST; 12h ago
Docs: man:systemd-sysv-generator(8)
Process: 12743 ExecStart=/etc/init.d/domoticz.sh start (code=exited, status=0/
Tasks: 28 (limit: 2059)
CGroup: /system.slice/domoticz.service
└─12751 /home/pi/domoticz/domoticz -daemon -www 8080 -sslwww 443 -log

Sep 17 11:31:19 redcasepi systemd[1]: Starting LSB: Home Automation System...
Sep 17 11:31:20 redcasepi domoticz.sh[12743]: 2022-09-17 11:31:20.042 Status: D
Sep 17 11:31:20 redcasepi domoticz.sh[12743]: 2022-09-17 11:31:20.042 Status: B
Sep 17 11:31:20 redcasepi domoticz.sh[12743]: 2022-09-17 11:31:20.042 Status: S
Sep 17 11:31:20 redcasepi domoticz.sh[12743]: domoticz: Domoticz is starting up.
Sep 17 11:31:20 redcasepi domoticz[12750]: Domoticz is starting up....
Sep 17 11:31:20 redcasepi domoticz[12751]: Domoticz running...
Sep 17 11:31:20 redcasepi systemd[1]: Started LSB: Home Automation System.

[uschuga]

Hello willemd - thank you for the assistance.

With try and error (by using a 2nd Rasp, 2nd Zwave Stick and older backups) it turns out that polling is not the issue. This seems to be a coincidence. I assume that Domoticz is running permanently well. In some cases the web interface works fine, but not for more than a few minutes. This is not reproducible fo me at the moment.
Now, I concentrate on browser types, clearing the cash (private mode does not help in all cases) and proper IP adress assignment.

[uschuga]

The problem seems to be solved. It was due to the power supply. The micro USB plug had a bad contact. However, this was not immediately noticeable because the connected Uninterruptible Power Supply (UPS) probably compensated for this to some extent.
At the end that cost quite some time and nerves. In hindsight, you're always smarter.
However, the Fibaro universal sensor FGBS-222 still does not work as expected. But this is another topic...