Alarmo fails on HA startup. about alarmo

[nielsfaber]

Could it be that you did not make any change to the alarmo settings in over 3 years?
The error suggest that your settings file is missing a property that was added a long, long time ago.

[ZinTheDog]

I've been running into the same problem the last few days. I just updated to 2024.1.6 and the issue persists.

[nielsfaber]

@ZinTheDog
Can you look up the alarmo.storage file in subfolder .storage (might be a hidden folder) in the HA configuration directory?
I would to see the version that is listed here, and if any section sensor_groups is present here. Could you share this information?

[ZinTheDog]

Version 6, Minor Version 2. "sensor_groups": [] is present at the end of the file.

[nielsfaber]

@ZinTheDog
I'm surprised you are running into this error since it suggest that the sensor_groups is missing from that file. An ampty list should not give such error. If I update my local file to match yours, the issue does not show up.

Do you mind sharing your complete storage file?
Any information that you consider as private can be replaced by "x" or similar (its just about the file structure).

[ZinTheDog]

@nielsfaber
My apologies, I think I may have jumped to conclusions based on timing of my issue and OP's and should probably take a step back. The Alarmo integration is starting in my system, but the alarm_control_panel.alarmo entity is showing as unavailable and won't allow me to enable it. Debug logging is turned on, but it's not reporting any errors that I have been able to find.

[nielsfaber]

@ZinTheDog
This indeed seems unrelated to the bug reported here.
You might want to check the developer tools > states page and look for the alarm entity.
There is another unresolved issue causing HA to create a new entity (under a different name) for alarmo.

[ZinTheDog]

@nielsfaber, My sincere apologies again for the wild goose hunt. There were no additional entities, just the original that was perpetually stuck in disabled/unavailable. I ultimately ended up deleting the device & entity and recreating my Alamo configuration. Still not sure what caused it, but it was easy enough to recreate new. Thank you for your quick action!

[flubba]

Alarmo failed to start up with the same error message for me as well. The issue was that "sensor_groups" was missing in the configuration. I reverted back to version 1.9.13, made changes to the configuration, and then switched back to the main branch. That fixed the problem.

[bcutter]

Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: homeassistant.config_entries
Source: custom_components/alarmo/panel.py:33
Integration: Alarmo (documentation, issues)
First occurred: 23:44:23 (1 occurrences)
Last logged: 23:44:23

Error setting up entry Alarmanlage for alarmo
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 383, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/alarmo/__init__.py", line 84, in async_setup_entry
    await async_register_panel(hass)
  File "/config/custom_components/alarmo/panel.py", line 33, in async_register_panel
    await panel_custom.async_register_panel(
TypeError: async_register_panel() got an unexpected keyword argument 'config_panel_domain'

Interestingly the control panel entity is created just fine:

It's "just" the Alarmo integration itself being not operational...

---

Happened after restarting HA after roughly a month, likely Alarmo integration has been updated meanwhile from HACS (to v1.9.14). How to fix this?

• For now I reverted back to v1.9.13 which "solved" the issue (Alarmo integration loaded and operational) - at least it buys some time for some expert here to figure out what causes this and how to fix it...
• What changed in 1.9.14 that breaks this?

---

Content of homeassistant / .storage / alarmo.storage:

{
  "version": 6,
  "minor_version": 3,
  "key": "alarmo.storage",
  "data": {
    "config": {
...
`

[nielsfaber]

@bcutter your issue is not related to the topic discussed here. I think your issue is caused by an incompatible HA version. The error is related to a property that was added to HA about half a year ago.

[bcutter]

@bcutter your issue is not related to the topic discussed here. I think your issue is caused by an incompatible HA version. The error is related to a property that was added to HA about half a year ago.

I created a seperate issue, sorry for mixing things here.

[robwiklu]

I renamed alarmo.storage and reverted to Alarmo verson 1.9.13. Now Alarmo works for me again. I haven't tested upgraded to .14 again after that - I just need it to work at the moment.

[MihaiP17]

For me it was sufficient to add in alarmo.storage (file is found in \config.storage) a new entry for sensor groups. The json file should look similar to this.

After a restart, everything started to work again as normal. This on last version (1.9.14) of alarmo.

[robwiklu]

For me it was sufficient to add in alarmo.storage (file is found in \config.storage) a new entry for sensor groups. The json file should look similar to this.
After a restart, everything started to work again as normal. This on last version (1.9.14) of alarmo.

Thank you, MihaiP17, for a helpful answer in this thread. I will test this.

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days