You're welcome. Sharing is caring, right?
So imagine you go for the full-vlan-option. Which means, in an ideal world, your wifi devices reside in their own (v)LAN. Some routers (eg asus ones) do have "guest wifi" which means that these wifi devices are automatically "restricted" for WAN only (eg read emails) but NOT for LAN access (eg hack your NAS), but the same magic can happen with vlans: your devices are properly secured in their own network. Opening iDMSS app would not show anything. Which is a good thing for "visitors", but for your precious mobile device, it is ... unuseful
But there are a couple of things that you can work with:
Option 1: you define "rules" (which are meaningful routings) that (as example) your phone (and not the misses) can access FROM wifi-vlan TO IPC-vlan. And hoppa, iDMSS works as a charm. --> takes 2 minutes in an ER-X to implement
Option 2 (my preferred way): you don't define "rules", as "rules" equal "management time/maintenance" because at each time you have a new device, you need to update these damn rules. But you configure an OpenVPN server on the ER-X, and work that when connecting with profileX opens the gates to IPC-vlan.
Why is this my preferred way: you can then, all the time, everywhere on the world, keep your OpenVPN client tunnel active. ALL your traffic will be encrypted and secured, and most of all: you can access your feeds ANYTIME and EVERYWHERE. On the couch, on the plane, on the moon... The sky is the limit! But .. OpenVPN is not done in 2 minutes (okok, 5 minutes max if you know what you're doing).
So coming back to your requirements: for the TV (as it might not run an openVPN client), you have to use option 1, but for all other "smarter" devices, I'd go for #2.
Hope this helps you out!
If not.. shoot!
CC