Radio Thermostat CT100 not working correctly

BakaMonogatari · May 27, 2021, 9:08pm

I just paired a CT100 thermostat and I’m getting some incorrect behavior. Firstly it created 2 Thermostat entities. I disabled the second one since I don’t see a reason for it.

Secondly the operating mode (idle vs cooling) isn’t getting pushed to HA. I can change the target temp and see it reflected in HA but operating status doesn’t always. I don’t think it’s an issue with the thermostat itself because I did have it working fine in Hubitat. I’m a new user so if there’s any additional troubleshooting steps I need to take please guide me.

Not sure how helpful it is but I found this in the Z-wave JS logs

2021-05-27T20:53:52.970Z CNTRLR « [Node 007] supports 1 association groups                          [Endpoint 1]
2021-05-27T20:53:52.971Z CNTRLR » [Node 007] querying association group #1...                       [Endpoint 1]
2021-05-27T20:53:53.033Z CNTRLR « [Node 007] received information for association group #1:         [Endpoint 1]
                                  maximum # of nodes: 2
                                  currently assigned nodes: 1
2021-05-27T20:53:53.037Z CNTRLR   [Node 007] Interviewing Thermostat Mode...                        [Endpoint 2]
2021-05-27T20:53:53.037Z CNTRLR » [Node 007] querying supported thermostat modes...                 [Endpoint 2]
2021-05-27T20:53:53.085Z CNTRLR « [Node 007] received supported thermostat modes:                   [Endpoint 2]
                                  · Off
                                  · Heat
                                  · Cool
                                  · Auto
2021-05-27T20:53:53.086Z CNTRLR » [Node 007] querying current thermostat mode...                    [Endpoint 2]
2021-05-27T20:53:53.234Z CNTRLR « [Node 007] received current thermostat mode: Cool                 [Endpoint 2]
2021-05-27T20:53:53.236Z CNTRLR   [Node 007] Interviewing Thermostat Setpoint...                    [Endpoint 2]
2021-05-27T20:53:53.236Z CNTRLR » [Node 007] retrieving supported setpoint types...                 [Endpoint 2]
2021-05-27T20:53:53.284Z CNTRLR   [Node 007] Thermostat Setpoint bitmap interpretation is unknown,  [Endpoint 2]
                                  assuming B for now
2021-05-27T20:53:53.285Z CNTRLR » [Node 007] querying current value of setpoint Heating...          [Endpoint 2]
2021-05-27T20:53:53.413Z CNTRLR « [Node 007] received current value of setpoint Heating: 70 °F      [Endpoint 2]
2021-05-27T20:53:53.414Z CNTRLR » [Node 007] querying current value of setpoint Cooling...          [Endpoint 2]
2021-05-27T20:53:53.520Z CNTRLR « [Node 007] received current value of setpoint Cooling: 75 °F      [Endpoint 2]
2021-05-27T20:53:53.524Z CNTRLR   [Node 007] Interviewing Multilevel Sensor...                      [Endpoint 2]
2021-05-27T20:53:53.525Z CNTRLR » [Node 007] querying current sensor reading...                     [Endpoint 2]
2021-05-27T20:53:53.613Z CNTRLR « [Node 007] received current sensor reading:                       [Endpoint 2]
                                  sensor type: Humidity
                                  value:       54 %
2021-05-27T20:53:53.624Z CNTRLR   [Node 007] Interviewing Association...                            [Endpoint 2]
2021-05-27T20:53:53.625Z CNTRLR » [Node 007] querying number of association groups...               [Endpoint 2]
2021-05-27T20:53:53.680Z CNTRLR « [Node 007] supports 1 association groups                          [Endpoint 2]
2021-05-27T20:53:53.681Z CNTRLR » [Node 007] querying association group #1...                       [Endpoint 2]
2021-05-27T20:53:53.727Z CNTRLR « [Node 007] received information for association group #1:         [Endpoint 2]
                                  maximum # of nodes: 2
                                  currently assigned nodes: 
2021-05-27T20:53:53.729Z CNTRLR   [Node 007] Interviewing Thermostat Mode...
2021-05-27T20:53:53.729Z CNTRLR » [Node 007] querying supported thermostat modes...
2021-05-27T20:53:53.774Z CNTRLR « [Node 007] received supported thermostat modes:
                                  · Off
                                  · Heat
                                  · Cool
                                  · Auto
2021-05-27T20:53:53.775Z CNTRLR » [Node 007] querying current thermostat mode...
2021-05-27T20:53:53.934Z CNTRLR « [Node 007] received current thermostat mode: Cool
2021-05-27T20:53:53.935Z CNTRLR   [Node 007] Interviewing Thermostat Setpoint...
2021-05-27T20:53:53.936Z CNTRLR » [Node 007] retrieving supported setpoint types...
2021-05-27T20:53:53.979Z CNTRLR   [Node 007] Thermostat Setpoint bitmap interpretation is unknown, assuming B fo
                                  r now
2021-05-27T20:53:53.980Z CNTRLR » [Node 007] querying current value of setpoint Heating...
2021-05-27T20:53:54.151Z CNTRLR « [Node 007] received current value of setpoint Heating: 70 °F
2021-05-27T20:53:54.153Z CNTRLR » [Node 007] querying current value of setpoint Cooling...
2021-05-27T20:53:54.308Z CNTRLR « [Node 007] received current value of setpoint Cooling: 75 °F
2021-05-27T20:53:54.326Z CNTRLR   [Node 007] Interviewing Clock...
2021-05-27T20:53:54.328Z CNTRLR » [Node 007] requesting current clock setting...
2021-05-27T20:53:54.606Z CNTRLR « [Node 007] received current clock setting: Friday, 16:45
2021-05-27T20:53:54.619Z CNTRLR   [Node 007] Interviewing Multilevel Sensor...
2021-05-27T20:53:54.620Z CNTRLR » [Node 007] querying current sensor reading...
2021-05-27T20:53:54.717Z CNTRLR « [Node 007] received current sensor reading:
                                  sensor type: Air temperature
                                  value:       72 °F
2021-05-27T20:53:54.720Z CNTRLR   [Node 007] Interviewing Thermostat Operating State...
2021-05-27T20:53:54.722Z CNTRLR » [Node 007] querying thermostat operating state...
2021-05-27T20:53:54.839Z CNTRLR   [Node 007] Interviewing Thermostat Fan Mode...
2021-05-27T20:53:54.840Z CNTRLR » [Node 007] querying supported thermostat fan modes...
2021-05-27T20:53:54.883Z CNTRLR « [Node 007] received supported thermostat fan modes:
                                  · Auto low
                                  · Low
2021-05-27T20:53:54.884Z CNTRLR » [Node 007] querying current thermostat fan mode...
2021-05-27T20:53:55.016Z CNTRLR « [Node 007] received current thermostat fan mode: Auto low
2021-05-27T20:53:55.027Z CNTRLR   [Node 007] Interviewing Thermostat Fan State...
2021-05-27T20:53:55.028Z CNTRLR » [Node 007] querying current thermostat fan state...
2021-05-27T20:53:55.127Z CNTRLR   [Node 007] Interviewing Configuration...
2021-05-27T20:53:55.128Z CNTRLR   [Node 007] ConfigurationCC: skipping interview because CC version is < 3 and t
                                  here is no config file
2021-05-27T20:53:55.132Z CNTRLR   [Node 007] Interview stage completed: CommandClasses
2021-05-27T20:53:55.135Z CNTRLR   [Node 007] Interview stage completed: OverwriteConfig
2021-05-27T20:53:55.136Z CNTRLR » [Node 007] requesting node neighbors...
2021-05-27T20:53:55.155Z CNTRLR « [Node 007] node neighbors received: 1, 5, 6
2021-05-27T20:53:55.156Z CNTRLR   [Node 007] Interview stage completed: Neighbors
2021-05-27T20:53:55.157Z CNTRLR   [Node 007] Interview completed
2021-05-27T20:53:55.158Z CNTRLR   [Node 007] The node is ready to be used
2021-05-27T20:55:44.417Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:44.442Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:45.189Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:45.212Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:51.642Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:51.667Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:58.205Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T20:55:58.230Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T21:05:25.208Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1
2021-05-27T21:05:25.232Z CNTRLR   [Node 007] Mapping unsolicited report from root device to first supporting end
                                  point #1

tykeal · May 29, 2021, 2:23pm

I’ve got a CT101 and I know your pain. But firstly, that second thermostat that was created actually controls half of the heating / cooling modes.

One thermostat (and I don’t know which but I believe it’s the first one created) controls heating and the second one controls cooling.

When in full auto mode then both of those thermostats should be set to the same values (which unfortunately isn’t happening automatically). When in either straight heating or cooling mode, then only the appropriate thermostat needs to be set to the needed values.

My other issue right now is that the Fan doesn’t register in the UI but it’s controllable via a dropdown when inspecting the entity.

AllHailJ · May 29, 2021, 4:11pm

I had 3 ct100’s and 1 ct100+ The control for the HVAC systems were never reliable. I ran on z-wave js and open z-wave and both had similar problems. Lovelace thermostat dying, values not being entered, lack of control. the two fireplace ct100’s were battery powered and I changed to 12v power to have system alive continuously. This changed nothing. I gave up on the ct100’s and I switched to ecobee for HVAC and shelly devices for fireplaces. I have created virtual thermostats using temperature sensors in the rooms where the shelly devices are installed.

I think the problem is z-wave related but can’t prove. I used the ct-100’s with homeseer and they worked on that system. I will say that the ecobee thermostats do a better job of maintaining temperature and have better logic than the ct-100’s. It sucked that I had to buy twice but glad I changed to ecobee.

dsweet · July 5, 2021, 4:20pm

Did you get a resolution to this. I have a CT100 and to get the Operating Mode sent to HA I had to set up polling. I use ZWaveJS to MQTT so what I did was:

Go to the ZWaveJS to MQTT Web UI (Home Assistant\Supervisor Link Left Menu\Info Tab\Click on “Open Web UI”
Click on “hamburger” Icon\choose “Settings”
Expand “General” List
Tap “NEW VALUE” link at bottom of expanded list
Choose your thermostat from the list of distinct types
Choose “Operating State” for value
Click on “Poll” Switch to turn on. Set poll interval

Press “ADD” link at bottom of dialog box.
Press “SAVE” link at bottom of window.
Click little reload icon upper right of window to reload the configuration.

I did not find a way to set up the device to automatically send the report to the Z-Wave controller. I’ve done so with other devices. That would be the preferred way, but with the wife returning tomorrow I had to set up something

If you’re not using ZWaveJS to MQTT I think you can set up an automation to send a query using the zwave or zwave_js service.

dhmsjs · June 22, 2022, 10:45pm

To anyone coming across this thread you should not need to poll the device. Instead update your ct100.json device config file. See CT100 doesn't show current temperature w/ Zwavejs2mqtt - #2 by dhmsjs