I use Pico remotes to control Lutron light switches in different buildings on my property. Each building is connected wirelessly on the same network. So I use Hub Mesh and Lutron Pro Hubs to accomplish this. I can use a Pico remote to turn a light switch on in a building that is way out of range for the Pico because it's going through my network.
I'm going to have to use a separate ISP in one of the buildings and set up a different network. I won't be able to use Hub link because they'll be on different local networks.
Does anyone have experience using a Pico to control a function on a non-local Hubitat hub using VPN or port forwarding?
If you only have a single device to worry about, I'd consider just making a rule with a cloud endpoint trigger on the "remote" hub, then create some automation that hits this endpoint on the "local" hub (the one with the Pico). If you want to share a lot of devices in a Hub Link-esque fashion, then either Hub Connect (third party but fairly easy to set up) or Maker API (built in but a bit more work and also involves endpoints you'd need to figure out and manually set up to hit on your local hub) might be a better fit.
If you already have a site-to-site VPN, then Hub Link should be able to work that way, or any of the above with local instead of cloud endpoints. Normally I'd suggest Hub Mesh (you must have set this up a while back?), but across different networks, even with a VPN, I'd say it's unlikely its built-in mDNS-based discovery will work for you.
So you will need a a pro hub at the very least in the new location for the pico to talk to. DO NOT USE PORT FORWARDING. You can use an always on VPN to have hubitat talk to the pro hub at the new location, but there will be lag. Hopefully not too bad. If you put a hubitat in the new location as well you could use Hub connect.
He’s talking about using a pico in one location to trigger automatons in a different location. If that’s correct, he doesn’t need a Caseta Pro hub at the remote location.
