Switching the default target domain for doors and windows from cover to binary_sensor

[tetele]

At the moment, only a single domain can be used for querying entities. Unfortunately, doors and windows are represented either as entities with {domain: 'cover', device_class: 'door'} or {domain: 'binary_sensor', device_class: 'door'} (and their window equivalents).

At some point, we decided that the cover domain should trump the binary_sensor domain in sentences such as How many doors are open? and, as such, people who have binary_sensor doors get a false response. That's not a problem, it's a design decision that was made.

However, judging by my own experience, support questions and available devices, I feel as though cover doors and windows are FAR less prevalent than door/window sensors. I was wondering if it would not be a good idea to change the sentences to point to the binary_sensor domain by default.

[davefx]

I honestly think that the problem is that we have binary_sensors vs covers. A door or window is a cover, no matter if it's actionable or not. IMHO, Home Assistant should allow the easy creation of non-actionable covers from binary_sensors.

…

-- David Marín Carreño ***@***.***> El lun, 13 may 2024 a las 10:00, Tudor Sandu ***@***.***>) escribió:

At the moment, only a single domain can be used for querying entities. Unfortunately, doors and windows are represented either as entities with {domain: 'cover', device_class: 'door'} or {domain: 'binary_sensor', device_class: 'door'} (and their window equivalents). At some point, we decided that the cover domain should trump the binary_sensor domain in sentences such as How many doors are open? and, as such, people who have binary_sensor doors get a false response. That's not a problem, it's a design decision that was made. However, judging by my own experience, support questions and available devices, I feel as though cover doors and windows are *FAR* less prevalent than door/window sensors. I was wondering if it would not be a good idea to change the sentences to point to the binary_sensor domain by default. — Reply to this email directly, view it on GitHub <#2168>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACHLVIZLRKM25NMKTYZGO3ZCBXKXAVCNFSM6AAAAABHTV3CQSVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGY2TSNBZHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[tetele]

Good idea! I've made an architectural proposal for this.

[tetele]

Alternative solution proposed here home-assistant/architecture#1084