#New automation target
1 messages · Page 1 of 1 (latest)
Do you have a binary sensor that has this tag? Ajd is the binary sensor meaningful? Keep in mind that more use cases will be added. For now you can find “when motion sensor is detected”” where binary sensor has to be of a certain device class
Developers said they found more than 200 use cases that will be gradually added over time.
I try input_number, knx switch, input_boolean, input text, group of light, and only some (not all) input_text are visible
What class is your binary sensor?
to come back to this, so HA developers were very clear about at least these 2 points:
- they need to find many use cases
- so far they identified more than 200 use cases of these target proposals.
Today, AFAIK, the use cases are around light, climate and occupancy sensors only. maybe some more. Other use cases will follow in the future releases. That means, at least in the case of binary_sensor, the new target picker will look at the sensor class field.
If you have a binary_sensor entity, and if you set the class (for test only) as Occupancy, it will show it as a target picker.
Let me give you an example. I have a place in living room called TV area, that contains no sensors which could be picked by targets selector:
if I create a custom template binary sensor under helpers, like below:
It will be always on, but it is not an occupancy sensor, since I didn't select any class. I also can't see it under the targets picker
When I select the area as TV area, it shows in the picker as an entity, but no triggers available:
When I add the correct class, which is today known to target picker, then the target picker proposes the action.
and I can see it in selector:
Bottom line is, the HA developers are yet to build more use cases to show as a picker choice, depending on the sensor class (in case of binary sensor type).
The target picker is today in beta stage, I cna assume there will be many more releases before it becomes priority choice for new users
Indeed changing from Motion to Occupancy works. As I am pretty new to hass and know the beta stage of that feature, I prefer to discuss it here. May be my usecase is more "target any device with that label" than what the one we are talking now.
I want to react to any binary that change and send a generic notification. It can be a wind alert, a door opening alert, a plug that turn off, a boolean template that change its state,....
I have some error for that reason, I "simulate" a knx input number by sending data to that adress. That adress is not linked to a device (like the speed of my VMC that is handle by a mqtt topic). It is just working because the "client" (loxone, hass, openhab) stores the data somewhere. However hass send read request to that input. Does sync_state: false will solve that issue?
If you want to target any device with that label, then maybe we will need to wait a bit until more use cases come ready for you? I am not sure if current release supports that.
You have the following options:
- Create a template sensor and include all the binary sensors inside that have the label/area and return the number of sensors being
on - Temporary create a group helper and manually put the sensors inside
- Use the template trigger without template sensor
Maybe there are some other possibilities.
not sure it is related to your question in this topic.