search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.72k stars 30.45k forks source link

Lifx integration hhas stopped working shortly after installing 2021.9.3 #55785

Closed sesquipedality closed 3 years ago

sesquipedality commented 3 years ago

The problem

Last night, home assistant stopped being able to talk to all my lights. I suspect this may be related to upgrading to 2021.09.03 (I am running in docker, and use watchtower to upgrade my containers automatically). Restarting does not bring the lights back. They continue to be on the network and accessible using my flic buttons so I am confident that the problem is to to with home assistant. I have log entries as follows:

2021-09-05 09:41:58 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.study

Nothing else useful appears to be in the logs, and all the lights are showing as "unavailable" in Lovelace.

What is version of Home Assistant Core has the issue?

core-2021.9.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Lifx

Link to integration documentation on our website

https://www.home-assistant.io/integrations/lifx/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2021-09-05 09:41:58 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.study

Additional information

No response

probot-home-assistant[bot] commented 3 years ago

lifx documentation lifx source (message by IssueLinks)

sesquipedality commented 3 years ago

Reverting to 2021.8 does not seem to fix anything.

sesquipedality commented 3 years ago

This intergration has spontaneously started working again. I am not aware of anything changing.

sesquipedality commented 3 years ago

And disappeared again after I restarted the server.

amelchio commented 3 years ago

I would like to investigate but there is too little information here and LIFX works fine for me with 2021.9.4.

sesquipedality commented 3 years ago

Thank you. What information would help? Happy to provide additional info, but I'm not sure what to say beyond "it stopped working after being fine for months to years and I can't work out why".

amelchio commented 3 years ago

Yeah I understand the quandary. At least the version where the problem appeared would be helpful. If the old version has broken retroactively, it seems more likely that it is due to a change in your local environment.

You can try to enable debug logging in configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.components.lifx: debug

(though not much is logged so it is unlikely to actually reveal the issue)

sesquipedality commented 3 years ago

OK. I have done this. This is what I have from the restart

$ grep -i lifx home-assistant.log
2021-09-08 13:34:07 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'cast', 'persistent_notification', 'group', 'zeroconf', 'python_script', 'history', 'default_config', 'updater', 'timer', 'media_source', 'switch', 'webostv', 'favicon', 'input_boolean', 'ssdp', 'input_select', 'lifx', 'esphome', 'harmony', 'tag', 'sun', 'mobile_app', 'blueprint', 'network', 'onvif', 'energy', 'input_number', 'my', 'ffmpeg', 'ipp', 'usb', 'panel_iframe', 'trace', 'sensor', 'light', 'mqtt', 'hacs', 'dhcp', 'tts', 'homekit_controller', 'configurator', 'tradfri', 'automation', 'counter', 'script', 'zone', 'localtuya', 'input_datetime', 'map', 'system_health', 'input_text', 'met', 'scene', 'cover', 'logbook', 'remote'}
2021-09-08 13:34:08 INFO (MainThread) [homeassistant.setup] Setting up lifx
2021-09-08 13:34:08 INFO (MainThread) [homeassistant.setup] Setup of domain lifx took 0.0 seconds
2021-09-08 13:34:08 INFO (MainThread) [homeassistant.components.light] Setting up light.lifx

Still getting the same error message as above:

2021-09-08 13:35:24 WARNING (MainThread) [homeassistant.helpers.service] Unable to find referenced entities light.sofa
sesquipedality commented 3 years ago

I'm honestly at a loss to identify a relevant change in my environment. I'd been having a couple of weeks of fiddling with various things, adding a couple of new integrations, but nothing that ought to have affected lifx. I first noticed the problem on the day of 4 Sep - watchtower updates me to the latest release automatically, so I can't say when precisely that happened.

Git tells me that the last bit of tinkering I checked in was on 29 August, which was adding a Tuca smart plug (via the localtuya integration) with an associated automation. This was about a week before the failure. I might have tinkered with lovelace a bit since then but nothing major (otherwise I'd have checked it into git).

amelchio commented 3 years ago

It is likely a network level issue; do you have VLANs, firewalls or something else that can complicate things?

sesquipedality commented 3 years ago

I have a UniFi Ubiquiti wifi AP connected to a wired switch connected to the Home Assistant server. There is a VLAN on the server (which is used to isolate a different device on the network) but as I mentioned, it's been running flawlessly like this for months to a year prior to failing, and I have made no changes to the network topology. Only the server port itself has any VLAN awareness. No firewalls between the server and the wifi router. All devices are on the same logical /24.

When I have a bit of time, I will fire the container up on a different machine to rule out any interference from the VLAN definitively.

francais01 commented 3 years ago

I just started using Home Assistant yesterday and have the same problem with LIFX. I have no VLAN's and the lights work fine with the LIFX app and HTTP API. I added the debug settings to configuration.yaml, did a fresh docker-compose pull, and restarted. I am now running 2021.9.5 and my log output looks the same as what @sesquipedality sees.

> rg lifx home-assistant.log    
43:2021-09-09 14:34:34 INFO (MainThread) [homeassistant.bootstrap] Setting up stage 2: {'updater', 'zone', 'default_config', 'lifx', 'coronavirus', 'ssdp', 'network', 'system_health', 'input_number', 'usb', 'gdacs', 'history', 'cast', 'input_boolean', 'input_datetime', 'timer', 'met', 'mobile_app', 'logbook', 'ipp', 'tts', 'input_select', 'zeroconf', 'braviatv', 'sun', 'energy', 'input_text', 'dhcp', 'group', 'script', 'scene', 'denonavr', 'map', 'tag', 'my', 'media_source', 'trace', 'counter', 'automation', 'blueprint'}
117:2021-09-09 14:34:36 INFO (MainThread) [homeassistant.setup] Setting up lifx
118:2021-09-09 14:34:36 INFO (MainThread) [homeassistant.setup] Setup of domain lifx took 0.0 seconds
146:2021-09-09 14:34:37 INFO (MainThread) [homeassistant.components.light] Setting up light.lifx
amelchio commented 3 years ago

@francais01 As you say it is a new install, make sure you have the network_mode: host setting in your docker-compose.yml file.

francais01 commented 3 years ago

@francais01 As you say it is a new install, make sure you have the network_mode: host setting in your docker-compose.yml file.

Yep, I copied it from the docs and it looks like this:

version: '3'
services:
  homeassistant:
    container_name: homeassistant
    image: "ghcr.io/home-assistant/home-assistant:stable"
    volumes:
      - /etc/homeassistant:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    privileged: true
    network_mode: host
francais01 commented 3 years ago

BTW, it wouldn't seem to be a networking issue as my new install had no trouble finding several chromecast devices, etc. (On the same WiFi as the LIFX lights.)

amelchio commented 3 years ago

The LIFX protocol is difficult to handle for connection tracking and NAT so it often is a networking issue even if other stuff works. If you have a firewall, you probably need to allow UDP from port 56700.

You can try something like this on the Home Assistant host to see what's going on:

sudo tcpdump -n -i eno1 'udp port 56700'

(you might have to change eno1 to your actual network device)

sesquipedality commented 3 years ago

Interesting. I am using bridged networking because I have virtual machines (one of which is my router) running on the same machine. Using tcpdump it looks like broadcast packets are being sent out, but nothing is coming back. as follows;

# tcpdump -n -i vmbr0 'udp port 56700'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vmbr0, link-type EN10MB (Ethernet), capture size 262144 bytes
23:49:43.184498 IP 192.168.37.20.59268 > 255.255.255.255.56700: UDP, length 36
23:50:24.719933 IP 192.168.37.70.56700 > 255.255.255.255.56700: UDP, length 36
23:50:48.195231 IP 192.168.37.20.59268 > 255.255.255.255.56700: UDP, length 36
23:51:24.722453 IP 192.168.37.70.56700 > 255.255.255.255.56700: UDP, length 36
23:51:53.204077 IP 192.168.37.20.59268 > 255.255.255.255.56700: UDP, length 36
23:52:24.725229 IP 192.168.37.70.56700 > 255.255.255.255.56700: UDP, length 36
23:52:58.216076 IP 192.168.37.20.59268 > 255.255.255.255.56700: UDP, length 36
23:53:24.730194 IP 192.168.37.70.56700 > 255.255.255.255.56700: UDP, length 36

.20 is the server. .70 is my LG TV. I can confirm the TV can still control the lights.

tcpdump -vv reveals something which may or may not be of interest

23:58:23.273963 IP (tos 0x0, ttl 64, id 26576, offset 0, flags [DF], proto UDP (17), length 64)
192.168.37.20.59268 > 255.255.255.255.56700: [bad udp cksum 0xe5f9 -> 0x5e11!] UDP, length 36

So it looks as though my UDP packets are somehow ending up malformed (the packets from the TV are OK).

I would be interested to know if @francais01 has the same symptoms.

sesquipedality commented 3 years ago

No, never mind. I don't think that's the problem. When I tcpdump from another machine (also running VMs and a bridged NIC), I get

00:05:58.340329 IP (tos 0x0, ttl 64, id 15957, offset 0, flags [DF], proto UDP (17), length 64)
192.168.37.20.59268 > 255.255.255.255.56700: [udp sum ok] UDP, length 36

Apparently this is some expected linux kernel weirdness - see https://sokratisg.net/2012/04/01/udp-tcp-checksum-errors-from-tcpdump-nic-hardware-offloading/

francais01 commented 3 years ago

I stand corrected. It may well be networking, but within docker. I'll do some further debugging in the next day or so. So far I added port 56700/udp to the firewall and added 56700:56700/udp to the docker-compose file but that hasn't helped yet. I can see Home Assistant sending out a broadcast and then several replies from lights on the host, but I'll need to debug inside of the container to see if packets are getting there. Here is the capture on the host:

  125 275.097485448 192.168.72.57 → 255.255.255.255 UDP 78 50648 → 56700 Len=36
  126 275.144120450 192.168.72.90 → 192.168.72.57 UDP 83 56700 → 50648 Len=41
  127 275.146208819 192.168.72.97 → 192.168.72.57 UDP 83 56700 → 50648 Len=41
  128 275.148556760 192.168.72.92 → 192.168.72.57 UDP 83 56700 → 50648 Len=41
  129 275.148556838 192.168.72.91 → 192.168.72.57 UDP 83 56700 → 50648 Len=41
amelchio commented 3 years ago

@francais01 Adding port-forwarding to Docker is not needed/possible with host networking. When you change the firewall, make sure that the filter is for source port 56700. Usually one makes rules for the destination port but that will not work with LIFX (or you can check the advanced section of the documentation to set a fixed port).

amelchio commented 3 years ago

@sesquipedality Your problem seems to be that bulb responses do not reach your Home Assistant host (or maybe the broadcast does not reach the bulb – but it does reach your other server so that would surprise me). Did you try power-cycling a bulb yet, I have seen them get their routing information wrong sometimes.

sesquipedality commented 3 years ago

Just tried power cycling one of the bulbs. It has not sprung back to life, sadly.

When I have a bit of time I might get the switch to port mirror the wifi router so I can see whether packets are coming/going in both directions there. Not sure if it brings me any closer to a fix though. It's such odd behaviour.

francais01 commented 3 years ago

I've fixed the issue on my end and will recap what I have running now that works:

amelchio commented 3 years ago

@sesquipedality You can actually run tcpdump on the Unifi AP itself, for example:

ssh admin@10.0.5.2 'tcpdump -n -e -i ath0 udp port 56700'

Make sure that both the IP and the MAC addresses are as expected.

See https://help.ui.com/hc/en-us/articles/227129127-UniFi-Methods-for-Capturing-Useful-Debug-Information#4 for more information.

sesquipedality commented 3 years ago

OK - with more effort than strictly ought to have been necessary I was able to run tcpdump on the unifi. I got

uap-BZ.5.60.9# tcpdump -n -i br0 'udp port 56700'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br0, link-type EN10MB (Ethernet), capture size 262144 bytes
18:27:42.638174 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:27:42.639272 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:27:52.415421 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:27:52.415414 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:27:52.415430 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:27:52.415434 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:27:52.415440 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:27:52.415444 IP 192.168.37.20.39526 > 192.168.37.51.56700: UDP, length 36
18:27:52.415735 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:27:52.415449 IP 192.168.37.20.40539 > 192.168.37.56.56700: UDP, length 36
18:27:52.415756 IP 192.168.37.20.41900 > 192.168.37.228.56700: UDP, length 36
18:27:52.419223 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:27:52.420513 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:27:52.421813 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:27:52.422224 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:27:52.422471 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:27:52.422714 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:27:52.422975 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:27:52.423157 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:27:52.425691 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:27:52.572837 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:27:52.573157 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:28:02.415750 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:28:02.415745 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:28:02.415754 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:28:02.415760 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:28:02.415763 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:28:02.415768 IP 192.168.37.20.39526 > 192.168.37.51.56700: UDP, length 36
18:28:02.416106 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:28:02.416115 IP 192.168.37.20.51936 > 192.168.37.227.56700: UDP, length 36
18:28:02.416094 IP 192.168.37.20.40539 > 192.168.37.56.56700: UDP, length 36
18:28:02.416111 IP 192.168.37.20.51474 > 192.168.37.50.56700: UDP, length 36
18:28:02.418696 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:28:02.420186 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:28:02.420485 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:28:02.421423 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:28:02.421553 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:28:02.421742 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:28:02.422351 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:28:02.422477 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:28:02.422827 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:28:02.606230 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:28:02.607131 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:28:12.415954 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:28:12.415948 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:28:12.415958 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:28:12.415981 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:28:12.415965 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:28:12.415969 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:28:12.415972 IP 192.168.37.20.39526 > 192.168.37.51.56700: UDP, length 36
18:28:12.416265 IP 192.168.37.20.51936 > 192.168.37.227.56700: UDP, length 36
18:28:12.416269 IP 192.168.37.20.41900 > 192.168.37.228.56700: UDP, length 36
18:28:12.417592 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:28:12.418346 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:28:12.420222 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:28:12.420739 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:28:12.420930 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:28:12.421219 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:28:12.421805 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:28:12.421590 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:28:12.422173 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:28:12.439918 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:28:12.442422 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:28:22.416913 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:28:22.416895 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:28:22.416938 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:28:22.416916 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:28:22.416920 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:28:22.416926 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:28:22.417203 IP 192.168.37.20.51936 > 192.168.37.227.56700: UDP, length 36
18:28:22.421341 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:28:22.421661 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:28:22.421943 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:28:22.423670 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:28:22.424255 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:28:22.424449 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:28:22.425485 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:28:22.425634 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:28:22.426886 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:28:22.578911 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:28:22.582701 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:28:27.386679 IP 192.168.37.20.47312 > 255.255.255.255.56700: UDP, length 36
18:28:27.484671 IP 192.168.37.54.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.484874 IP 192.168.37.58.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.485057 IP 192.168.37.50.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.485389 IP 192.168.37.53.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.485647 IP 192.168.37.52.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.485928 IP 192.168.37.55.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.486980 IP 192.168.37.51.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.487135 IP 192.168.37.56.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.488493 IP 192.168.37.227.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.490593 IP 192.168.37.228.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.493390 IP 192.168.37.58.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.493841 IP 192.168.37.53.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.494027 IP 192.168.37.54.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.495159 IP 192.168.37.56.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.495399 IP 192.168.37.52.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.495683 IP 192.168.37.50.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.495841 IP 192.168.37.51.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.496015 IP 192.168.37.55.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.496950 IP 192.168.37.57.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.497098 IP 192.168.37.227.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.498440 IP 192.168.37.228.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.504567 IP 192.168.37.57.56700 > 192.168.37.20.47312: UDP, length 41
18:28:27.798039 IP 192.168.37.70.56700 > 255.255.255.255.56700: UDP, length 36
18:28:28.098372 IP 192.168.37.56.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.098526 IP 192.168.37.58.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.099490 IP 192.168.37.52.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.099917 IP 192.168.37.51.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.100631 IP 192.168.37.54.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.101824 IP 192.168.37.57.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.101960 IP 192.168.37.53.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.102883 IP 192.168.37.50.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.104090 IP 192.168.37.55.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.105113 IP 192.168.37.228.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.106094 IP 192.168.37.227.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.106251 IP 192.168.37.54.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.106955 IP 192.168.37.56.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.107436 IP 192.168.37.58.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.107937 IP 192.168.37.50.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.108117 IP 192.168.37.51.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.108524 IP 192.168.37.55.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.109090 IP 192.168.37.52.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.109742 IP 192.168.37.53.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.109973 IP 192.168.37.57.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.115401 IP 192.168.37.228.56700 > 192.168.37.70.56700: UDP, length 41
18:28:28.116121 IP 192.168.37.227.56700 > 192.168.37.70.56700: UDP, length 41
18:28:32.417831 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:28:32.417853 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:28:32.417867 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:28:32.417896 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:28:32.417872 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:28:32.418115 IP 192.168.37.20.51936 > 192.168.37.227.56700: UDP, length 36
18:28:32.417877 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:28:32.418130 IP 192.168.37.20.41900 > 192.168.37.228.56700: UDP, length 36
18:28:32.417901 IP 192.168.37.20.51474 > 192.168.37.50.56700: UDP, length 36
18:28:32.423630 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:28:32.423966 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:28:32.424258 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:28:32.424454 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:28:32.424710 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:28:32.424911 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:28:32.425897 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:28:32.426064 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:28:32.426783 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:28:32.714240 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:28:32.714665 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:28:42.418518 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:28:42.418511 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:28:42.418548 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:28:42.418526 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:28:42.418532 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:28:42.418536 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:28:42.418539 IP 192.168.37.20.39526 > 192.168.37.51.56700: UDP, length 36
18:28:42.420876 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:28:42.422157 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:28:42.422282 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:28:42.423045 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:28:42.424546 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:28:42.425339 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:28:42.425559 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:28:42.425820 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:28:42.427043 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:28:42.544076 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:28:42.545580 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
18:28:52.420594 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:28:52.420601 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:28:52.420628 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:28:52.420605 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:28:52.420612 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:28:52.420615 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:28:52.420619 IP 192.168.37.20.39526 > 192.168.37.51.56700: UDP, length 36
18:28:52.420924 IP 192.168.37.20.51936 > 192.168.37.227.56700: UDP, length 36
18:28:52.420623 IP 192.168.37.20.40539 > 192.168.37.56.56700: UDP, length 36
18:28:52.420911 IP 192.168.37.20.51474 > 192.168.37.50.56700: UDP, length 36
18:28:52.422158 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:28:52.425812 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:28:52.427114 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:28:52.427250 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:28:52.427445 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:28:52.427852 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:28:52.427996 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:28:52.429313 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:28:52.430410 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:28:52.480022 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:28:52.480733 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
^C^C
186 packets captured
205 packets received by filter
16 packets dropped by kernel
uap-BZ.5.60.9# 
uap-BZ.5.60.9# tcpdump -n -i eth0 'udp port 56700'
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
18:29:02.421635 IP 192.168.37.20.37885 > 192.168.37.52.56700: UDP, length 36
18:29:02.421625 IP 192.168.37.20.33066 > 192.168.37.55.56700: UDP, length 36
18:29:02.421640 IP 192.168.37.20.59291 > 192.168.37.53.56700: UDP, length 36
18:29:02.421679 IP 192.168.37.20.37367 > 192.168.37.54.56700: UDP, length 36
18:29:02.421651 IP 192.168.37.20.58693 > 192.168.37.58.56700: UDP, length 36
18:29:02.421658 IP 192.168.37.20.51268 > 192.168.37.57.56700: UDP, length 36
18:29:02.421664 IP 192.168.37.20.39526 > 192.168.37.51.56700: UDP, length 36
18:29:02.425847 IP 192.168.37.53.56700 > 192.168.37.20.59291: UDP, length 88
18:29:02.427385 IP 192.168.37.54.56700 > 192.168.37.20.37367: UDP, length 88
18:29:02.427907 IP 192.168.37.52.56700 > 192.168.37.20.37885: UDP, length 88
18:29:02.428612 IP 192.168.37.55.56700 > 192.168.37.20.33066: UDP, length 88
18:29:02.429588 IP 192.168.37.56.56700 > 192.168.37.20.40539: UDP, length 88
18:29:02.430072 IP 192.168.37.58.56700 > 192.168.37.20.58693: UDP, length 88
18:29:02.430527 IP 192.168.37.50.56700 > 192.168.37.20.51474: UDP, length 88
18:29:02.430905 IP 192.168.37.57.56700 > 192.168.37.20.51268: UDP, length 88
18:29:02.432371 IP 192.168.37.51.56700 > 192.168.37.20.39526: UDP, length 88
18:29:02.511120 IP 192.168.37.228.56700 > 192.168.37.20.41900: UDP, length 88
18:29:02.511926 IP 192.168.37.227.56700 > 192.168.37.20.51936: UDP, length 88
^C
18 packets captured
22 packets received by filter
4 packets dropped by kernel
uap-BZ.5.60.9#

I conclude that the AP is responding fine to the UDP requests and correctly bridging them to the wired ethernet.

sesquipedality commented 3 years ago

Aand ... it's working again, for the moment.

It's possible that a reboot of the Unifi kicked things into order (since that's the only thing I did (except renaming the AP to match its name in DNS) whilst investigating what was going on on the access point). I will keep an eye out and report if there is a further failure.

amelchio commented 3 years ago

If this is still working, I guess we can close the issue?

sesquipedality commented 3 years ago

Yes, please do close. It appears to have been a weird one off problem with the wifi AP. Thanks for your help.

amelchio commented 3 years ago

Okay, I'm glad you got it solved 👍