Use 'occupancy' device_class instead of 'motion' for occupancy sensors #22896
Conversation
'occupancy' matches the zigbee terminology more closely and is more consistent with other Home Assistant entities of this type. https://www.home-assistant.io/integrations/binary_sensor/ In general, it looks like 'motion' is more for alarms, and 'occupancy' for non-alarm situations. Z2M currently makes no distinction between these concepts, but they could be separated (with a fair amount of work).
|
Thanks! |
… sensors (Koenkk#22896) 'occupancy' matches the zigbee terminology more closely and is more consistent with other Home Assistant entities of this type. https://www.home-assistant.io/integrations/binary_sensor/ In general, it looks like 'motion' is more for alarms, and 'occupancy' for non-alarm situations. Z2M currently makes no distinction between these concepts, but they could be separated (with a fair amount of work).
|
put everything back, now the motion sensor shows the "house" icon instead of the "running man"! |
|
Yes, unfortunately there is not currently a separate category for "occupancy" vs "motion" in z2m. It would be more work to add this. You can always override the type in Home Assistant, see https://www.home-assistant.io/docs/configuration/customizing-devices/ |
so this is a temporary solution? Maybe I don’t need to change anything yet? Does this require some work on your part or on the home assistant side? |
'occupancy' matches the zigbee terminology more closely and is more consistent with other Home Assistant entities of this type.
https://www.home-assistant.io/integrations/binary_sensor/
In general, it looks like 'motion' is more for alarms, and 'occupancy' for non-alarm situations. Z2M currently makes no distinction between these concepts, but they could be separated (with a fair amount of work).