Nuki 4th Gen Pro MQTT Entity does not get recognized as a valid Alarmo sensor

[dejanpan]

Checklist

• I am using the latest version of Alarmo (latest version can be found here)
• I checked for similar existing requests (both open and closed) before posting.

Alarmo Version

v1.10.7

HA Version

2024.12

Bug description

Hi and big thanks for this really awesome project!!!

According to the docs, the entities of type Lock should be supported as a sensor: https://github.com/nielsfaber/alarmo?tab=readme-ov-file#sensor-types.

I have Nuki 4th Gen Pro MQTT Entity does not get recognized as a valid Alarmo sensor:

It seems to me that the sensor entity validation happens here:

alarmo/custom_components/alarmo/frontend/src/views/actions/automation-editor-card.ts

Lines 542 to 545 in 64368ff

	if (services.length == 1 && services[0]?.includes('lock'))
	state = this.hass.localize('component.lock.state._.locked');
	if (services.length == 1 && services[0]?.includes('unlock'))
	state = this.hass.localize('component.lock.state._.unlocked');

but I am not very familiar with this code.

I for now did this workaround but it would be better if Nuki Lock would get recognized directly by alarmo.

Steps to reproduce

See above.

Relevant log output

[nielsfaber]

Alarmo only supports binary_sensor entities as also is clearly mentioned in the documentation.
So creating a template sensor based on the state of your lock entity is an OK solution.
Given that this is not a bug, I’m closing this.

[dejanpan]

Alarmo only supports binary_sensor entities as also is clearly mentioned in the documentation. So creating a template sensor based on the state of your lock entity is an OK solution. Given that this is not a bug, I’m closing this.

Thanks @nielsfaber. I needed to today draw a picture to understand again what Device, Entity, Device Class, Attributes, Domain and States are.

1. Device → Domain: Devices are grouped into domains based on their functionality. (light, sensor, binary_sensor`, ...)
2. Domain → Device Class: Domains are refined by device classes, adding context. (motion, door, battery, temperature, ...)
3. Domain + Device Class → Entity: Entities are created by combining domain and device class. Entity represents an individual control or sensor that Home Assistant can interact with.
4. Entity → Attributes: Entities have additional details (e.g., brightness, battery level). (brightness, color, battery level, ...)
5. Entity → States: Entities also define their current condition or behavior. (on, off, ...)

So Alarmo currently supports binary_sensor type of Domain with the following Device Classes.

What is confusing is that HA uses Lock as a domain https://www.home-assistant.io/integrations/lock and as a device class for e.g. binary sensor: https://www.home-assistant.io/integrations/binary_sensor/#device-class.

Thanks

[nielsfaber]

Device_class should have been called entity_class if you ask me.
This is an attribute for an entity of type binary_sensor.

Devices have not much meaning in HA. It is just a collection of entities that all correspond to a physical object in your house (like your nuki lock will consist of a ‘lock’ entity but maybe also a battery level sensor etc). It is only a means of organising the many entities that a HA setup has.