[ul][li]trigger devices, plugins and scenes already on Vera[/li]
[li]react to status updates from your Vera on your Android device[/li]
[li]retrieve current information from any device, scene or plugin and use in Tasker variables[/li]
[li]dynamically build menus and scenes on your Android device with information from Vera devices[/li]
[li]integrate Vera with hundreds of other Tasker plugins and Android appications[/li][/ul]
The logs indicate an issue with connectivity, either to the internet or Vera. On that same device, can you access http://LOCAL_VERA_ADDRESS:3480/data_request?id=lu_sdata via a broswer? Obviously you should be connected to the same local wifi network as Vera and input its local IP address. If you get a return from that URL, you should be able to proceed and try to authenticate AutoVera again. Ensure the username and password are being passed along as well.
Currently, AutoVera will only work remotely with UI5. If you’ve upgraded to UI6, AutoVera should work locally, however remote connections will timeout. UI version wasn’t mentioned in your post, but I thought it may be worth noting.
Yes, I was able to access the Vera using AuthomationHD and ImperiHome fine. I got diverted onto something else yesterday and stopped working on it. When I got up this morning it had found the Vera and everything was working. Go Figure
Verified the hyperlink is valid and network in working order (I’m a network engineer–it’s working). Reinstalled the app, the app on my micasaverde, and no luck. Any ideas?
Sorry you’re having trouble. I suspected that clippermiami’s issue was related to the status of MiOS servers at that time and can relay that as of right now, I am experiencing the same issue as yourself.
I hope this issue is resolved immediately, I certainly wouldn’t want it impairing your judgement of AutoVera.
If you have any further questions once you’re eventually up and running, I’ll be glad to help.
