-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Low performance due to high cpu usage of deconz add-on #2649
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
After a while the system was restarted the cpu load is increasing in causing slow performance on reacting on events like motion events or switch pressed events. This began with the first 2022.8-Version. All 2022.7.x Versions no problems.
Dont know if this can be caused by new Conbee II Firmware or so.
But all is working correctly, only after 5-7 days its too slow, average of 2-5 seconds for responding on events. Thats very unpleasant.
This is my first problem with deconz integration. No problems until then.
Running latest versions:
Home Assistant 2022.8.7
Supervisor 2022.08.5
Operating System 8.5
Frontend 20220802.0 - latest
Running on Synology virtual maschine manager with usb cabel 2 meters and conbee II.
Any hints very welcome.
A restart of the deconz integration is sufficient to regenerate normal operation as you see on screen shot above.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
deCONZ
What is the version of the add-on?
6.15.0
Steps to reproduce the issue
...
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
config_entry-deconz-a198b989cee311b87b9589379e8b448b.json.txt
The text was updated successfully, but these errors were encountered: