search

Blueforcer / awtrix3

Custom firmware for the Ulanzi Smart Pixel clock or self made awtrix. Getting started is easy as 1-2-3
https://blueforcer.github.io/awtrix3/
Other
1.41k stars 112 forks source link

[BUG] VLANs supported? #579

Closed canoben closed 2 months ago

canoben commented 3 months ago

Bug report

Describe the bug

I configured my PixelClock initially for usage with a wireless network associated to a VLAN used by all of my IoT devices. Although I could see (and configure) the device just fine using the browser on my main network, the Home Assistant instance running on a server on the main network could not see the device. Putting the device on the main network and it is immediately recognised by HA. All my VLANs have mDNS activated.

Additional information

To Reproduce

put device on IoT VLAN -> not connection to HA put device on main VLAN -> works fine

Expected behavior

With mDNS activated, device should be seen on any network HA is running

Anybody else saw this behaviour, and if so, knows a fix?

Blueforcer commented 3 months ago

HA Discovery works the other way. AWTRIX sends a couple of Mqtt messages to the HomeAssistant broker, so HA knows which entities to create. So make sure awtrix can communicate with the mqtt broker on your main vlan.

canoben commented 3 months ago

My understanding of mDNS may very well be wrong, but this pops up in my router software when hovering over the mDNS option:

mDNS

Anyway, I created a firewall rule granting access to the Pixel Clock from the IoT VLAN to the Home Assistant instance IP address (and only that one) and it is working fine now.

Blueforcer commented 3 months ago

mDNS has nothing to do with the HA Discovery. It's a complete own proprietary "protocol" by HomeAssistant