Finally received my Atom v2 and plugged it into an always-on USB charger port. But I’m feeling a bit dense trying to follow the steps outlined in the Beta PDF (see below) to connect to the Atom.
When I open the Vera Mobile app (per Step A), I only see my existing Vera Plus and Vera Edge controllers listed.
I don’t follow at all what Step B is trying to convey, but can definitely see the ATOM_xxxxx WiFi network SSID on my Android phone’s list of nearby networks, and can connect to it easily. Yet doing so doesn’t “do anything” and re-opening the Vera Mobile app I still only see the existing Vera controllers.
Can someone please lay out the exact steps you undertook to establish your initial connection from the Vera app to the Atom? Thanks!
EDIT 1: I got a bit further by following earlier advice, to TURN OFF my phone’s WiFi, restart the Vera app (it kept not allowing me to login, so I had to briefly turn on WiFi to login), whereupon it finally showed the green (+) button in the lower-right corner which had not been present before. I clicked it and chose ATOM as my new controller.
[Why are these steps not included in the Beta PDF?]
At that point, the app instructed me to connect to the ATOM_xxxxx WiFi network, which I’ve done, BUT the app just stays on that Setup screen. Only clickable things shown on that screen are “Open Settings” and “Need Help?”; there is no “Next” button.
EDIT 2: Progress! Clicking “Open Settings” a 2nd (or was it 3rd?) time brought up a list of WiFi networks, from which I could indeed choose my home WiFi network, which seems to have coerced the remaining steps to deploy, resulting in a “Congratulations” screen with a “Start” button. Seems I’m in good shape now.
Woke up this morning to find my Atom showing “4 devices are no longer connected”. It was complaining about the GE remote - which, being a battery operated device, I wouldn’t expect to communicate much?, as well as the aeon 4-in-one sensor that I have plugged in to constant power. Somewhat oddly though, it only showed the three “child” devices of the sensor as offline, not the parent device. Also oddly, the first time I went into the failed device list, it showed the GE remote twice - Once as a “Remote Control”, and once as a “humidity sensor”. The second time I went into the list, it showed as expected.
I think Atom v2 set bad parameters to my Fgms-001 when including. I wonder if same issues hapenned with Ezlo Plus ? @Oleh what do you think of that problem ?
With the caveat that I am still testing things, and so the list might change:
Zooz ZEN16 multirelay. Shows up mostly correctly as three “lights” and a fourth “master” device (at least, that’s what I am assuming), however only the master device has an on off switch, thereby preventing me from actually controlling the individual relays:
EDIT: I just tried this device on my Vera Plus, and aside from complaining about being “unable to configure device”, it works properly there (all three switches have on-off toggles). So this device is functional on the old Vera UI7 firmware, but not on the new Ezlo firmware.
EDIT 2: I just tried this again on the atom, except adding without encryption. The first time I tried, it just went off into la-la land, with the light on the atom blinking rapidly and the versa software saying “please wait” for several minutes. After I killed the vera app and restarted, I went through the process again (having to exclude the device first), and again attempted to add it unencrypted. This time it worked, and lo and behold, all three relays now have on-off switches! So apparently this device does work, but only if added unencrypted.
Aeon 4-in-one sensor. Appeared to work correctly at first, but the “child” light, humidity, and temperature sensors are now showing “device failed to communicate”. The master (motion) sensor continues to work properly, however. So a bit of a mixed bag.
EDIT 3: After power cycling my atom, the child devices no longer show an error, however they also don’t show any values, and the battery level on all of them shows as 0% (even though the device is plugged in)
New small issue: In the scene editor, when adding devices as triggers, the device name isn’t shown, only the state. This makes it difficult to know what is actually triggering the scene, especially when multiple devices with identical state are added as triggers:
Haven’t gotten that far. I’m still stuck at the “World Map” stage, where two things have me flummoxed:
(1) The red “No Internet Connection” banner keeps popping down every few seconds (this is not a new “bug” or “feature”, since I’ve been reporting it for the past 5+ revisions of Vera Mobile), so I can’t click the uppermost part of the screen;
and,
(2) No matter how I position the “World Map” I receive a warning to “Please select a location that contains at least the country name and the zip/post/postal code.” (Which makes no sense, as I’ve clicked SAVE with the map zoomed in and out at various scales.)
Happily, I got past these obstacles by finally accessing the “Address” field (top of screen), typing my home address, and clicking SAVE. It appears to have worked, since now the screen says “Please wait… loading.”
Will edit this reply further once I get to next stage.
EDIT 1: At first, Vera Mobile app showed no sign of the newly added Atom. Logging out of app, then logging back into it, then waiting 25-30 seconds for “Controllers” screen to populate finally revealed new Atom in list.
EDIT 2: However, for quite a while all three controllers were shown as “Offline”, with red “No Internet Connection” banner incessantly popping down. Approximately 1-2 minutes later, all three controllers transitioned to “Online” so I could finally click the Atom. Success!(?)!
TEST 1: Ezlo VOI works with the Atom setup as well as it did with the Edge controller before it. Calling this a success.
@ibrewster,
thanks for your description of issues and devices behaviour.
It would be great if you write all of the issues with different devices in your setup.
I thought that’s what I just did. See the post that you just replied to. It has all of the issues with different devices in my setup, to the point that I have set up so far. Am I missing something??? Sorry!
Glad I wrote down all the steps involved in adding an Atom v2 to one’s account. I just think all those same steps should be included in the PDF so testers like me don’t have to figure them out from scratch each time. As written, the PDF is clearly too simplified (if not misleading).
For what it’s worth, the PDF instructions worked for me, as written (on iOS). Went to the controllers section, clicked to add a new controller, connected to it’s WiFi signal, came back to the vera app, and ran through the rest of the steps. Easy, peasy. Actually, it was so smooth, I don’t even remember exactly what steps I did, but I definitely didn’t have to “figure anything out”. Apparently it didn’t work quite as intended for some people though…
I would normally agree with you, except as written the PDF steps don’t even make sense (e.g. no “home router” is involved in the entire process). Other parts are unclear (e.g. “Open WiFi settings” … on what device? or in the app?).
Likewise, there’s no “Ezlo Atom” to choose from if this is your first time setting one up. Even the last sentence shown above is oversimplified because it implies having a Vera Mobile app account (which I had before today) is sufficient to “simply add” an Ezlo Atom v2 to it, rendering the instructions themselves almost circular in logic.
Guys like us might power through, but a total n00b? No way. And that’s the intended market from all indications. Hence my feedback.
I decided to add my Schlage deadbolt to the controller. I unpaired it from my Vera Edge, no issues.
The Atom did not recognize it. It partially paired once but there were no parameters or control so I deleted it and started over with no luck. I moved the Atom to an outlet that is right under the door when open, it is just around the corner from where it was (15 feet). It was able to pair it. But now the light switch that I had previously had working shows offline. (it is through the wall and a closet behind the controller.
Since I added the lock the app repeatably crashes on both startup and when I switch to devices.
On startup it sits with the spinning circle in the mode block and then crashes. However if I start Vera Mobile and go to my vera edge (it loads right away) and then switch controllers to the Atom it loads. However it still sometimes crashes when I go to the devices page.
I cannot get the devices to appear on the dashboard even though they are marked as favorites.
Okay, I have the PlugHub V2 added with devices added to the hub. I have only been able to send commands to the hub once where they actually worked. It says it is connected but no events actually get to the hub or from the hub to the app. I started with 2 devices. One switch and One dimmer. I was able during this time the hub and app were talking to get the scenes to work add, delete, function, etc. I tried to remove device from account and would not let me. I will try to remove and re-add to account again today. I will update as soon as I complete, @melih, @Ioana Thanks!
Just as some general feedback: from what I’ve seen the reliability and speed of the Atom is much improved over my Vera Plus. With the plus, I often see some delay - or even, occasionally outright failure - when a scene is triggered. So far at least the Atom V2 has responded quickly and properly to every request.
The caveat here, of course, is that I don’t have very many devices added to the Atom as of yet, nor is it (yet) capable of becoming my primary controller. Without support for my DSC security system, which drives most of my logic, the bulk of my devices can’t move over. The lack of a web interface is also limiting.
EDIT: May have spoken too soon. Just now the Atom dropped offline for no reason I could determine. If I am interpreting the blinking blue light correctly (one short flash per second), it lost connection to my wireless network. After watching it blink for several minutes without it re-connecting, I power cycled it, whereupon it came right back up within a handful of seconds.
