Guess December is not happening? Quite frustrating to see updates about EzloPi showing up when there are still so many things not finished on the Ezlo controller.
1 Like
ā¦Quite frustrating to see updates about EzloPi showing up when there are still so many things not finished on the Ezlo controllerā¦
I couldnāt agree more. EzloPi is nice but until you have peer LAN interoperability (i.e. Meshbots work across controller without need for the cloud meshbots, it is seriously impaired. Further the absence of a master-slave construct is a flawed design choice in my estimation. That being the Ezlo Plus is a master of all EzloPis on the same LAN.
Meanwhile updates on EzloPlus are few and far apart. Additionally there doesnāt appear to be any meaningful traction with 3rd party application development as there was with Vera. I donāt know if its because the API isnāt well published/documented and/or tools unavailable or there is no economic incentive for developers to add to the platform. Maybe Ezlo should incentivize ($$$) a few Vera app developers (of the most popular plug-ins) to port over to Ezlo if nothing more than to prime the pump on 3rd partyā¦ My vote would be Reactor, Honeywell Ademco Vista Alarm Panels with RS232 Interface, Garage Door, Honeywell WiFi Thermostats, FOSCAM HD,ā¦
I think some tougher product management calls are needed to focus the finite resources of the R&D team. The āall to everyoneā approach isnāt working since in the end it is finite resources so it becomes a dribble for everyone. 50% complete syndrome, everybody gets left unsatisfied.
EzLogic is the native rule engine. If you tell us what is it that you canāt do with EzLogic that you need to, weāll get the team on it.
we have a ātakeover moduleā that we are launching for DSC and Honeywell panels.
we have an RF Blaster we are launching that you will be able to control all RF based devices with, garages included.
we have quite a few different variations of WiFi thermostats that we will be releasing with EzloPi enabled in them.
Hello @Tim88
Weāve already released new versions of the Nest plugin and the dashboard that contain fixes and improvements. We are re-checking the use cases you reported on our setup with the latest versions. Then I can confirm that the issues are fixed.
This looks like a bug, guessing this should be the Heat/Cool mode. ezloDashboard.dashboard_heatcool
Iām curious as to why the plugin setup/configuration process is so complicated? I just added a starling hub for HomeKit support and all I had to do was log in with my google/nest account. The process was so easy and worked flawlessly and supports all of my devices including my protects. How is Starling able to do this as it looks like they are not using the standard google device access API and bonus itās also local and not cloud-based.
1 Like