So I am not sure if this is the correct location for this or not but whatever since this was a project I was working on at home and it involved SmartThings to some extent we’ll go with it here.
Now to probably oh lets say 90% of the ST population this will not apply to you.
Here’s to the rest of the 10%. If you’re like me at home and you have your own home lab setup with servers and firewalls and vlans then this applies to you.
Up until recently I had 2 VLAN’s in my house. 1 for everything and 1 for the DMZ.
So I recently decided to change my firewall over from Sophos UTM to PFSense. If you’re curious why I did that PM me and I’ll let you know. So in doing so I decided that it was also a good time to slice the house up into multiple VLANs.
So we now have the following
LAN (you know just PCs)
Servers
DMZ
Management
Cameras
Kids
Connected Devices
So once I sliced it all up I then moved all of my Kodi boxes off to the connected devices because there is no reason for the FW to proxy them or filter them with squid guard so off you go to your own vlan.
Ok so you’re probably like get to the point. So here we go.
What I discovered when I initially did this is that with ST still on my regular house LAN and the Kodi devices off on their own vlan, ST will no longer talk to them. It doesn’t know how to properly utilize its gateway and just let the router take care of routing the traffic off.
So what I ended up doing was figuring out which port ST was plugged into, in my switch and I moved it off to the vlan with the rest of my connected devices so now ST is able to once again talk to Kodi as well as some other things over there like a Foscam WiFi camera.
I’m not sure if this has been brought up before or if ST staff like @slagle knew about this either.
Like I said at the beginning to most of the user community this is a moot and null issue but for those of us who go a little more on the advanced side it could be a headache when you’re like why won’t you just talk to them.