New version of Z-Wave Sensor and Child Thermostat Mc
Name Z-Wave Sensor and Child Thermostat Mc
Added option for single or multiple mosaic of virtual child thermostat. It allows the new version 18.104.22.168 of the Android App to not fail and close with multiple mosaics, selecting by default single tile
By default, when the new version is installed, a simple mosaic is assigned with which the app will work without having to delete the virtual thermostat
New version 6 of the Z-Wave Sensor and Child Thermostat Mc driver.
To adapt the driver to the HUB firmware libraries, the LAN type Child devices are replaced by the EDGE_CHILD type.
Everything will work the same way as old version.
This improve the operation performance and facilitates future updates since it uses the resources of the default libraries of the Hub.
This update will be done manually so that each user can do it when they see fit, since the LAN-type child devices will have to be deleted and recreated as CHIL_EDGE type. There is no rush, do it when you can, everything will continue to work
HUB smart Wifi users, who have libraries lower than 45.x should not change to this new driver since their HUB firmware libraries do not support CHILD_EDGE devices. They must wait for their hub to be updated.
IMPORTANT: HOW TO UPDATE DRIVER AND NOT LOSE THE ROUTINES OF THE CHILD DEVICES:
Wait for your current installed version to be Z-Wave Sensor and Child Thermostat Mc-(OLD)
Install the new version of the driver Z-Wave Sensor and Child Thermostat Mc
The routines of the real devices are not lost nor do they have to be modified.
Procedure to facilitate the modification of child device routines:
Without deleting the child Devices, change the driver from the Z-Wave Sensor and Child Thermostat Mc-(OLD) to the new VERSION Z-Wave Sensor and Child Thermostat Mc.
The child devices created will stop working and will keep all the routines. You can rename them to easily identify them.
With the new driver: Create the new Child devices you need.
Enter to the old Child devices menu Routines: Edit every routine and add the new child device and delete the old one.
Save the edited routine, which will go to the list of the new child device.
Once all the routines have been modified, delete the old child devices.
The version of the old driver will be renamed Z-Wave Sensor and Child Thermostat Mc-(OLD) and the new one Z-Wave Sensor and Child Thermostat Mc
Driver Id 351974e8-d7de-46cb-a34f-92cc1371f80e
Name Z-Wave Sensor and Child Thermostat Mc
Package Key zwave-sensor-child-v6
@Mariano_Colmenarejo, following the steps of your excellent documentation, I’ve successfully completed the update procedure on my two thermostats and uninstalled the old driver from my hub.
N.B. I use SharpTools rules instead of SmartThings routines. Adding the new child device to an existing rule’s trigger worked just fine.
I have SharpTools rules that turn off the thermostat after a time of motion inactivity. Adding the new child device to an existing rule’s action of “setThermostatMode with argument(s): [“off”]” wouldn’t give me a thermostat mode pull-down list. I had to (easily) create a new action within the rule, then delete the old action.
thanks a lot for your edge drivers! I’ve got four Eurotronic Spirit Z-Wave Plus thermostats, that I haven’t been able to get recognized with your z-wave Thermostat driver. Could you please try to incorporated them? As far as I know they use the Standard z-wave protocol (i attached screenshots from the Manual regarding commands, sorry about the Order, the third ist the First page). I would appreciate this a lot. Would you need additional data about the device?
Cheers and a good sunday
First of all, thanks for your great work. I’ve been using your drivers and virtual thermostats for a few months. I’d like to ask a question if you don’t mind.
What is the effect of the « Select radiant floor and type » on the behavior of the thermostat?
I’ve read the information you gave for v2 of the Zibgee driver but it seems to have no effect when I try to use it. My radiant floor has a huge inertia so I’d like to configure the thermostat to start heating as soon as the temperature dips below the set point and stop heating as soon as the temperature starts to rise again but I don’t really understand how to configure both the radiant floor and the differential temperature settings to avoid a large difference between the lowest temperature and highest temperature.
Thanks very much for the detailed reply. In the meantime, I have understood why I thought the radiant floor setting had no effect. It seems the Info Panel does not always refresh immediately. Sometimes I need to exit the tile and open it again to get the Info Panel information updated.
I will try new settings as per your suggestion and will get back to you.
The virtual thermostat has independent temperature compensation adjustment in its profile.
The real device depends on the model.
The zwave usually have the adjustment with some configuration parameter, so the stock profiles do not usually have compensation adjustment.
The zigbee all have compensation in the profile
I think that nothing would happen if the temperature and humidity compensation is added to the profile, since the compensation is not done by the driver, it is done on the platform together with the change of units from °C to °F
If you tell me which device it is, I’ll add it as soon as I can.
So as you kindly suggested I tried to set the differential temperature to 0.2 degrees with my radiant floor. It behaves better than 0.5, thank you. It overshoots the set point by around 0.6 degrees but I think it is ok. FYI, heating control in my house is tricky fir 2 reasons:
the water-based radiant floor has a lot of inertia
the house is extremely well insulated
As a consequence, the inertia is not really bad with regards to the « heating start » level because the temperature dips very slowly. So even if the heating system is slow to produce heat, it’s not a big deal as the temperature will not decrease much in the meantime. On the contrary, it is a bigger problem for the « heating stop » level. Once the floor gets warm, the temperature will keep rising for a long time even in case heating is switched off soon after the temperature starts rising.
By the way I noticed a behavior that is a bit annoying. I use the « Lock » function when I want to force a specific mode (e.g. Eco or Away) that will not be changed by my cyclic time-based routines. However, I noticed that sometimes the thermostats get « magically » unlocked without any human or routine action. Do you have an idea about how it could happen? Could it be linked to driver updates?