Hello
I’ve had a problem for a few days
Hi @Prof_Techno,
Can you tell us more about your hardware?
Have you checked whether there was something limiting on your machine in terms of resources (CPU at 100% because of another program, RAM full, disk full?)
Is there anything special in the Gladys logs? (docker logs gladys)
Thanks 
1 Like
for the hardware I have a mini PC with 16 GB of RAM and a 256 GB SSD with only 128 GB used
for the processor I’m at 8% with Firefox running
however I don’t know where to find the log
When you say that the scenes remain frozen in a state, what is the symptom?
I’m not sure I understand
to keep it simple everything works: the heating starts and turns off according to the scenes, no problem
and suddenly I don’t know why the state of the radiators, and consequently the radiator contactors, remains stuck in a
So are you sure it’s Gladys that’s the problem and not just your radiators?
I can recommend adding messages during the execution of your scenes to verify they run correctly (using the « Send a message » action)
The log you see is completely normal
1 Like
Ok, I’ll test the messages on two radiators: the one in rad and
1 Like
No change
It still gets stuck in one position and there’s nothing unusual in the logs. A reboot is enough to restart everything, but it’s annoying
Are you sure the signal is good? Is it Wi‑Fi or ZigBee?
I had a problem like that once, and it turned out to be a device that, when powered on, caused interference on the ZigBee channel. Once replaced, no more issues…
So the problem is that it’s never the same heater that gets stuck, and otherwise it’s Zigbee.
I sometimes have problems triggering scenes for thermostatic heads, lights, or sockets.
If you offset all the scene triggers and add a Telegram message, it could help you see where it’s failing, when and who (basically: one heater per scene — long live duplication!).
I already have 49 scenes for the heating; I actually wanted to redo them to reduce that.
And I’ve already checked the Telegram messages to see where the problem is, but found nothing.
I’ll redo it tomorrow and I’ll keep you posted.
If the scene change works, then there must have been a conflict that occurs in certain circumstances which I can’t find.
Maybe you’ve created an infinite loop with your scenes using triggers and actions in some cases?
Example: You create a state in an action that triggers a scene which itself creates a state?
1 Like
It’s possible, but since this occurs randomly and never on the same radiator, I think the best thing is to redo everything.
I think I have a few hours to think things through and redo everything properly (I’ll take the opportunity to improve it with Gladys’s new features)