OK, so I’ve found out (from CJ) that my issue with notifications not working was the result of my box and findvera.com not being properly synchronized. Findvera thought devices and users were different than my box was reporting. I screwed this up somehow, but can someone point me to info on how I keep these two in sync? I didn’t even know there was a synchronization issue. Is there a way to force them to re-sync? MCV have manually fixed my problem, but I dont’ want to hassle them again if I can fix this myself. I don’t even know how I messed it up. My search of the forum and the wiki hasn’t yielded much.
Had you tried the new UI beta. This might have caused an issue.
If CJ or whoever else you worked with at MCV was able to fix the problem, they would be the best resource to tell you how to prevent it in the future. Are they not willing to discuss it further with you?
First, no, my issues with notifications developed before the new UI although it appears it might be accentuated by downgrading from a higher version. Second, I would guess that MCV are willing to help me out about this, but I tried searching the forums and wiki first, and didn’t find much. I just want to make sure that this isn’t well trodden ground. They’ve gotten me back on line for now. Mostly I just want to make sure I don’t screw up again and waste their time. If there is a link to follow, I’m happy to do my own work and not clog the support channel. So if someone knows about the issues of syncing between vera and findvera.com I’d appreciate a link or two.
At the moment there’s no way to do a simple resynchronization of all the devices.
I’ve manually modified the json data and restarted the engine.
I’ve identified this issue happening if:
- you have your system working and make a backup on your pc
- reset your zwave network or remove and re-add some of the devices/scenes/users
- then restore the setting on your unit with a backup.