After upgrade to 2024.5.0, Dreame Vacuum integration is stalling HA startup sequence #523
Comments
adizanni
added
bug
|
I retrieved a picture from another thread, even if it is not coming from my installation it is exactly the error that I saw in the console: |
|
Same issue here |
|
|
|
Same issue here, anyone found a workaround? I can't access the HA UI but unpluggind and plugging in the Raspberry worked for a short period. Anyone have an idea how we can disable the Dreamee integration via HA CLI? |
|
Same issue here. |
I managed to disable the Integration before HA loaded it.. |
|
Same behavier here. But it is a very nice add on and I hope you can fix it |
|
Same here. I connected trough SSH, forced a reboot, went into HA GUI web panel and disabled Dreame integration. This stops HA from crashing. It's either disable or rollback to 24.4 for now. Hopefully developers can push Dreame update. |
|
The same thing. Here are excerpts and logan on integration. Freezes when parsing the map. Строка 18772: 2024-05-02 18:36:53.466 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.dreame_robot_vacuum_mop_f9_map (<class 'custom_components.dreame_vacuum_.camera.DreameVacuumCameraEntity'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/Tasshack/dreame-vacuum/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation |
I did not find the same log entries, but happy that you add some clue on the root cause. Everybody is saying in the various forum that HA 2024.5.0 is forcing thread safety and the custom integration that are not following the guidelines may have some memory issues |
|
Just got my HA instance back up and running. Dreame integration was the culprit as others suspected. I could not get into web ui at all. But found this post that explained how to remove integration via cli. https://community.home-assistant.io/t/disable-integration-from-cli/405778 Remove Dreame entry from config and reboot. You will be back up and running. |
|
Same issue with 2024.5.0 here. I was able to downgrade to 2024.4.4 through the terminal and will now stay on that version until the issue is resolved. |
|
Yeah i filed #522 before, but it was closed... |
|
I managed to disable config entry, boot, remove integration and re-add it.
|
|
Same problem here. Disabling it allowed me to upgrade, but when I re-enabled it under 2024.5 Home Assistant crashed instantly. Here is everything in the log from when I re-enabled it...note that the last line was the last line in the log before everything crashed. 2024-05-02 16:27:58.049 INFO (MainThread) [homeassistant.setup] Setting up dreame_vacuum |
|
For now it all looks like it has some loop on map camera feed generation, which leads to OutOfMemory crash... |
|
Saying that HA is not working with the integration is not enough for me understanding and fixing the underlying issue because I cannot reproduce it on my setup and seems like it only affects HA OS installation.
@adizanni can you create an issue to the HA Core to get more information from a HA Core developer about the changes on 2024.5.0 that causes this and also what needs to changed from the integration to fix it. |
|
@g470258 says Beta version of the integration works without a problem on 2024.5.0, can anyone alse confirm this? |
|
Beware trying to install it on 2024.5 - I re-enabled the integration and it crashed HA instantly and then somehow broke something and I wound up not even being able to roll back to 2024.4.4, but actually had to do a complete restore of a backup... |
I will try it, notwithstanding my previous comment... (tomorrow...if I kill my HA the TV doesn't work properly and I'll get in trouble) |
There isn't a lot in the logs to work with, other than the soon to be deprecated stuff (which you would hope wouldn't cause critical errors prior to the date). |
Just installed beta 2.0.0b14 on HA 2024.5.0. Confirming, it works for me. |
|
Command for upgrading to the Beta from cli.
This will confuse the HACS so you may need to reinstall the integration over HACS after your HA is up and running again. |
Why doing it, if you can go to HACS, hit 3 dots -> "Reinstall", and tick "show beta versions" there? I did it like this, and installed beta successfully. |
For the people cannot get up and running their HA because integration prevents from it. |
Oh. Well, I deleted my vacuum, upgraded and added it back - it even put same entity IDs, no hassle. :) |
|
New version released https://github.com/Tasshack/dreame-vacuum/releases/tag/v1.0.4 Installation without HACS |
I can confirm it works fine now (supervised installation on Debian 12), thanks! |
Works for me. Thanks a lot |
I will test this afternoon and close the ticket if the 1.0.4 fixes the stalling (and based on the feedbacks above) |
I don't need information from Core developers anymore because I have been able to reproduce the issue myself and found out that new HA blocks async calls from threads that will lead on an infinite loop in the camera entity render function resulting memory leak until no memory has been left on the device. I think there are still some async calls from threads in the integration that i need to address so I may need to release a new version later this day. |
|
Nice work team ! Great reactivity ! Thanks a lot. |
|
As far as I'm concerned, after upgrading to v1.0.4 the stalling issue is resolved. |
Thank you very much for jumping on this - I appreciate it!! |
|
Thanks a lot! |
|
Hi great job, but i'm on 2.0 betas version for the dreame app compatiblity, can you update the beta version too? |
Beta version does not have this issue, you can safetly upgrade your HA. |
|
You're right, I was on an older beta, the latest works like a charm! Thanks again! |
|
Hi, I have a problem with both the latest beta and version 1.0.4. The beta crashes my server. As it is described above. If I install version 1.0.4 I get to the dialog where I can submit. The button turns into a circle that rotates endlessly. |
Your system may not have enough memory to run the integration. You can select |
Thanks for the quick reply. Of course that could be the case. I was hoping it wouldn't be that when I read #556. I chose the beta with Do you have a recommendation? |
|
Buy a new mini pc. |
Describe the bug
After upgrade to 2024.5.0, Dreame Vacuum integration is stalling HA startup sequence.
I have no additional info to share because as HA was restarting in a loop it was difficult to retrieve any evidence.
Only evidence I can share is that, during the 30 seconds window in which the UI was available, in the startup norification message at the bottom left of the browser, Dreame Vaccum was the last custom integration to be loaded before the system crashed.
I managed to disable the integration during the 30 seconds window and now the system is up and running without problems.
Also in the console of the machine running HA, there was a general error for out of memory prior to the reboot.
To Reproduce
Upgrade HA to 2024.5.0
Expected behavior
I was expecting HA to startup and Dreame caused a reboot loop
The text was updated successfully, but these errors were encountered: