Interesting... Yes, following those steps, I do see data coming in, but it is spotty - probably 25% of the packets sent are seen, and of course I see the MDNS traffic from other devices. So, yes, this proves it "works" but I need to reliably use other UDP addresses and ports. Shame it doesn't seem t...

I tried the MDNS trick before joining the multicast group - in my case it made no difference. Data is still not received, but can send data to others. Very weird. I'd rather not write my own firmware to handle this, but if the AT lib won't work, and there is no source available, it looks like we wil...

Interesting... I will give that a try today. Sounds like an interesting project. I still need to get the AT firmware working over SPI. I have done all the config and it builds, but haven't tested it yet. Remoting the IP stack should be possible, but haven't tried that yet. For our project, the ESP h...

I'm also having the same problem. Using the latest AT firmware (built from current GitHub source), I am able to change the multicast group using AT+CIPSTART="UDP","228.5.6.1",6789 (tried with CIPMUX=0 and 1) but it never receives any data from others in the group - it does however transmit fine. Am ...