jocnnor
February 8, 2020, 1:31am
2
mmiller7:
if this was normal code instead of YAML I’d make function calls to “OR” together, or a global integer counting how many things want a device to be on which can increment +1 when another thing wants it on, or decrement -1 when it wants to go off) and then compare if >0 conditions want it on. But I don’t see a way to do that here.
You can do that if you want. Look at the ‘input_*’ integrations.
input_number, input_text, input_datetime, input_select, input_boolean
These are all input devices that you can easily set from any automation to keep track of global state things.
I don’t personally use it, but this is a perfect example of why Node Red is so powerful…and popular.
[hassio-addons] This add-on is provided by the Home Assistant Community Add-ons project.
[GitHub Release] [GitLab CI] [Project Stage] [Project Maintenance]
[Supports armhf Architecture] [Supports armv7 Architecture] [Supports aarch64 Architecture] [Supports amd64 Architecture] [Supports i386 Architecture]
[screenshot]
About
Flow-based programming for the Internet of Things.
Node-RED is a programming tool for wiring together hardware devices, APIs and online services in new and interestin…
Take a look at some of the flow diagrams:
You can define all of your flows and group them together into a single thing. And if you suddenly want to tie other info other places, you can do that.
If you don’t like the gui approach of Node Red, why not look at AppDaemon. You simply write everything you want in python!
