Broken integration on HA 2024.5.0

[formatBCE]

Describe the bug
After update to Home Assistant 2024.5.0, i got into boot loop. When i disabled Dreame integration during startup, HA started successfully, but then rebooted again as soon as i turned Dreame entry on again.
Then i tried to delete entry, and re-add vacuum after HA is started. Configuration succeeded, but entry failed to initialize (logs reported connection time out).
I rolled back to 2024.4.4, it works as expected so far.

To Reproduce
Update to Home Assistant 2024.5.0.

Expected behavior
Integration works.

Additional Information (please complete the following information)

• Model Name [e.g. dreame.vacuum.p2028]: dreame.vacuum.r2228o
• Firmware Version [e.g. 1156]: 4.3.9_3204
• Home Assistant Version: 2024.5.0
• Configuration Type [With or without map support]: With map support
• Errors or warnings shown in the HA logs (if applicable): connection time out

[Tasshack]

#479

[formatBCE]

#479

Not applicable @Tasshack - mentioned fix is for 2024.4, but current problem is on 2024.5.0.

[Tasshack]

@formatBCE information that you have provided is not enough for me to confirm, understand and solve the issue.

[formatBCE]

@formatBCE information that you have provided is not enough for me to confirm, understand and solve the issue.

What exactly is unclear?
Integration gives boot loop on 2024.5.
If you update to 2024.5.0, which released today, you will get the same.
Instead you're giving solution to previous HA version...

[Tasshack]

Yeah that is the problem. I won't see any issue on my both development and running HA setups same as with the #479. I have only been able the fix that issue with the help of an actual HA developer. Also disabling the integration and seeing that HA runs correctly does not mean that the problem is not related to your setup and something I can fix.
If the problem actually caused by the integration how do you expect me to solve it by just saying "it does not work"?

[formatBCE]

Yeah that is the problem. I won't see any issue on my both development and running HA setups same as with the #479. I have only been able the fix that issue with the help of an actual HA developer. Also disabling the integration and seeing that HA runs correctly does not mean that the problem is not related to your setup and something I can fix.
If the problem actually caused by the integration how do you expect me to solve it by just saying "it does not work"?

Well, when I re-enabled integration after successful HA booting, it immediately led to HA reboot again, while trying to initialize it. I have no clue how to provide logs of this, since it's rebooting before I can get into logs.

So to be clear: you claim that your HA setup now is on 2024.5, today's release, and integration works?

[Tasshack]

So to be clear: you claim that your HA setup now is on 2024.5, today's release, and integration works?

Yes.

[rmxs]

Got the same issue, the latest HA version rollback when integration is active

[brandgul01]

Same issue here as well. Managed to reboot and disable dreame before it started and system works. Glad to help if I know how to provide logs.

[formatBCE]

@Tasshack so I'm not the only one with this issue.
Maybe, instead of closing it right away, we will think how to debug it? I'm ready to help with providing any info required. Bummer is, that HA is dying before something gets visible in log.

[adizanni]

Between github and community I've counted at least 15 people with the exact same problem. Disabling dreame allowed to run 2024.5.0 smoothly

[formatBCE]

Yes

Given that you had to release 1.0.4 to fix this, i can't imagine how it could work before. I can assume only different setup (no map probably).