@SchippieNL 

Your vlans are on different subnets? You appear to have it configured correctly, assuming you blocked the IoT from Home.  Typically your permit ACL allowing Home to contact IoT would allow the IoT to respond. If not you would need another permit ACL to allow specific IoT devices, on specific ports, to address specific devices on the Home vlan. 

Also chromecast and apple devices use mDNS to locate and communicate with other like devices on the network.  If the devices are on different subnets (Home-IoT) the mDNS broadcast will not repeat on the other subnets. This requires MDNS relay/repeater which is not currently available on the Omada routers. 

@1207 yeah I've got mine configured on different VLAN's what would you suggest I'd do? Just wait for a future update that fixes it or re-configure all the subnets to make this work? And if so how would you advice I'd configure it?

@SchippieNL 

You can either put all the devices on the same vlan (or allow access) for now and wait for TP-link to implement a mDNS repeater/reflector on the ER605, or run Avahi on a NAS or other server.

"Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite." It is a light weight application that runs on Linux platforms and only requires one ethernet connection to the network.

TP-link is updating the router firmware by the end of this month, but there is no indication it will include mDNS.

@KLX 

This video just shows basic configuration and does not address mDNS issues with apple and chromecast devices, but it is a good video.

@KLX most of my configuration comes from this video. Sadly the problems with IOT devices remain.