devolo_home_network - Error fetching... #110555

jusicgn · 2024-02-14T16:34:41Z

The problem

Hi folks,

I've got 4 devolo devices in total and get a lot of errors in the log:

Logger: homeassistant.components.devolo_home_network
Source: helpers/update_coordinator.py:345
Integration: devolo Home Network (documentation, issues)
First occurred: 13. Februar 2024 um 22:46:33 (724 occurrences)
Last logged: 17:11:57

Error fetching connected_plc_devices data: The device is currently not available. Maybe on standby?
Error fetching connected_wifi_clients data: The device is currently not available. Maybe on standby?
Error fetching switch_guest_wifi data: The device is currently not available. Maybe on standby?
Error fetching switch_leds data: The device is currently not available. Maybe on standby?

My devices:

Magic 2 LAN DINrail
Magic 2 WiFi 6
Magic 2 WiFi next
Magic 2 LAN 1-1

As i read in other tickets that it might help to switch off the firmware update entity, I did that just before writing this issue.
Will report if it "fixes" the issue.
But even if it does. Would be nice to have the firmware update information back :)

Best, Julian

What version of Home Assistant Core has the issue?

2024.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

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

config_entry-devolo_home_network-ff0a70262b3e7b097fbace716cdee82f.json
config_entry-devolo_home_network-1968c964fce199541b93cb53879a9ce7.json
config_entry-devolo_home_network-fa7fab6646b974bdf985f740be1cdd04.json
config_entry-devolo_home_network-773d8476514eb8ae134f1976d98d6510.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.devolo_home_network
Source: helpers/update_coordinator.py:345
Integration: devolo Home Network (documentation, issues)
First occurred: 13. Februar 2024 um 22:46:33 (724 occurrences)
Last logged: 17:11:57

Error fetching connected_plc_devices data: The device is currently not available. Maybe on standby?
Error fetching connected_wifi_clients data: The device is currently not available. Maybe on standby?
Error fetching switch_guest_wifi data: The device is currently not available. Maybe on standby?
Error fetching switch_leds data: The device is currently not available. Maybe on standby?

Additional information

No response

home-assistant · 2024-02-14T16:34:46Z

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.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

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

Shutgun · 2024-02-15T07:47:24Z

Hi @jusicgn , those are too many errors to be explained by the firmware endpoint. The polling interval of that endpoint was reduced to once every 5 hours, so I doubt, that deactivating it will help. I also see this in my setup, but way less. How are your average PLC data rates?

I guess we cannot avoid those errors completely. The devolo devices have weak CPUs that assumingly answer API calls with low priority to keep the main purpose (bridging traffic) up and running. I could try to increase the timeout I use, however the currently used 10 seconds already feel long to me.

Do you have any real service interruptions by those errors or are they "just" annoying you?

jusicgn · 2024-02-15T19:52:41Z

Hi @Shutgun , I've made a screenshot from my plc data rates for you :)

I'm not aware of service interruptions by those errors.
But from your words I'm wondering if these API calls are "stressing" the devices and I should turn them all off...?

Todays logs look like this:
Logger: homeassistant.components.devolo_home_network
Source: helpers/update_coordinator.py:345
Integration: devolo Home Network (documentation, issues)
First occurred: 13. Februar 2024 um 22:46:33 (1845 occurrences)
Last logged: 20:44:42

Error fetching connected_plc_devices data: The device is currently not available. Maybe on standby?
Error fetching connected_wifi_clients data: The device is currently not available. Maybe on standby?
Error fetching switch_guest_wifi data: The device is currently not available. Maybe on standby?
Error fetching switch_leds data: The device is currently not available. Maybe on standby?

Shutgun · 2024-02-15T21:37:17Z

Your data rates look ok, they aren't an issue. I definitely have weaker rates in my setup. I don't think the devices are stressed, they just don't answer in time. But what I did is to deactivate all entities I don't need. However, a few entities rely on the same API endpoints, so you'd have to deactivate them all in order to really reduce the number of calls.

Device attached to the router shares the same API with Number of PLC devices and PLC PHY rates
Number of connected Wi-Fi clients shares the same API with Presence detection
QR code of your guest Wi-Fi credentials shares the same API with Turn on/off guest Wi-Fi

The LAN 1-1 and the DIN-rail would be my first victims for this optimizations as the WiFi devices have better CPUs.

I will additionally try a larger timeout in my setup. Maybe that helps, too.

issue-triage-workflows · 2024-05-15T23:05:12Z

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Alf-Tupper · 2024-05-20T21:05:25Z

I have started to see the same issue... Should I just disable the entities?

Logger: homeassistant.components.devolo_home_network
Source: helpers/update_coordinator.py:347
integration: devolo Home Network (documentation, issues)
First occurred: 19 May 2024 at 13:59:13 (57 occurrences)
Last logged: 20:04:49

Error fetching switch_leds data: The device is currently not available. Maybe on standby?
Error fetching connected_wifi_clients data: The device is currently not available. Maybe on standby?
Error fetching switch_guest_wifi data: The device is currently not available. Maybe on standby?
Error fetching connected_plc_devices data: The device is currently not available. Maybe on standby?
Error fetching regular_firmware data: The device is currently not available. Maybe on standby?

Shutgun · 2024-05-23T12:45:14Z

Hi @Alf-Tupper , assuming your devices are not really on stand-by and the connection between them is rather stable, the devices sometimes are simply to slow to answer in time and sometimes they aren't. I cannot really tell when nor can my contacts at devolo.

What I would suggest if you can't live with ignoring the messages is to deactivate entities you don't need. That will reduce the presure on the device and increase the probability it will answer in time. So you don't necessarily need to deactivate those who log, but any deactivated entity can help.

CaptInsano · 2024-06-22T11:13:17Z

To add to this issue:

I have had a Devolo device that has been constantly giving the error "failed setup will retry" in Home Assistant.

I followed advice from other issue threads here and disabled any entities that I was not interested in but still had issues.

I then completely removed the device from Home Assistant but not I cannot re-add it? I have restarted both Home Assistant and the Devolo Wifi devices many times, but still no joy.

Standby is disabled on all devolo devices

Logs and pics below:

Logs below: (can provide them in-line if preferred)

home-assistant_2024-06-22T11-00-13.873Z.log

Shutgun · 2024-06-22T14:52:58Z

Hi @CaptInsano , this looks like a different issue. It seems like an IP protocol mismatch to me. While you show an IPv4 address in the screenshots there is an IPv6 address in the logs and that seems to be unreachable for your Home Assistant. Have you tried to restart the Magic 2 WiFi? Maybe it's not advertising itself properly via mDNS...

CaptInsano · 2024-06-22T17:07:02Z

I had restarted both Home Assistant and Devolo Magic 2 WIFI a few times before I added to this issue with no joy and I also restarted them again just now with no change.

I have always used IPv4 addresses and never had issues, I am also accessing my Home Assistant instance over IPv4.

CaptInsano · 2024-06-22T17:22:33Z

I just tested removing another devolo device from Home Assistant and re-adding it but that worked with no issue.

I have not changed any settings on my Magic 2 WIFI that I am aware of. Is there anything I should be trying/checking?

Shutgun · 2024-06-22T17:29:48Z

Do you know how to make an mDNS snapshot of your network, e.g. using avahi-browse? We could then check what the device advertises.

CaptInsano · 2024-06-23T11:43:38Z

I ran avahi-browse -a on my server hosting my HomeAssistant VM and left it run for a while, I also restarted the Magic 2 WIFI during this time but I don't see any sign of it here:

I am not sure if this is the command/output you are looking for?

# avahi-browse -a
+    br0 IPv6 oop-316                                       _mqtt._tcp           local
+    br0 IPv4 oop-316                                       _mqtt._tcp           local
+    br0 IPv6 Magic 2 LAN 1-1 #2                            _dvl-deviceapi._tcp  local
+    br0 IPv6 Magic 2 LAN triple                            _dvl-deviceapi._tcp  local
+    br0 IPv6 Magic 2 LAN 1-1                               _dvl-deviceapi._tcp  local
+    br0 IPv4 Magic 2 LAN 1-1 #2                            _dvl-deviceapi._tcp  local
+    br0 IPv4 Magic 2 LAN triple                            _dvl-deviceapi._tcp  local
+    br0 IPv4 Magic 2 LAN 1-1                               _dvl-deviceapi._tcp  local
+    br0 IPv6 _dvl-plcnetapi                                _tcp                 local
+    br0 IPv6 _http                                         _tcp                 local
+    br0 IPv6 _workstation                                  _tcp                 local
+    br0 IPv6 _mqtt                                         _tcp                 local
+    br0 IPv6 _dvl-deviceapi                                _tcp                 local
+    br0 IPv4 _workstation                                  _tcp                 local
+    br0 IPv4 _services                                     _dns-sd._udp         local
+    br0 IPv4 _nvstream_dbd                                 _tcp                 local
+    br0 IPv4 _mqtt                                         _tcp                 local
+    br0 IPv4 _dvl-deviceapi                                _tcp                 local
+    br0 IPv6 Magic 2 LAN 1-1 #2                            _http._tcp           local
+    br0 IPv6 Magic 2 LAN 1-1                               _http._tcp           local
+    br0 IPv6 Magic 2 LAN triple                            _http._tcp           local
+    br0 IPv4 Magic 2 LAN 1-1                               _http._tcp           local
+    br0 IPv4 Magic 2 LAN triple                            _http._tcp           local
+    br0 IPv4 Magic 2 LAN 1-1 #2                            _http._tcp           local
+    br0 IPv6 Magic 2 LAN 1-1 #2                            _dvl-plcnetapi._tcp  local
+    br0 IPv6 Magic 2 LAN triple                            _dvl-plcnetapi._tcp  local
+    br0 IPv4 Magic 2 LAN 1-1 #2                            _dvl-plcnetapi._tcp  local
+    br0 IPv4 Magic 2 LAN triple                            _dvl-plcnetapi._tcp  local
+    br0 IPv6 _googlecast                                   _tcp                 local
+    br0 IPv4 _googlecast                                   _tcp                 local
+    br0 IPv6 Android-TV-XXXXXXXXXXXXXXXXXXXXXXXXXXX   _googlecast._tcp     local
+    br0 IPv6 Nest-Audio-XXXXXXXXXXXXXXXXXXXXXXXXXXX   _googlecast._tcp     local
+    br0 IPv4 Nest-Audio-XXXXXXXXXXXXXXXXXXXXXXXXXXX   _googlecast._tcp     local
+    br0 IPv4 Android-TV-XXXXXXXXXXXXXXXXXXXXXXXXXXX   _googlecast._tcp     local
+    br0 IPv4 _androidtvremote2                             _tcp                 local
+    br0 IPv6 _androidtvremote2                             _tcp                 local
+    br0 IPv6 Living Room TV                                _androidtvremote2._tcp local
+    br0 IPv4 Living Room TV                                _androidtvremote2._tcp local
+    br0 IPv6 xxxxxxhomeassistant [XXXXXXXXXXXXXXXXXXXXXXXXXXX] _workstation._tcp    local
+    br0 IPv4 xxxxxxhomeassistant [XXXXXXXXXXXXXXXXXXXXXXXXXXX] _workstation._tcp    local
+    br0 IPv6 Magic 2 LAN 1-1                               _dvl-plcnetapi._tcp  local
+    br0 IPv4 _home-assistant                               _tcp                 local
+    br0 IPv6 _home-assistant                               _tcp                 local
+    br0 IPv6 XXXXXXXX                                      _home-assistant._tcp local
+    br0 IPv4 XXXXXXXX                                      _home-assistant._tcp local
+    br0 IPv6 _googlezone                                   _tcp                 local
+    br0 IPv4 _googlezone                                   _tcp                 local
+    br0 IPv6 XXXXXXX-XXXX-XXXX-XXXXX-XXXXXXXXXX          _googlezone._tcp     local
+    br0 IPv4 XXXXXXX-XXXX-XXXX-XXXXX-XXXXXXXXXX          _googlezone._tcp     local
+    br0 IPv4 _arduino                                      _tcp                 local
+    br0 IPv4 OMG_lilygo_rtl_433_ESP                        _arduino._tcp        local
+ ztc3q3atnx IPv4 _ssh                                          _tcp                 local
+ ztc3q3atnx IPv4 _sftp-ssh                                     _tcp                 local
+ ztc3q3atnx IPv4 _smb                                          _tcp                 local
+ ztc3q3atnx IPv4 _device-info                                  _tcp                 local
+ ztc3q3atnx IPv4 Tower-2                                       _sftp-ssh._tcp       local
+ ztc3q3atnx IPv4 Tower-2                                       _ssh._tcp            local
+ ztc3q3atnx IPv4 Tower-2                                       _device-info._tcp    local
+ ztc3q3atnx IPv4 Tower-2                                       _smb._tcp            local
+    br0 IPv4 Magic 2 LAN 1-1                               _dvl-plcnetapi._tcp  local
+    br0 IPv4 _http                                         _tcp                 local
+    br0 IPv4 _dvl-plcnetapi                                _tcp                 local
-    br0 IPv4 Magic 2 LAN 1-1                               _http._tcp           local
+    br0 IPv4 Magic 2 LAN 1-1                               _http._tcp           local
-    br0 IPv4 Magic 2 LAN 1-1 #2                            _dvl-deviceapi._tcp  local
+    br0 IPv4 Magic 2 LAN 1-1 #2                            _dvl-deviceapi._tcp  local
-    br0 IPv4 Magic 2 LAN 1-1                               _dvl-plcnetapi._tcp  local
-    br0 IPv4 Magic 2 LAN 1-1 #2                            _dvl-plcnetapi._tcp  local
+    br0 IPv4 Magic 2 LAN 1-1                               _dvl-plcnetapi._tcp  local
+    br0 IPv4 Magic 2 LAN 1-1 #2                            _dvl-plcnetapi._tcp  local

CaptInsano · 2024-06-23T12:03:50Z

Just to say: I also just did a factory reset of my Magic 2 WIFI device and still the same issue?

Shutgun · 2024-06-23T13:06:58Z

ok, that looks very weird. The Magic 2 WiFi is indeed not advertising itself via mDNS and that is why the connection to Home Assistant is broken. If you already factory reset it, I'm a bit our of options. If you click on the device in the devolo app: do you have options to e.g. turn of the LEDs or restart the device? Those functions are using the same API like I do. I assume, the device is on latest firmware?

CaptInsano · 2024-06-23T14:17:22Z

I can confirm I had full control over the device via the app.

I had also previously restarted my router and wireless APs but this time I disabled IPv6 on my router and restarted and then I started seeing Magic 2 WIFI on mDNS. It was then automatically detected by Home Assistant and is currently working.

I really appreciate your help but I believe it may have been an IPv6 issue that had never presented before.

I will monitor and then try and re-enable IPv6 to see if it continues to work

home-assistant bot added the integration: devolo_home_network label Feb 14, 2024

issue-triage-workflows bot added the stale label May 15, 2024

issue-triage-workflows bot removed the stale label May 20, 2024

Shutgun mentioned this issue Jul 30, 2024

Set parallel updates in devolo_home_network #122847

Merged

19 tasks

frenck closed this as completed in #122847 Jul 30, 2024

github-actions bot locked and limited conversation to collaborators Aug 29, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

devolo_home_network - Error fetching... #110555

devolo_home_network - Error fetching... #110555

jusicgn commented Feb 14, 2024

home-assistant bot commented Feb 14, 2024

Shutgun commented Feb 15, 2024 •

edited

Loading

jusicgn commented Feb 15, 2024

Shutgun commented Feb 15, 2024

issue-triage-workflows bot commented May 15, 2024

Alf-Tupper commented May 20, 2024

Shutgun commented May 23, 2024

CaptInsano commented Jun 22, 2024 •

edited

Loading

Shutgun commented Jun 22, 2024

CaptInsano commented Jun 22, 2024

CaptInsano commented Jun 22, 2024

Shutgun commented Jun 22, 2024

CaptInsano commented Jun 23, 2024

CaptInsano commented Jun 23, 2024

Shutgun commented Jun 23, 2024

CaptInsano commented Jun 23, 2024

devolo_home_network - Error fetching... #110555

devolo_home_network - Error fetching... #110555

Comments

jusicgn commented Feb 14, 2024

The problem

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

home-assistant bot commented Feb 14, 2024

Shutgun commented Feb 15, 2024 • edited Loading

jusicgn commented Feb 15, 2024

Shutgun commented Feb 15, 2024

issue-triage-workflows bot commented May 15, 2024

Alf-Tupper commented May 20, 2024

Shutgun commented May 23, 2024

CaptInsano commented Jun 22, 2024 • edited Loading

Shutgun commented Jun 22, 2024

CaptInsano commented Jun 22, 2024

CaptInsano commented Jun 22, 2024

Shutgun commented Jun 22, 2024

CaptInsano commented Jun 23, 2024

CaptInsano commented Jun 23, 2024

Shutgun commented Jun 23, 2024

CaptInsano commented Jun 23, 2024

Shutgun commented Feb 15, 2024 •

edited

Loading

CaptInsano commented Jun 22, 2024 •

edited

Loading