Hi all -
For those into advanced networking who want to put your Roku on a separate VLAN/subnet/network/wifi/ssid from your smartthings hub I’ve figured out how to make that work.
In Roku Settings, go to System/Advanced System Settings/Control by mobile apps/Network Access and set to Permissive.
In your router/firewall, permit traffic from ST Hub to Roku in both directions (I recommend DHCP reservations so the IP doesn’t change)
My firewall is a Fortigate, I’m not sure if the multicast-ttl-notchange setting is required or not. That setting prevents the firewall from lowering the TTL on multicast packets as I’ve read some devices send out a mutlicast with a TTL of 1 which prevents forwarding. It’s working so I"m not gonna mess with it.
Nice to see another fortinet user. Yes, the multicast-ttl-nochange is required to get mcast across vlans…tons of stuff set ttl to 1.
My roku and st hub are on my iot vlan so it just works but this is nice to know. I just spent the time to get casting from a separate vlan working the other day. Happy to share the details if someone wants it.
This is important info, so thanks to you both for sharing.
The Edge platform doesn’t allow drivers to change the TTL parameter when creating network sockets, so there is that limitation. I’ve asked SmartThings to provide that option but it’s not a priority for them.
@TAustin What is the cycle time/interval expected before the Roku driver will identify and update an IP change on a Roku device? Say the address changes from 192.168.1.34 to 192.168.1.67, all other things on the network remain the same?
Sweet! Took about 10 mins for the device to be fully functional in Smartthings on the new IP.
Thank you again for supporting these awesome drivers!
I’m doing some DHCP policy work so I can put all my Roku TVs within a specific IP range and then do some dynamic routing over a preferred ISP through the firewall but didn’t want to have to reconfigure all my Roku devices and automations in Smartthings.
@TAustin anyone else reporting issues with Roku devices intermittantly not responding to on/off commands over the last couple of days?
I’m seeing some interesting results where I have routines setup to monitor power on time of a TV and then turn it off after it exceeds a certain timeframe… typically it is after 2 or 4 hours.
What I’m seeing in multiple TVs is that the routine appears to trigger and sends the off command but that command doesn’t actually make it to the TV.
I was able to replicated it manually were intermittently, if I press the on off key on the driver, the TV doesn’t respond, but if I try again 30 seconds later, it works.
I have been having intermittent connectivity to my Roku devices. Most times they show offline. I have given them static IPs when I set them up in ST, but I don’t know what else to check to troubleshoot…let me know some ideas to keep these online.
My Roku devices are falling off too. Most, I can delete and then rescan and they are found… But, it’ll be offline again later. One particular tv, can’t get it to come back.
OK. Just making sure I didn’t need any type of Roku hub such as a TV. I read something about Roku TVs being a Roku hub. Now if I can just get it to see the cameras, that would be great.
If your Roku devices are not responding, try removing the power (cable and batteries) and the Ethernet cable from your SmartThings hub. Wait 10 seconds, then power the hub back on. Wait 30 seconds and plug the Ethernet cable back in. This worked for me with a V2 hub; it seems this old trick from the old SmartApp days still helps with the new firmware too.
I am also having my roku TVs lose connection to smartthings. The above suggestion of restarting the hub does work but it is only a temporary fix with them losing connection again later that day.
