Did support for Generic IO devices ever get added ? I’ve tried adding one but it doesn’t then appear in the Vera mobile app connected to the Ezlo Plus controller.
Door contact sensors and Motion sensors on the Ezlo Plus hub via the Vera to Ezlo bridge, don’t have Armed / Disarmed controls in the new Ezlo web GUI for some reason I can’t figure out.
This is a “real” door contact sensor I have paired on my Ezlo Hub, as you can see in their new web GUI it has a disarmed / armed tile.
However all my emulated / virtual door contact sensors on the Ezlo Plus, none of them have any disarmed / armed controls.
Any thoughts why this might be ?
I have tried removing this “Front Door” contact sensor from the Ezlo plus hub, by editing the VeraBridge.json file and unregistering / registering the plugin etc in SSH.
And then adding back in again the “Front Door” contact sensor etc, however this makes no difference to how the device looks in the Ezlo web GUI, I am just going to start calling it UI8 I think
I have not looked at this for a couple of months as the API is still lacking functions to make a real plugin. This is also why the armed function is not working as the Lua API does not have functions to control a device armed status (oddly enough the hub API does). I asked for it to be added, but has not yet been.
The generic_io device is not added. Will be once I get the time and reason to look at Ezlo plugins again.
This is a virtual switch device created directly on the Ezlo Plus hub, using the Ezlo supported method with their Online API Tool. As you can see its just a switch tile and nothing else.
However virtual switch devices I have created myself on the Vera Plus and used your bridge for.
Those virtual switch devices also have KWH tiles, which I’d rather not see in the UI1 web GUI.
By the looks of things it seems that the tile for current Wattage is incorrectly labeled with KWh in the web GUI. That is for sure a bug for Ezlo to fix. It also looks it creates a tile for every item a device has. You would need to look using the API tool what items a device has. If that does not match, the web GUI is the one in error.
For a switch device the VeraBridge creates a device with those three items yes. At this moment the bridge does not query the Vera for the states/variables a device really has. The items are created based on a physical device. Maybe something for a future release.
thanks for a great plugin. Wonder if you can help with a query I’m trying to resolve?
I’m looking to pick up a virtual switch device from my VeraPlus and to pull the latest value into my EzloPlus. Do you support virtual switches from either VirtualSwitch or Switchboard? If so, could you advise on the necessary device details to include in the VeraBridge.json file?
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.
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.
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.
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?