Thanks. I ran it a few times and I’m getting the following errors:
On the device that’s been a problem - “Could not update neighbors”
On another device that is only for seasonal use - “Could not assign new route,” “Could not delete old routes,” and “Could not update neighbors.”
On a third connected device which seems to be working correctly - “Could not update neighbors”
Could the one (intentionally) offline seasonal device be affecting the mesh and preventing the problem device from connecting?
If you look in the logs, it’ll tell you what device id is giving you a problem. If it matches up to the id of that seasonal device, then there’s your problem. I’ve had ghost devices in the past cause mesh routing issues. In this case, you create a zwave device in IDE, give it that same device id, then delete it again. Run the repair and it should fix itself.
OK, I removed the device and did a few more Z-Wave Repairs. It usually finishes clean, but nothing has improved on the original device with the problem. Probably time for an exclusion…just such a PITA considering I have to fix my WebCore pistons, Alexa Routines, etc. Thanks for your help. I learned something about Z-Wave repairs
Passing along more feedback, which shouldn’t be new news, but PLEASE figure out how we can see what Automations a device is used in like we can for SmartApps. I really don’t care if it’s in the IDE or mobile app, but it’s driving me nuts not knowing now that I’ve moved everything to the new app. Tagging @jody.albritton
Not possible. We were told that it was designed to eliminate the possibility of race conditions. We were told they would take another look at it but that was several months ago.
The ST is just expensive playground… It just does not work as it supposed to do… Too much delay, too much offline. This is something you can not trust!!
Hmm. Sorry for the problems you’re having. Although not perfect, my system runs pretty much without error most of the time. Most consumer Home Automation systems are the same way.
Does anyone know what percentage of ST Customers have gotten the notification to make the switch? I’m thinking they have enough functionality for my system. A few of the custom device handlers have some different data and Rachio still doesn’t work but 80 plus others are reading data.
I was optimistic when I first saw this thread- started using the “new” app and thought it looked pretty good. After trying for some time now, I’ve concluded it’s simply far inferior to the “classic” app.
The app has seriously latency issues. Often, it takes 2-3 seconds to perform a simple action. The device pages cause the user to scroll too often to see the device attributes. At times, pages won’t even refresh. Only correction is to close app, and open again. It’s beyond ridiculous.
Yup, one of my biggest complaints. It’s slow, so slow that it’s not usable and I don’t trust what the devices say for their current state.
I’ve already moved my wife back to Classic to save my marriage, and unfortunately I’m back to using Classic 99% of the time. The only thing I use the new app for now is for SHM, and to manage Scenes and Automations, which is still painfully slow.
I wish they would turn the classic app into the ‘pro app’ even if it requires a subscription… Though I very much hate subscriptions, if it keeps the groovy idea alive I’ll accept it.
It’s going to take a very expensive subscription for this to happen. A lot of money has already been sunk to move away from Groovy, and for what seems like good reasons so far.
The first wave of very basic users has been offered the banner to switch. The group right now is users with slightly more complicated setups and only a small percentage have been offered the banner.
