From 519e123b69542e376f1d777cd0eca07275cb5559 Mon Sep 17 00:00:00 2001 From: Adam Goode Date: Sun, 2 Jun 2024 15:11:00 -0400 Subject: [PATCH] fix: Use `occupancy` `device_class` instead of `motion` for occupancy sensors (#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). --- lib/extension/homeassistant.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/extension/homeassistant.ts b/lib/extension/homeassistant.ts index aab120509..5eb828f35 100644 --- a/lib/extension/homeassistant.ts +++ b/lib/extension/homeassistant.ts @@ -656,7 +656,7 @@ export default class HomeAssistant extends Extension { moving: {device_class: 'moving'}, no_position_support: {entity_category: 'config', icon: 'mdi:minus-circle-outline'}, noise_detected: {device_class: 'sound'}, - occupancy: {device_class: 'motion'}, + occupancy: {device_class: 'occupancy'}, power_outage_memory: {entity_category: 'config', icon: 'mdi:memory'}, presence: {device_class: 'presence'}, setup: {device_class: 'running'},