@d_j_w 

Is a hardware controller needed for this to work or do these even have the capability?

No need a hardware controller. TP-Link EAP can forward the Multicast packets though there is no such option to enable it(enabled from factory default). I don't use IoT devices in different networks across VLANs, without known more your actual purpose and network setup, sorry I don't know how to help you. Perhaps you may contact TP-Link support for further guidance. 

@Yannie Sorry, it's for Chromecast and my Google Home. I want to be able to allow different VLANs to be able to cast to those devices. I had it working before with the Meraki but it could be a setting I changed on my switch. Thanks, I'll reach out to them!

@d_j_w do you have your problem solved ?

have same issue after migrated EAP225 to v4 Omada controlled and upgraded EAP225 firmware to 2.20.1.

My wireless devices (TVs ant laptops)  doesn't see DLNA server on same subnet. It was working with Omada controller v3 and same EAP225

When I simply reconnect TV to same subnet but with ethernet cable TV see and can play from DLNA server

@Fae thanks

will try to install new version on Win desktop since today I use Omada Controller (software version) on QNAP NAS and latest pkg I can get here is 4.1.5

my EAP225 are already on newest version EAP225(EU)_V3_5.0.0 Build 20200918

I dont expect that somethiong will change with controller upgrade since it is mostly offlice. I use it just when I make changes

@limis 

I have not, I've had to focus on other things. My plan was to setup the Meraki AP and test. It's possible a misconfiguration on my Dell switch.

@d_j_w @limis Did either of you find a solution to this problem?

@atvking 

Not yet. I think there is another update, but still having to be on the same SSID to cast.