Try it without "template:" like
binary_sensor:
Thanks for the suggestion, @NeoNachtwaechter.
But doing that makes configuration.yaml invalid:
Give us the plain English of what you think this is supposed to do first ๐
Your error suggests a yaml formatting issue.
If any of these 4 things happen, set the sensor to "Detected", otherwise set it to "Not Detected":
As I said, this is working correctly in the template editor. The problem is that I can't make a sensor out of it.
Okay, but the post being responded to threw an error that certainly seems like a yaml formatting error.
If you simply deleted the "template" portion, and then changed the "binary_sensor" line without correcting the spacing in the lines after that, you'd get this error. Yaml is strict about leading spaces.
What I did was de-indent the binary_sensor section so it was at the same heirarchy as the template section, like this:
But I realize now that I have to remove the hypen before "binary_sensor". When I do, I Studio Code Server still shows a couple errors:
It says I'm missing the "entities" and "platform" properties, and that "state" is not an allowed property.
Move everything back two spaces. You may need a yaml linter. Your problem is just the format from what I'm seeing.
I think Studio Code Server is a linter. It's telling me what the syntax problems are - I just don't know how to fix them. Now that I removed the hypehn, it's not telling me there are any spacing/formatting issues. But it currently says I'm missing the "entities" and "platform" properties, but I don't know what the values should be. And It also says "state" is not an allowed property, but that's the property that holds all the important stuff about this sensor - so how can I remove it?
I think you can make a template from the helpers page, see if that works
Thanks for the suggsetion @Matt The Horwood.
It looks like a "Combine the state of several sensors" or a "Group" helper only allow you to combine sensors of the same type.
I created a binary sensor from a template using the helper, but it also returns "'binary_sensor' is undefined" when I try to access its value in the template editor with {{ states(binary_sensor.lounge_presence) }}
I found the solution. configuration.yaml needed to have the following syntax, with the defined values being true or false (instead of "Detected" or "Not Detected"):
template:
- binary_sensor:
- name: "Lounge Presence"
state: >-
{% if states('sensor.apollo_mtr_1_cca750_presence_target_count') | int > 0 %}
true
{% elif is_state('binary_sensor.apollo_msr_2_c7bfe8_radar_zone_1_occupancy', 'on') %}
true
{% elif is_state('binary_sensor.apollo_msr_2_c7bfe8_radar_zone_2_occupancy', 'on') %}
true
{% elif is_state('binary_sensor.apollo_msr_2_c7bfe8_radar_zone_3_occupancy', 'on') %}
true
{% else %}
false
{% endif %}
device_class: presence
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io