(EDGE Driver-Mc): Zigbee Temp Sensor and Child Thermostat Mc, Zigbee Temp Sensor with Thermostat Mc

First i will try to use it without the offset temperature and monitor it.
I use it only to monitor the temperature in a zone that has UFH system and to set the thermostat (Tado) to start the boiler. Because Tado has and old app integration, i used webcore to start it when Aqara sensor detect a specific temperature.

Temperature on my Aqara sensor is accurate, almost matches in decimal point in Fahrenheit units, with an ecobee thermostat, and about 6 different temperature sensors. I have 0 correction.
Stand same for Humidity.
I am always testing sensors by placing them next to other sensors sand comparing the values. Also old fashion mercury thermometer is there just in case.

Only one that I am comparing to AccuWeather is Atmospheric Pressure, as I don’t have other device that can do accurate measurement. Some times I have to trust internet.

A post was split to a new topic: [ST Edge] Issue with the atmospheric pressure default library

Everything OK. It works perfectly. I just had to restart HUB

1 Like

@milandjurovic71 I also compared the Aqara sensor temperature with other thermostats that I have and mine is also accurate. I use temperature offset because is a 0.3 C difference between center of the room and the place where is mounted ( i can’t move it ) . Is not a big deal, i just wanted to correct this difference with temperature offset.

(NEW RELEASE) Version 2.2 of Beta Edge Drive Zigbee Temp Sensor with Thermostat Mc

Thanks to @milandjurovic71, he had tested this new version of Driver.

Thanks to @GiacomoF, for suggesting to show atmospheric pressure in mBars to compensate for the low precision shown in kPa (10 mBar) , as could be seen in the groovy DTH.

For sensors with capability of measuring atmospheric pressure, a Custom Capability is added to display the information in mBar.

It has been tested with an Aqara Weather and Smartthings Motion sensors.

To improve the information of Battery for Aqara sensors, the xiaomi_utils.lua that @Zach_Varberg shared in github repository has been used. Thanks

The sensor models that are in Zigbee Temp Humidity Sensor Mc driver will also be added to the Zigbee Temp Sensor with Thermostat Mc driver, in case want to convert it into a sensor with thermostat functions.

As it has a custom capability, in Hubs that do not have firmware version 40.0006, they will have to do a Reboot from the Hub IDE or turn it off, only once after the first installation of a device.

Need delete app memory cache for new capability presentation.

To facilitate the update, I am going to change version 2.0 to the name Zigbee Temp Sensor and Thermostat Mc-(OLD).
I will publish the new version 2.2 with the original name Zigbee Temp Sensor and Thermostat Mc .

In this way, your driver installed will have the name with (OLD) , indicating that there is a new version available and you can install the new version with a driver change whenever you want.

1 Like

Hi @Catalin_S,
Install version 2.2 and see if it works better for you with temp offset.

I have modified so that it takes the current temperature directly from the message sent by the sensor, instead of get the last state stored.

At this temperature the offset will be added and it will be the Current temperature for the calculations.

It works well for me with both methods, but I like this one better.

In the temperature graph of the app you should see temperature information every 5 minutes even if it is repeated, and in the history you will only see events with temperature changes of at least 0.1 °

I have Installed new driver and restarted the hub at 7AM. All was ok until 12 PM. I think I will use it without offset settings.
Now I will test the driver without the thermostat settings.
. See the attached photo

1 Like

How odd!!!
Could it have to do with some intermittent device failure?

I have had 2 devices running with negative temp offset for a whole day and no bad event came out.

It could be.
For now, i installed only the sensor driver, set the temperature offset to -0.1C an rebooted the hub.
I will monitor it to see how it works.

1 Like

Hey Mariano, could you add this sensor? Thanks

Added to

│ Name │ Zigbee Temp Sensor with Thermostat Mc │ │
│ Version │ 2021-11-17T15:16:02.560903

And to:

│ Name │ Zigbee Temp Humidity Sensor Mc │
│ Version │ 2021-11-17T15:18:10.009658

  - id: "eWeLink/66666"
    deviceLabel: Temp Humidity Sensor
    manufacturer: eWeLink
    model: 66666
    deviceProfileName: temp-humid-therm-battery
1 Like

Strangely, it did pair but paired as a eWelink motion Sensor using zigbee motion sensor driver. it didnt do that when i tried before
. always jpined as stock dth thing

Yes, there is a motion sensor with the same model and manufacturer.

Don’t worry, you can make a driver change from the device, menu driver, use another driver

  - id: "eWeLink/Motion 66666"
    deviceLabel: eWeLink Motion Sensor
    manufacturer: eWeLink
    model: 66666
    deviceProfileName: motion-battery

I tried that but there wasn’t a driver available even though I do have it installed

A post was split to a new topic: [ST Edge] Issue while trying to change the device’s driver


Could you check with a multipurpose sensor, which I think you have, if the temperature offset correction works correctly?

I see strange things when I have a negative correction set (-0.1).

it sends temperature events without temperature change, only when there is a temperature change +/- 0.1 °, in the default configuration it should send an event.

When the temperature offset is 0 ° it works fine.

A user @Catalin_S, even gets to have temperature events equal to the offset temperature.

That has not happened to me.

I can’t find information about where and how the default libraries are calculated.

these are the captures.

I tested sensor temp and humidity driver without the thermostat capability and the temperature offset is working normally.
What I did:
Removed all driver, installed only temp and humidity driver and rebooted the hub.
After that I set the offset temperature to -0.1C

No error in the last 24 hours

Well, if it works with a driver it should work well with the thermostat driver.
The capabilities handlers for temperature, humudity and atm pressure are identical in the two drivers.

Are you using the standard preference of temperature offset?

What reporting change is configured for this capability? I believe the preference offset only adds/subtracts from the value received, but it shouldn’t modify the set “reporting change” which indicates when the report must be sent (Eg. if the temperature changes 0.1º, 1º, etc.)

Which thermostat capability is @Catalin_S referring to? Please share both drivers’ URLs in Github so I can see their configuration.