[Port] Enhanced Z-Wave Thermostat (CT-100 w/ Humidity and Time Update)

jrfarrar · October 21, 2018, 11:53pm

I'm getting some errors with this when trying to set it. Receiving data from it...but can't change parameters.

dev:402018-10-21 19:49:23.393 error groovy.lang.MissingMethodException: No signature of method: 
dev1540146974691666542007.createEvent() is applicable for argument types: (java.lang.String) values: 
[]
Possible solutions: zwaveEvent(hubitat.zwave.Command), 
zwaveEvent(hubitat.zwave.commands.basicv1.BasicReport), 
zwaveEvent(hubitat.zwave.commands.batteryv1.BatteryReport), 
zwaveEvent(hubitat.zwave.commands.multiinstancev1.MultiInstanceCmdEncap), 
zwaveEvent(hubitat.zwave.commands.sensormultilevelv2.SensorMultilevelReport), 
zwaveEvent(hubitat.zwave.commands.thermostatfanmodev3.ThermostatFanModeReport) on line 48 
(parse)
dev:402018-10-21 19:49:07.349 error groovy.lang.MissingMethodException: No signature of method: 
dev1540146974691666542007.createEvent() is applicable for argument types: (java.lang.String) values: 
[]
Possible solutions: zwaveEvent(hubitat.zwave.Command), 
zwaveEvent(hubitat.zwave.commands.basicv1.BasicReport), 
zwaveEvent(hubitat.zwave.commands.batteryv1.BatteryReport), 
zwaveEvent(hubitat.zwave.commands.multiinstancev1.MultiInstanceCmdEncap), 
zwaveEvent(hubitat.zwave.commands.sensormultilevelv2.SensorMultilevelReport), 
zwaveEvent(hubitat.zwave.commands.thermostatfanmodev3.ThermostatFanModeReport) on line 48 
(parse)

dkkohler · October 22, 2018, 12:17am

Ah okay, I'll take a look. I haven't been using that functionality.

dkkohler · October 22, 2018, 12:25am

What parameter are you changing that's giving the error message?

jrfarrar · October 22, 2018, 12:38am

That error was thrown while hitting configure in the DH screen. Was trying to set HeatingSetpoint from there. However I can send a "Heating Setpoint" to it. But it doesn't change anything.

I only snipped the part where you can see the heatsetpoint get set to 67...then a refresh showing still at 68

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:36:14.803:debugParse returned [[value:68, unit:F, displayed:false, name:heatingSetpoint]]

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:36:12.467:debugParse returned [[displayed:true, isStateChange:true, value:68.0, unit:F, name:temperature]]

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:36:12.350:debugClock set age: 1366.9045333333 minutes

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:36:12.349:debugFetching fresh battery value

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:36:12.348:debugBattery report age: 1440.00005 minutes

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:36:12.344:infoRequested a refresh

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:35:52.344:debugParse returned [[value:fanAuto, name:thermostatFanMode, displayed:false]]

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:35:52.171:debugParse returned [[value:auto, name:thermostatMode]]

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:35:51.143:tracesetCoolingSetpoint(75.0, 30000)

[dev:40](http://192.168.13.46/logs#dev40)2018-10-21 20:35:51.095:tracesetHeatingSetpoint(67.0, 30000)

dkkohler · October 23, 2018, 11:34am

Strange about your issue. I was able to recreate the error after pressing Configure in my setup, but not the other issue. I'm able to change setpoints etc. no problem on all my thermostats. Does it work for you using the generic Zwave thermostat driver?

jrfarrar · October 23, 2018, 12:14pm

I ended up using the one mentioned here and it seems to work good included RH.

I'll have to try with the generic DH again to answer your question. I can say that the DH above does change the heating/cooling set points.

dkkohler · October 23, 2018, 12:40pm

Thanks for the link, I'll take a look. Glad you found something that works for you!

jrfarrar · October 23, 2018, 12:41pm

I'm willing to test out anything I can help with. I'm all about supporting those that help make all of this possible. So if there is anything you ever want tested...I'm here. Mine is a 2gig unit.

Ultrasmart.pl · March 16, 2019, 7:50pm

Hi guys. I used this driver for my Spirit Z-Wave Thermostat TRV but wanted to enhance it more with temperatureUp/Down methods. So i did.

It's here https://github.com/MarioHudds/hubitat/blob/master/EM%20Enhanced%20Z-Wave%20Thermostat

jrfarrar · April 30, 2019, 6:30pm

Updating this since there is now a built in CT101 DH.

Called: Radio Thermostat CT101

working well so far

dkkohler · April 30, 2019, 6:44pm

That's good news - does it support humidity reporting?

jrfarrar · April 30, 2019, 6:47pm

Yes it reports humidity, or are you asking if it's configurable to report humidity at specified intervals? So far it only seem to report when it actually changes.

dkkohler · May 1, 2019, 9:46pm

Are you sure about the humidity reporting? I updated one of me devices to use the new driver, and haven't received any humidity updates since...

jrfarrar · May 1, 2019, 9:54pm

Mine just reports when it changes it seems by a whole number:

JasonJoel · May 1, 2019, 9:56pm

Most thermostat humidity sensors are only +/-5% accurate anyway...

dkkohler · May 1, 2019, 10:31pm

After turning on debug logging for the device, I can see that the thermostat is reporting the humidity, but it is being skipped. Perhaps because the current humidity level is already 37, but I'm surprised the humidity level didn't change at all overnight.

jrfarrar · May 1, 2019, 10:36pm

That's odd, wonder if @mike.maxwell could explain what's going on?

mike.maxwell · May 1, 2019, 10:43pm

Awesome, there must be different firmware versions for these things, I don't recall mine skipping any multi instance commands.
Off the top of my head I don't know the command that's being skipped.

Per chance have you run configure on this device?

dkkohler · May 1, 2019, 11:20pm

Hi Mike,

I did run configure previously, but I just tried again followed by a Refresh with the same result. If it helps, the driver I posted at the top of this thread was working for humidity.

This PDF has some details on the humidity reporting.

Let me know if there's anything I can help test.

jrfarrar · May 3, 2019, 5:20pm

@mike.maxwell as you suggested in the other thread I removed and rejoined my t-stat to HE.

Something got worse. Now what shows on my t stat screen and what shows up in HE device page don't match. T-stat shows 67 as a set temp (heating set point) and HE shows 70. Something is definitely amiss. Should I got back to the old driver while this waits to get sorted out? Also when I rejoined it, it was picked up as a Generic Zwave thermostat. I had to manually change to Radio Thermostat CT101

I sent an email to support about another issues but haven't heard back in days.