Core: Secondary LAN (not connected) is now detected

[chemelli74]

The problem

Latest build, 0.110b0, detect also secondary LAN that is not connected.

Environment

• Home Assistant Core release with the issue: 0.110.b0
• Last working Home Assistant Core release (if known): 0.110.dev20200513
• Operating environment (Home Assistant/Supervised/Docker/venv): Docker
• Integration causing this issue: synology_dsm
• Link to integration documentation on our website:

Problem-relevant configuration.yaml

-

Traceback/Error logs

-

Additional information

[probot-home-assistant[bot]]

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

[uvjustin]

The setup information should come from the zeroconf integration. Can you provide the zeroconf information for your setup? Instructions here: https://github.com/home-assistant/core/issues/27371#issue-504907798
Maybe there is a mDNS reflector/repeater across the two interfaces? Is the forked-daapd server on the same machine as HA? If so, it could also be related to this: https://github.com/home-assistant/core/issues/35031

[chemelli74]

The setup information should come from the zeroconf integration. Can you provide the zeroconf information for your setup? Instructions here: #27371 (comment)

I see all my services but not the one detected :-S

Simone

[uvjustin]

This is from the HA container?

---

From: Simone Chemelli [e-mail]
Sent: Saturday, May 16, 2020 12:34:11 AM
To: home-assistant/core [e-mail]
Cc: uvjustin [e-mail]; Comment [e-mail]
Subject: Re: [home-assistant/core] Secondary LAN (not connected) is now detected (#35642)

The setup information should come from the zeroconf integration. Can you provide the zeroconf information for your setup? Instructions here: #27371 (comment)https://github.com/home-assistant/core/issues/27371#issue-504907798

I see all my services but not the one detected :-S

Simone

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/35642#issuecomment-629358570, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK7SUVN4IDVZJPUMRPIGJIDRRVVIHANCNFSM4NBDMLUQ.

[chemelli74]

This is from the HA container?

Nope, I used windows utility on my laptop.

Simone

[chemelli74]

Maybe there is a mDNS reflector/repeater across the two interfaces?

Nope, appeared just now , previous build didn't show

Is the forked-daapd server on the same machine as HA?

Nope, is detected on the Synology NAS

Simone

[uvjustin]

Nope, appeared just now , previous build didn't show

I don't think 0.110.dev20200513 had the forked-daapd integration at all, so there wouldn't be any discovery of a forked-daapd integration. But the host detection and host information should come from zeroconf, so what I think you are seeing isn't a problem with the forked-daapd integration itself.

Can you do another zeroconf scan from the HA machine?

[chemelli74]

Can you do another zeroconf scan from the HA machine?

Which tool in HA shell should I use ?
I found a "avahi-brose" on another container; run it shows this (removed other devices):

+   eth1 IPv4 HomeNAS                                       _http._tcp           local
+   eth0 IPv4 HomeNAS                                       _http._tcp           local
+   eth1 IPv4 HomeNAS                                       _afpovertcp._tcp     local
+   eth0 IPv4 HomeNAS                                       _afpovertcp._tcp     local
+   eth1 IPv4 HomeNAS                                       _daap._tcp           local
+   eth0 IPv4 HomeNAS                                       _daap._tcp           local
+   eth1 IPv4 HomeNAS                                       _smb._tcp            local
+   eth0 IPv4 HomeNAS                                       _smb._tcp            local
+   eth1 IPv4 HomeNAS                                       _device-info._tcp    local
+   eth0 IPv4 HomeNAS                                       _device-info._tcp    local
+   eth1 IPv4 HomeNAS                                       _webdavs._tcp        local
+   eth0 IPv4 HomeNAS                                       _webdavs._tcp        local

I can see there is both eth1 and eth0 listed.
Maybe because Docker is on top of that NAS.
Is there a way to limit zeroconf to discover on same network segment as HA ?

Simone

[uvjustin]

@robbiet480 @Kane610 While it should be possible to get the zeroconf integration to test whether an advertised service is available, I think the correct thing to do is to get your Synology setup from broadcasting incorrect zeroconf information.

[chemelli74]

Updated to b2 and now I have the following screenshot:

You can see a change in behavior, now the ip is the working eth.

Simone

EDIT: I noticed that there is no logo for this window, while all embedded integration has one usually.

[uvjustin]

I don't think anything changed in the forked-daapd or zeroconf code that would affect the behavior. It's possible that this is just a race condition and that this time the proper zeroconf entry was processed first.
The logos were already uploaded to the logo repository a few days ago.

[chemelli74]

It's possible that this is just a race condition and that this time the proper zeroconf entry was processed first.

Good point, this can be the reason I never saw it before.
Maybe the fix for UPnP fixed a underlining issue that made this discovery appear for the first time.

Simone

[chemelli74]

It's for sure a race condition.
Last reboot log:

2020-05-18 13:55:09 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 129, in async_init
    flow, flow.init_step, data, init_done
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step
    result: Dict = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/forked_daapd/config_flow.py", line 168, in async_step_zeroconf
    if entry.data[CONF_HOST] != discovery_info["host"]:
KeyError: 'host'

Simone

[uvjustin]

The last log you left is actually the issue raised here: https://github.com/home-assistant/core/issues/35764 which affects ignored forked-daapd zeroconf entries. That should be resolved when PR 35772 gets pulled.
Your main issue still seems to be that your NAS device is advertising some services on the wrong interface.

[chemelli74]

Your main issue still seems to be that your NAS device is advertising some services on the wrong interface.

Ticket opened with Synology support.

Simone

[DavidFW1960]

@uvjustin that PR seems merged and included in 0.110.0b4 but I see this error now:

Log Details (ERROR)
Logger: homeassistant.core
Source: components/forked_daapd/config_flow.py:161
First occurred: 10:03:58 AM (1 occurrences)
Last logged: 10:03:58 AM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 129, in async_init
    flow, flow.init_step, data, init_done
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step
    result: Dict = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/forked_daapd/config_flow.py", line 161, in async_step_zeroconf
    and float(discovery_info["properties"].get("mtd-version", 0)) >= 27.0
ValueError: could not convert string to float: '0.2.4.1'

I did show ignored and forked_daarp was there so I deleted it and restarted HA and it was not redetected but I still see the error.

[uvjustin]

@uvjustin that PR seems merged and included in 0.110.0b4 but I see this error now:

Log Details (ERROR)
Logger: homeassistant.core
Source: components/forked_daapd/config_flow.py:161
First occurred: 10:03:58 AM (1 occurrences)
Last logged: 10:03:58 AM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 129, in async_init
    flow, flow.init_step, data, init_done
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step
    result: Dict = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/forked_daapd/config_flow.py", line 161, in async_step_zeroconf
    and float(discovery_info["properties"].get("mtd-version", 0)) >= 27.0
ValueError: could not convert string to float: '0.2.4.1'

I did show ignored and forked_daarp was there so I deleted it and restarted HA and it was not redetected but I still see the error.

Thank you for this. It seems you have a firefly media server and the version numbering of that is different than what we get with forked-daapd. I will submit a PR to address this.

[DavidFW1960]

firefly media server

I don't even know what that is much less have one lol...
Thanks.
My TV detects the following media servers:
OSMC - a Vero4 running Kodi
Fetch TV STB (www.fetch.com.au)
FritzBox 7490 repeater
Fritzbox 7590 Router
Netgear Stora UPNP-AV
Synology NAS
Maybe one of those identifies as a Firefly Media Server....

[uvjustin]

The iTunes Server package on the Synology NAS is actually a repackaged Firefly Media Server (the predecessor to forked-daapd). Edit: PR here https://github.com/home-assistant/core/pull/35796

[DavidFW1960]

Gotcha. It was only the other day that I installed and configured Video Station as I was having difficulty with teh TV seeing some of the video folders. I do have iTunes Server installed there but never used it that I know of (but clearly it advertises itself)

[chemelli74]

@uvjustin that PR seems merged and included in 0.110.0b4 but I see this error now:

Log Details (ERROR)
Logger: homeassistant.core
Source: components/forked_daapd/config_flow.py:161
First occurred: 10:03:58 AM (1 occurrences)
Last logged: 10:03:58 AM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 129, in async_init
    flow, flow.init_step, data, init_done
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 201, in _async_handle_step
    result: Dict = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/components/forked_daapd/config_flow.py", line 161, in async_step_zeroconf
    and float(discovery_info["properties"].get("mtd-version", 0)) >= 27.0
ValueError: could not convert string to float: '0.2.4.1'

I did show ignored and forked_daarp was there so I deleted it and restarted HA and it was not redetected but I still see the error.

Thank you for this. It seems you have a firefly media server and the version numbering of that is different than what we get with forked-daapd. I will submit a PR to address this.

Same error on beta4 and same NAS ;-)

Simone

[uvjustin]

Same error on beta4 and same NAS ;-)

Simone

Don't worry, read above... #35796 should take care of this.

[DavidFW1960]

Seems fixed now in b5. Thanks.

[chemelli74]

I can confirm that log error is fixed in b5, but what about the original issue of this thread ?
Should I expect it to be fixed as well ?

Simone