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

[Mariano_Colmenarejo]

@William_Knecht

Or are folks using to control space heaters and things that don’t have built in smart thermostats?

This is the most normal use, to replace a physical thermostat or one that does not exist.
I use it to control my gas-oil heating and the BEOK Wi-Fi physical thermostat that I used before (less precise 0.5ºc. virtual has 0.1ºc precision) I have left it as a back-Up with 2ºC below in case the virtual one ever fails. This is the second year that I am using it and it has never failed.

I have it programmed with three routines, which change the thermostat mode:
Asleep mode: at 18ºc at night: 10:30 p.m. to 09:00 a.m.
Auto mode: at 19ºc from 9:00 a.m. to 2:30 p.m.
Rush hour mode: at 20ºc from 2:30 p.m. to 10:30 p.m.

This is the day temperature result:

You can also use it with automations to combine a physical and virtual thermostat, for example, if you have the temperature sensor in another part of the room, it activates the heating with the lowest temperature in any of the thermostats (physical and virtual).

[milandjurovic71 (Milan)]

You can setup whichever devices (plugs, heaters, fans, a/c, humidifier etc.) you want to come on with heating, cooling or fan only with routines. Originally when this driver was developed, I have tested it with ecobee, and I could control it. It does have multiple presets that you can call through routines, or you just simply change temperature with +/- to your liking.
For example I have simple garage heater that I am controling through virtual thermostat in the winter, and through summer it’s bringing fresh air using gabble fan.
Another one is controling humidifier.
Feel free to ask here with what do you want to accomplish, and someone will come up with solution

[William_Knecht]

I see. I’m just thinking of ways to automate my z-wave thermostats when webcore goes away. I have separate thermostats for heat and AC (both z-wave). Replicating the webcore with routines is daunting and I haven’t seen a z-wave driver that takes full advantage of the scheduling the thermostats have.

So thinking this could be an option, but is it possible to somehow mirror the zwave one to this virtual one (temp set points, mode)? I don’t see that ability in the app.

[Mariano_Colmenarejo]

@William_Knecht

but is it possible to somehow mirror the zwave one to this virtual one (temp set points, mode)?

This thermostat uses a physical sensor to make the calculations for both heat and cold.

It does not support reflecting temperature from another sensor or thermostat.

There are other virtual Thermostats like @TAustin , which don’t have a physical sensor and need to reflect the temperature from a sensor or thermostat.
I think they use the rules API to reflect the temperature to the virtual Thermostat, I don’t know how to do it.

Maybe you could use the rules API to convert your webcore pistons.

Others are using Sharp tools, but I guess you’ve already read about this.

[Geir_Skalvik]

The option to create a virtual thermostat seems to be missing when using the driver for a smartthings multipurpose sensor. Is this intended?

[Mariano_Colmenarejo]

@Geir_Skalvik

The option to create a virtual thermostat seems to be missing when using the driver for a smartthings multipurpose sensor. Is this intended?

Hi @Geir_Skalvik

Yes, driver Zigbee Temp Sensor with Thermostat Mc convert the sensor in a Thermostat with all function of the sensor, motion, Contact… And has not option to child device.
It was the first driver to manage only one device if there is problem with 200 device limit

[Sylvain]

Hi @Mariano_Colmenarejo
I’ve got a Moe’s temperature and humidity display it is working with you driver temp and child thermostat. But humidity show it divide by 10 in the app .

And that’s the device

In that picture humidity is at 49% so in the app it will show 5%

Can you fix that ?
Thank you

[Mariano_Colmenarejo]

@Sylvain

But humidity show it divide by 10 in the app .

Hi @Sylvain

I modified the humidity event for this manufacturer.
It’s a bit strange, if you could send me a log doing a refresh of the device to see the raw value that the device is sending

─────────────────────────────────────────────────────────     
 Name         Zigbee Temp Sensor and Child Thermostat Mc 
 Version      2023-01-05T11:16:57.702185985
─────────────────────────────────────────────────────────

[Sylvain]

@Mariano_Colmenarejo
Thank you seem to be working perfect.

There was the log before the driver was update.

2023-01-05T00:06:39.623011959+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/01/05 Time: 00:06
DNI: 0xEF3E LQI: 107 RSSI: -89dbm
”},“visibility”:{“displayed”:false}}
2023-01-05T00:06:39.722521417+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:24.9}}
2023-01-05T00:06:39.762891376+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Temp Tuya display device thread event handled
2023-01-05T00:06:41.578462251+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler zigbee
2023-01-05T00:06:41.583475584+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xEF3E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, lqi: 0xFF, rssi: -64, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xD8, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x01D6 > > > >
2023-01-05T00:06:41.594961834+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Found ZigbeeMessageDispatcher handler in st-zigbee-temp
2023-01-05T00:06:41.598082418+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc Executing ZclClusterAttributeValueHandler: cluster: RelativeHumidity, attribute: MeasuredValue
2023-01-05T00:06:41.602687543+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/01/05 Time: 00:06
DNI: 0xEF3E LQI: 255 RSSI: -64dbm
”},“visibility”:{“displayed”:false}}
2023-01-05T00:06:41.615989959+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> emitting event: {“attribute_id”:“humidityTarget”,“capability_id”:“legendabsolute60149.humidityTarget”,“component_id”:“main”,“state”:{“value”:“Equal-Up”}}
2023-01-05T00:06:41.627365834+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> emitting event: {“attribute_id”:“humidity”,“capability_id”:“relativeHumidityMeasurement”,“component_id”:“main”,“state”:{“value”:5}}
2023-01-05T00:06:41.639194668+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Temp Tuya display device thread event handled
2023-01-05T00:06:44.448523460+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler zigbee
2023-01-05T00:06:44.453313293+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xEF3E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, lqi: 0xFF, rssi: -69, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xD9, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x02EE > > > >
2023-01-05T00

[Mariano_Colmenarejo]

@Sylvain

2023-01-05T00:06:41.583475584+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xEF3E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, lqi: 0xFF, rssi: -64, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0xD8, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x01D6 > > > >

Thanks @Sylvain

It is true, it is sending the humidity value divided by 10 (0x01D6 = 470)
According to the default libraries, have to divide the received value by 100 and round it.
470 /100 = 4.7% = 5%

@Sylvain

2023-01-05T00:06:41.627365834+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: da024ddd-edd2-4fad-99ee-cdd1b3c945f1 [0xEF3E] (Temp Tuya display)> emitting event: {“attribute_id”:“humidity”,“capability_id”:“relativeHumidityMeasurement”,“component_id”:“main”,“state”:{“value”:5}}

[Fernando_Garcia]

Hola @Mariano_Colmenarejo , aunque también soy español paso al inglés para la comunidad .

This is my first post, after having read all your posts and I am using your Edge driver for the thermostat for 2 months working perfectly… until today.

It seems that with the latest update of SmartThings App on my phone, your driver (this is my guess) makes the mobile App crash. I can open the App as usual, I can use it (check scenes, go to settings, etc.) but if I start scrolling down in my list of favourite devices, it works as normal until it is about to show the tile for your virtual thersmostat when it crashes. I’ve checked that it also happens if I go to the room view and try to check a room where the virtual thersmostat is located.

The driver seems to work prefectly as I can use my scenes or routines to turn it ON/OFF but can’t see the tile to check temperature or change manually the status.

Version of the App: 1.7.93.26
Mobile phone: Huawei Mate 20 Pro

Could this be an issue with the presentation of your Edge driver in the App? Could it be that this tile or some of the visual layout components that you use is no longer supported?

If you need some logs or a screen-recorded video I can send it to you (I can’t upload a video here, only images). Should I do some reinstalation of your driver?

Thanks in advance, Mariano

          Fernando

[Johnnybegoode (John)]

There is a thread on this subject but no real conclusion that it is provoked by a driver…

New version ( 1.7.93.26 ) of smart things app for android won't load

Does anyone have such problems, with the newest version for android?

[Jepajo (Patrik Johansson)]

It was no problem for me using the single tile. But then i had to try with the multi tile and then the app crash.

[Mariano_Colmenarejo]

@Fernando_Garcia

Could this be an issue with the presentation of your Edge driver in the App?

Hola Fernando

It does seem to be a problem when app try to display a multiple massaic.

I don’t think they’ll fix it, as it’s a documented feature and it’s worked so far, but I wouldn’t be surprised if they changed something without notice. It wouldn’t be the first time.

Then I will try to make the multiple mosaic as optional to see if everything works until they solve it or tell us the new conditions.

[milandjurovic71 (Milan)]

@Mariano_Colmenarejo I don’t believe that is mosaic presentation. For me app crashes when I go to specific room, with only 3 devices. Only to that room. If I search for those lights with all devices option, not rooms, I can use them without any problem.

[Mariano_Colmenarejo]

New version of Zigbee Temp Sensor and Child Thermostat Mc

─────────────────────────────────────────────────────────     
 Name         Zigbee Temp Sensor and Child Thermostat Mc 
 Version      2023-01-07T14:25:11.388743217
─────────────────────────────────────────────────────────

@Fernando_Garcia @Johnnybegoode
Improvements:

• Added option for single or multiple mosaic of virtual child thermostat. It allows the new version 1.7.93.26 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

[Mariano_Colmenarejo]

@milandjurovic71

If I search for those lights with all devices option, not rooms, I can use them without any problem.

That did not work for me and I had to uninstall the app again so that the option all devices is removed and the app does not close

Worse, not even uninstalling the app removes the option to show all devices and I can no longer use the app.
Don’t do it!!!

[Fernando_Garcia]

Hola @Mariano_Colmenarejo and gracias for your quick modification.

Perhaps this is a stupid question, but how do I install the new version of your driver?
I can’t touch in your previous Thermostat tile as the App crashes.

Should I try to “Add a new device” or remove the previous one (if so, how? in the App or in the online SmartThings IDE?)

[Mariano_Colmenarejo]

@Fernando_Garcia

but how do I install the new version of your driver?

New version Will be installed automatically in 12 hiurs Max.

You can install with CLI manually

[Dick_Karlsson]

Hi there,
Maybe im doing something wrong here (atleast lets hope so)
Ive added this driver and using it with a aqara temp & humidity sensor and after created a virtual thermostat, problem is.
Thermostat has a fixed temperature and not the temperature from the aqara temp sensor, it even has additional temperature called vtemp.
So is aqara not supported correctly? Or if it is, why is thermostat showing the right temperature, makes it quite hard to actually control anything? Have to make automations using the sensor and thermostat and not only thermostat.
Thanks