A few days ago there was an update of the Dynamic Dashboard to version 1.1.29. A few tiles have apparently been adjusted in design. As you can see from a few examples, some devices are being adjusted in the display.
In principle, I think it’s good if the different device types are displayed in a uniform manner. The design of the humidity and temperature sensor tiles is good: symbol at the top left, unit in the middle, description at the bottom. When offline, this is displayed at the top right. Additionally, no values instead of the last measured values and then everything is grayed out.
Smoke sensors are displayed a little differently, but also make a good impression in terms of design.
Heat sensors should be adjusted to match the smoke sensors in terms of design. The same applies to the motion detectors.
Particular attention should be paid to what happens if something is displayed in two lines in translations due to long device names or longer names. If this causes symbols or other things to shift in the tile, it no longer looks uniform. The language setting should also be consistent. Some texts are translated and in other places English is used again.
Long text, short summary:
Something is happening with the Dynamic Dashboard. A few symbols have already been renewed and standardized. Others still need to be adjusted. And: once again no changelog
By the way, devices created via the IP plugin no longer display any values.
The MeshBots on the controller can be set up to adjust the Z-Wave radiator thermostat once the required condition is met on our Ezlo Thermostat. This provides a method for integrating the Ezlo Thermostat with Z-Wave radiator thermostats, allowing for flexible and automated control through the Ezlo platform.
Regarding the “Easy Scheduling”, we will attempt to replicate the situation on our end and will report any issues we encounter.
So the temperature sensor and the temperature set on the device are transmitted to the controller via Z-Wave. Then I could use the built-in temperature sensor instead of the sensors in the radiator thermostat and set the desired temperature directly on the wall thermostat.
I created the feature request ECS-830 for “Easy Scheduling” some time ago. I could imagine it going something like this:
At the moment I can only solve this in a complicated way with lots of MeshBots:
Is the ‘roadmap’ published anywhere for users to see? Does a plan really exist or is everything ‘seat of the pants’ so to speak?
We still haven’t see the rewrite of cloud services among many, many other things.
It’s becoming very hard to stay positive as an end user. The ezlo still isn’t a viable alternative to the vera.
It would be nice to know the direction of the platform and timeframe to know whether to be searching for a different solution that will meet my/our needs.
Another month passed and we still don’t have cloud device integration geofencing integration or any of the items discussed in this thread or others.
It would be nice to know if the ezlo hardware is still on the development roadmap or is it the intent to drop ezlo development for ezlopi?
