TypeError: get_all_addresses() missing 1 required positional argument: 'address_family'

Configuration
1

Upgraded from 0.77.3 to 0.78.1 and during start, I notice this in my logs:

TypeError: get_all_addresses() missing 1 required positional argument: 'address_family',
  File "/usr/local/lib/python3.6/site-packages/netdisco/ssdp.py", line 225, in scan,
    for addr in zeroconf.get_all_addresses():,
  File "/usr/local/lib/python3.6/site-packages/netdisco/ssdp.py", line 89, in update,
    entry for entry in scan(),
    self.update(),
  File "/usr/local/lib/python3.6/site-packages/netdisco/ssdp.py", line 41, in scan,
    self.ssdp.scan(),
  File "/usr/local/lib/python3.6/site-packages/netdisco/discovery.py", line 57, in scan,
    netdisco.scan(),
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/discovery.py", line 194, in _discover,
    result = self.fn(*self.args, **self.kwargs),
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run,
    results = await hass.async_add_job(_discover, netdisco),
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/discovery.py", line 168, in scan_devices,
Traceback (most recent call last):,
2018-09-20 20:40:58 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved

I’ve also noticed Home Assistant is no longer seeing my Harmony Hub because when I try to run a switch I have setup to turn on/off activities, it does not work and this is showing up in the logs:

2018-09-20 22:35:16 WARNING (MainThread) [homeassistant.core] Unable to find service remote/turn_off,
2018-09-20 22:35:33 WARNING (MainThread) [homeassistant.core] Unable to find service remote/turn_off,
2018-09-20 22:35:48 WARNING (MainThread) [homeassistant.core] Unable to find service remote/turn_off,
2018-09-20 22:36:17 WARNING (MainThread) [homeassistant.core] Unable to find service remote/turn_on

I didn’t change anything in my configuration.yaml after upgrading. This is running on Home Assistant installed inside a container (Docker).

Edit: Looks like it might be related to this issue.

1 Like
2

Is there any solution?

When I installed hassio last week the very first time I was able to use tts to send messages to my google home devices. Then I started to configure hassio but when I tried to use this feature yesterday it did not work. I thought there are issues with DuckDNS, SSL and so on. I even restored several older snapshots from hassio, even the very oldest which I did after the fresh install: it was version 0.77…
But there was no way to get tts working again.

Then I decided to make a completely new setup of hassio, I started from the very beginning with flashing the image to the SD card.
But I was very suprised that nothing was detected.

And now I see, that at first install today I got hassio 0.78.1 and I get exactly these discovery issues. Nothing is detected.

Is there a way to downgrade to an older hassio, where discovery worked fine?

But when I only restore my latest backups from my first installation then tts will still not work. So I need to investigate which step in my configurations and adding components avoided tts to work. But for this I need a valid and working starting point.

BTW, what about new users, starting the first time just with the 0.78.1 release: discovery will not work for them all?

1 Like
3

I’m having the same issue, but on Hass.io. I’m also having issues with tts, where some of my automations work and others don’t. I don’t really know where to go with this one.

4

Fixed in 0.78.2

5

Just upgraded to 0.78.3 and it fixed this issue. Thanks!