I can’t use this mode!
When I check « Start scene on any state change, regardless of value » and select a device, the option disappears!
Hello Chris75,
Thank you for the feedback and screenshots, they are very clear. What you are observing is not a bug, it is an intentional behavior of Gladys. I’ll explain why.
How the « on every state change » mode works
This mode does not look at a specific value. It compares the new value sent by the device to the previous value, and only triggers the scene if the two are different. This is perfect for a temperature sensor, a plug, or a switch, whose value really changes over time.
Why it is not offered for a button
A button does not really have a « state »: it sends an event. When you do a single click, it sends the value « single click ». If you do another single click, it sends exactly the same value. For the « state change » mode, there is therefore no change between the two clicks, and the scene would not be triggered.
Concretely, if Gladys allowed this mode on a button, your scene would be triggered on the first click, then never again unless you change the type of click. It would be a real trap. That is why, as soon as you choose a button, Gladys removes this option and instead offers you the « Button Click » widget.
What to do for your case
- Leave the « on every state change » box unchecked.
- Select your button from the left list.
- In the right menu, choose the type of click that should trigger the scene (single click, double click, long press…).
With this configuration, the scene is triggered on every click of this type, without any limitation, even if you click ten times in a row. This is exactly the behavior you were looking for.
If your need is rather « any type of click triggers the scene », it is not possible today in one line: you need to add a trigger per click type. Do not hesitate to open a dedicated topic if this is what you are looking for, it could become an evolution.
Have a nice day!
Oh okay, I just understood how this option works: it would be better then to only display the affected devices to avoid the confusion I had and to explain it well in the documentation!
And indeed, this is not the feature I would want: I will make a separate request