Hello everyone,
I propose that in the « Continue only if » block, in addition to a manual value as today, there be the possibility to choose a device, e.g.:
I have a temperature setpoint device; I would like to be able to specify whether the value from a thermometer is >, <, = … compared to the setpoint device.
I hope I was clear.
Unless I’m mistaken, I couldn’t find any request to this effect.
Thanks
If I understand correctly, you can do it.
You need to retrieve the latest state of your device "setpoint temperature
Hello everyone,
This could also be useful for other scenes, for example:
- Turning on an ambient light when presence is detected, only between sunset and sunrise?
If I’m not mistaken, it’s already possible by putting all the conditions one after the other… Isn’t it? ![]()
@guim31 , @Tlse-vins , I haven’t fully understood the workings of Gladys yet, but if I’m not mistaken it’s not quite what I want.
In my specific case for heating management, I have a room thermostat with a setpoint adjustment that I can change from Gladys or physically; in my scenes I want to be able to say: retrieve the measured temperature, then continue only if it is > the setpoint feature, not a hard-coded value.
This would avoid modifying the scenes to change the values, and allow managing the setpoint either manually or via scenes with time-based conditions, calendar…
Also, on rereading, this should be combined with another request already made, I believe, which is to be able to perform operations on the criterion
What about calling your « consigne » scene from your scene, to continue only if it wouldn’t work?
To work around this I have in a scene:
- Retrieval of the setpoint temperature value
- Retrieval of the room temperature value
An HTTP request to perform a subtraction
I still need to compare the result to zero.
This trick runs on 2 scenes: one to turn off, the other to turn on

It seems to me that this makes sense and will help simplify some scenes and reduce their number, because today you have to work around it via Node-RED or other tools, which is not within everyone’s reach.
Let’s let the votes do their work
Hello everyone,
Well, I think that with the latest versions part of the request concerning the « continue only if » block has been addressed, and with the ability to perform additional calculations as well ![]()
Great update, this 4.23 ![]()
@gaelbillon great
I think we can close this request, right?
I don’t know if this request makes much sense in the « state change » trigger
@pierre-gilles yes it can be closed.
For the one about the state change, I think there could be interest, but I’ll think about it a bit more and I’ll make another request if needed.
Thanks