Plugin: Bridge Vera with Ezlo: VeraBridge for Ezlo

Hi Tony,

I have not included any plugin devices and do not have time to work on this plugin any more. Ezlo is working on something they told me. No idea what/when/how though.

Cheers Rene

Switchboard specifically uses the Vera-native device types, services and variables for the virtual devices, with the intention that other integrations (specifically dashboards, Alexa, and Google Home) would not be able to tell the difference and handle them accordingly. I would think, unless @reneboer has had to do something unusual for eZLO firmware, that the bridge would just see the Switchboard virtual devices as they would any other switch or dimmer and handle them the same, without any special attention or coding.

Its working i have tried it.

Thanks, had a senior moment! Put in the wrong ip address for my VeraPlus! All working well now.

Thanks all :slight_smile:

1 Like

Sorry realize this thread is old but are there instructions on how to get access to the hub to upload the files and run the commands from the instructions on GitHub? Not quite sure how to get this installed and running.

Logging into the Ezlo controller with the root username and password.

On my Windows 10 laptop I used WinSCP application (similar to file explorer) to connect to the Ezlo hub to upload the files to the correct directory.

And I used Putty application to connect to the Ezlo controllers terminal command line to run the command(s).

1 Like

Oh same as the Vera, got it thanks!

1 Like

Just double checking the steps here. If we want to update the device mapping we have to edit and re-upload the VeraBridge.json and then you have Uninstall the plug-in and re-register is? How do you do the step that says to use the Ezlo API Tool?

Yeah update your json file and upload it again to the controller.

Then unregister and register the plugin with the commands.

Thats what I do.

Not sure about the API Tool step what does that say to do?

On git hub it also said to do:

Call from the Ezlo API Tool using

{ “method”: “extensions.plugin.run”, “id”: “12345”, “params”: { “script”: “HUB:VeraBridge/scripts/reset_plugin” } }

between the unregister and re-register step, to “reset” the plug-in, I wasn’t sure if that was required. Sounds like you just have to unregister and re-register and that above step is only for if you are trying to completely uninstall the plug-in

Dont think you need to do that. I never have.

Not sure if @reneboer is still around.

I was trying to create a new Meshbot rule for a motion sensor that is bridged from my Vera Plus to the Ezlo Plus. But the trigger option I wanted to use for Armed is true is not available.

I do have that option for a real motion sensor device that is paired directly to the Ezlo Plus however, as you can see in this screen shot.

Looking in the Ezlo API Tool

Lounge Motion - Bridged Device it says "security": "no"

},
        "name": "Lounge Motion",
        "parentDeviceId": "",
        "persistent": false,
        "reachable": true,
        "ready": true,
        "roomId": "61df58c2123e434bebf2091d",
        "security": "no",
        "status": "idle",
        "subcategory": "motion",
        "type": "sensor"

Hallway Motion - Real paired device is says "security": "low"

},
        "name": "Hallway Motion",
        "parentDeviceId": "",
        "persistent": false,
        "reachable": true,
        "ready": true,
        "roomId": "61f2b4e1123e431219fbc8de",
        "security": "low",
        "status": "idle",
        "subcategory": "motion",
        "type": "sensor"

Not sure what “low” means its low when the sensor is Armed or Disarmed.

On a real paired device instead of selecting “Security Threat” on the Capability drop down menu, you can just select “Motion” instead and then choose your “Armed State”

I cannot do this for a bridge motion sensor however, I just have Motion is true or false, no option for Armed State.

Hi @cw-kid

Still here as I’m still using my Vera’s, but turned off my ezlo hub as I had no real use for it. So sorry, but I cannot help.

Cheers Rene

Yes I understand Rene.

However for the record I did a little more digging with a dev at Ezlo and this is what he said about, why the bridged sensor devices don’t have “armed state” functionality on the Ezlo controller / system.

"It should be like that.

1- The device you are showing is not a security device in our terms. It has no “security_threat” item onboard.
Only such devices receive device.armed flag.

The device.armed flag is assigned by the House Modes system. It’s not a part of the device schema and cannot be added by a Lua plugin developer.

So, you can ask the plugin author to add the “security_treat”.item to devices that need to have armed/disarmed functionality.

2- As you already know, only “controllable” items can appear in a scene’s Actions part. For that, the item.hasSetter field should be true.

So, this is also a plugin’s responsibility.
Also, there is a field show: true, but I’m not sure if it will affect this UI or not. As far as I heard, items with the show: false were hidden from item lists in mobile UIs."

And this is what I sent him from the Online API tool for one of my bridged Motion Sensor devices.

Device ID information:

{
        "_id": "61f08f2a123e431284c14065",
        "batteryPowered": true,
        "category": "security_sensor",
        "deviceTypeId": "VeraBridge_motion_sensor",
        "gatewayId": "61df48bb123e431276092984",
        "info": {
          "manufacturer": "Rene Boer",
          "model": "VeraBridge",
          "remote_device": "Plus_677"
        },
        "name": "Kitchen Motion",
        "parentDeviceId": "",
        "persistent": false,
        "reachable": true,
        "ready": true,
        "roomId": "61df58da123e434bebf2091f",
        "security": "no",
        "status": "idle",
        "subcategory": "motion",
        "type": "sensor"

That devices “Items”

{
  "api": "1.0",
  "error": null,
  "id": "1687794547591",
  "method": "hub.items.list",
  "result": {
    "items": [
      {
        "_id": "61f08f2a123e431284c14066",
        "deviceId": "61f08f2a123e431284c14065",
        "hasGetter": true,
        "hasSetter": false,
        "name": "battery",
        "show": true,
        "value": 100,
        "valueFormatted": "100",
        "valueType": "int"
      },
      {
        "_id": "61f08f2a123e431284c14067",
        "deviceId": "61f08f2a123e431284c14065",
        "hasGetter": true,
        "hasSetter": false,
        "name": "motion",
        "show": true,
        "value": false,
        "valueFormatted": "false",
        "valueType": "bool"
      }
    ]
  },
  "sender": {
    "conn_id": "3addd73b-79a9-4f63-8303-2b44b18223c6",
    "type": "ui"
  }
}

In comparison here is a REAL motion sensor actually paired to the Ezlo Plus controller .

Device ID information:

{
        "_id": "61f0a01a123e431284c14134",
        "armed": false,
        "batteryPowered": true,
        "category": "security_sensor",
        "deviceTypeId": "520_512_6",
        "firmware": [
          {
            "id": "us.520.1536.0",
            "version": "1.6"
          }
        ],
        "gatewayId": "5eda80680000001515e27a51",
        "info": {
          "firmware.stack": "4.38",
          "hardware": "2",
          "manufacturer": "Hank",
          "model": "HKZW-MS01",
          "protocol": "zwave",
          "zwave.node": "3",
          "zwave.smartstart": "no"
        },
        "name": "Masterbed Motion",
        "parentDeviceId": "",
        "persistent": false,
        "reachable": true,
        "ready": true,
        "roomId": "61f08c15123e431284c13fbf",
        "security": "no",
        "status": "idle",
        "subcategory": "motion",
        "type": "sensor"
      },

That devices “Items”

api: "1.0"
error: null
id: "1687952584915"
method: "hub.items.list"
result:
items:
0:
_id: "61f0a01a123e431284c14135"
deviceId: "61f0a01a123e431284c14134"
enum: Array[3] ["unknown","no_tampering_cover","tampering_cover"]
hasGetter: true
hasSetter: false
name: "tampering_cover_alarm"
show: true
value: "no_tampering_cover"
valueFormatted: "no_tampering_cover"
valueType: "token"
1:
_id: "61f0a01a123e431284c14136"
deviceId: "61f0a01a123e431284c14134"
hasGetter: true
hasSetter: false
name: "battery"
show: true
value: 5
valueFormatted: "5"
valueType: "int"
2:
_id: "61f0a01a123e431284c14137"
deviceId: "61f0a01a123e431284c14134"
hasGetter: true
hasSetter: false
name: "motion"
show: true
value: false
valueFormatted: "false"
valueType: "bool"
3:
_id: "61f0a01a123e431284c14138"
deviceId: "61f0a01a123e431284c14134"
hasGetter: true
hasSetter: true
name: "security_threat"
show: true
value: false
valueFormatted: "false"
valueType: "bool"

Its number 3 with “security_threat” that seems to be missing from the bridged devices.

Hi cw,

I remember something that, at the time, there was no api call to arm or disarm a device. No idea if that has changed. Ezlo asked if they could take over the plugin a while ago and I gave my ok. I would ask them to make any updates needed. I am not supporting it anymore.

Cheers Rene

1 Like