AlarmDecoder doesn't work with 2024.6.1 or 2024.6.2 about core HOT 8 OPEN

alarmdecoder documentation
alarmdecoder source

from core.

cc @tichris0

from core.

Hmm. Given that this has happened in the past, I wonder if there isn't something else at play than the AlarmDecoder update in 2024.6

@scottgehman I suspect that all of your elements have simply changed names. Can you confirm that your alarmdecoder device is still recognized and configured in Home Assistant?

Steps:

• Settings
• Devices & Services
• Alarm Decoder

At that point you should see either the port or socket,
1 device and entities

If that all seems fine, follow the following steps:

• Click on "1 device"
• Verify that you can see your control panel as well as all the sensors
• Click on the alarm panel in "Controls"
• Click on the gear
• Note the "Entity ID"

Compare that ID vs the entity ID of the control panel in the dashboard/UI

• Click edit in the dashboard where you have your control panel
• Click on "Edit"
• Compare the "Entity ID" against the one you noted previously

PS: When comparing the entity ID, please note the fully qualified name. aka: Click on the entity field to reveals not just the friendly name of it, but the ID that references it.

from core.

This happened to me as well, looks like all my AD entities got renamed with alarmdecoder_ prefix. For example: binary_sensor.bedroom_window became binary_sensor.alarmdecoder_bedroom_window.

from core.

This happened to me as well, looks like all my AD entities got renamed with alarmdecoder_ prefix. For example: binary_sensor.bedroom_window became binary_sensor.alarmdecoder_bedroom_window.

That's good feedback. I believe I originally marked the change as a breaking change since it did that to me as well when I first ran it and from memory, someone made a comment that it shouldn't be breaking and that the naming should stay the same. I didn't pay too much attention to that since I know a ton of things changed as I was developing the new entity model. I'll look and see if there's perhaps an easy fix we could do to maintain the names. Otherwise it may simply have to be added to the notes that the device name will be appended in front of the entity names.

from core.

If the unique id of an integration stays the same, the entity id should not change

from core.

If the unique id of an integration stays the same, the entity id should not change

Looking at my code change again; I don't see anywhere where the entity_id was touched. new unique_ids were created, but I haven't touched the entity_id.

aka: https://github.com/home-assistant/core/pull/117357/files

from core.

Yes, but a unique_id was added, which isn't considering a breaking change, but yet, entity_ids rename and after this it wont happen anymore (or its a bug)

from core.