Currently, there are 29 different classes of binary sensors. These classes range form "running" to "safety" to "cold" and everything in between. All of these classes are aimed at providing additional behaviors by default based on the device class so that the icon/color/state may be more intuitive when viewed in the front end UI. Proposal device map (Optional) Information about the device this binary sensor is a part of to tie it into the device registry. Only works through MQTT discovery and when unique_id is set. At least one of identifiers or connections must be present to identify The above is in a file named blogger.com and I've got binary_sensor:!include blogger.com in my blogger.com The four binary sensors all show up on my overview page. However when I trigger one of the door sensors, its binary sensor will not change, even though the access_control entity does
Add binary sensor home assistant
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Currently, there are 29 different classes of binary sensors.
These classes range form "running" to "safety" to "cold" and everything in between. I would like to propose the addition of a "custom" class that would enable the user to specify what icon, color, state text, etc.
The IOT world is exploding and if people find that HA can't easily represent their needs and a spouse keeps wondering what it means when it says "cold" is "on" they are less likely to stick with HA which would ultimately result in less support. A custom device class for binary sensors would open up a WORLD of possibilities that are currently not possible with the existing list. To illustrate this point, consider which binary sensor you would use for the following scenarios:.
The purpose of the additional classes is to provide added customization for scenarios that don't quite make sense with just an "on" or "off" label.
Thus, instead of having to manually go through each users request to add an additional class, I would like to propose the addition of a custom class to take care of this issue once and for all.
From a development perspective, it does not make sense to continue adding device classes when someone comes up with another class that they need. It would be far easier to just have a handful of default ones perhaps the existing 29 and then a custom option so that users can fiddle with it binary sensor device class their hearts content. The text was updated successfully, but these errors were encountered:.
The purpose of device classes are not to have binary sensor device class better translation in the UI, it's to standardize the device type in the binary sensor device class. Which has as side effect better UI, binary sensor device class.
Making up your own device classes won't do this. Sorry, something went wrong. balloob can different icons be used this way for both states? Binary sensor device class All entities have an icon property that can be implemented. frenck a single icon per entity, yes. But an icon for each state? When implementing an entity you can return a different icon for each state taking in mind that architectural discussions are for someone who wants to implement something in core.
A user can use template you can have a different icon for each state. Anyhow it makes more sense to add support for easy customization of binary sensors icons rather than a custom device class.
Skip to content. Star Code Issues Pull requests Discussions Actions Security Insights. New issue. Jump to bottom. okridgway opened this issue Mar 3, · 5 comments. Custom Device Class for Binary Sensors okridgway opened this issue Mar 3, · 5 comments. Copy link. Context Currently, there are 29 different classes of binary sensors. Proposal I would like to propose the addition of a "custom" class that would enable the user binary sensor device class specify what icon, binary sensor device class, color, state text, etc.
Consequences The IOT world is exploding and if people find that HA can't easily represent their needs and a binary sensor device class keeps wondering what it means when it says "cold" is "on" they are less likely to stick with HA which would ultimately result in less support.
okridgway mentioned this issue Mar 3, Adding an Alarm Device Class for Binary Sensors All reactions. frenck closed this as completed Mar 4, frenck reopened this Mar 4, Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment.
You signed in with another tab or window, binary sensor device class. Reload to refresh your session. You signed out in another tab or window.
Home Assistant Templating Masterclass (Full Course)
, time: 46:18configure binary sensor from mqtt - Stack Overflow
Configuration variables:¶ pin (Required, Pin Schema): The pin to periodically check.. name (Required, string): The name of the binary sensor.. id (Optional, ID): Manually specify the ID used for code generation.. All other options from Binary Sensor.. Activating internal pullups¶. If you’re hooking up a button without an external pullup or see lots of ON/OFF events in the log 30/06/ · binary_sensor: platform: gpio pin: 13 name: "PIR Sensor" device_class: motion. These instructions are coming from the official ESPhome webpage and the only thing that you have to modify here is the pin section where you should type This is because we connect the PIR Sensor to GPIO13 (D7) on the D1 Mini Binary Sensor Device Classes. Is there a simple way to represent (remap) binary sensors as true/false or yes/no? My understanding is that to customize, we need to assign it to a device classes. There doesn’t seem to be any class that matches what I’m looking for. Is there another way to customize a binary sensor? 0 comments. share
No comments:
Post a Comment