Sinope TH1124ZB

Thanks! Here's some of the logs. I am home at lunch and it's not 1pm yet (13:00), so I'll have to check this driver again when I get home, but I wanted to go ahead and post as it seems to be throwing another error.

dev:4172020-11-03 12:43:51.422 pm errorgroovy.lang.MissingMethodException: No signature of method: user_driver_erilaj_Sinope_TH1300ZB_Thermostat_545.traceEvent() is applicable for argument types: (null, java.lang.String, null) values: [null, Sensor type is 10k, null] on line 280 (configure) dev:4172020-11-03 12:43:51.393 pm infoSet to Floor mode dev:4172020-11-03 12:43:51.391 pm infoSet to 12h AM/PM dev:4172020-11-03 12:43:51.389 pm infoSet Clock : Tue Nov 03 12:43:51 CST 2020 dev:4172020-11-03 12:43:51.368 pm infoconfigure() dev:4172020-11-03 12:43:50.331 pm infoupdated() : re-scheduling configure() every 3 hours, and once within a minute. dev:4172020-11-03 12:43:46.336 pm errorgroovy.lang.MissingMethodException: No signature of method: user_driver_erilaj_Sinope_TH1300ZB_Thermostat_545.traceEvent() is applicable for argument types: (null, java.lang.String, null) values: [null, Sensor type is 10k, null] on line 280 (configure) dev:4172020-11-03 12:43:46.306 pm infoSet to Floor mode dev:4172020-11-03 12:43:46.303 pm infoSet to 12h AM/PM dev:4172020-11-03 12:43:46.300 pm infoSet Clock : Tue Nov 03 12:43:46 CST 2020 dev:4172020-11-03 12:43:46.274 pm infoconfigure() dev:4172020-11-03 12:43:45.209 pm infoupdated() : re-scheduling configure() every 3 hours, and once within a minute. dev:4172020-11-03 12:42:21.851 pm infoheatingSetpoint: 68 dev:4172020-11-03 12:42:21.581 pm inforefresh() dev:4172020-11-03 12:42:20.430 pm errorgroovy.lang.MissingMethodException: No signature of method: user_driver_erilaj_Sinope_TH1300ZB_Thermostat_545.traceEvent() is applicable for argument types: (null, java.lang.String, null) values: [null, Sensor type is 10k, null] on line 280 (configure) dev:4172020-11-03 12:42:20.397 pm infoSet to Floor mode dev:4172020-11-03 12:42:20.395 pm infoSet to 12h AM/PM dev:4172020-11-03 12:42:20.392 pm infoSet Clock : Tue Nov 03 12:42:20 CST 2020 dev:4172020-11-03 12:42:20.364 pm infoconfigure() dev:4172020-11-03 12:42:16.671 pm errorgroovy.lang.MissingMethodException: No signature of method: user_driver_erilaj_Sinope_TH1300ZB_Thermostat_545.traceEvent() is applicable for argument types: (null, java.lang.String, null) values: [null, Sensor type is 10k, null] on line 280 (configure) dev:4172020-11-03 12:42:16.639 pm infoSet to Floor mode dev:4172020-11-03 12:42:16.636 pm infoSet to 12h AM/PM dev:4172020-11-03 12:42:16.632 pm infoSet Clock : Tue Nov 03 12:42:16 CST 2020 dev:4172020-11-03 12:42:16.604 pm infoconfigure() dev:4172020-11-03 12:42:15.554 pm infoupdated() : re-scheduling configure() every 3 hours, and once within a minute. dev:4172020-11-03 12:41:40.074 pm errorgroovy.lang.MissingMethodException: No signature of method: user_driver_erilaj_Sinope_TH1300ZB_Thermostat_545.traceEvent() is applicable for argument types: (null, java.lang.String, null) values: [null, Sensor type is 10k, null] on line 280 (configure) dev:4172020-11-03 12:41:40.039 pm infoSet to Floor mode dev:4172020-11-03 12:41:40.036 pm infoSet to 24h dev:4172020-11-03 12:41:40.023 pm infoSet Clock : Tue Nov 03 12:41:40 CST 2020 dev:4172020-11-03 12:41:39.960 pm infoconfigure() dev:4172020-11-03 12:41:38.898 pm infoupdated() : re-scheduling configure() every 3 hours, and once within a minute.

@haganwalker, please use the Preformatted button option when posting logs...

Paste log, highlight the text and press button </> in the bar just over the compose box.

Here are the logs after doing that:

Thanks @nclark!

@haganwalker I removed 2 lines left from sinope's smartthings driver. I think that's why the clock settings was not working. The exception was raised before the zigbee configuration commands were send.

You can grab the new version on github.

Received the remaining 3 thermostats. 1 is sadly not compatible with my garage heater, it just displays OL1. I had a hunch it would be since it's on a 30a breaker all by itself, but I have never once used the thing so I'll just leave it as a temp sensor for the garage and a way to display the outside temp on the way out the door.

All 3 of the new thermostats are on FW# 2002 with a build date of 20200225.
All 3 display the word "Out" under the outside temperature.

I'll probably order up the GT130 since it's under $100 and just connect them 1 at a time, update the firmware, then move them back.

1 Like

Hi @nclark, my apologies!

Thanks again, @erilaj! Now it seems that there's a bug and that the display clock is false perhaps by default. Upon using the new driver and immediately upon clicking configure, the clock disappears from the device totally. You'll see where I then togged the Preference of the "enable display of clock" to off, which is in the log, but I toggled it back on and did not see that recorded. Did you happen to look at the temp display also? No big deal if not, I was just going to also report back on that if so.

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:31.586 pm [info](http://192.168.1.133/device/edit/417)refresh()

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:31.579 pm [info](http://192.168.1.133/device/edit/417)Sensor type is 10k

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:31.577 pm [info](http://192.168.1.133/device/edit/417)Set to Floor mode

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:31.574 pm [info](http://192.168.1.133/device/edit/417)Set to 12h AM/PM

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:31.571 pm [info](http://192.168.1.133/device/edit/417)Set Clock : Tue Nov 03 18:00:31 CST 2020

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:31.549 pm [info](http://192.168.1.133/device/edit/417)configure()

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:30.513 pm [info](http://192.168.1.133/device/edit/417)updated() : re-scheduling configure() every 3 hours, and once within a minute.

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:15.317 pm [info](http://192.168.1.133/device/edit/417)refresh()

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:15.311 pm [info](http://192.168.1.133/device/edit/417)Sensor type is 10k

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:15.309 pm [info](http://192.168.1.133/device/edit/417)Set to Floor mode

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:15.307 pm [info](http://192.168.1.133/device/edit/417)Set to 12h AM/PM

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:15.304 pm [info](http://192.168.1.133/device/edit/417)The clock was hide. DisplayClock = false

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:15.281 pm [info](http://192.168.1.133/device/edit/417)configure()

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:14.237 pm [info](http://192.168.1.133/device/edit/417)updated() : re-scheduling configure() every 3 hours, and once within a minute.

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:06.227 pm [info](http://192.168.1.133/device/edit/417)heatingSetpoint: 68

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.650 pm [info](http://192.168.1.133/device/edit/417)heatingSetpoint: 68

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.222 pm [info](http://192.168.1.133/device/edit/417)refresh()

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.216 pm [info](http://192.168.1.133/device/edit/417)Sensor type is 10k

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.214 pm [info](http://192.168.1.133/device/edit/417)Set to Floor mode

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.212 pm [info](http://192.168.1.133/device/edit/417)Set to 12h AM/PM

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.209 pm [info](http://192.168.1.133/device/edit/417)Set Clock : Tue Nov 03 18:00:04 CST 2020

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:04.185 pm [info](http://192.168.1.133/device/edit/417)configure()

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 06:00:03.124 pm [info](http://192.168.1.133/device/edit/417)updated() : re-scheduling configure() every 3 hours, and once within a minute.

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:40.366 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating temperature is 67.9°F

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:40.349 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating thermostatSetpoint is 68°F

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:40.341 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating heatingSetpoint is 68°F

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:40.323 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating thermostatOperatingState is idle

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:40.320 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating thermostatMode is heat

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:38.052 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating temperature is 67.9°F

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:38.047 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating thermostatSetpoint is 68°F

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:38.044 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating heatingSetpoint is 68°F

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:38.038 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating thermostatOperatingState is idle

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:59:38.035 pm [info](http://192.168.1.133/device/edit/417)Master Bath Floor Heating thermostatMode is heat

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:57:45.676 pm [info](http://192.168.1.133/device/edit/417)heatingSetpoint: 68

[dev:417](http://192.168.1.133/logs/past#dev417)2020-11-03 05:57:45.453 pm [info](http://192.168.1.133/device/edit/417)refresh()

Hi everybody and thanks a lot for sharing the driver code!
I have been using the @kris2k2 driver for a few weeks now on 5 thermostats, and I updated yesterday their driver with @erilaj 's. So far works great too!!
.. Except for one thermostat which worked very well using the hubitat driver but seems problematic with either one of the homemade drivers.


For this thermostat, the display comes back to normal for few seconds when I press one of the key to adjust the temperature (second picture).

The difference between this and the 4 others is that this one is a 4kW comparing to 3kW for the rest. But I don't think this is much of a problem here since I believe they share the same firmware, maybe not the same version however (this is just a guess though).
By any chance, would you know what is the cause here?
My current mitigation is to switch off the backlight but I miss having the info at all time.

By the way, additional thanks to @erilaj for sharing his sinope dimmer driver code!! Works as charm!

I had some weird display issues on one of mine, turned out when I was shoving the wires back into the box one had come loose and wasn't making a complete connection.

I've just checked the connections in the box and everything seems alright. Wires are well connected, nothing loose.
The thermostat works well, the only issue concerns the display.

I have issue with my 4kW thermostat as well. The clock went blank on me the other day and I have to click on set clock in the driver page to get it back on. My other 4 3kW thermostats have zero issue :man_shrugging:t2:

I have a couple of 4kW myself but haven't seen a difference between them and my multiple 3kW ones. Odd that you are seeing something different...

Using kris2k2 driver from https://github.com/kris2k2/hubitat/drivers/kris2k2-Sinope-TH112XZB.groovy

I struggled with this one almost daily. 1 random thermostat somewhere in the house would suddenly have the time go blank. @mbeaulieu32 was experiencing the same thing. This would happen with both the built-in driver as well as the modified driver. I had to setup a rule where once per hour it would "configure" every thermostat in the house. I still had issues where I would set the temperature and the thermostat itself would show the correct set point but the driver and the dashboard would still show the previous set point until I did a "refresh". So I had to setup another rule to constantly refresh the thermostats. It just got messy.

Ultimately I ended up moving these to zigbee2mqtt on a conbee ii stick in early September and it completely solved both issues I was having. Right now z2m can be brought into HE through an mqtt add-on or through node-red. These devices are also supported on Deconz with the conbee ii stick, which can then also be brought into HE through a deconz custom driver or node-red. So there are options out there

Looking at my zigbee route table. That thermostat has the lowest LQI even though it's closest to the hub. Not sure if it's related but I am going to rotate my hub a little to see it will help. If not then I will swap it to another location.
Clock went blank again this morning. Weird.

LQI:242, age:4, inCost:5, outCost:1

If you've got an LQI of 242 I guarantee you that is not your issue. If I'm not mistaken the maximum LQI value is 250 or somewhere in that vicinity.

Max is 255. It's the only device in my mesh with the lowest LQI.

New version of the driver for TH112XZB (3KW and 4KW).

  • Clock Display/Hide logic has been inverted. Now the preference setting is Hide the Clock and it's false by default. This might help if you have the clock disappearing on you. I am suspicious that maybe some preference settings lose their values between execution. I have no proof of that, it's just a theory. Anyway probably 99% of us want the Clock displayed all the time so it make sense to invert the logic.

  • Added 24h / 12h AM/PM preference settings. Default value is 24h.

  • Added the unit measure when event are send. This will add °C or °F in the thermostat dashboard or in the event log. Also W (Watt) for the output power.

image

  • The thermostatSetpoint attribute is now set at the same time as the heatingSetpoint. I had an issue with Google Home not reporting the correct setpoint of the thermostat and I realized that these 2 attributes needs to be set together. It's done this way in the Sinope SmartThing driver.

Again, this is based on @kris2k2 driver and I am just adding/correcting things that I think are useful. Most of the hard work as been done by Kris.

Don't forget to hit "Save Preference" after you update the driver.

https://github.com/erilaj/hubitat/blob/main/drivers/Sinope/erilaj-Sinope-TH112XZB.groovy

3 Likes

I ordered the GT130 based on Sinope support's communication where they stated that by connecting the thermostats to the GT130 gateway they would automatically receive the firmware updates.

It arrived yesterday so I moved my kitchen thermostat and my storage thermostat over right away as a test. At some point overnight they both updated, but it was the software not the firmware. Both thermostats are now on software version 0.6.4. My kitchen thermostat is still on firmware 1723 and the storage is still on firmware 1573. As a point of reference, the new ones I just received are on firmware 2007.

The kitchen thermostat still does not display the word "Out" under the outside temperature.

For me, the TH1300ZB driver from 2 days ago broke the clock. Whatever I do, it doesn't show up, while the previous version worked. The HE driver does restore the clock though but as soon as I put @erilaj 's new driver, it disappear.

Is that the version with the preference setting "Hide Clock"? Did you hit "Save preferences" after updating?

Please take a screenshot of the log after you have hit the Configure command.

I have the same logic on the TH112XZB driver and my 10 thermostats have the clock displayed properly.

Edit : @haganwalker seem to have the same problem with the clock. If anyone using the TH1300 driver would like to share a screenshot of the log, that would help me find the problem.

Also check the value of the State variable hideClock in the driver's page.

Seems like I can't upload screenshots, but here's the log after pressing "Save Preferences", with "Enabling the display of outdoor temperature" at true and "Hide the clock" at false :

dev:302 2020-11-07 19:49:05.291 info refresh()
dev:302 2020-11-07 19:49:05.281 info Sensor type is 10k
dev:302 2020-11-07 19:49:05.279 info Set to Floor mode
dev:302 2020-11-07 19:49:05.276 info Set to 24h
dev:302 2020-11-07 19:49:05.273 info The clock is visible. HideClock = false
dev:302 2020-11-07 19:49:05.271 info Set Clock : Sat Nov 07 19:49:05 EST 2020
dev:302 2020-11-07 19:49:05.249 info configure()
dev:302 2020-11-07 19:49:04.182 info updated() : re-scheduling configure() every 3 hours, and once within a minute.

State Variables :
hideClock : false
scale : C

@Tabrak, your log indicate that the clock should be visible, that's odd!

I had a good look at the Sinope's SmartThing driver and they don't offer an option to display the clock or not and the way they send the time to the thermostat is different. So I did the same as them.

You can try the latest version on GitHub.

Download the Hubitat app