It still lacks access by web browser, it is less practical with the application but useful thing we see the percentage of progress and the messages during the inclusion.
exclusion is very quick.
I tried adding my Zooz Zen16 multi relay device today, with similar results to the Atom: It added without complaint as a secure device, but the relays were not controllable as such. Only by unpairing it and re-adding it as āinsecureā am I able to control the relays. Once added as āinsecureā it works properly.
When removing, I got the message asking me if I was sure I wanted to exit the process early, same as I got on the Atom2, so Iām thinking that is probably an iOS app thing, not a controller thing.
I then set up a scene using it, with the following observations (though these may be iOS app issues):
Under activation events, the individual switches are not identified, even when going into an activation event to edit it. This means that if the scene has more than one trigger, it will be very difficult, if not impossible, to edit it, as you will only know which trigger you are editing by trial and error:
When first adding actions, the actions werenāt identified at all. I was adding delay actions, and all it said was āWait for 1s and thenā. When going in to edit, it just showed a blank screen with the heading of āDevice Controlā. After exiting the scene and coming back in, however, everything shows up as expected.
All that said, once set up the scene works as expected.
One thing I was just thinking: any number of the issues I have noticed could be attributed to the iOS Vera app rather than the controller. For example, the lack of identification of the switches used as triggers in the scene seems to me to probably be an issue with the app, not the controller, since the scene does work properly (and quickly, I might add). As such, is there a way I can tell the difference, and if so where should I report the app issues?
Of course, at the end of the day, a ānormalā user probably wouldnāt differentiate the two.
Received my Ezlo Plus this afternoon and started testing according to the test plan. I did not test anything else yet.
So far all scenarios from the test plan worked without any issue.
Install and connect via Vera Mobile and via Mios app both work well.
Add, edit and remove room, OK
Add CoolCam door sensor, Ok
Door sensor works as expected
remove door sensor, Ok
Add door sensor again, OK
Add CoolCam in wall switch, OK
use CoolCam in wall switch, OK
create scene using door sensor and CoolCam in wall switch, OK
Successfully paired (and was then able to create a Scene with) the Aeon Labs MiniMote battery-powered remote. Process went very smoothly with pretty good on-screen instruction (except my remoteās pairing button is labeled JOIN, so the reference to it by another name confused me a bit).
Created a scene to respond to pressing Button 1 one time, which ran successfully on testing, and delivered expected email notification.
Just received my device this morning (surprise! Iād given up on it coming), put it onto the guest network, and successfully moved a plugin outlet onto it. This evening, Iāve noticed itās broadcasting its own wifi signal - how do i turn that off?
The Atom does that,too. When I asked, I was told it will be addressed in a future release. Iām not testing until this is fixed as I donāt need a rogue AP in my network.
Created scene using Spetu motion sensor and VOI via Google switching on kitchen lights and switching off after 5 seconds, OK
Added fibaro fgms001 multi sensor, went very smooth, OK
Reboot EzloPlus and check if all is still there, OK
Added Alexa, OK
Created scene using VOI via Alexa, OK
The scene editor is basic and is not consistent in options offered (e.g. during create scene an action can be added to inform a user while this canāt be done during edit), but this is only a first version of the scene editor. Scene editor might be a seperate topic.
After a while the battery operated Fibaro sensor fgms001 canāt be detected anymore while my cheap Spetu motion sensor still is okay. The fgsm001 shows battery level zero, NOT OK
Well, I did something stupid. I sshād in and disabled the wireless radio with uci. Except upon reboot, it gets an address on the wired port, still brings up wifi, and thatās about it (as far as I can tell). Doesnāt call home, doesnāt respond to ssh. Open to suggestions.
Its access point which is working the same way like on the Vera controllers.
Its up all of the time and ready for connection. Password is printed on the box.
