search

nielsfaber / alarmo

Easy to use alarm system integration for Home Assistant
1.24k stars 117 forks source link

http 500 error / UI broken #961

Closed mac22321 closed 3 weeks ago

mac22321 commented 3 weeks ago

Alarmo Version

v1.9.10

HA Version

2024.6.0

Bug description

Updated Alarmo from prior version to current and now the UI to enable/disable the alarm is not shown - an error message is displayed instead. Additionaly, when I click the only "Areas" entry for Alarmo, an http 500 error dialog is displayed.

AFAICT, my alarm still functions properly using my physical Ring keypad. Actions fire when the alarm is active and a sensor is opened.

The UI functioned perfectly prior to the update to the most recent version. I'm apprehensive to uninstall and reinstall Alarmo due to the many sensors and actions I have (had) configured.

https://imgur.com/a/28tL3rm

https://youtube.com/shorts/lra4vwOThvc?si=RbhgZqvAZPMp7xKQ

Steps to reproduce

Upgrade from prior version of Alarmo to v1.9.10 and note the UI is missing the functionality to enable/disable Alarmo.

Relevant log output

Logger: homeassistant.components.automation.disarmed
Source: components/automation/__init__.py:744
integration: Automation (documentation, issues)
First occurred: 1:41:06 PM (3 occurrences)
Last logged: 4:44:04 PM

Error while executing automation automation.disarmed: required key not provided @ data['message']

------

Logger: homeassistant.components.automation.arming
Source: components/automation/__init__.py:744
integration: Automation (documentation, issues)
First occurred: 1:41:09 PM (1 occurrences)
Last logged: 1:41:09 PM

Error while executing automation automation.arming: required key not provided @ data['message']

------

Logger: homeassistant.components.automation.arming
Source: helpers/script.py:2005
integration: Automation (documentation, issues)
First occurred: 1:41:09 PM (1 occurrences)
Last logged: 1:41:09 PM

Arming: Error executing script. Invalid data for call_service at pos 1: required key not provided @ data['message']
mac22321 commented 3 weeks ago

Upgrading to the same version that was released an hour after I reported this issue resolved my reported issue. Not sure why the version number wasn't incremented.