develo Home Network - fails setup, keeps initializing

[JeroenTuinstra]

The problem

I have a set of Magic 2 Wifi Powerlines from Develo Home Network. They are no longer loading in but keep initializing with the error: "Failed setup, will retry".
This started with the latest version of Home Assistant: 2023.9.2. Nothing is mentioned in the log files of Home Assistant. So there is no clue as to why the initializing is failing.
Have already deleted all devices and rebooted them.

What version of Home Assistant Core has the issue?

core-2023.9.2

What was the last working version of Home Assistant Core?

core-2023.9.1

What type of installation are you running?

Home Assistant Container

Integration causing the issue

devolo Home Network

Link to integration documentation on our website

https://www.home-assistant.io/integrations/devolo_home_network

Diagnostics information

home-assistant_devolo_home_network_2023-09-13T15-54-48.084Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing is mentioned in the log files! It just keeps saying "Failed Setup, will retry."

Additional information

No response

[home-assistant]

Hey there @2Fake, @Shutgun, mind taking a look at this issue as it has been labeled with an integration (devolo_home_network) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of devolo_home_network can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign devolo_home_network Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

devolo_home_network documentation
devolo_home_network source
_{^{(message by IssueLinks)}}

[Shutgun]

Hi @JeroenTuinstra ,

I'm experiencing the same thing, but up to know I suspected the firmware I'm running because devolo provides Alpha firmware to me for testing purposes. However, I see that you are running the GA firmware, so that can't be the reason. Interestingly, nothing changed in my scope on HA's side from 2023.9.1 to 2023.9.2, so I assume that the issue exists since 2023.9.0. In that version, new entities were added.

So I plan to do the following:

1. I will ask my friends at devolo, if there is a rate limit that we might hit since I added new entities.
2. To verify, if it is a matter of calls the device has to take, I will deactivate some rarely used entities in my setup. Maybe you can do the same.

btw: rebooting the devolo device always helped me, I never had to delete the integration from HA. Maybe reloading the integration after rebooting is also enough.

[JeroenTuinstra]

@Shutgun Thank you very much for looking into this. It indeed started around 2023.9.0. I noticed the continual disconnection when it was 2023.9.1, and when it updated to 2023.9.2 (I have automatic updates ... I know), devolo was the one integration that refused to come back online. In the meantime they are back online, but response seems to be very slow and the it gives the same errors as in #100310

Unfortunately it seems to all come as a perfect storm. Fritz!Box's new OS no longer shows roaming devices as online when they connect through the devolo Home Network. So bascially I can no longer have 1 source for device tracking but have to add the device trackers of the Powerlines. When they also stop working, Home Assistant basically thinks nobody is at home, unless you are connected straight to the Fritz!Box.

I'll disable some not used entities and see whether it is working better. Thanks again for looking into this and for the speedy answer.

[bosco688]

Same here, first seen with HA 2023.9.1 after a reboot
My Magic 2 are on firmware 7.12.9.142 (2023-05-02)

[Shutgun]

I identified the root cause. If I put HA aside and query the device directly with a bigger timeout, the UpdateFirmwareCheck endpoint answers with UNKNOWN_ERROR. But as the normal timeout isn't that big I raise assuming the device is offline. This leads to a three steps solution:

1. Everybody having this issue can temporarily disable the update entity. This will make the device usable in HA again.
2. I will update the library to handle this case gracefully and submit a PR as soon as possible.
3. I will ask my friends at devolo why this UNKNOWN_ERROR occurs in a first place.

[Shutgun]

Hi @JeroenTuinstra and @bosco688 , with 2023.9.3 the issue seems to be much better, but not completely gone. Since I cannot tell for sure, that I'm not seeing a different issue: could you check your setups?

[JeroenTuinstra]

I've enabled on one powerline all the entities again and I will monitor it. So far it seems it remains online. Is it enough to enable all entities on one of them or should it be done on all of them.

[Shutgun]

A single device should be enough. If the device tends to go offline again, could you tell me, which entities you enabled?