Hopefully you don’t have to many devices, routines modes, rules to recreate. Glad to heat st is replacing it for you though. Good luck!
yeah, I don’t have a very complex environment at the moment, but was working towards that, so I will have some recreation to deal with, but shouldn’t be too difficult.
I have to tell you, as someone that just went through a complete system rebuild, is really not that bad… If you prepare.
Take screen shots of either each page of each apps setup.
Or
Take a screen shot of the api page showing all of your apps by name.
That will help dramatically in the rebuild process.
If you have a Minimote your device exclusion will be amazingly fast.
Start the rebuild with the devices closest to the hub, and work your way out. Do a Zwave repair after about every ten or so device adds.
Same with the zigbee devices.
When you start revising your apps you’re going to find that note that you know more about how it all works, your logic prices will be different.
I managed to streamline the majority of my automations, and actually made them better.
Don’t get in a rush… Be patient…
Do all of your prep work before the new hub arrives.
Good luck
Try port forwarding the following ports to your hub.
- 11111
- 37
- 443
We need “line of sight” on these ports to get the update to happen.
I’m having the same problem as Guy with a rule and unfortunately the DB change doesn’t seem to have resolved it.
1 Like
Concur - I still can’t remove the offending rule in either the app or the IDE.
I just got another ‘your network is having issues’ red popup in the app, whilst sitting next to my 5Ghz Wifi router with full bars, and 125Mbps down, 5Mbps up (measured by speedtest)…
I’ll continue to check for the dreaded ‘undeclaredThrowable’ error in other places in the UI, but, clearly, this DB migration didn’t fix the stuck rule issue - I was hoping that since others have been seeing undeclaredThrowable errors, that ST had a bead on what was causing this… @slagle, thoughts? I almost PM’d you, but this message came out before I got to it, so I figured I’d put it here.
Thanks.
I just tried this, with a reboot… no luck… also tried putting smartthings into DMZ and rebooted… should it at least attempt for an update on start up?
I see nothing in the events during startup beside pings, hubinfo and register
Bug where Set Level v2 during local smart lightning was not being set appears to be fixed.
I do NOT see this mentioned in the release notes.
Was a fix for this bug actually included in this firmware release?
Can someone confirm this?
1 Like
This should of been fixed in the last firmware push actually.
I believe it was fixed according to this thread. I gave up on the dimmer level using smart lighting and went with rule machines because it worked on me GE dimmers.
Funnily enough I can actually confirm this too, last night we got back home from work and my outside lights were correctly set at 10% which is what the SmartApp has always been set to do but never worked.
It even alternates correctly, I have another SmartApp set to make them 100% when the garage door opens or if there is motion outside and then go back down to 10% after, works perfectly!
Tim, asked me to do the same. Ports are forwarded, not sure how long it may take to attempt an upgrade. Powered off, removed batteries, powered back on after a wait (without batteries for now as it was getting to be a PITA). As of 20 mins, no upgrade.
I cannot log into the app at all. I have reset every thing, rebooted everything and I get “internet connection issue, please try again”. Any advice? Everything worked prior to the update today.
Login should be good now! 
2 Likes
All is back up and running for me
2 Likes
Yep, things are working again…
… and so that awesome little red banner
@slagle When is the banner issue going to be taken care of?
1 Like