Hi Michel,

 

I ran that program minutes later. It reset the cool setpoint to the proper setting.

 

Here is the event log 5 minutes later setting CSP to 76 (98H/2):

 

Fri 09/21/2012 12:10:40 PM : [ Time] 12:10:42 2(0)

 

Fri 09/21/2012 12:10:40 PM : [iNST-TX-I1 ] 02 62 11 B5 F0 0F 6C 98

 

Fri 09/21/2012 12:10:40 PM : [iNST-ACK ] 02 62 11.B5.F0 0F 6C 98 06 (98)

 

Fri 09/21/2012 12:10:40 PM : [iNST-SRX ] 02 50 11.B5.F0 19.75.3A 27 6C 98 (98)

 

Fri 09/21/2012 12:10:40 PM : [standard-Direct Ack][11.B5.F0-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Certainly well after the phantom command. What caused the cool setpoint to be set to 36 degrees?

 

Thanks.

Hi ski2020,

 

Good question. As I mentioned before, there's absolutely nothing in the logs/event viewer that says ISY was the culprit. At this point it's either the thermostat or something else that was linked to the thermostat before.

 

With kind regards,

Michel

The mystery remains what was the stat acking. And since it does not appear to be the ISY, I have to assume that the stat did something strange. Its not linked to anything. Hopefully it won't happen again.

 

Thanks for the time and effort!

Hi ski2020,

 

I am not sure which ACK you are referring to. There's nothing in your logs that says the thermostat was ACKing anything from the PLM. The only ACK is when you reset the thermostat yourself.

 

With kind regards,

Michel

Per original posts at start of thread, the issue still exists with 3.3.10 -- maybe I'll still get to swap thermostat adapters again . I don't have detailed logs but still have program running that looks for the condition. Log entries below:

 

Master Suite / Master Bedroom:Thermostat Heat Setpoint 168â–‘ Thu 2013/03/07 11:13:21 AM System Log

Master Suite / Master Bedroom:Thermostat Status Queryâ–‘ Thu 2013/03/07 11:13:21 AM Program Log

Master Suite / Master Bedroom:Thermostat Heat Setpoint 40â–‘ Thu 2013/03/07 11:13:25 AM System Log

Master Suite / Master Bedroom:Thermostat Status Queryâ–‘ Thu 2013/03/07 11:13:26 AM Program Log

 

What can I provide so we can find the issue?

Hello hart2hart,

 

Is this random or does it happen all the time?

 

With kind regards,

Michel

Random. Has happened twice in last week and a half.

Michel:

 

I replaced thermostat adapters with Rev 2.5 (firmware v.95) and the issue still occurs. From the original posting and what I've seen recently, it appears the adapter may be corrupting the setpoints when it receives a command to change mode from ISY. Originally it was setting thermostat mode and this time we've added fan mode. In following log, the repeats that are 10 seconds apart of setting fan mode existed as insurance but I've removed them.

 

Thanks,

 

Paul

 

Hi Paul,

 

This is quite odd. So the program was in heat mode but the cool set point changed to an invalid value. This all happened after a program changed the fan mode. Is it possible to try and reproduce this but having the same parameters but, this time, use the Admin Console to change the fan state. If you see anomalies in the set point, please make sure that the thermostat actually shows the corrupted set point on its screen.

 

With kind regards,

Michel

Looking at thermostat screen is how I arrived at the phantom and bad set point naming scheme. Phantom is in log, corrected by query, but not displayed on thermostat. Bad are in log, not corrected by query, and is displayed on thermostat.

Hi Paul,

 

I think we'll need to take your case back to SmartHome and see what would like us to do and/or proceed.

 

Please send an email tech@Universal-devices.com with your event viewer and I'll forward.

 

Please note that I'll be off till Thursday so please excuse non-responsiveness.

 

With kind regards,

Michel