Hi,
When I manually toggle the Neo Plug on or off the controller does not pick this up. On Vera this is not an issue.
It also does not report the Wattage. There is no item listed other than the Boolean switch, no electric_meter_… device as I would expect for this type of power reporting plug.
Cheers Rene
I think you mean defect log 
Backlog sounds quiet &^%$
It sounds they are using Agile Scrum as the method to manage the software development. The backlog is the to-do list in that context.
Fair point.
Hi all,
We’ve just updated your Vera Edge controllers to latest Ezlo Linux firmware - please check the release notes here.
To get the update you need to do one of the following actions:
ssh <vera hostname or ip> reboot invokes the upgrade as well.
Hi,
The issue that manually toggling the on-off state of a Neo Power plug is not fixed. Also still no power reading. Would it make any difference to exclude and re-include?
Cheers Rene
@reneboer. The power meter reading bug that I reported a couple firmware versions ago for the Zooz power switch 2.0 hasn’t been fixed either. I’m curious, if you look at /var/log/ha-luad.log do you see anything that looks like the following?
Float value updated, node id: 2, channel id: 0, class id: 50
2020-03-13 09:27:29.365992 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/634_257_13.lua
2020-03-13 09:27:29.366988 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/generated/634_257_13.lua
2020-03-13 09:27:29.368042 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/.lua
2020-03-13 09:27:29.378235 ERROR: LuaInterpreter: Couldn't run a Lua code: [handler.update_float_value]: Item id not found by item descriptor: item name: electric_meter_watt, node id: 2, channel id: 0, class id: 0x32, tag: nil
stack traceback:
=[C]
=?
=?
(...tail calls...)
2020-03-13 09:27:29.378747 WARN : LuaAddon: a script: HUB:zwave/scripts/events/events_handling has been terminated abnormally
Reachable state was updated, node id: 2, new state: true
2020-03-13 09:27:59.340345 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/634_257_13.lua
2020-03-13 09:27:59.341348 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/generated/634_257_13.lua
2020-03-13 09:27:59.342544 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/.lua
2020-03-13 09:27:59.352846 INFO : LuaAddon: a script: HUB:zwave/scripts/events/events_handling has been executed successfully
Product Management team: pls deal with this asap.
In my case, it might be that my Zooz Zen15 v2.0 isn’t fully supported yet on the Ezlo Z-Wave stack. I see the Zen15 v1.0 but not Zen15 v2.0.
In my last communication with the Team, they asked for the Zooz firmware version but the new Ezlo Linux firmware doesn’t expose that information to end users through the interface so I asked if there was a way to get it (i.e. command-line, logging, etc.) other than excluding and including on my Vera Plus just to get the Zooz firmware version. Haven’t heard back yet.
All of that said, I’m not super worried that it hasn’t been corrected yet, I was just comparing notes with @reneboer.
Hi @reneboer @blacey - we’ve captured your reports and we’ll work on them. I’ll be back with news once I have them.
Hi @blacey,
This is a bit of what I see in that log. Some code issues not handling some exceptions it seems.
Reachable state was updated, node id: 49, new state: true
2020-03-13 16:24:26.682063 ERROR: CoreDRemoteInterface::getSingleDevice(5e5f8e9e10d0762c552f3059), exception : fail to fetch a string at such key: "type"
2020-03-13 16:24:26.682966 ERROR: LuaInterpreter: Couldn't run a Lua code: ?:-1: attempt to index a nil value
stack traceback:
=?
=?
=?
(...tail calls...)
2020-03-13 16:24:26.683449 WARN : LuaAddon: a script: HUB:zwave/scripts/events/events_handling has been terminated abnormally
2020-03-13 17:44:29.775238 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/devices_info/generated/0_0_0.lua
2020-03-13 17:44:29.778937 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/0_0_0.lua
2020-03-13 17:44:29.780116 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/generated/0_0_0.lua
2020-03-13 17:44:29.781128 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/.lua
2020-03-13 17:44:29.795689 INFO : LuaAddon: a script: HUB:zwave/scripts/set_item_value has been executed successfully
Reachable state was updated, node id: 48, new state: true
2020-03-13 17:44:29.940117 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/devices_info/generated/0_0_0.lua
2020-03-13 17:44:29.943687 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/0_0_0.lua
2020-03-13 17:44:29.944915 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/generated/0_0_0.lua
2020-03-13 17:44:29.945873 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/.lua
2020-03-13 17:44:29.956368 INFO : LuaAddon: a script: HUB:zwave/scripts/events/events_handling has been executed successfully
Value updated, node id: 48, channel id: 0, class id: 37, value: 255.0
memory_consumption: value updated 1: 18158.0
memory_consumption: value updated 2: 18243.0
2020-03-13 17:44:29.972967 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/devices_info/generated/0_0_0.lua
2020-03-13 17:44:29.976941 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/0_0_0.lua
2020-03-13 17:44:29.977953 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/generated/0_0_0.lua
2020-03-13 17:44:29.978905 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/.lua
memory_consumption: value updated 3: 61351.0
memory_consumption: value updated 4: 92088.0
2020-03-13 17:44:29.996812 INFO : LuaAddon: a script: HUB:zwave/scripts/events/events_handling has been executed successfully
Cheers Rene
Hi @blacey Thank you for your feedback, I checked with the team if there is any other way to get the Zooz FW version withouth the excluding and including it to your Vera plus but there is none. They also thought about sending an API request but it was not possible 
So is it possible for you to do an exclude and than include it back on your Vera Plus and provide us the values of ManufacturerInfo and VersionInfo fields from the device Advanced Tab. Btw can you please also provide some more details on the bugs you are experiencing (or if you have already done that can you point me to them 
) But please do this update first if you have not done already Ezlo Linux pre-Alpha for Vera Edge Update - Official Announcements - Ezlo Community
Thanks a lot
Hi @MCakan,
Good news. I excluded (via the EzloApiTool) the device and included it again (worked first time) and now it is working as expected. This is for the Neo Power plug that has a wizard.
Cheers Rene
@reneboer, thanks for comparing notes. Your log looks similar to what I am seeing but with a different root cause. I believe the firmware maps product attributes to a device-shim script and from your logs, it seems that the firmware doesn’t know about your device or have the mapping. Sounds like the team is on it so time will tell. Maybe your idea of re-including is a good one? (edited, looks like you posted positive results while I was typing) 
Did that as soon as it hit the wild and before reporting that the issue still exists.
cat /usr/lib/opkg/info/firmware-common-git_version.control
Package: firmware-common-git_version
Version: 1.0.16
Depends: libc
Section: eZLO Innovation
Architecture: ramips_24kec
Installed-Size: 4616
Description: Just firmware-common-git_version package
Absolutely. The only barrier is that in the most recent Vera Plus legacy firmware update lost a device that I need to recover/resurrect before messing with my network fabric. I’ll try to knock this off in the next day or so.
Sure - here is a region bug that I reported and still exists in 1.0.16.
And here is the one that we are discussing,
Screenshots from my V+ with the requested info are attached but it is worth noting a few observations during my exclude/include process:
Excluding the Zooz Zen15 on the Alpha firmware was fast.
Adding the Zen15 with the legacy firmware on the V+ is much slower than than the new Linux firmware on the Vera Edge. The legacy firmware has to reload the engine so the user is forced to wait for that to complete. Nice to see that is gone in the new Linux firmware.
Excluding the Zen15 with the legacy firmware on the V+ is slower because the legacy firmware has to reload the engine so the user is forced to wait.
Pairing the Zen15 on the Vera Edge running the Alpha firmware is fast and painless - no more waiting for engine reloads! I don’t know if the speed improvement is the z-wave stack re-write or the number of devices (I have far fewer on the Edge running the new Linux firmware). I’m hoping it is the new z-wave stack.
Power usage status updates are nearly instantaneous on for devices on the new Linux firmware. With the iOS app launched and displaying the Zooz device, I used tail -f /var/log/ha-luad.log to watch the events fire as I plugged and unplugged a power-consuming device. As soon as I plugged the device into the Zen15, the event log updated and the iOS App UI updated - the legacy firmware updates in a similar fashion but subjectively it feels slower.
Power usage reporting includes watts and volts on the new Linux firmware
Excluding and re-including a device on the Vera Edge increases the node number - shouldn’t the node numbers be re-used?
Excluding and re-including the Zoon Zen15 V2 on the Vera Edge enabled the power usage reporting (as @reneboer first reported), however I still see the following warnings in the log:
Float value updated, node id: 4, channel id: 0, class id: 50
2020-03-13 14:57:38.856400 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/634_257_13.lua
2020-03-13 14:57:38.857657 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/generated/634_257_13.lua
2020-03-13 14:57:38.858637 WARN : Plugin script reader: Could not find plugin file /opt/firmware/plugins/zwave/scripts/model/devices/monitoring/.lua
2020-03-13 14:57:38.876120 INFO : LuaAddon: a script: HUB:zwave/scripts/events/events_handling has been executed successfully
Thank you @blacey for this detailed answer you provided so fast. Have you applied for Atom v2 beta yet? We would like to have you also here 
Beta enrollment opened for Ezlo Atom v2 - Official Announcements - Ezlo Community
I’ll double check on that!
thanks for confirming that power usage reporting is up also in your case like @reneboer. I will look also into these warnings.
Yes, I applied yesterday
I have successfully upgraded but the unit’s Wi-Fi is on. I would like to turn it off, but none of the command line methods work. Can you provide guidance?
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules
