Also if you want to be able to control these devices inbound by sending a HTTP command to your Ezlo Plus controller see items 2 & 3 on this post here.
We have asked Ezlo for a proper bug tracking and feature request system, but alas we are just using the forums. So likely lots of our feedback is being missed in the mass or threads and posts.
3 Likes
Maybe if you say so. 
The other problem is I might have reported a bug or asked for a feature rrwuest, which there have been many.
And then later I forget what I asked for LOL and probably wonât know where to even find it on the forum again.
A tracking system would of been better.
1 Like
The problem is I canât see your internal system.
So I cant track the progress of bugs I have reported, to see if they are fixed or not yet?
So I am just guessing and waiting, maybe having to test the same thing several times to see if it now works as expected or not?
As no one tells me they are fixed necessarily.
Kodi for example have a public bug tracking system you can report bugs and see there progress by the Devs.
2 Likes
Just an idea on issue tracking, why donât you run a weekly report from Jira and make it available in here?
2 Likes
While opening the Vera mobile app I keep getting the message âsorry we couldnât establish a connectionâŠâ. I then have to select the Ezlo plus controller to be able to use it. After closing the app and opening it again it runs into the same message. However if I select my VeraPlus the app seems to be able to connect right away and after closing and opening the app it opens the VeraPlus dashboard right away.
Why is this different for EzloPlus??
Just to be clear: Can you confirm that there will come a web UI?
The Web GUI will have to come, there is s no way I am spending hours / weeks / months migrating to and setting up an Ezlo hub on a mobile phone app.
We have been told there will be a Web GUI before.
They have done it all the wrong way round IMHO, they should of built the Web GUI before further developing the existing Vera mobile app.
3 Likes
Yes, they already committed to it. I truly hope theyâll not leave it behind for too much, because right now itâs complicated to develop on the platform. And I hope theyâll add more dev tools into it.
1 Like
Hi @Ioana,
I included a scene controller with two buttons and used it as scenes trigger. Initially it worked fine, but after a few hours the scenes stop firing. In the ha-zwaved.log I can see the keypresses to get detected.
znet: central scene notification (node id: 8)
2020-09-12 13:59:56.103883 INFO : onUpdateSceneValue, nodeId: 8, command: 91, channelId: 0, sceneNumber: 1, value: press_1_time
znet: central scene notification (node id: 8)
2020-09-12 14:00:08.808378 INFO : onUpdateSceneValue, nodeId: 8, command: 91, channelId: 0, sceneNumber: 2, value: press_1_time
Also not seeing a broadcast message when buttons are pressed.
This is the device:
_id: "5f5b4715124c4110b0d0714e"
batteryPowered: true
category: "remote_control"
deviceTypeId: "816_768_41735"
firmware: 0:
id: "816.771.0"
version: "1.28"
gatewayId: "5eb2a5d200000014fb88839e"
info:
firmware.stack: "5.3"
hardware: "1"
manufacturer: "Unknown"
model: "Unknown"
protocol: "zwave"
name: "SK_SchakLinks"
parentDeviceId: ""
reachable: true
ready: true
roomId: "5f5b7e0c124c4110b0d07153"
security: "no"
status: "idle"
subcategory: ""
type: "device"
Update. I found that the HC2 had crashed again and I needed to reboot it. 2nd time that has happened.
Cheers Rene
Cheers Rene
The app does not let you save any parameters. Itâs letâs you add them, but the desired value and data size just do not save.
After adding the parameter if you close the Vera app and go back in to that devices Z-Wave settings again, is it then showing as being set?
I think itâs a view / refresh issue.
Hi Rene
What is the scene controller was used here ?
I mean manufacturer and p/n.
Was it crashed during scene execution or when you pushed the button on the scene controller ?
Hi Oleh,
It is a local brand, probably some OEM, ROBB smart ROB_100-002-0 (www.robbshop.nl) included insecure. This I see on the device.
deviceTypeId: â816_768_41734â,
firmware id: â816.771.0â, version: â1.28â
info firmware.stack: â5.3â, hardware: â1â
I now see that the ha-zwave.log shows the button presses and release events, but scenes rarely trigger. I need to test a bit more there, but I suspect a problem with scenes. I see a scene started broadcast, but never scene finished from the controller. Android app has trouble whit that.
The Lua demon stopped again some time at night. I had a quick and dirty http plugin polling a vera every 10 secs even through time outs. Not sure if that killed it. I redesigned that and see what happens now.
Update the Lua deamon stopped again this morning. I do still suspect the http handler.
Cheers Rene
Hi
when will we have an update please ?
Iâve noticed over the past week or so of testing out the plus that it doesnât seem to respond as quickly on a regular basis as the Atom 2. This morning, for example, there was a delay of around 7 seconds between when Alexa accepted a command, and when the device in question was activated.
Of course, in all fairness, I canât say if the delay was on the Ezlo Plus itself, or somewhere earlier in the Alexa -->cloudâ>Ezlo Plus chain - it could easily have been a delay in the Alexa processing, or on the Ezlo servers. That said, however, my gut feeling is that I am experiencing such delays more frequently with the plus than I did with the Atom. shrug
I still see a lot of cannot detect device messages on the wall plugs and battery wall controllers. I can operate the devices just fine, so it is a polling thing I presume. All these are not (yet) on the supported list and included as generic zwave (Fibaro, HeatIt). The Neo water leak that is on the supported list does not have this problem.
Cheers Rene