Personally, I prefer better security provided it isn’t inconvenient. Without a token, it would be wise for users to be able to restrict requests to certain local netmasks.
With security enabled, it would be useful to be able to set token expiration durations and to revoke an authentication token via the portal or API or better yet, both. In other words, provide more standard controls for the authentication tokens.
Fibaro RGBW controller 1 & 2 - FGRGBW-441 & FGRGBW-442 respectively.
I paired an FGRGBW-441 as a generic z-wave device on the latest ezlo RTOS firmware. The device is a 4-channel (MOSFET) device with power metering. There seems to be an extra(?) child device?
{
"method": "hub.devices.list",
"result": {
"devices": [
{
"_id": "ZE8F5D86",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "Z2598D039",
"category": "power_meter",
"subcategory": "",
"gatewayId": "zwave",
"name": "Power Level Sensor",
"type": "sensor",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
},
{
"_id": "Z2598D039",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "",
"category": "dimmable_light",
"subcategory": "dimmable_colored",
"gatewayId": "zwave",
"name": "Fibaro RGBW Controller",
"type": "light.bulb",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
},
{
"_id": "Z90DB804C",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "Z2598D039",
"category": "dimmable_light",
"subcategory": "dimmable_colored",
"gatewayId": "zwave",
"name": "Fibaro RGBW Controller 1",
"type": "light.bulb",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
},
{
"_id": "Z3BB5DDD6",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "Z2598D039",
"category": "dimmable_light",
"subcategory": "dimmable_colored",
"gatewayId": "zwave",
"name": "Fibaro RGBW Controller 2",
"type": "light.bulb",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
},
{
"_id": "Z39EA101",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "Z2598D039",
"category": "dimmable_light",
"subcategory": "dimmable_colored",
"gatewayId": "zwave",
"name": "Fibaro RGBW Controller 3",
"type": "light.bulb",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
},
{
"_id": "Z4B0C5AB7",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "Z2598D039",
"category": "dimmable_light",
"subcategory": "dimmable_colored",
"gatewayId": "zwave",
"name": "Fibaro RGBW Controller 4",
"type": "light.bulb",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
},
{
"_id": "Z35AFEF5",
"deviceTypeId": "271_2304_8192",
"parentDeviceId": "Z2598D039",
"category": "dimmable_light",
"subcategory": "dimmable_colored",
"gatewayId": "zwave",
"name": "Fibaro RGBW Controller 5",
"type": "light.bulb",
"batteryPowered": false,
"reachable": true,
"persistent": false,
"serviceNotification": false,
"roomId": "",
"security": "no",
"ready": true,
"status": "idle"
}
]
},
"error": null,
"id": "4x8fawjeod6",
"sender": {
"conn_id": "<redacted>",
"type": "ui"
}
}
I have the zooz rgbw controller (which is manufactured by fibaro) on my homeseer and it has 5 devices too. I believe it is a master plus red, green, blue, white.
If master is off, the rest turn off. I believe is master is on, the others resume their prior state. I have had it installed for a whopping 28 hours so I am still experimenting.
Hi @ezlo @melih @MCakan
Try to integrate the devices that we ask of you on this forum, please raise them to the top of the stack of your integration list.
Fibaro smart implant and other fibaro, aeotec doorbell6 , qubino, etc…
Best regards
Hi @Pitt13, Yes we are still following this post and trying to prioritize items from all requests. As you know we are aiming to integrate everything with our platform 
Btw I can also say for now that 8 of top 15 devices to integrate are Fibaro ones.
I think Fibaro as a whole should be a top priority rather than particular individual devices of theirs.
Same for Aeotec, Everspring and Qubino those are the main four Z-Wave devices for the EU markets, along with these other manufacturers here.
Also Harmony hubs the 3rd party plugin needs to be ported over to Ezlo platform…
I’d also like to see support for Hikvision IP cameras integration into Ezlo hub for virtual motion sensors. There was an old Vera plugin that after some tweaks I was able to get working.
And when can we expect support for Philips Hue Bridge and Hue lights? In Vera we currently have the Philips Hue 2 plugin and the AltHue plugin.
AltHue is better and supports more Philips Hue and other Zigbee devices like the bulbs from IKEA.
I tried to add one Zigbee device so far directly to the Ezlo Plus a Xiaomi Aqara temp / humidity sensor but it did not work or detect the device.
I totally agree. However we are forced to look into this device per device because sometimes it is very fast to integrate a particular device and sometimes we find lots of issues we need to solve, report, etc particularly just for that device. That also effects the order/priority of that particular device.
I have tried Hubitat with new zwave700chip for a while. Fibaro has become a Hugh problem since they have changed som multicast bla bal ( dont exactly now what). so all fibaro drivers suck and dev team says they can’t do much its a silicon labs problem… So now I’m trying better luck with Shellys who are not in this world fast… Still have my VP for some old 433mhz and follow the dev of ezlo plus…/MAttias
zigbee:
visonic MCT-340e sensor (zigbee) (works with vera plus)
honywel smoke detektor (xiaomi/zigbee) (Works with vera plus)
Bosch motion sensor (zigbbe works with vera plus)
lan
Harman Kardon Omni serie speakers (relly like to se this integritet
wled service
Home assistant (so ezlo kan be controld from HA)
Emby
Unifi
cloud:
volvo on cal
amazon music
Ring
Wyze camera
Neos Camera
Please add support for sending sensor data from the Ezlo hub to a Time Series database such as InfluxDB.
There is a current 3rd party InfluxDB plugin for Vera you can see here.
I am using Grafana to visualise the data from Vera, here is what I have setup so far.
Or better yet add native support in Ezlo for time series logging and graphing.
HVAC
Door / Window Sensors
Battery Levels
Glances Hardware Monitoring
And embedded in to Imperihome app as Kiosk mode:
Home Assistant
Home Assistant?
How does Home Assistant currently work with Vera?
Presumably your Z-Wave devices are paired with Vera and Home Assistant sends HTTP commands to Vera’s local API to then control those devices and also read back the devices current status for feedback / 2 way comms?
Or is it a deeper integration at the Z-Wave chip level?
If the HTTP API then unfortunately Home Assistant and every other 3rd party integration into the Vera system out there now, will be broken when using the new Ezlo platform as they have “shot themselves in the foot” and changed the entire structure of how the HTTP server API works.
So all 3rd party apps and platforms that can currently talk to Vera will break for the new Ezlo hubs.
It’s up to those 3rd parties to rewrite their integrations in to Ezlo hub using the new API.
FEATURE REQUEST
Decent Push Notifications and notifications management / search functions.
I’ve always used 3rd party notifications integrations for Vera as the native inbuilt notification system was always sub standard and needs improving.
I’m currently using Telegram messenger app and my Vera scenes and logic actions send out notification commands to Telegram.
As a feature request I’d like to see decent push notifications and a decent dedicated area on the Mios app to view and search for them via keyword and time and date etc.
When @melih took over the reigns we discussed metrics and data. No roadmap on that I have ever seen. The focus is on device integrations and the new firmware.
I believe Home Assistant leverages this library for Vera integration.
In terms of current connectivity, yes Z-Wave devices connected to Vera which Home Assistant relay commands back and forth.
As for methods, I would assume HTTP api, MQTT, etc. would be options, but that is beyond my area of expertise.
What about an easy to use heating management? Today you have to create many scenes for “set thermostat xy temperature at night”, “set thermostat xy temperature at morning”, “set thermostat xy temperature when away”, … and if you want to use a window sensor or use an external temperature sensor you have to write lua scripts.
There should be a separate category for heating where you can define heating zones, assign your themostats, temperature sensors and window contacts to that zones and then mark in a timeline what temperature should be at what time of the day (and a second mark in timeline when in holiday mode).
Lidl supermarket in the UK have just launched a range of cheap Zigbee products
More cheap Zigbee devices.
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules
