This is related to #23728
My router is a Fritz!Box 6590. HA is running as hass.io on a Raspi 3b.
Whenever I restart HA the entities of the UPNP integration become unavailable.
To solve that I have to remove the integration and add it again.
There are additional symptoms:
Every now and then, when I remove and re-add the integration, it comes up with device and entity names that differ from the names normally found (see screenshots below). When I remove and re-add it a second time, the original names most often re-appear. This happens about 1 or 2 times in 10.
Normal names start with: InternetGatewayDeviceV2 - FRITZ!Box 6590 Cable
Wrong names start with: FRITZ!Box 6590 Cable
Could it be, that on HA restarts the wrong names are found and thus the known entities with the original names become unavailable?
Correct device name:

Wrong device name:

Correct entity names of device:

Wrong entity names of device:

*Correct single entity:*

Wrong single entity:

Home assistant core (hass.io) 0.107.7 running on Raspberry Pi 3b
UPnP/IGD integration
configuration.yaml
Integration UPnP/IGD added through frontend configuration, not through configuration.yaml.
Output of upnp-client search (reduced to all LOCATION items with router's IP address):
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.248963",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_timestamp": "2020-04-08 20:30:26.252072",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:MediaServer:1",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36::urn:schemas-upnp-org:device:MediaServer:1",
"_timestamp": "2020-04-08 20:30:26.271411",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/avmnexusdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.275851",
"_address": "192.168.178.1:1900",
"_udn": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/avmnexusdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36",
"USN": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.278138",
"_address": "192.168.178.1:1900",
"_udn": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/avmnexusdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:avmnexus:1",
"USN": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-upnp-org:device:avmnexus:1",
"_timestamp": "2020-04-08 20:30:26.280215",
"_address": "192.168.178.1:1900",
"_udn": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/l2tpv3.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.282192",
"_address": "192.168.178.1:1900",
"_udn": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/l2tpv3.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36",
"USN": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.284173",
"_address": "192.168.178.1:1900",
"_udn": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/l2tpv3.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:l2tpv3:1",
"USN": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-upnp-org:device:l2tpv3:1",
"_timestamp": "2020-04-08 20:30:26.286160",
"_address": "192.168.178.1:1900",
"_udn": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.288251",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36",
"USN": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.290212",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:InternetGatewayDevice:1",
"USN": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-upnp-org:device:InternetGatewayDevice:1",
"_timestamp": "2020-04-08 20:30:26.292217",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36",
"USN": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.294181",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:WANDevice:1",
"USN": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36::urn:schemas-upnp-org:device:WANDevice:1",
"_timestamp": "2020-04-08 20:30:26.296144",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"USN": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.298223",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:WANConnectionDevice:1",
"USN": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36::urn:schemas-upnp-org:device:WANConnectionDevice:1",
"_timestamp": "2020-04-08 20:30:26.300228",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.304290",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36",
"USN": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.310171",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:InternetGatewayDevice:2",
"USN": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36::urn:schemas-upnp-org:device:InternetGatewayDevice:2",
"_timestamp": "2020-04-08 20:30:26.312146",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36",
"USN": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.315988",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:WANDevice:2",
"USN": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36::urn:schemas-upnp-org:device:WANDevice:2",
"_timestamp": "2020-04-08 20:30:26.318048",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"USN": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.319978",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:WANConnectionDevice:2",
"USN": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36::urn:schemas-upnp-org:device:WANConnectionDevice:2",
"_timestamp": "2020-04-08 20:30:26.321948",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/fboxdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.323898",
"_address": "192.168.178.1:1900",
"_udn": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/fboxdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36",
"USN": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.325798",
"_address": "192.168.178.1:1900",
"_udn": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/fboxdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:device:fritzbox:1",
"USN": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-upnp-org:device:fritzbox:1",
"_timestamp": "2020-04-08 20:30:26.327754",
"_address": "192.168.178.1:1900",
"_udn": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/satipdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "upnp:rootdevice",
"USN": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36::upnp:rootdevice",
"_timestamp": "2020-04-08 20:30:26.329677",
"_address": "192.168.178.1:1900",
"_udn": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/satipdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36",
"USN": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36",
"_timestamp": "2020-04-08 20:30:26.331560",
"_address": "192.168.178.1:1900",
"_udn": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/satipdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:ses-com:device:SatIPServer:1",
"USN": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36::urn:ses-com:device:SatIPServer:1",
"_timestamp": "2020-04-08 20:30:26.333487",
"_address": "192.168.178.1:1900",
"_udn": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:ContentDirectory:1",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36::urn:schemas-upnp-org:service:ContentDirectory:1",
"_timestamp": "2020-04-08 20:30:26.335780",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:ConnectionManager:1",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36::urn:schemas-upnp-org:service:ConnectionManager:1",
"_timestamp": "2020-04-08 20:30:26.338439",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36::urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1",
"_timestamp": "2020-04-08 20:30:26.340851",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/MediaServerDevDesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:avm.de:service:AVM_ServerStatus:1",
"USN": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36::urn:avm.de:service:AVM_ServerStatus:1",
"_timestamp": "2020-04-08 20:30:26.343082",
"_address": "192.168.178.1:1900",
"_udn": "uuid:fa095ecc-e13e-40e7-8e6c-444e6d893b36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/avmnexusdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-any-com:service:avmnexus:1",
"USN": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-any-com:service:avmnexus:1",
"_timestamp": "2020-04-08 20:30:26.345191",
"_address": "192.168.178.1:1900",
"_udn": "uuid:535502409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/l2tpv3.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-any-com:service:l2tpv3:1",
"USN": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-any-com:service:l2tpv3:1",
"_timestamp": "2020-04-08 20:30:26.347474",
"_address": "192.168.178.1:1900",
"_udn": "uuid:95802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-any-com:service:Any:1",
"USN": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-any-com:service:Any:1",
"_timestamp": "2020-04-08 20:30:26.349665",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1",
"USN": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1",
"_timestamp": "2020-04-08 20:30:26.351872",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6b-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANDSLLinkConfig:1",
"USN": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36::urn:schemas-upnp-org:service:WANDSLLinkConfig:1",
"_timestamp": "2020-04-08 20:30:26.354097",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANIPConnection:1",
"USN": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36::urn:schemas-upnp-org:service:WANIPConnection:1",
"_timestamp": "2020-04-08 20:30:26.356055",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igddesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANIPv6FirewallControl:1",
"USN": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36::urn:schemas-upnp-org:service:WANIPv6FirewallControl:1",
"_timestamp": "2020-04-08 20:30:26.358240",
"_address": "192.168.178.1:1900",
"_udn": "uuid:76802409-bccb-40e7-8e6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-any-com:service:Any:1",
"USN": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36::urn:schemas-any-com:service:Any:1",
"_timestamp": "2020-04-08 20:30:26.360322",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1",
"USN": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1",
"_timestamp": "2020-04-08 20:30:26.362366",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6b-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANDSLLinkConfig:1",
"USN": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36::urn:schemas-upnp-org:service:WANDSLLinkConfig:1",
"_timestamp": "2020-04-08 20:30:26.364370",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANIPConnection:2",
"USN": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36::urn:schemas-upnp-org:service:WANIPConnection:2",
"_timestamp": "2020-04-08 20:30:26.366404",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/igd2desc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-upnp-org:service:WANIPv6FirewallControl:1",
"USN": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36::urn:schemas-upnp-org:service:WANIPv6FirewallControl:1",
"_timestamp": "2020-04-08 20:30:26.368806",
"_address": "192.168.178.1:1900",
"_udn": "uuid:75802409-bccb-40e7-9f6a-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/fboxdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:schemas-any-com:service:fritzbox:1",
"USN": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36::urn:schemas-any-com:service:fritzbox:1",
"_timestamp": "2020-04-08 20:30:26.371041",
"_address": "192.168.178.1:1900",
"_udn": "uuid:123402409-bccb-40e7-8e6c-444E6D893B36",
"_source": "search"
}
{
"LOCATION": "http://192.168.178.1:49000/satipdesc.xml",
"SERVER": "FRITZ!Box 6590 Cable UPnP/1.0 AVM FRITZ!Box 6590 Cable 148.07.12",
"CACHE-CONTROL": "max-age=1800",
"EXT": "",
"ST": "urn:ses-com:service:satip:1",
"USN": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36::urn:ses-com:service:satip:1",
"_timestamp": "2020-04-08 20:30:26.373080",
"_address": "192.168.178.1:1900",
"_udn": "uuid:663d5d6c-f9f8-4bb4-84d4-444E6D893B36",
"_source": "search"
}
Same here with an FRITZ!Box 7490 (FRITZ!OS: 07.12) and running Home Assistant 0.107.7 in Docker on Ubuntu.
Output of upnp-client search (reduced to all LOCATION items with router's IP address):
output.txt
Hey there @StevenLooman, mind taking a look at this issue as its been labeled with a integration (upnp) you are listed as a codeowner for? Thanks!
Thank you for reporting.
I have taken the liberty to group it with #33108. It saves the device type (version) and, if given, requires the discovered device to be of the same device type (version.)
This should should be fixed with #33108. Please test in home assistant 0.109.
I am still seeing the problem on docker dev branch container version 0.109.0.dev20200413
which from git contains the alleged fix.
The symptom is that I have my router (a vodafone Vox3.0) previously registered via the uPNP component that disappeared (no data available) upon a restart of the container. In my case removing and re-adding the integration has NOT fixed the problem and the router remains undetected (no devices found) even though upnp-client search from inside the container detects it OK.
Is there anything else I can do to reset/restore the system without a complete refresh since it in use in production with operational implications should it be taken down for any length of time?
So removing and re-adding the integration does not fix it? The searching for the router is the same code used in both the upnp-component and the upnp-client search command. Can you report if the search-command finds the device with ST being urn:schemas-upnp-org:device:InternetGatewayDevice:1 or urn:schemas-upnp-org:device:InternetGatewayDevice:2?
Home Assistant stores data in JSON format the (hidden) .storage directory. Perhaps you can find something there.
To be fair, I doubt restarting home assistant will fix the problem. There shouldn't be that much state that is saved. Perhaps your container is not properly network and thus cannot discover any devices?
I'm struggling with unreliable operation. There are always references to my router relating to different urns e.g. urn:schemas-upnp-org:service:ContentDirectory:1 and urn:schemas-wifialliance-org:device:WFADevice:1 whenever I do the upnp-client search from inside the container or some other host tool like GUPnP universal-control point or gssdp-discover.
Just once over the last 4 hours of trying various approaches I have manage to get the following back from the upnp-client search:
{"CACHE-CONTROL": "max-age=120", "DATE": "Tue, 14 Apr 2020 23:57:16 GMT", "ST": "urn:schemas-upnp-org:device:InternetGatewayDevice:1", "USN": "uuid:b077ddef-aa61-4ea4-9397-0a37ea32c201::urn:schemas-upnp-org:device:InternetGatewayDevice:1", "EXT": "", "SERVER": "OpenWRT/OpenWrt/Attitude_Adjustment__r43446_ UPnP/1.1 MiniUPnPd/1.8", "LOCATION": "http://192.168.149.8:5000/rootDesc.xml", "OPT": "\"http://schemas.upnp.org/upnp/1/0/\"; ns=01", "01-NLS": "1", "BOOTID.UPNP.ORG": "1", "CONFIGID.UPNP.ORG": "1337", "_timestamp": "2020-04-15 00:57:16.473554", "_address": "192.168.149.8:1900", "_udn": "uuid:b077ddef-aa61-4ea4-9397-0a37ea32c201", "_source": "search"}
which is what you were expecting and when that happens HASS then picks it up OK.
My router has been up for many months (ie no reboots and no significant config changes) but I have been altering various things like connecting via wifi rather than wired network this evening and packet capturing the results in my attempts to get it to work. I have also rebuilt my docker containers but with no obvious beneficial effect.
Maybe it is a network timeout issue on the discovery process?
Discovery via upnp-client search uses a timeout of 4 seconds (as per specification I believe.) Home Assistant already has a increased timeout of 10 seconds.
What if you do discovery from another device, does it have the same issue?
Some devices behave badly when they have been running for longer times. My router stops doing WiFi after some time, I'm guessing about 3 weeks. Perhaps a reboot will help of your router will help in this case?
Also, that other service types do get discovered each time, but InternetGatewayDevice does not, does not seem like a coincidence.
I used to design military and safety critical systems where up-time is critical so I am fully aware of the lousy quality of many domestic products and the need to reboot. It's why I only use linux professionally. Vodafone's Vox 3.x is know to be buggy and lacking features (still a work in progress) and so it wouldn't surprise if that is the root cause.
Previously the router was always returning other urn's OK so I had sorted of discounted this as the root cause and it stopped around the time I restarted the HASS container. The grafana graphs of the metrics delivered via HASS to my logging influxdb show this (but not 100% conclusively).
It's working perfectly now without any having done any router reboots and the command below shows the urn is discoverable:
gssdp-discover -i br0 --timeout=10 | grep Inter
USN: uuid:b077ddef-aa61-4ea4-9397-0a37ea32c201::urn:schemas-upnp-org:device:InternetGatewayDevice:1
USN: uuid:b077ddef-aa61-4ea4-9398-0a37ea32c201::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
It returns with minimal delay from the scan being initiated.
Interestingly before I got it working the router was showing unknown UDP packets in its own logs when the discovery was attempted but not now.
Overall I think you are right its a composite error with a known bug in HASS combined perhaps with the router getting itself internally confused and the combination of the upgrade of HASS and prodding it from various directions has fixed it.
Without getting into trying to reproduce the problem on what is a production system (I'm reluctant to keep bouncing HASS for the impact this has elsewhere) I can only think to keep an eye on it and report if I see anything else.
Thanks for your help.
I'm glad the problem has been resolved.
Shall we close this, or do we want to wait for test results? @dgomes
@StevenLooman let's wait for 0.109 so I can test too. Should be available very soon.
@Jpsy Please open a new issue when any problems arise.