Looking forward to using this, but I have not yet been able to add a control. I downloaded HomeWave 2 days ago if that matters for versions.
When I started the app for the first time (iOS over wifi) it detected my VeraLite. However, when I add controls, I can’t link any devices or scenes to a new button. The “Select a scene” box opens, and the wheel keeps spinning. Haven’t been able to add/link any of my wall module dimmers either.
From my Unit Settings: I have a VeraLite with Application Version: 1.7.583. I have the Secure Your Vera box checked. My understanding is that VeraLite does not communicate via wifi…
I’m assuming I could enter my mios username/password and get it to work(?), but I’m wondering if I’m missing anything here.
I’ve not heard anyone using Secure my Vera before, and I’m actually not sure what it does to the local connection. In any case, entering your GetVera credentials in HomeWave should give you access via the remote access service, but connecting to your Vera will be slower.
My understanding is that “Secure My Vera” blocks local access to Vera. “Secure My Vera” must be disabled if you want to use HomeWave on an iOS device that is connected via WiFi to the same LAN that Vera is connected to. At least, that is what I had to do in order to get it to work. The alternative is to disable WiFi on the iOS device, and to connect to Vera over a cell data connection to the internet.
My understanding is that “Secure My Vera” blocks local access to Vera. “Secure My Vera” must be disabled if you want to use HomeWave on an iOS device that is connected via WiFi to the same LAN that Vera is connected to. At least, that is what I had to do in order to get it to work. The alternative is to disable WiFi on the iOS device, and to connect to Vera over a cell data connection to the internet.[/quote]
This is correct to a certain extent. Secure my vera forces you to use VERA servers (which needs user and password) to login into your vera.
To use homewave or any app you need to force to remote mode on that app not local. You can keep wifi on if you want (same as if your at work on wifi and trying to connect to your home vera on a different network).
Understood. But how do you force HomeWave to only connect via a cell data connection if the iOS device also has an active WiFi connection, without turning off the WiFi connection?
Understood. But how do you force HomeWave to only connect via a cell data connection if the iOS device also has an active WiFi connection, without turning off the WiFi connection?[/quote]
It doesn’t have to be on cell data connection to connect remotely to your vera.
Same example again. If you have an iphone, ipad and you go to your friends house, work, what ever and you connect to their wifi. You open homewave with wifi on. You will connect remotely to your Vera even if your phone or ipad is on a wifi network.
Secure your vera only says you can not use a local IP without a password and user to gain access. Doesn’t mean your device can not be on the same or different wifi network.
Homewave if unable to connect to your vera locally (most if not all apps try to connect locally) then when they fail switch over to remote network. In the homewave settings this time to switch over or timeout time is adjustable also if I remember right.
Interesting, thank you. So logging in will solve it.
If you’re willing to speculate… is there much value in using Secure my Vera? I’m just the kind of person who checks those things because it looks like a good idea. Let’s assume that I’m reasonably confident that my wifi password and network are secure… I don’t have any cameras set up inside the house, and can’t imagine what anybody would get from hacking into my VeraLite. Although I’ve got motion detectors to arm/disarm, the types of thieves I’m concerned with are not sophisticated enough to do hack in (and if they are I’ve got bigger problems).
In Windows it says my wifi is secured with WPA2-Personal with AES encryption.
Thanks again, I’ll try logging in and see if it feels klunky going through the web.
This hasn’t been my experience when Vera has its “Secure My Vera” feature enabled. If the iOS device is connected to the same LAN as Vera is connected to, it attempts to connect locally but then hangs. In that situation HomeWave doesn’t time out and attempt a remote connection instead.
[quote=“CasaUser, post:8, topic:187379”]Interesting, thank you. So logging in will solve it.
If you’re willing to speculate… is there much value in using Secure my Vera? I’m just the kind of person who checks those things because it looks like a good idea. Let’s assume that I’m reasonably confident that my wifi password and network are secure… I don’t have any cameras set up inside the house, and can’t imagine what anybody would get from hacking into my VeraLite. Although I’ve got motion detectors to arm/disarm, the types of thieves I’m concerned with are not sophisticated enough to do hack in (and if they are I’ve got bigger problems).
In Windows it says my wifi is secured with WPA2-Personal with AES encryption.
Thanks again, I’ll try logging in and see if it feels klunky going through the web.[/quote]
Probem is if the web is ever down, servers are down, Vera hangs up. Your stuck without any connection as you can’t get back in locally without the web and vera servers.
This very well might be the case, but that’s not what is supposed to happen. And Homewave (unlike say ImperiHome) doesn’t even have a section to input what your “home” network name is. So Homewave has no idea if your connected to the same wifi or a different wifi network on your phone. All it knows is the local IP address you have set and it will try to reach vera for a response there and if that doesn’t work then it falls over to the VERA servers after an adjustable (or preset?) amount of time.
Which raises the question… what exactly is it that HomeWave looks at to determine whether Vera is on the same local LAN as the iOS device? I suspect it is something more basic than being able to successfully login - hence the reason it doesn’t time out to a remote connection.
HomeWave takes a short (limited) time to retrieve the Discovery message from MiOS; this indicates if there are any Vera units on the same LAN. If any unit is found or the discovery process times out, it will attempt to connect to Vera using the stored IP address, using a short timeout. If the connection fails or if the incoming data fails to parse, it will switch back to Remote access.
If HomeWave doesn’t switch to Remote access on secured Veras, I suspect there is a bug in the routine that parses the incoming data. I’ll have to look into that.
Thanks all, so far it’s worked fairly quickly as long as I’m connected.
Only surprise was when returning home, I brought up the app (previously open, in the background on my phone) and there was a delay turning off the motion detectors with a scene. To test, I tried shutting down the app and re-opening, then running the scene right away. That also didn’t take. I suspect it was the delay where the app figures out if it has local access or not.
FYI I do not have the Direct to Vera option turned on in the app. It’s pretty much default settings.
I’m considering shutting off the Protect my Vera option. Seems like some of you don’t use it, and you presumably know what you’re doing…
I don’t know who you think knows what they are doing. ;D
But I don’t think many use that protect my Vera option, and I never have myself. The ones who are using it would be worried about someone hacking their wifi or network, then finding out you have a vera on the network, and being able to access it without any user or password being used.
The ones who don’t use it would be would be worried about being locked out of their own vera, if internet is down, vera servers are down or vera goes belly up. I’m also assuming you would have more lag and delay going threw there servers at all times vs. being able to go local when your home.
Best Home Automation shopping experience. Shop at Ezlo!