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

Alarmo on HA Core 2025.1.1 causing processor spike /inaccessibility during ARM process. #1091

Open
2 tasks done
GeoffreyMcGuire opened this issue Jan 9, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@GeoffreyMcGuire
Copy link

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

2025.1.1

Bug description

When ALARMO is armed I have noticed a processor spike (Pi 4 4GB) that renders the web interface unreachable, the spike lasts for approximately 10 minutes, at which point it is possible to access the HA web interface again.
ProcessorUtilitsation

Steps to reproduce

When Arming, either by using occupancy (all users leaving the house, or manually using the alarm card/keypad) the HA instance becomes unreachable and processor spikes to 15% to 30% for approximately 10 minutes (this seems enough prevent access to the web interface).

Relevant log output

No response

@GeoffreyMcGuire GeoffreyMcGuire added the bug Something isn't working label Jan 9, 2025
@nielsfaber
Copy link
Owner

Unfortunately I cannot help you with this.
I suppose this behaviour is related to your own usage, as I (and 1000+ users) don’t experience such issue.
The code is written to the best of my abilities, but I cannot say whether there is a memory leak or similar somewhere.
As I cannot reproduce your problem and I have nowhere to look in the code, there is no way to address this problem.

@GeoffreyMcGuire
Copy link
Author

Thanks, it would seem that this must have been some other interaction, is it was definitely repeatable, however, since going to 2025.1.2 this seems to have stopped now. It's a great add in BTW.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants