To get the state value, use this format: value_template: '{{ states.weather.home.temperature.state }} or states("weather.home.temperature")
But if it is a weather entity, the temperature is not in the state but in an attribute, so you should use this: states.weather.home.attributes.temperature
With this solution, I have searched again in the forum & docs but couldn’t find a lot.
The reason I’m saying this: I’m curious about how could I have found this solution?
Hi Nick,
O learned the way you just did, by asking in this Forum and searching for something that was similar to my issue. Specifically for Yaml stuff like this, I can recommend that you use the Developer Tools (Found in the menu on the left side) and then Template to test stuff out. That has really helped me a lot, because you see if you get the values you expect, without having to restart HA all the time.
I’ve very new to HA, but already love it with all my heart. I’ve looked through lots of posts, but this one seems to be the closest to what I’m chasing down. My wife and I live in a tiny house on wheels and often need to hack our water source. But each winter I’m faced with a similar challenge of how to keep out water supply from freezing. Last year (pre home assistant) I came up with something that worked quite well! I used IFTTT to trigger a Smart Life scene that would allow a small amount of water to trickle down the drain should the temperature go below freezing. (In some situations, that could be considered wasteful, but not so in ours). It kept 150’ of hose just laying on the ground from freezing all winter long! I’ve refined the idea significantly since then and am all set for it to run, but can’t seem to get the trigger to work! Any help would be greatly appreciated as the temperature has just begun its frosty descent!
I made it with the frontend scene and automation functions, but because the switch only registers as an entity and not a device, I made a scene using some tp-link switches, changed the entities in the .yaml then had the automation activate the scene… It works when I hit “execute” but the temp trigger doesn’t work. Any insight on how to register an entity as a device would be amazing! Also, how important is the id#? I’m only a few weeks into this and have loads of basics to learn.
Thanks for reading! Sorry for the longwinded explanation!
The timing fully depends of the refresh timing of the Weather Entity you use. If that is hourly, then the state of the temperature value will only change once an hour.
In my view this automation depends on very local temperature data, and as you only need the temperature value, I would recommend you acquire a device that can measure Temperature, and that is suited for outdoor use. Then take the temperature value from this device, instead of the weather entity.
There are many device types out there that can do this, but what you should buy depends on your setup (Zigbee, Zwave, WiFi etc).
You’re totally right. I just set up a trigger, using what you showed me, with one of my indoor Wireless Sensor Tags and the trigger is instant.
(I also really like that it’s continuous; in that, if while the trigger is within the set threshold, even if I manually deactivate it, it automagically pops right back on.)
Thank you guys! Feeling confident to face the winter!
Okey doke! So I ordered a Sonoff TH10 (which arrived very quickly) and have it all set up. It seems to be reporting in celsius so I changed the values to account for it. Other than that, I really just linked it to HA and swapped the entity_id. It’s currently about 14 degrees celsius here, so I ran a test with the trigger set to below: ‘15’; even after waiting ten minutes and restarting HA multiple times, it still isn’t triggering. Any thoughts? Again, very grateful for your time! (If this is getting annoying, would it be better for me to start a new topic on the boards? I’m really not sure what the etiquette is! haha)
Current automations:
- id: '1605217304373'
alias: Trickle Off (auto)
description: ''
trigger:
- platform: numeric_state
entity_id: switch.sonoff_outsideprob
attribute: temperature
above: '0'
action:
- scene: scene.trickle_off
mode: single
- id: '1605217449763'
alias: Trickle On (auto)
description: ''
trigger:
- platform: numeric_state
entity_id: switch.sonoff_outsideprob
attribute: temperature
below: '0'
action:
- scene: scene.trickle_on
mode: single
Hi Joey,
When you have a trigger that says above or below the trigger will ONLY fire when the entity state changes to a value lower or higher than that. So in your case, the value was 14 and you want it to do something if it goes below 15, that will never fire, as you are already there. Try experimenting with other values, and see if it does not do what you want.
What do you think of this?
The temperature is certainly below 60 (48 in fact), yet the Night Light remains off!
I’ve restarted HA. I’ve also verified that the action works by clicking ‘EXECUTE’ on the frontend. It appears to be something with the trigger.
It might still be the issue I described before: This automation will ONLY trigger, when the state goes from something higher than 60 to below 60. So if you restart HA, and the temperature is 48, it will not trigger, but it will trigger if the temperature goes to 61 and then back to 59.
So basically things should work when the temperature goes up and down and passing the thresholds
You could add an automation that ensures this is run when you restart HA:
OR you could play with the new Choose template in Automations. The below example will trigger on any change of the temperature sensor, and then either turn off or turn on. You will get some Turn On and Turn Off’s even if the entity is already On or Off, but that does not really matter, I guess. If you create a new Automation, and click the three dots in the upper right corner, you can switch to yaml mode and copy the below directly.
Any thoughts? Again, very grateful for your time! (If this is getting annoying, would it be better for me to start a new topic on the boards? I’m really not sure what the etiquette is! haha)