Getting errors for both Frit!Repeater 2400's

[JCPvanHooren]

I have 2 Fritz!Repeater 2400's.
Working with chemelli74 on a fix to avoid an error for the extender I usually don't have plugged in (unless when I use it), we updated Home Assistant AVM FRITZ!Box Tools to use v1.8.0 of fritzconnection library and got 2 errors for both extenders (both the one plugged in, as well as the one not plugged in).

IP.2 is the one plugged in.
IP.3 is the one not plugged in.

The Home Assistant log:
2021-12-29 17:19:25 INFO (SyncWorker_0) [fritzconnection] Unable to retrieve resource 'http://192.168.1.2:49000/igddesc.xml' from the device. 2021-12-29 17:19:28 ERROR (SyncWorker_6) [fritzconnection] Unable to get a connection: HTTPConnectionPool(host='192.168.1.3', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8c829640>: Failed to establish a new connection: [Errno 113] Host is unreachable')) 2021-12-29 17:19:29 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Kelder' for fritz integration not ready yet: Unable to get a connection: HTTPConnectionPool(host='192.168.1.3', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f8c829640>: Failed to establish a new connection: [Errno 113] Host is unreachable')); Retrying in background 2021-12-29 17:19:31 WARNING (MainThread) [homeassistant.helpers.entity] Entity climate.nefit (<class 'custom_components.nefiteasy.climate.NefitThermostat'>) implements device_state_attributes. Please report it to the custom component author. 2021-12-29 17:19:40 ERROR (SyncWorker_1) [fritzconnection] Unable to get a connection: HTTPConnectionPool(host='192.168.1.3', port=49000): Max retries exceeded with url: /igddesc.xml (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f85813ee0>: Failed to establish a new connection: [Errno 113] Host is unreachable'))

[kbr]

The INFO entry for IP.2 is ok. It's just the information that the igddesc.xml resource is not available (it's not a router with this service). But otherwise the device is responsive.

For IP.3 it's different. The library is unable to establish a physical connection.