#Sensors state automation
33 messages · Page 1 of 1 (latest)
What does "each sensor has 6 different values" mean exactly?
While waiting for your answer.
There is a helper that does the job.
Go to Devices and Services, Helper tab
Create new helper > Group > Sensor Group and select Last as type.
Your new sensor will update every time the child sensor update.
Then automate on it
6 entities
Then what I propose should work....
I am wondering if it's the most elegant solutions 🤔
Actually.... Scratch that.
You can skip the helper altogher.
Just trigger your automation on state change of each of your entities
You can have as many trigger as you wish on a single automation.
Yeah...I'm looking for a shroter way if possible
Define shorter.
platform: state
entity_id:
- sensor.1
- sensor.2
- sensor.3
Is pretty short in my book
Sensor = device with 6 entities
When using helper: ADD Group, I need to select 30 entities of 5 different devices. I thought I can define automation according to device state level and not entities state. ok...I will do it the hard way 🙂 my intention is to send MQTT message to my control4 controller in order to flag if sensors are connected to the network meaning "alive"
Thanks....
There is indeed no way to circumvent triggering on your entities as of today
But you actually do not need the group
Just trigger on your entities
I have a PR in the works that allows templates to trigger automations
that would essentially solve this
Would be cool
What i'd love *We're thinking about it) is label trigger.
Trigger on everything that has this label.
In fact.... target trigger