Hello,
For a little while now, I’ve had a significant latency that has appeared between my HMI (interface homme-machine) and the action executed on my devices. Over time it increased until last night when my lamps would no longer turn off via the interface.
I investigated a bit on my side based on what I found on the forum, but nothing conclusive so far:
Hi @plikam!
Several points to confirm:
htop can be useful to check that)To go further in the investigation, locally, in your browser, you can do on your dashboard: « Right click » + « Inspect Element »
Then open the « Network » tab, and trigger sending a command by toggling a light’s on/off on the dashboard.
Then look at the request’s execution time, to see if the problem is between your browser and Gladys (or Gladys being slow to process the request), or if the problem is further along (between Gladys → the final device)
It looks like a limitation of the data read speed in the database.
Did you check the « keep all history » option?
How long have you been using Gladys?
I don’t know why, but I just tried again and no problems, on the computer as well as on the phone.
I access it locally, my Pi isn’t underwater at all.
I have unlimited history retention, but I don’t see why that would cause me problems turning a lamp on/off.
I’ll redo the tests on a day when it doesn’t work.
What is also possible is that it was updated and that the initial startup slowed your first interaction with Gladys or Zigbee (do you use it?).
