Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

removing alarm control panel constants breaks my alarm control pannels, They now show up as "Unknown" #296

Closed
yougotborked opened this issue Nov 16, 2024 · 5 comments

Comments

@yougotborked
Copy link

Describe the bug
I upgraded to 9.37 and all my synced alarm control panels are not able to be controlled anymore in HA. And their status shows up as unknown and an error appears when I try to change their alarm state. I rolled back to 9.34 as a test and it started working again.

I think its because of this change
0d50ea0

To Reproduce

Happens immediately on upgrade.

Screenshots

Environment

  • Home Assistant version: 2024.11.2
  • Integration version: 9.37
@jason0x43
Copy link
Owner

Yikes! If possible, could you update again and post any errors that show up in the logs?

@yougotborked
Copy link
Author

yougotborked commented Nov 16, 2024

I think this was the error before,

2024-11-16 13:32:49.649 WARNING (MainThread) [homeassistant.components.alarm_control_panel] Entity None (<class 'custom_components.hubitat.alarm_control_panel.HubitatSecurityKeypad'>) is setting state directly which will stop working in HA Core 2025.11. Entities should implement the 'alarm_state' property and return its state using the AlarmControlPanelState enum, please report it to the custom integration author.

For some reason now though I've upgraded again and it is not failing.

But this is what the devices looked like last night when I upgraded, "Became unknown" and then downgraded
image

HA also did release 11.2 last night, so mabye they fixed something too?
https://www.home-assistant.io/blog/2024/11/06/release-202411/#2024112---november-15

This? home-assistant/core#130479

@jason0x43
Copy link
Owner

I believe you're right. It looks like AlarmControlPanel is switching to a new enum-based state value, and it temporarily ignored the existing _attr_state value, which is what this integration was using.

If you get a chance, could you try out v0.9.38-pre0 and see if that behaves a bit better? It should support both the existing state attr as well as the new one.

@yougotborked
Copy link
Author

yougotborked commented Nov 27, 2024 via email

@jason0x43
Copy link
Owner

Closing this since the issue is resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants