Jump to content

2441TH/2441ZTH Themostat - Ctl State Does Not Report


vspete

Recommended Posts

I am currently using two Insteon thermostats. Both are controllable from the ISY and report temperature and humidity without any issues. The control state fields never populate for either thermostat therefore making them unusable for programming purposes.

 

I realize that these do not respond to a query command, but these never update when heating or cooling is called for by either the ISY or the thermostats. I would question the thermostat if the issue was limited to only one of the thermostats.

 

I seem remember that these fields populated when I first installed the thermostats. I have subsequently updated the ISY firmware a couple of times - currently running v.4.2.30.

 

Any ideas how I can get the ISY to populate these values?  If I initiate cooling manually on TH thermostat, and observe received events on the ISY, I receiver CLISPH 134 followed by CLISPC 154 which indicate the changes in setpoints, but I do not receive anything reporting a change in control state.

 

Is there anything I need to set at the thermostat to cause these states to report?

 

Many thanks, Pete

Link to comment

I have two different versions of the 2441ZTH. The older unit can be set by ISY no problem while the newer unit cannot.

 

I only use my two thermostats as probes and they update well based on their design. Humidity updates every minute and temperature only updates on a temperature change of about 1-1.5 degree C. Unfortunately they did not put a heartbeat temperature update or a "update -all" time based cycle to supplement the report by exception technique.

 

When linking these units I find there has never been a 2441ZTH unit listed in ISY and I suspect that UDI thought the 2441TH profile would work sufficiently but many features do not function including increment and decrement temperatures for the 2441ZTH. That is totally internal to ISY firmware.  

 

As  I reported here, SH has changed the communications profile somewhat and I suspect not released the new styles to UDI for update in their database of devices.

 

Until better and proper support for the only native Insteon thermostats is produced for the ISY, I give up on attempting to do anything further or serious with them. They are just probes at the moment.

See signature line for f/w version. I have updated with almost every version since 4.0. They never worked completely for me but I also suspect some features have quit in later ISY versions.

Link to comment

Non-line powered devices don't always report their status. I have several programs that depend on the state of our 2441TH thermostats. The programs run successfully every time.

 

I also have some 2441ZTH thermostats that control the wired ones, but no programs that depend on the wireless thermostat's state.

Link to comment

Thanks Stu. It is good to hear that these thermostats are working for someone.  My ISY firmware is v.4.3.30 and 2441TH is v.0F  When I started this thread, I was getting regular reports the thermostat visible in the ISY event viewer.  I performed a thermostat factory reset and now only get updates when I query the device from the administrator. I do get unsolicited updates every 15 minutes from the ZTH thermostat (which is not the master).  Here is what is returned from the wired master thermostat:

 

Mon 08/17/2015 04:28:32 PM : [  2F 79 E8 1]   CLISPC 156

Mon 08/17/2015 04:28:32 PM : [  2F 79 E8 1]   CLISPH 136

Mon 08/17/2015 04:28:32 PM : [  2F 79 E8 1]   CLIHUM  40

Mon 08/17/2015 04:28:34 PM : [  2F 79 E8 1]    CLIMD   3

Mon 08/17/2015 04:28:34 PM : [  2F 79 E8 1]    CLIFS   8

Mon 08/17/2015 04:28:34 PM : [  2F 79 E8 1]      UOM   2

Mon 08/17/2015 04:28:35 PM : [  2F 79 E8 1]       ST 157

 

What I don't see returned is CLIHCS which should be the "State" which ISY would use to create the Cool Clt and Heat Clt status. Do you see a value for CLIHCS returned in your event viewer log?

 

When I run a thermostat query command from within a program, I do not see any response in the event viewer.  What am I missing?

Link to comment

I get a similar readout at level 1 of the event viewer. A query of either Coot Ctl or Heat Ctl gives no result in the Current State box. But programs run as they should. Here's a couple of programs, one triggered by status and one by control:

 

Fans-Front
If
        Status  'LR / Devices / LR Thermostat Main / LR Thermostat Cool Ctl' is On
 
Then
        Set Scene 'LR / Scenes / LR Ceiling Fan' On
        Set Scene 'CR / Scenes / CR Fan-Low' On
        Set Scene 'MR / Scenes / MR Fan' On
 
Else
   - No Actions - (To add one, press 'Action')
 
LR HVAC On
If
        Control 'LR / Devices / LR Thermostat Main / LR Thermostat Cool Ctl' is switched On
     Or Control 'LR / Devices / LR Thermostat Main / LR Thermostat Heat Ctl' is switched On
 
Then
        Set 'BR / Devices / LR HVAC Indicator' On
 
Else
        Set 'BR / Devices / LR HVAC Indicator' Off
 

Link to comment

The 2441ZTH thermostat (powered by a dongle) at our vacation home is controlled by a LampLinc Dimmer (Dualband). Occasionally, the thermostat's current condition is blank in the ISY and on MobiLinc. By turning the LampLinc off and then back on using the LampLinc the thermostat reboots but loses its mode (heat/cool) and its setpoint (degrees). An ISY program (see below) runs automatically when it detects that the mode has been lost and resets it and the set point. The current temperature will then appear correctly in the ISY and on MobiLinc.

Since this program automatically reboots the thermostat it inserts the temperture setpoint specified in the program. It the mode and/or setpoint needs to be changed, it must be first changed in the program.

Thermostat Setpoint Reset (Power Outage) - [iD 0011][Parent 0001][Not Enabled]
If
        Status  'Thermostat / Thermostat (Main)' is Mode Off
Then
        Wait  15 seconds
        Set 'Thermostat / Thermostat (Main)' Mode Heat
        Set 'Thermostat / Thermostat (Main)' 50° (Heat Setpoint)
Else
   - No Actions - (To add one, press 'Action')
 

The thermostat has worked flawlessly since implemented this method. I realize that more robust programming can address different modes/settings, I just don't need them. And, by the way, I have a notification sent to me each morning with the current temperature. I have another sent only when the temperature drops below setting indicating the heating system has failed. I can then call for assistance in addressing the problem.
 

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...