Beta feedback Ezlo Plus

I did that, and after a while it started pulsing yellow, not red.
Still can’t get in, hangs on “please wait”, og “something unexpected happened”.

I reported this behaviour to our devs. @Oleh will get back to you with the next steps.

Does anybody else noticed that there is not an option "what to do when this mode is selected?

here is the house mode on vera firmware

here is the house mode on ezlo firmware

i’m using iOS

1 Like

Any news about fixing motion sensors trip state in UI for iOS app? still does not show if the sensor is tripped or not.

Yes, I also noticed it. It’s a very userful setting missing.

I kind of went production with my Plus, I bought a lot of IKEA Trådfri bulbs and they are all working perfectly.

Got really tired of the sunrise/sunset issue and missing presets for modes though so thanks to @therealdb Virtual HTTP Devices I integrated them in my Vera that now does all the scheduling.
As a bonus my Vera is connected to HomeKit so I now got full Apple Home support for my Ezlo Plus devices :smiley:

A few issues I worked around:
@Oleh IKEA Trådfri Wireless control outlet shows as dimmable, I’m almost certain it’s only on/off switches.
My INNR bulb refuses to be part of the Trådfri mesh network and has really short range so has to be close to the hub.

EDIT: The limit of 20 scenes also forced me to move the logic to Vera. What’s up with that? Is it an upcoming subscription feature?

1 Like

Glad it’s useful :smiley: Let me know if you need something special, I’ve recently integrated new stuff and I’ve no TODOs on the backlog :wink:

1 Like

Just noticed by coinsidence that the problem was the local connection, i can get in if im not at the wifi…

I put the ezlo plus in production environment, and for now the results are mixed.

  1. The speed is much better than Vera
  2. the scenes are hit and miss.
  • Simple scene when you open a door turn on light after 2 minutes turn off light, sometimes it does not fire.
  • Another scene when light is on send a http command to another system same thing sometimes it does not complete.
  • Also i have scene where 5 lights are turned on and a scene where the same 5 lights are turned off, only the first light on the scene is turned on or off, with other lights nothing happens.
  1. Gui for motion sensor does not work on iOS
  2. VOI is not working
  3. Dimming the light is not fluent, you put the light to 50% and when you release it it goes back to 0 than to 50, (this is only in the app) the light it self goes to 50%
  4. Fibaro Double switch does not report W to second channel.

This is for now.

What happend with the bug tracking system i know that some of the bugs that i reported just now are maybe reported previously for sure the motion sensor for ios was reported by me couple of months ago but nothing happens, i feel like everybody from ezlo is on vacation. on the forum only few community members are active and trying to do something with the platform and from ezlo side they add one new future once a month or once every two months and with this tempo i hope that my grandchild will be able to enjoy the ezlo plus as fully functional device with all the promises from March :slight_smile:

3 Likes

More feedback for further use as a production system…when its working its working fast but that “when” is very important :slight_smile:

All of the zwave devices that i included in ezlo stopped responding and behaving strangly, i had devices that are off they were showed on in the app and vice versa

Kitchen light shown on and in fact its off as you can see from W consumption

Same here with the hallway light

After waiting for 10 minutes it started to work for 1 minute and managed to click some of the lights and they got stuck again now the dish light was actualy off and the app showed on and kitchen was on as you can se from W consumption and the app showed off

Same here with the hallway

I thought that maybe i had too much devices on the ezlo because beside the 6 zwave devices i had installed rene’s plugin and bridged vera devices to ezlo arround 30 and unnistalled the plugin rebooted the controller and it started to work again.

After 1 hour same story with only 6 zwave devices and arround 20 virtual sensors which are triggered via http most of them door sensors and couple of motion sensors. Because it was a bed time for my kid there was no movement in the area where motion sensors were or minimal movement.

Rebooted the controller and now its working but i dont know for how long.

P.S when i press the lights while they were stuck they were not responsive only way to turn on or off the lights was through the switch but the state in the app didnt change

You were brave!

I’ve seen the issues you described about the device state being incorrect in the app.

On the Android app I have to either pull down from the top to refresh it.

Or leave the devices list and go to another area of the app and then back in to the devices list area and then the devices show their correct state

BTW I have 80 virtual devices on the Ezlo Plus via the Vera bridge.

Hi @eonnet,
thanks for the description.
Did you have a chance to check our online API tool ?
Just wanted to ask you, next time you see this behaviour, can you send several request from API tool, not from the app.
You need to send hub.items.list and hub,devices.list requests and send the results to us.
Also sending you couple instructions what we can do with SSH.

Yes i’m using the api tool, i will send the requests via the api tool and send you the results.

Cant send you to response via message

Body is limited to 32000 characters; you entered 143873.

Give me you email.

Well i had to try it in more dynamic environment i put the lights that i used most in automations so i can see the behaviour, at the moment the automations are faster than vera, in vera often i get retrying … bla bla bla but here while its working is ok :slight_smile:
Will see i will keep it up couple of more days and i will get back to vera again if this continue.

1 Like

Received it and checking, thanks.

Initial setup: Time zones are typically listed by UTC offset not by alphabetical, it may be a personal opinion but I find that a much more intuitive approach. The search feature worked well enough, it is how I found my time zone, but it could be better. The search currently requires an exact match such that "America/ " finds zero results because there is a space after the /; A fuzzy search would be easier for users to use.

After selecting a time zone and renaming device the user presses save. The information seems to save, since there is briefly a progress wheel on the screen but it would be a good idea to then exit that screen so that the user is assured that the process completed.

1 Like

Device setup: Inovelli LZW36 – Fan and Light switch (https://inovelli.com/red-series-fan-light-switch-z-wave)

I used the QR code feature which worked well, I gave it a name and assigned it to ‘Kids room’. The app reported that the device had been included. When I looked for it in the Devices tab it was not there. I assume that the controller was restarting or reloading the Lua engine but unlike the web UI there is nothing in the app to indicate this. For a new user this could leave them believing something went wrong. I tried adding it again and the controller correctly gave me a message that it had already been added even though it still did not show up in the device tab. It took more than 5min (less than 10min) for the device to show up. I suggest changing the message from ‘your device was added’ to “Your device is being added and will be available in about 5min”.

Once the switch showed up (switch plus two child devices) they showed up in the “no room” group and not in the “Kids room” where I had assigned it/them. I was able to rename all them as “Kids Switch”, “Kids Light” and “Kids fan”.

When controlled from the physical device, the child devices do not update their status. The app has no way (that I see) to force a poll of the device but even left for over an hour the child devices did not update. The “kids switch” does seem to support instant updates.

When I turned off each child device both the light and the fan turned off but the toggle in the app was set to “on” and the slide bars were set to 53% and 51%. I tried the off toggle again and this time the UI reported the correct “off” and 0% for each.

I set some parameters on “Kids Switch” and found that the changes were reflected on the physical device virtually instantly. Assigning a name and a description, the overall parameter interface is much better than the Web UI on Vera Plus.

As nice as the parameter interface is the app lacks any insight into the device settings. Trying to troubleshoot is difficult without things like the last poll time/success or commands like poll now.

In the web UI I can ‘open’ a device and see an ON button and an OFF button. With this I can send an off command to a device that is actually ON but is being reported in the UI as OFF. Without these buttons and only using the toggle in the app I have to turn a device ON in order to turn it OFF if the status is not synced properly.

Overall there are things that could be improved or corrected but the major issue I see with the LZW36 switch is that the child devices are not being updated for any status change. This makes the switch largely unusable.

Hi,

I am not able to include the Z-wave.me WallC-S wall controller. On several attempts try as generic device (as it is not on the supported list) it typically fails to even start the interview. Once it got a little bit further. The inclusion fails at the 5 sec mark. See bits of the ha-zwaved.log

2020-11-10 14:06:41.216052 INFO : Disabling Smart Start Listen mode.
2020-11-10 14:06:47.891619 INFO : znet: start add node (node id: 20)
2020-11-10 14:06:47.892165 INFO : nodeCreate: nodeCreate, nodeId: 20
2020-11-10 14:06:48.343553 INFO : znet: add node success (node id: 20)
2020-11-10 14:06:48.343918 WARN : Unexpected interview progress step 4
2020-11-10 14:06:48.404753 INFO : znet: application node report (node id: 20)
2020-11-10 14:06:49.071262 INFO : znet: command version report: nodeId: 20, CC: 0x5E, version: 2
2020-11-10 14:06:49.394116 INFO : znet: command version report: nodeId: 20, CC: 0x86, version: 2
2020-11-10 14:06:49.717557 INFO : znet: command version report: nodeId: 20, CC: 0x72, version: 1
2020-11-10 14:06:50.451944 INFO : znet: command version report: nodeId: 20, CC: 0x70, version: 1
2020-11-10 14:06:50.775872 INFO : znet: command version report: nodeId: 20, CC: 0x85, version: 2
2020-11-10 14:06:51.098743 INFO : znet: command version report: nodeId: 20, CC: 0x8E, version: 2
2020-11-10 14:06:51.421486 INFO : znet: command version report: nodeId: 20, CC: 0x80, version: 1
2020-11-10 14:06:51.745112 INFO : znet: command version report: nodeId: 20, CC: 0x84, version: 2
2020-11-10 14:06:52.068096 INFO : znet: command version report: nodeId: 20, CC: 0x59, version: 1
2020-11-10 14:06:57.155472 ERROR: SendDataFailNoAck  node_id = 20
2020-11-10 14:06:57.162006 ERROR: Fail on getting cc 0x5b version, fail 1
2020-11-10 14:06:57.162353 ERROR: znet: command version report for node err: -7, nodeId: 20
2020-11-10 14:06:57.162543 ERROR: znet: Interview for node 20 failed
2020-11-10 14:06:57.162748 INFO : znet: activateMode Monitoring handler
2020-11-10 14:06:57.162916 INFO : Enabling Smart Start Listen mode.
.....
.....
2020-11-10 14:28:23.670478 INFO : znet: activateMode Include handler
2020-11-10 14:28:23.670806 INFO : Disabling Smart Start Listen mode.
2020-11-10 14:28:32.363388 INFO : znet: start add node (node id: 23)
2020-11-10 14:28:32.364057 INFO : nodeCreate: nodeCreate, nodeId: 23
2020-11-10 14:28:36.596377 ERROR: SendDataFailNoAck  node_id = 23
2020-11-10 14:28:42.493945 INFO : znet: add node success (node id: 23)
2020-11-10 14:28:49.205923 ERROR: znet: application node update notification  fail. Error no = -1
2020-11-10 14:28:49.206222 ERROR: znet: Interview for node 0 failed
2020-11-10 14:28:49.206458 INFO : znet: activateMode Monitoring handler
2020-11-10 14:28:49.206618 INFO : Enabling Smart Start Listen mode.
2020-11-10 14:28:50.435405 ERROR: SendDataFailNoAck  node_id = 23
2020-11-10 14:28:50.443659 ERROR: znet: command version report for node err: -7, nodeId: 23

Cheers Rene

With the new update. It seems to have stopped me changing the temperature on the TRVs I have

It lets me turn them on and off, but temperature does not get sent.

It’s does however get received from the device if i change it on the TRV itself.

Eurotronic Spirit