If you change the behavior you must delete the device and then restart the plugin so it gets recreated. It will not update a device category yet. I think the latest FW does support that so it is time for an update.
Also note that the supported_behaviours is just for documentation and has not functional propose.
I used this to connect an Ezlo Plus to two z-wave plugin outlets on a Vera Plus, and noticed a couple things. 1) it takes about 10 seconds to turn on/off 2) regular mentions in ha-luad.log of āERROR: plugin has no permissions to use the required module lpegā
The ten seconds can happen as you have a couple of devices at work. If you mean the physical device switches ten seconds after you change its virtual equivalent in the Vera App it looks a bit long. If you are looking at the GUI there will be some delay as the Ezlo plugin polls the Vera every five seconds.
The error message has no effect on the plugin. It just signals that the Ezlo FW is still missing some modules to make it perform faster.
Right - i click the MiOS app (Vera app doesnāt work with my Ezlo Plus recently), thereās a log line, 10 seconds pass, thereās a bunch of more log lines, and the light turns on/off.
If I set the setpoint of this virtual thermostat device in the Vera app, it does send the command OK to the real thermostat device on the production Vera Plus and the set point is changed OK accordingly.
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?