![]() ![]() It might be better to change the conditions to check for an integer > 1 instead of a string equal to “1”.Īnd one other question - what is the purpose of the dummy sensor? In that case none of your condition tests will be satisfied and since you didn’t give a default action I’m not sure how the system handles that. If I change the template in the history stats to multiply by 5 instead of 7 the sensor works as expected.Īnother thing I just thought of is that you could get into a situation that the history_stats sensor may return a value > 1 if the light was switched off & on more than once in those 30 seconds that the history stats is looking at. My recorder is set to purge data every 5 days so if I set the history stats sensor as you have it configured (7 days) then the state is always “unknown”. You should probably note that you need to make sure that for this to work either the recorder integration needs to be set to keep data longer than 7 days or the history stats sensors need to be set to pull data for no longer ago than the recorder is keeping data. # Use this sensor as a dummy placeholder in the blueprint automationįriendly_name: 'Do Nothing - Dummy Sensor' This sensor will do absolutely nothing other than act as a selectable placeholder that lets you save the blueprint as an automation
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |