You can turn on / off the cameras via the Alexa integration. I have a routine that will turn off the inside cameras when my Apple iPhones (via the homekit integration) reports presence for any of the household members.
SmartThings Got's to go!!!! I'm 99% there. I just use it for the Samsung TV integration and even that's not via the bridge.
Mine is still working normally as I write this. I have a 'shoulder tapping' automation that executes every 5 minutes via HubConnect that lets me know if my ST and HE hubs can't interact with each other, and it hasn't skipped a beat. Maybe they're shutting things down on a shard by shard basis.
Like others, my Hub Connect stopped working about 9 days ago. It forced me to finally move the last of my devices. Everything is done, and now there's an empty hole where ST once stood.
Some reading this TOPIC have concluded that HubConnect is "discontinued" but that's wrong. HubConnect works as well today as it ever has between Hubitat Hubs and (via dan.t ) Homebridge.
Recent messages in this topic on SmartThings and Samsung's destruction of Groovy apps and drivers closes that one use. Hubitat to Hubitat on disparate networks is the niche left to HubConnect, and it's great at that, as always.
I got a weird one. I'm using HubConnect for its remaining (and awesome) use-case--Hubitat to Hubitat on disparate networks. Honestly it's been so rock solid I haven't touched in a year or two. I actually have two child HubConnects from my one server hub in one location connected to each of two remote hubs in another location. It's been working perfectly for awhile.
Today however I noticed (via the Device Watchdog app) that the remote hub device hadn't been updated in a few days. When I looked, sure enough the remote hub showed "Error: Instance in use by another hub". I read the conversation above in this thread where @srwhite suggested deleting the remote hub device and then Done'ing out of the server instance app. When I tried that, the remote hub device didn't recreate and the "Offline" tag on the app persists. There are no errors or warnings in the logs.
it's been almost that long since I've done it and there's only a dim and fuzzy image remaining in my brain. My 4 production hubs are all still working and I've had no need to touch the "interconnect" side of things in a very long time. The advice above is certainly the best "memory" and I'd defer to it if I get this wrong...
On the Server hub, for the remote, there's this button:
The traffic traverses Hubitat's cloud in this disparate network scenario. Not being able to converse would have me looking at the hub to cloud path, I think... both ends.
Hmm, you know what's even weirder? Even though both server and client show "offline", along with aforementioned error message, everything is working as expected functionally. Any event on one side is instantly reflected on the other. Weird.
The ability to add new "legacy" Groovy-based integrations with SmartThings was disabled in October. Existing setups would still continue to work. At the end of this year, those will stop working as the entire "legacy" Groovy backend for SmartThings is shut down. That will affect HubConnect if you had it installed and working before October. There's a whole list of the timeline for that over at the SmartThings Community.