update on network issue..
A couple of months ago, I mentioned that it appeared the networking scheme had changed in a house: my processor is on 192.168.10.70 but when I connected to the house's wifi like I had done for the last 5 years at least, I couldn't find the processor and found that the laptop was using the 192.168.50.x scheme. I wasn't sure whether it was a VLAN or the AV guy had changed the whole house and just forgot to let me know and somehow his remote control was still working. Oh and he was off the job after let's just say some "Drama".
Today I actually got to talk to him and according to him, the wireless network is set up to 192.168.50.x but the wired devices like my lutron processor is set up to 192.168.10.x so as long as I manually type in the lutron's processor address, it SHOULD still find it. Obviously it didn't... So my question is why?
Having been on this forum for a few years now, one of the most common gripes with both HWQS and Ra2 has been processors not showing up on the designer software. When it's brought up, the blame game begins: First with the victim blaming with things like "Did you use WIFI?! That's not recommended even though it's almost 2021 and pretty much every IOT device uses it with no issues!". Then comes the blame game on Windows and the router, etc. and we're asked to turn off all the firewalls, and connect directly, etc.
So before we get in the blame game, if everything is set up correctly in the network, is there a reason why one subnet can't talk to another subnet? I'm pretty sure they're using a Ubiquiti network there and I'm assuming the guy who set it up knows what he's doing. Everything else in the house seems to talk to each other but since HWQS relies on the mythical multicast, is this setup preventing multicast from working?
I haven't had a chance to go back to the house but I COULD find the network closet and connect via wired ethernet and then end up in the same subnet but am trying to get some ideas of what situations cause the processor to not be found.