I currently have a lot of my light automations setup by first having an automation that turns the light on at a certain time, then another that turns the light off at another time. This works, and it has for years, but I’m imagining there must be blueprints or other methods to do this on/ off behavior in a single automation rather than having them in pairs (this is not scaling very well).

Anyone have suggestions? The image is a blueprint I have for turning lights on/ off based on a time window which is very handy, and I’m hoping there’s something similar out there for my needs.

  • Zwuzelmaus@feddit.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 days ago

    Just to provide a different point of view:

    My general strategy is to decentralize these simple condition-action things.

    Where only one sensor controls only one action/state, the function should run on the device itself, not on HA. Either the sensor or the switch or both is “smart”, and it is good that HA knows and shows the state, and you can switch it on/off there in the HA app, but it should not depend on HA. It should still work when HA is down.

    In my case, Tasmota runs on all the light switches and a rule in Tasmota does the job.