I have 2 Vera’s at different locations. If i log in via mios.com both Vera’s are listed and i can go to both dashboards without any problems. However if i use the automator.app it lists both devices, but only connects to one of them. It keeps on trying to connect to the second one, but returns “disconnected” all the time, except when i’m on that devices local network (then automator.app connects directly).
Everything worked fine until a week ago (so regardless of the network i’m on, it would connect to both Vera’s correctly via mios.com). I noticed one thing that points me to a possible cause, but i don’t know how to fix it. If i login with a browser via mios.com, the problem device is using fwd4.mios.com. If i lookup the details in automator.app the problem device is using fwd2.mios.com (and fwd1 as backup).
Rebooting Vera, routers, etc doesn’t help. Also, this behavior is identical on all ios devices.
BTW - i’ve just been testing with eControl Lite and manually configured a system using fwd4.mios.com. Looks like that’s indeed the issue with automator, 'cause this works fine. Although logging into cp.mios.com automatically sends me to fwd4, the ipad app uses fwd2 as primary and fwd as backup.
Noticed another strange behavior. I purchased Vera 1 for location B (vacation home) and set it up at location A (home address) giving it the name “vacation address”. I liked it so much i decided to purchase another Vera. I changed the name of the first unit to “home address” and setup the new unit with name “vacation address”. When i login via mios.com all iphones show the two different names. However if i use the ipad it lists the 2 units both with name “vacation address”.
[quote=“wavandam, post:5, topic:173386”]BTW - i’ve just been testing with eControl Lite and manually configured a system using fwd4.mios.com. Looks like that’s indeed the issue with automator, 'cause this works fine. Although logging into cp.mios.com automatically sends me to fwd4, the ipad app uses fwd2 as primary and fwd as backup.
Noticed another strange behavior. I purchased Vera 1 for location B (vacation home) and set it up at location A (home address) giving it the name “vacation address”. I liked it so much i decided to purchase another Vera. I changed the name of the first unit to “home address” and setup the new unit with name “vacation address”. When i login via mios.com all iphones show the two different names. However if i use the ipad it lists the 2 units both with name “vacation address”.
Rg,
Wim[/quote]
Can you perform the following to test something? In the app, while you are not local (wifi) to the unit), change your mios.com username to something bogus, hit the “done” button. The units should disappear from the system list. Then go back into settings and change your username back to the correct name. This should fix, I believe, both the fwd4.mios.com issue and the name of hte system not being updated.
[quote=“automator.app, post:7, topic:173386”][quote=“wavandam, post:5, topic:173386”]BTW - i’ve just been testing with eControl Lite and manually configured a system using fwd4.mios.com. Looks like that’s indeed the issue with automator, 'cause this works fine. Although logging into cp.mios.com automatically sends me to fwd4, the ipad app uses fwd2 as primary and fwd as backup.
Noticed another strange behavior. I purchased Vera 1 for location B (vacation home) and set it up at location A (home address) giving it the name “vacation address”. I liked it so much i decided to purchase another Vera. I changed the name of the first unit to “home address” and setup the new unit with name “vacation address”. When i login via mios.com all iphones show the two different names. However if i use the ipad it lists the 2 units both with name “vacation address”.
Rg,
Wim[/quote]
Can you perform the following to test something? In the app, while you are not local (wifi) to the unit), change your mios.com username to something bogus, hit the “done” button. The units should disappear from the system list. Then go back into settings and change your username back to the correct name. This should fix, I believe, both the fwd4.mios.com issue and the name of hte system not being updated.[/quote]
Thanks, indeed this fixed the connection issue. Automator now correctly connects to both units, regardless of my network location! Also the names of both units are now presented correctly on the iPad.
[quote=“automator.app, post:7, topic:173386”][quote=“wavandam, post:5, topic:173386”]BTW - i’ve just been testing with eControl Lite and manually configured a system using fwd4.mios.com. Looks like that’s indeed the issue with automator, 'cause this works fine. Although logging into cp.mios.com automatically sends me to fwd4, the ipad app uses fwd2 as primary and fwd as backup.
Noticed another strange behavior. I purchased Vera 1 for location B (vacation home) and set it up at location A (home address) giving it the name “vacation address”. I liked it so much i decided to purchase another Vera. I changed the name of the first unit to “home address” and setup the new unit with name “vacation address”. When i login via mios.com all iphones show the two different names. However if i use the ipad it lists the 2 units both with name “vacation address”.
Rg,
Wim[/quote]
Can you perform the following to test something? In the app, while you are not local (wifi) to the unit), change your mios.com username to something bogus, hit the “done” button. The units should disappear from the system list. Then go back into settings and change your username back to the correct name. This should fix, I believe, both the fwd4.mios.com issue and the name of hte system not being updated.[/quote]
So the situation is that Automator is preserving some information it initially discovered about a mios system and not updating that information should it change. It seems that MCV has added new forward servers and moved existing units to use the new server(s). Since Automator.app was “caching” the original list of forward servers and not updating this information when it changed, it did not properly find the new servers to use. A clean install or changing your mios username had the effect of Automator.app discovering the list of forward servers for the first time.
A related bug prevented changes to a system’s name once it had been “discovered” in Automator from occurring.
A bug fix will be submitted to Apple but since there is a short term work around I am going to put a few other things in it before submitting.
[quote=“automator.app, post:10, topic:173386”]So the situation is that Automator is preserving some information it initially discovered about a mios system and not updating that information should it change. It seems that MCV has added new forward servers and moved existing units to use the new server(s). Since Automator.app was “caching” the original list of forward servers and not updating this information when it changed, it did not properly find the new servers to use. A clean install or changing your mios username had the effect of Automator.app discovering the list of forward servers for the first time.
A related bug prevented changes to a system’s name once it had been “discovered” in Automator from occurring.
A bug fix will be submitted to Apple but since there is a short term work around I am going to put a few other things in it before submitting.
Thanks for the reports![/quote]
I was having the same issue on my iPhone and this fixed it too. Normally I’m connected at home on the WiFi so never had issues but went to turn some lights off while at a restaurant and couldn’t connect.
I have tried the username solution as well as delete and install and have had no luck.
Has there been any more work on resolving this issue? Other than this I really like this app but this issue makes it fairly useless.
[quote=“typedoss, post:12, topic:173386”]I have tried the username solution as well as delete and install and have had no luck.
Has there been any more work on resolving this issue? Other than this I really like this app but this issue makes it fairly useless.[/quote]
Can you please e-mail me at support [AT] automatorapp.com. For everyone else the username and/or fresh install has resolved any known connection issues.
FYI, a new release to handle the new servers is in Apple’s queue but they have been shut down for the holidays. However, if the fresh install option doesn’t resolve it you may have a different issue. E-mailing me is the best way to get 1 on 1 help.