I’ve started getting this. Does anyone have any idea why that might be or what it means?
018-07-07 09:05:14 WARNING (SyncWorker_17) [soco.discovery] Can't make a discovery socket for 92.242.132.15: OSError: [Errno 99] Address not available
I’ve started getting this. Does anyone have any idea why that might be or what it means?
018-07-07 09:05:14 WARNING (SyncWorker_17) [soco.discovery] Can't make a discovery socket for 92.242.132.15: OSError: [Errno 99] Address not available
+1 here – haven’t gotten the root of the issue, occurring since 0.73 I believe.
Hi @klogg & @jamie_shaw I’m seeing this and just starting to dig into it a bit. Are you with BT by any chance?
I looked up IP 92.242.132.15 and it belongs to:
organisation: ORG-BL53-RIPE
org-name: Barefruit Ltd.
address: 5 Windmill Street
address: W1T 2JA
address: London
address: UNITED KINGDOM
phone: +44 207 637 0304
Barefuit appear to being an advertising company. Barefruit generates highly targeted traffic for ISPs by replacing DNS and HTTP errors with relevant advertising. http://www.barefruit.com/
It looks like BT use them for DNS error / HTTP errors:
Also looks like we can opt out http://preferences.webaddresshelp.bt.com/selfcare/
However, this does suggest there is some DNS / HTTP error from Hassio
I’ve opted out but still see this logged. Will give it some time
soco.discovery seems to be used by the Sonos component. Does anyone of you use Sonos in Home Assistant?
2 for 2 here. Sonos user, and BT customer – that said, I do not use BT routers, if that should make any difference?
I’ve also moved my Mac-based install over to a Ubuntu VM and not noticed this issue recently.
@niven01, @jamie_shaw, @danielperna84.
2 for 2 here too
Thanks for the info and I am just about to follow that link to opt out (even if it doesn’t remove the warning in my log!!)
Just done a restart and actually received this error – the IP address is just my own, so it could be the one above is just a now redistributed dynamic address?
Yep, I am still getting this error too. I also have Sonos
Will continue to look into this
Same problem here. Sonos user, on BT but don’t use their P.o.S. router. I also use have the following music services enabled on my Sonos - Spotify x 5, Plex, Amazon Music, Amazon Music Library and also local media on CIFS share.
Disabling Sonos discovery doesn’t rectify the problem either.