New Plugin: Ezlo Bridge

ElCid · July 28, 2020, 7:47pm

PM sent. I would add that the sensor has not included correctly into Ezlo plus, as it is a door sensor as well, but it only shows as a temp sensor. The temp displays correctly in Ezlo but in OpenLuup it shows as 2000.

reneboer · July 29, 2020, 9:28am

Hi @eonnet,

Can you do an update and see if it works now?

Cheers Rene

eonnet · August 10, 2020, 7:19am

Hello @reneboer, sorry for long delay i was optimizing my IT hardware and moving everything on one server with dockers so i finaly installed OpenLuup on docker and connected ezlo plus without problems to openluup. But… i have some strange things showing.

i have 2 fibaro dimmers that are working fine in Vera App but in open luup on one dimmer it shows Load error state : unknown on the second dimmer it shows Hw state : unknown
on the motion sensor zigbee that i have it does not report the states but in the variables it shows DisplayLine1 Motion : true and DisplayLine1 Motion : false
Temperature sensor does not show any value in the interface but there is value in variable.
the zigbee thermostat does not have any interface and controls but i think that the support for thermostat is limited… variables are ok and are all there.

reneboer · August 10, 2020, 8:19am

Hi @eonnet,

Can you go to the API tool Ezlo API Tool, select your Ezlo controller and send me a PM with the out put of hub.device.list and hub.items.list? Maybe these zigbee devices show a little different than the zwave ones.

Cheers Rene

reneboer · August 12, 2020, 12:14pm

Hi,

An updated version (1.03) of the EzloBridge is available to update on openLuup. Updates include:

Added logging, variables, json and utils modules.
Log level is a user setting.
Removed rooms, scenes and device ID removed from stored mapping.
Changes SID/device type to rboer.
Added periodic full pull of devices and items for full status refresh.
Display Can’t Detect Device message if hub shows as unreachable.
Handle broken device status. (Message shows as Cannot reach or broken)
Fixed issue for unwanted State variables created for Ezlo device items we want to ignore.
Fixed duplicate creation of CurrentTemperature.
Display Device Broken message if hub shows as broken
Able to reconnect if VM running openLuup is restarted without needing a luup reload.
Changed items mapping to generic sensor to item name and not all the CurrentLevel.
Better HVAC support.
Fix for SetArmed action as Ezlo changed value name.
Fix for scalar type variables.
Fix for action mapping functions.
Some logging fixes.

You will have to remove the current bridge device and then re-install the plugin unless you have installed the development version prior.

Keep the feedback coming.

Cheers Rene

eonnet · August 12, 2020, 12:38pm

Hi Rene,

i reinstalled the ezlo bridge and recieved the following error:
8/12/2020, 2:37:12 PM #6:Ezlo Bridge:[string "L_EzloBridge.lua"]:1958: attempt to index field 'data' (a userdata value) the controller is stuck on Connecting to Ezlo Hub… Getting tokens from Ezlo Portal

reneboer · August 12, 2020, 4:14pm

Hi eonnet,

I cannot reproduce this. Can you check the settings?

Also set the log level to debug and let me know what is shown in the log file.

Cheers Rene

reneboer · August 13, 2020, 6:54pm

Hi,

Found a quite serious bug in V1.03 it that it did not add the required device number offset (10000, or 20000, etc.). Just pushed out V1.04 with this fixed.

Hope no one messed up a key openLuup system. Lesson to learn. Make a copy of the user_data.json before installing any new plugins.

Cheers Rene

ElCid · August 13, 2020, 7:45pm

I do a Auto back up daily, i save 30 days of backups.
Thanks for the heads up. No issues here, hope every one else is ok to.

eonnet · August 14, 2020, 6:33am

Now i’m receiving the following error:

× 14/08/2020, 08:32:26 #4:Ezlo Bridge:[string “L_EzloBridge.lua”]:1960: attempt to index field ‘data’ (a userdata value)

And on ezlo bridge it displays
Connecting to Ezlo Hub…

Getting tokens from Ezlo Portal

reneboer · August 14, 2020, 8:48am

Hi @eonnet,

Found the issue. I test with just Ezlo hubs on the account. In your case you have both Vera and Ezlo. I found that mixing them gives me grief and is especially not good for the WAF.

Anyhow, I just uploaded 1.05 that has this fixed.

Cheers Rene

eonnet · August 14, 2020, 9:25am

everything is ok now, thanks.

reneboer · August 19, 2020, 9:24am

Hi,

Updated the github to V1.06 with a fix for numeric values on the Athom hubs. No changes for Linux based.

Cheers Rene

anon37769099 · September 14, 2020, 11:51am

I just installed this, and its stuck on “getting devices”.

2020-09-14 12:43:28.823   openLuup.context_switch::  ERROR: [dev #60] [string "L_EzloBridge.lua"]:2521: attempt to perform arithmetic on upvalue 'lastFullStatusUpdate' (a nil value)
2020-09-14 12:43:28.823   luup.delay_callback:: function: 0x55e5c2170f10 ERROR: [string "L_EzloBridge.lua"]:2521: attempt to perform arithmetic on upvalue 'lastFullStatusUpdate' (a nil value)

Only one generic z-wave on the ezlo now…

reneboer · September 14, 2020, 2:43pm

Hi @anon37769099,

Just pushed an update on gitub that should fix this. Please let me know.

Cheers Rene

anon37769099 · September 15, 2020, 10:46am

The error is gone, but it still seems to stop at “Getting devices”. I removed the one device connected to it (heat-it 8-switch doesnt work well with EzloPlus), but it should still show “0 devices 0 scenes” right?

luup log:

2020-09-15 11:39:00.921   openLuup.scheduler:: [60] Ezlo Bridge device startup
2020-09-15 11:39:00.925   luup_log:60: var.GetSet: empty data value for variable IncludeDevices
2020-09-15 11:39:00.925   luup_log:60: var.GetSet: empty data value for variable ExcludeDevices
2020-09-15 11:39:00.926   luup.variable_set:: 60.urn:upnp-org:serviceId:altui1.DisplayLine1 was: Getting devices and scenes... now: Connecting to Ezlo Hub... #hooks:0
2020-09-15 11:39:00.926   luup.variable_set:: 60.urn:upnp-org:serviceId:altui1.DisplayLine2 was: [x.x.x.x] now: Opening web-socket to Hub. #hooks:0
2020-09-15 11:39:01.009   luup.variable_set:: 60.urn:upnp-org:serviceId:altui1.DisplayLine1 was:Connecting to Ezlo Hub... now: Getting devices and scenes... #hooks:0
2020-09-15 11:39:01.010   luup.variable_set:: 60.urn:upnp-org:serviceId:altui1.DisplayLine2 was:Opening web-socket to Hub. now: [x.x.x.x] #hooks:0
2020-09-15 11:39:01.010   luup.set_failure:: status = 0
2020-09-15 11:39:01.010   luup.variable_set:: 60.urn:micasaverde-om:serviceId:HaDevice1.CommFailure was: 0 now: 0 #hooks:0
2020-09-15 11:39:01.010   luup.variable_set:: 60.urn:micasaverde-com:serviceId:HaDevice1.CommFailureTime was: 0 now: 0 #hooks:0
2020-09-15 11:39:01.010   openLuup.scheduler:: [60] Ezlo Bridge device startup completed: status=true, msg=OK, name=EzloBridge

reneboer · September 15, 2020, 4:39pm

Hi @anon37769099,

Can you set the log level to debug in the plugin settings? Maybe that gives more clues. I have not tried with no devices and scenes so it could be that.

Cheers Rene

anon37769099 · September 15, 2020, 5:55pm

log level is at 1, set it to 0?

reneboer · September 16, 2020, 1:07pm

It is in the settings tab for the plugin, last drop down.

anon37769099 · September 16, 2020, 1:35pm

Ok, so:
is starts up fine, then 2 seconds later:

2020-09-16 14:28:14.041   luup_log:60: EzloBridge_debug: MessageHandler false, receiver error: closed
2020-09-16 14:28:14.041   luup_log:60: EzloBridge_debug: MessageHandler, opcode = false? receiver error: closed

4 seconds later:

2020-09-16 14:28:18.236   luup_log:60: EzloBridge_debug: MessageHandler false, receiver error: closed
2020-09-16 14:28:18.236   luup_log:60: EzloBridge_debug: MessageHandler, opcode = false? receiver error: closed
2020-09-16 14:28:18.237   luup_log:60: EzloBridge_warning: EzloBridge_Async_WebSocket_Reciever. Lost connection to Hub, closed. Try reconnect in 30 seconds.