Hi all
Ive a small Gladys setup here in Australia. Suddenly it stopped reporting the temperatures (and humidities) from all the different sensors around, from Hot Water Service down. Nothing else stopped. See the screen grabs from my phone.
So having misplaced the system password, I simply restarted the whole server, and things started again. But for reasons I dont know, it has now happened again.
Im guessing I need to reinstall Gladys and take more care with the pswd, and then I will be able to ‘look at the logs’ and find out what is going on. But someone here might have some suggestions?
I note that the graphing of the HWS temperature over the last 7 days seems to have also stopped around the 13th, today being the 17th. Does that provide a cue to the problem?
Cheers, Barney
Hi @drBarns,
Which sensors are you using, and which integration are they connected to?
Turns out it is all the devices using the Zigbee2mqtt integration. Including, I now realise, a dual GPO which ran the Xmas lights a few months ago, and are now not responding either.
I assume that there is some way to restart it, from the CLI. But I remembered the Setup command, under the Zigbee2, menu, has an ‘ Enable or disable the service’.
This does indeed restart things on next refresh… But doesn’t explain what caused the issue in the first place.
Any idea pls on how it happened and how to avoid it in future?
Cheers, Barney
It really seems like a hardware issue.
What hardware are you using to run Gladys?
If you’re using a Raspberry Pi, especially with a micro-SD for storage, I strongly recommend switching to a mini-PC with an SSD.
Raspberry Pis are known to have USB power issues when used with Zigbee2MQTT and a Zigbee USB stick.
Micro-SD cards should be avoided at all costs—they’re unreliable and will inevitably lead to disk corruption.
I personally use and recommend the Beelink Mini S12 Pro (powerful & power-efficient N100 CPU, 16GB RAM, 500GB SSD). It’s been working great for me! 