Jump to content
View in the app

A better way to browse. Learn more.
Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Thermostat erroneously returning 0 as status value

CompKing
in ISY994

Featured Replies

Posted

I have a program which regularly (every 5 mins) queries the thermostat for its reported temperature. I have a program which monitors the value and if below a threshold it adjusts the set temperature. I have had this program running for approx 4 months in all the prior betas.

 

A symptom I have is occasionally the program is executed when the temperature reported is erroneously reported as "zero", which may be a default on bad comm's. As a "wireless device", perfect communication is likely not possible.

 

So far, I only have a capture of my log with the Temperature entries. I have turned on event viewer to see if I can capture level 2 comms when this happens.

 

The funny part is this only happened weekly previously. Now, it seems to happen multiple times in a single day.

 

Here is a log of the applicable portion.

 

THERMOSTAT Status Query░ Sat 01/03/2009 11:51:51 AM Program Log

THERMOSTAT Status Query░ Sat 01/03/2009 11:51:51 AM Program Log

THERMOSTAT Humidity 0.24 Sat 01/03/2009 11:52:04 AM System Log

THERMOSTAT Fan State On Sat 01/03/2009 11:55:59 AM Program Log

THERMOSTAT Status 26░ Sat 01/03/2009 11:56:10 AM System Log

THERMOSTAT Humidity 0.23 Sat 01/03/2009 11:56:22 AM System Log

THERMOSTAT Fan State Auto Sat 01/03/2009 11:56:25 AM Program Log

THERMOSTAT Humidity 0.24 Sat 01/03/2009 11:57:01 AM System Log

THERMOSTAT Status Query░ Sat 01/03/2009 11:57:09 AM Program Log

THERMOSTAT Status Query░ Sat 01/03/2009 11:57:09 AM Program Log

THERMOSTAT Status Query░ Sat 01/03/2009 12:03:31 PM Program Log

THERMOSTAT Status Query░ Sat 01/03/2009 12:03:31 PM Program Log

THERMOSTAT Status 27░ Sat 01/03/2009 12:03:33 PM System Log

THERMOSTAT Fan State On Sat 01/03/2009 12:04:10 PM Program Log

THERMOSTAT Status 0░ Sat 01/03/2009 12:04:44 PM System Log

THERMOSTAT Heat Setpoint 18░ Sat 01/03/2009 12:05:16 PM Program Log

THERMOSTAT Status 27░ Sat 01/03/2009 12:05:20 PM System Log

THERMOSTAT Setpoint 18░ Sat 01/03/2009 12:05:53 PM System Log

THERMOSTAT Thermostat Mode Heat Sat 01/03/2009 12:06:37 PM Program Log

THERMOSTAT Humidity 0.23 Sat 01/03/2009 12:07:20 PM System Log

 

Note the "Status 0".

 

Also note the number of entries in each "5 minute" time period varies. Some have 2 lines with values, some have 3 lines. Some show 'Query' and no results, and some are quite comprehensive.

 

Regardless of how good/poor my wireless traffic, I would argue that a zero value should not be assumed unless on poor data packets.

 

Regards

 

Geoff

  • Author

I have captured the event using Event Viewer. I hope this helps.

 

The time of "status" being reported as "0" in the event log shows as 03:06:01 PM

 

The relevant areas of the log are:

 

2009/01/03 15:04:11 : [iNST-SRX ] 02 50 0A.3C.92 0C.A5.CB 41 13 01 LTOFFRR(01)

 

2009/01/03 15:04:12 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00)

 

2009/01/03 15:04:20 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00)

 

2009/01/03 15:04:21 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 32 (32)

 

2009/01/03 15:04:21 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:04:30 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:04:39 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:04:40 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 32 (32)

 

2009/01/03 15:04:41 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:04:49 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:04:50 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 23 6A 18 (18)

 

2009/01/03 15:04:50 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:04:59 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:04:59 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01)

 

2009/01/03 15:04:59 : [ Time] 15:05:29 1(0)

 

2009/01/03 15:05:16 : [ Time] 15:05:46 1(0)

 

2009/01/03 15:05:18 : [iNST-ACK ] 02 62 00.00.21 CF 11 FF 06 LTONRR (FF)

 

2009/01/03 15:05:19 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 07 06 (07)

 

2009/01/03 15:05:28 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 07 06 (07)

 

2009/01/03 15:05:30 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 07 (07)

 

2009/01/03 15:05:30 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00)

 

2009/01/03 15:05:30 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 00 (00)

 

2009/01/03 15:05:31 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:05:39 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:05:40 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 32 (32)

 

2009/01/03 15:05:40 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:05:49 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:05:50 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 18 (18)

 

2009/01/03 15:05:50 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:05:59 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:06:08 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:06:09 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01)

 

2009/01/03 15:06:09 : [ A AD 16 4] ST 255

 

2009/01/03 15:06:09 : [ 9 91 5D 5] ST 255

 

2009/01/03 15:06:09 : [ B E3 76 1] ST 255

 

2009/01/03 15:06:09 : [ E 63 53 1] ST 0

 

2009/01/03 15:06:09 : [iNST-ACK ] 02 62 00.00.24 CF 11 FF 06 LTONRR (FF)

 

2009/01/03 15:06:10 : [iNST-ACK ] 02 62 0E.63.53 0F 6D 24 06 (24)

 

2009/01/03 15:06:12 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6D 24 (24)

 

2009/01/03 15:06:12 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00)

 

2009/01/03 15:06:12 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 00 (00)

 

2009/01/03 15:06:12 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:06:13 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 24 (24)

 

2009/01/03 15:06:13 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:06:22 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:06:23 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 19 (19)

 

2009/01/03 15:06:24 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:06:25 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01)

 

2009/01/03 15:06:26 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 04 06 (04)

 

2009/01/03 15:06:35 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 04 06 (04)

 

2009/01/03 15:06:35 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 04 (04)

 

2009/01/03 15:06:35 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00)

 

2009/01/03 15:06:44 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 00 06 (00)

 

2009/01/03 15:06:46 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 23 6A 32 (32)

 

2009/01/03 15:06:46 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:06:55 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 20 06 (20)

 

2009/01/03 15:06:56 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 24 (24)

 

2009/01/03 15:06:56 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:07:05 : [iNST-ACK ] 02 62 0E.63.53 0F 6A 60 06 (60)

 

2009/01/03 15:07:05 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6A 19 (19)

 

2009/01/03 15:07:05 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:07:14 : [iNST-ACK ] 02 62 0E.63.53 0F 6B 02 06 (02)

 

2009/01/03 15:07:15 : [iNST-SRX ] 02 50 0E.63.53 0C.A5.CB 27 6B 01 (01)

 

2009/01/03 15:07:15 : [ A AA F5 8] ST 255

 

2009/01/03 15:07:15 : [ A AE 44 5] ST 255

 

2009/01/03 15:07:15 : [ 9 91 5D 4] ST 255

 

2009/01/03 15:07:15 : [ E 63 53 1] CLISP 36

 

2009/01/03 15:07:16 : [ E 63 53 1] CLIHUM 25

 

2009/01/03 15:07:16 : [iNST-ACK ] 02 62 00.00.24 CF 11 FF 06 LTONRR (FF)

 

2009/01/03 15:07:16 : [ E 63 53 1] ST 50

Hello CompKing,

 

This has been fixed in 2.6.14 ... just for reassurance, this is a LOG bug where instead of saying Query, the log is just showing 0. In short, those entries are the query REQUEST and not the response.

 

With kind regards,

Michel

  • Author

Thank you for the prompt response. So it sounds to me even though there is a bug in the log, the "fix" will also impact the erroneous impact on my programs which rely on the returned value of the thermostat?

 

Thanks

Hello again,

 

The bug should not impact your programs right now. If you see 0 for the status of your thermostats, then please go to Help->About and let me know the version number.

 

With kind regards,

Michel

 

Thank you for the prompt response. So it sounds to me even though there is a bug in the log, the "fix" will also impact the erroneous impact on my programs which rely on the returned value of the thermostat?

 

Thanks

  • Author
Hello again,

 

The bug should not impact your programs right now. If you see 0 for the status of your thermostats, then please go to Help->About and let me know the version number.

 

With kind regards,

Michel

 

Thank you for the prompt response. So it sounds to me even though there is a bug in the log, the "fix" will also impact the erroneous impact on my programs which rely on the returned value of the thermostat?

 

Thanks

 

I confirm this DOES impact my programs in 2.6.13 (as confirmed with Help -> About)

 

My Product is ISY99/IR Pro (1050)

 

The zero value both triggers a program, shows up in Admin Console device status, and under regular device status on the web interface.

 

Keep in mind I am running in Celcius, not Farenheit.

 

It is intermittent, and a subsequent query of the thermostat will typically clear up the zero value to the proper room temperature.

Hello CompKing,

 

Thanks so very much for the update. I shall have it checked out again though I have not been able to reproduce it under 2.6.13. If another query resolves this, then perhaps we can also move the AccessPoint close to the thermostat to see if it helps the issue.

 

With kind regards,

Michel

 

Hello again,

 

The bug should not impact your programs right now. If you see 0 for the status of your thermostats, then please go to Help->About and let me know the version number.

 

With kind regards,

Michel

 

Thank you for the prompt response. So it sounds to me even though there is a bug in the log, the "fix" will also impact the erroneous impact on my programs which rely on the returned value of the thermostat?

 

Thanks

 

I confirm this DOES impact my programs in 2.6.13 (as confirmed with Help -> About)

 

My Product is ISY99/IR Pro (1050)

 

The zero value both triggers a program, shows up in Admin Console device status, and under regular device status on the web interface.

 

Keep in mind I am running in Celcius, not Farenheit.

 

It is intermittent, and a subsequent query of the thermostat will typically clear up the zero value to the proper room temperature.

  • Author
Hello CompKing,

 

Thanks so very much for the update. I shall have it checked out again though I have not been able to reproduce it under 2.6.13. If another query resolves this, then perhaps we can also move the AccessPoint close to the thermostat to see if it helps the issue.

 

With kind regards,

Michel

 

By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between)

Hello CompKing,

 

I totally agree with you. The main issue is that we have nothing to do with the error detection/correction (the PLM is doing all that) and, as such, we can only report back what the PLM sends back to us.

 

Would you be kind enough to do one more test? Would you move your Access Point back to where it was originally, reboot your thermostat, and retry?

 

With kind regards,

Michel

 

Hello CompKing,

 

Thanks so very much for the update. I shall have it checked out again though I have not been able to reproduce it under 2.6.13. If another query resolves this, then perhaps we can also move the AccessPoint close to the thermostat to see if it helps the issue.

 

With kind regards,

Michel

 

By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between)

  • 2 weeks later...
  • Author
Hello CompKing,

 

I totally agree with you. The main issue is that we have nothing to do with the error detection/correction (the PLM is doing all that) and, as such, we can only report back what the PLM sends back to us.

 

Would you be kind enough to do one more test? Would you move your Access Point back to where it was originally, reboot your thermostat, and retry?

 

With kind regards,

Michel

 

Hello CompKing,

 

Thanks so very much for the update. I shall have it checked out again though I have not been able to reproduce it under 2.6.13. If another query resolves this, then perhaps we can also move the AccessPoint close to the thermostat to see if it helps the issue.

 

With kind regards,

Michel

 

By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between)

 

I haven't been ignoring your response, I have been on vacation. I do note that in the 4ft location that I still do occasionally get 0 thermostat values in my programs, though not as often (once ever 40 hours or so). I can try moving it back to the original location (when I have a sec), and see if the problem worsens. Regardless, even at 4 ft I still get the invalid/zero values.

 

Regards

HI CompKing,

 

We are going to have 2.6.14 released in a few minutes. So, perhaps, it would be best if you tried your experiments with the latest release?

 

With kind regards,

Michel

 

Hello CompKing,

 

I totally agree with you. The main issue is that we have nothing to do with the error detection/correction (the PLM is doing all that) and, as such, we can only report back what the PLM sends back to us.

 

Would you be kind enough to do one more test? Would you move your Access Point back to where it was originally, reboot your thermostat, and retry?

 

With kind regards,

Michel

 

Hello CompKing,

 

Thanks so very much for the update. I shall have it checked out again though I have not been able to reproduce it under 2.6.13. If another query resolves this, then perhaps we can also move the AccessPoint close to the thermostat to see if it helps the issue.

 

With kind regards,

Michel

 

By moving the AP from 40ft to 4ft away from the thermostat module, I have not detected a zero value for the returned value since. It is unfortunate that noise would be interpreted as a zero instead of an invalid result (and thus ignored). I am assuming that noise caused the issue since it did resolve itself, but even 40 ft away shouldn't be a problem (same floor, neighboring room, mostly open space between)

 

I haven't been ignoring your response, I have been on vacation. I do note that in the 4ft location that I still do occasionally get 0 thermostat values in my programs, though not as often (once ever 40 hours or so). I can try moving it back to the original location (when I have a sec), and see if the problem worsens. Regardless, even at 4 ft I still get the invalid/zero values.

 

Regards

  • Author
HI CompKing,

 

We are going to have 2.6.14 released in a few minutes. So, perhaps, it would be best if you tried your experiments with the latest release?

 

With kind regards,

Michel

 

So far, so good. Been almost 24 hours, and no zero's noted. Fingers crossed

Hello CompKing,

 

Thanks so very much for the update.

 

With kind regards,

Michel

 

HI CompKing,

 

We are going to have 2.6.14 released in a few minutes. So, perhaps, it would be best if you tried your experiments with the latest release?

 

With kind regards,

Michel

 

So far, so good. Been almost 24 hours, and no zero's noted. Fingers crossed

Guest
This topic is now closed to further replies.
Go to topic listing

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.