I created an account on cp.mios.com and can add devices and create scenes. But for some reason I can’t get my Vera3 to connect to my MIOS account. My Vera3 isn’t detected. Any help would be appreciated. Thanks.
Is this a new or newly upgraded Vera? Do you know if it is running UI5(blue themed home screen) or UI6(green themed home screen)?
If you are using UI6, you need to create the account at https://home.getvera.com
Same issue here. UI5 in my case. I am using the correct cp.mios.com with UI5. Opened a ticket, but so far no response. I’ll post here if they get it working.
Ok just to update. Tech support contacted me and had me open up port 232 on my router. This seems to at least let my iPhone app see the Vera3 inside my house. Something that had not worked before. However, outside my home network I still cannot see the system.
I have since noticed another issue which I think may be contributing to the problem. The log in from the web UI to cp.mios.com has a stay logged in timing function. A drop down with various periods from 15 minutes to I believe a month. What I have noticed is that the system is not honoring this drop down. No matter what time you select the system logs out in 15 minutes. I am very suspicious that this is in fact the major cause of my problem at this point now that I have the port opened.
Begs the question this is like the 3rd setting that the UI just doesn’t seem to honor? What’s up with that since apparently this one and especially the deactivate scene from a controller are pretty important functions. The needed settings appear in the drop downs, they just don’t seem to do anything.
Yeah! Hopefully final update. Tech Support had to force the unit to report to their servers. Short version, with out an opened port 232, the unit gave up trying to phone home and something had to be done to restart.
So first, forward port 232 to your unit assuming you aren’t using Vera3 as you home router. Then if that doesn’t work, you will need to contact Tech Support so they can do something from their end.
It’s impossible for me to know what the real issue was in @airic499’s case. Anything is theoretically possible. My guess is that portforwarding port 232(Vera uses it for SSH tunnels) was a hamfisted method for overcoming a cheap router’s TCP session timeout cutting off Vera’s tunnels. But, that is a WAG.
However, let me state for the umpteenth time; you should not ever portforward to your Vera. Portforwarding to Vera is a gaping security hole that is NOT needed for Vera to function! Normal operating conditions for Vera utilize only outbound connections.
If my previous guess as to the issue was correct, tech support should have recommended replacing the router with another brand. Do not portforward!