The logbook only logs entities with binary states (on/off, true/false), not sensors that report continuously variable analogue levels. It would rapidly fill up if it logged every change in analogue level.
There is a History page for analogue sensors.
What automations?
Please post the correctly formatted text (not a screenshot of text) of one of your automations that does not trigger.
and then I see two different platform: under the trigger block.
(Not sure why we need a switch here under the trigger section…?)
and then I’m not sure type: value or platform: device or domain: sensor being a thing for trigger, since I don’t find those in the aforementioned trigger document.
I’m sure other experts would chime in. But… @Alfonsolsl could you help elaborate what you are trying to achieve with this automation? Also does this automation do what you are trying to do, when you manually click the button?
Hello and thanks to spot that, basically this is the reason the conditions was not meet.
For some reason I coded this in a different way I normally do and for some reason though in a OR when set the thresholds on the humidity sensor.
Dumb… xD
I will remove the limits and use choose options for each case.
What this automation does:
This control when my fan exhaust turns on, based on the humidity of the room and the state of the light.
If the light is on the fan will turn on only when the humidity is above 78% and turn off when is below 75%. But I have the two triggers cos if you turn on the light and the humidity is already above the threshold should turn on but if the humidity raises 78% when the light is already on should turn on also.
If the light turns off the fan should turn off no matter the humidity levels.
Edit: I just had to remove the device trigger and set a state trigger for humidity with any condition on it. My choose already check the conditions on each case.