Recently purchased a new Vera3 to upgrade my existing Vera1. I am still experimenting with the Vera3, and only have two Schlage locks, one light, and some Virtual Switches on it. The rest of my stuff is still on my Vera1, which is on a separate ZWave network. I am also experimenting with the AutoVera application.
So far I am only using AutoVera Scenes, and AutoVera Device Info. And I got them working (good stuff). Got up the next morning, and when I went to play with the tasker code some more, discovered that AutoVera is no longer seeing the Vera3. Trying to do an AutoVera “Device Info” operation causes AutoVera to abort with a bad pointer. Running the AutoVera application through the Android launch icon shows that AutoVera still seees the Vera1, but does not see the Vera3. I have multiple Android devices, the Vera3 has disappeared on all of them. Refresing the Vera devices has no effect.
Access to the Vera3 is done through my Linksys router. The Wifi on the Vera3 has been turned off. I use a fixed IP address for the Vera3, utilizing the router to assign a specific IP address based on the Vera3’s MAC address.
The Vera3 is still fully functional. I am able to access the Vera3 through the Home.GetVera.com interface. The Vera3 is running UI6. The Vera3 scenes and triggers are working correctly, as well as my LUA code.
I have tried rebooting the Android devices, and rebooting Vera3 both by the reboot command and by power cycling the Vera3. I also tried de-installing and re-installing the AutoVera app on one of my Android devices. I had installed the AutoVera plug-in on the Vera3. I de-installed it as well. AutoVera is still not seeing the Vera3.
Anyone else see this? Any suggestions on what to try next?