Andy

I'm only just installing zigbee2mqtt for the first time, and ran into this error when trying to add my first device. I'm running in docker, and I see the error...

@double16 Thanks, you give me hope! However, I have tried various macvlan configurations and have had no luck. I ended up finding people with similar issues saying it had to...

@itzg Update on this... I found this line in the Dockerfile: `EXPOSE 19132/udp` I removed that and rebuilt the image, and that appears to have solved the 'docker ps' mystery....

Can you share your understanding of what the EXPOSE command does? If I'm reading the [docs](https://docs.docker.com/engine/reference/builder/#expose) correctly, it seems like it should have no effect unless you use "docker run"...

The bit I wasn't understanding was why 19132 was appearing in the "docker ps" output if it was meant to have no effect without using the -P option to docker...

I've put together a proof of concept of the idea I had. It's basically a separate container that listens for a Minecraft client ping on 19132 and responds with multiple...

The Minecraft client sends out a broadcast ping on 19132, and the pong that the servers send in response contains a 'ServerName' string that looks like this: ``` MCPE;Creative Test;419;1.16.101;0;10;11049514815015922850;Bedrock...

Yes, thankfully the Minecraft clients don't have a problem with two different pongs being returned from the same IP, and they correctly read the ports to use from each packet....

Just installed this extension and it works great (thanks!), but I'm also looking for the feature mentioned in this issue. Maybe the existing "commands" array could be for commands that...