Agree with @csstup but one additional point of clarification… the hub will need an update to date/time otherwise the scheduled automations may not fire on time. You can setup a local NTP server and there are community solutions to update the hub time as well. This question is probably best on the Hubitat Community.
Some features of the mobile app require Internet access (to get back to your hub when you are off your local network). But the mobile app isn’t the primary way to interact with the hub.
The hub admin interface and control dashboards are via a local webserver hosted on the hub.
The mobile app can access the hub on a local network without the Internet.
If you want to admin the hub remotely you can either setup your own VPN, or you can add the Remote Admin addon. It will let you access the hub remotely either thru the mobile app or browser. I subscribe to it and it’s worth the couple bucks a month.
If I have a z-wave device setup with “groovy”, if I switch over to the new Edge drives and it doesn’t work out, can I switch back to the groovy handler? Thanks.
If you are using a custom device handler you can switch back. If you are using a stock device handler and they have switched over to Edge then you will not be able to. If you provide the brand/model, someone may be able to provide a definite answer,
Question is - why would you want to switch back with less than 8 weeks left using groovy
During the transition period for the next few weeks, maybe, at least to a custom groovy handler that you already had on your account. But once the free Groovy cloud is shut down, it’s gone, and you won’t be able to switch back.
It’s for a FortrezZ MIMOlite, which I was using to send a notification for my smoke detectors. I copied the handler from somewhere else, but then I published it for myself if that sounds right.
I normally don’t keep up on Smartthings that much, but I have a Zooz Zen17 that I’m trying to add for some garage control. And when I went to add that I discovered I couldn’t add things to Groovy anymore. So, I was contemplating on abandoning the groovy stuff and switching things over to Edge. Homeseer leak sensors are the other hardware that’s in handlers.
Clarification: how would you switch back if you have to delete the custom device handler in order to get the new edge drivers to take priority over the legacy custom device handler?
Have a similar situation I’m trying to solve for across multiple hubs using the same custom device handler.
at this point, you are kinda trapped. You can switch to Edge but you can’t switch back to a custom device handler that you would need to remove in order to get the Edge Driver. In 2 weeks (tentative), groovy should go away unless they modify the end date.
2 posts were split to a new topic: Need help with after groovy options
Also the ability to pause/unpause a rule.
Add variables too?
When is RULES API going into effect? I want to have better notification options like when Door opens, push notify me, but only once every xxx minutes.
Maybe I’m a little confused, but how do I activate and use the Rules API on ST? I’m been using Routines, after the disabling of Webcore.
You can use the rules api now.
Github rules docs and examples
Once I got postman set up I was able to replicate all of my webcore stuff, plus add a few new automations which I had been thinking of doing but never got around to.
Start with the smartthings cli. Having that set up makes postman easier, for me.
Routines is a GUI for the Rules API. So is Smart Lighting.
Routines are slightly different, in my experience. For example, routines sunrise/sunset work dynamically, sunrise/sunset only pick up the time when the rule is published (is static) in rules api.
Rules support if/then/else, with nested if/then/else. Routines are if/then.
Just because the API supports it doesn’t mean the GUI does
So for clarification, the Rules API is the “engine” that supports the Routines (which is the GUI). So if I’m still seeing lack of options on Routines setup, I just know this is the best we got natively using ST routines at this moment?
That is a bug which I believe only appears in cloud executing Rules. It broke in about September 2021 and hasn’t been fixed yet.