hart2hart

I'm using thermostat heat and cool nodes in scenes. Even though , information frequently does not reflect correctly in ISY and MobiLinc the scenes do appear to work as expected.

I've read online and manual and it appears to me that when thermostat is plugged in it should respond to query including current temp. This would enable programs to keep information in sync. I'm calling them to see what's wrong. Just to make sure I understand when ISY queries a device ,it simply processes what is returned. In other words, ISY does not qualify what it is requesting.?

I've been busy replacing with dual band devices and assorted other INSTEON and zwave projects. Want to let it all settle before I upgrade firmware. I'll do upgrade next couple weeks and report on new feature.

That exactly what I've been seeing. Take a blow dryer and get temp to about 90 for a minute and it'll report temp. In effect you have to prime the pump if normal temps are in narrow range since query does not work.

Thanks. Does that mean you get nothing or just not current temp.. I get set points, mode, fan mode and humidity and can see update.

Stusview,s, thanks for the information. Techman, I'm running FW V.0E. You're descriptions confirm what I thought. The issue is two thermostats a matter of few feet from Access Point and other PLM do not report current temp on any regular schedule or degree change that I can see (used blow dryer test) -- and more importantly, current temp is not returned when queried (looked at many level 3 event logs and saw one that may have been from cooling down from a blow dryer test that was coincidental with query). Worst of all, when current temp is displayed, a query renders it blank including the 3am query all version. In addition, on ISY side, the Heat Mode Node can be On but the Thermostat Heat/Cool state will be blank. All this gets compounded when a power failure occurs. Stusviews, What do you mean by "The display is updated on a 2º change, but the ISY does not monitor the display."? Are you saying ISY does not listen for Insteon messages from thermostat or that thermostat does not send Insteon messages on 2 degree changes. Sorry to be dense, but I feel I'm missing something here. Again thanks to all. I really want this to work.

Yes Stand-alone Yes 2 times

Yeah I can see temp reported at .5 level when it bothers to report. I. believe SOME MATERIAL specifically says a 2 degree change is required before an update is reported. Can't locate it right now but it does say it reports :00 :15 :30 :45. each hour on page 23. of manual. The problem is it's not clear difference when acting as standalone vs as slave/master to a wired 2441TH. On page 18 of manual sub mode 9 activation time that can be set from 5 to 20 minutes. What is this setting.? From details section on SH website. "Temperatures from the linked INSTEON Thermostat, Wireless Thermostat and/or Waterproof Temperature Sensor are displayed in smaller digits centered above the main temperature display in positions 2 and 3, with the master thermostat featuring "Master" below its temperature reading. The display information updates every time the temperature sensed changes by 2°. In other words. What are we supposed to expect if different environments.. I'm not happy with it. I'll be calling SH soon To see how all this fits together. ... Unless someone here already knows.

Something is wrong with this tstat. It does not keep the current temp even close to updated on ISY and I've got them on AC adapters. Humidity is sent routinely. You Can't query to get current temp. In fact, the nightly query all causes current temp to be lost. An ISY Reboot results in unpredictable tstat display including mode and current state. To get results close to desired I've used the heat and cool nodes in scenes. Also got several programs looking for conditions and attempting repair. However, these are all workarounds. I would like to see current temp. Are Others having issues so we can raise voice at SH? Documentation says change of 2 degrees are reported but it appears that at startup does not get state via query so a 2 degree change required for first reading.

Thanks. I'll look at PC based and Android apps for Bluetooth snooping for future reference. At some point maybe find a device that could be directed via REST command to issue a Bluetooth command. Global cache does it for IR maybe somebody does it for Bluetooth.

I don't have bed yet but downloaded app. You are correct because the first thing the app wanted to do was pair iPad with bed via Bluetooth. Again, I'm not going to spend any time but out of curiosity can Bluetooth be snooped (like wire shark) and then reverse engineered?

In theory can Bluetooth be manipulated? No intention of going further.

Just downloaded iOS app. The app can control bed setting but it is via paired Bluetooth not as a back and forth to cloud which is how demo appeared so in essence app is the same as their controller.

It looks like you control Sleep settings from iPad arrive at bed via a SleepIQ cloud service. My question is has anyone listened to Wifi via Wireshark and or decoded the commands coming back so it could be automated with ISY. My friend says best thing to do is set it at 100 each week and then lower it to your setting to calibrate. Sounds kinda ridiculous but interesting at same time.

Resolved Thanks to Steve Lee for reminding me to test in smaller segments. There is nothing wrong with structure or logic of the programs. It is more fundamental to the fact that the program at issue is disabled. For anyone else that attempts, hopefully following describes: A program Runs If a disabled program and the Then branch of disabled program is evaluated true based on a variable (State1) value. You can see the disabled program "Running Then" since it has a wait 10 minute command in the then branch. Now one can change the value of the variable (State1) so that the Then branch is no longer true but ISY does not re-evaluate and hence does not stop the program. I changed variable (State1) via REST and just by simply updating variable in Admin console with same results. This behavior was not what I originally expected given that disabled program was "Running Then" but because program was disabled I understand why it would not be in ISY data structure containing programs being constantly (re-)evaluated. I accomplished required using: 'Garage:Garage Doors Opened So Check for Intruder' If Control 'Garage / Garage:Double Door is Closed' is switched Off Or Control 'Garage / Garage:Single Door is Closed' is switched Off Then Run Program 'Garage:Garage Doors Opened Are We Leaving with Exit Delay' (If) Wait 10 minutes Run Program 'Garage:Garage Doors Opened Have We Arrived Home' (If) Wait 15 seconds Send Notification to 'JPaulText' content 'Garage Possible Intruder' Else - No Actions - (To add one, press 'Action') ---------------------- 'Garage:Garage Doors Opened Are We Leaving with Exit Delay' (Disabled Program) If $SecSys_Exit_Delay is 1 (variable set direct by DSCLink via REST from DSC Alarm Panel) Then Stop program 'Garage:Garage Doors Opened So Check for Intruder' Else - No Actions - (To add one, press 'Action') ------------------------------------ 'Garage:Garage Doors Opened Have We Arrived Home' (Disabled Program) If $SecSys_Armed is 0 ($SecSys_Armed_Away & $SecSys_Armed_Stay from DSCLink via REST were combined into one variable through simple program already in use) Then Stop program 'Garage:Garage Doors Opened So Check for Intruder' Else - No Actions - (To add one, press 'Action') There may be a simpler and more straight forward method to accomplish but today it works. I'm blind for now will consider refactoring later.

I don't know correct answer or if you can always predict. However, depending on circumstances, you might consider a method so you force the order of events. Example below will provide method of ordering events but will have issues if your four programs have different Else statements. Program Overall If Some Condition Run Program A (Then) Wait X seconds (as desired of not) Run Program B (Then) Wait X seconds Run Program C (Then) Wait X seconds Run Program D (Then) Else As noted if Else clause for A-D required then this is probably not right method. Programs A,B,C, and D would not have an If statement.

Anyone from UD see where I've gone wrong or is this a genuine issue?

DSCLink Screen captures occurred between 6:03 and 6:06. Relevant variable changed at 5:58:53 per listing of variables.

I've got a series of programs that monitor for the garage doors to open. Once they open ISY runs a program to see if you are within 10 minutes of the start of exit delay (aka leaving home). Then it checks to see if the security is system is armed either Away or Stay. The variables that indicate Stay or away or set to 0 indicating not armed within seconds of event (by DSCLink) happening but I am getting text indicating someone may have forced their way into the garage and are awaiting someone to return home. Per screen captures of the actual event in progress what am I missing? This happens frequently so I ran inside after arriving home and captured these images while all was in progress and sure enough after 10 minutes I received text saying "possible intruder". Obviously, I'm doing something very wrong (and am completely blind to it) or ISY is not seeing the State variable (in this case Armed Away) change from 1 to 0. Capture of program that determines if you are exiting are possibly have an intruder Program it runs as part of else to see if system is armed and gives me 10 minutes to get into house (program Disabled so only run as request by other program) Evidence that program is running the Then clause Even though both armed away and armed stay have been set to 0

Techman thanks. Based on advice here I stopped using temp and started using the heat and cool ctl devices. It reacts much faster and allows better control. My issue has become making sure it stays in correct mode and set point. Back to original question, what have people seen when Tstat loses power? Does ISY need to monitor and get it back in last state?

After the factory reset, its working as expected updating for 2 degree changes. I've got it controlling a heater via appliancelinc for my dog. It appears from reading a little testing that if the thermostat loses power, (attached to AC and batteries installed but just in case) it starts up in Mode Off. Have others confirmed this to be the case. I'm guessing I need to create programs to restore mode and setpoints? at startup of if Mode shows as Off. Can anyone confirm what they have done before I experiment to confirm tstat behavior? Thanks

As a final effort of the day, I removed from ISY and did a factory reset on Tstat. (manual says if you get a two digit error code call SH -- I got 00 which would not usually be an error but I'll call?) I added it back to ISY. To test I did a query and it did give ST of 138 but a few minutes later I performed query again and ST was not returned and even further the displayed Current Status value of 69 on ISY device screen was cleared. Log of Query returning Temp/Status follows: It is not updating Temperature but appears to update Humidity. Temp is at 69 but will rise with blow dryer test. Sun 12/14/2014 08:58:06 PM : [iNST-TX-I2CS] 02 62 22 0D 10 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 Sun 12/14/2014 08:58:06 PM : [iNST-ACK ] 02 62 22.0D.10 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02) Sun 12/14/2014 08:58:09 PM : [iNST-SRX ] 02 50 22.0D.10 30.6C.0B 03 6E 8A (8A) Sun 12/14/2014 08:58:09 PM : [std-Direct ] 22.0D.10-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 12/14/2014 08:58:09 PM : [D2D EVENT ] Event [22 D 10 1] [sT] [138] uom=0 prec=-1 Sun 12/14/2014 08:58:09 PM : [ 22 D 10 1] ST 138 Sun 12/14/2014 08:58:18 PM : [iNST-TX-I2CS] 02 62 22 0D 10 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 Sun 12/14/2014 08:58:18 PM : [iNST-ACK ] 02 62 22.0D.10 1F 2E 02 00 00 00 00 00 00 00 00 00 00 00 00 92 96 06 (02) Sun 12/14/2014 08:58:19 PM : [iNST-SRX ] 02 50 22.0D.10 30.6C.0B 2B 2E 02 (02) Sun 12/14/2014 08:58:19 PM : [std-Direct Ack] 22.0D.10-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/14/2014 08:58:20 PM : [iNST-ERX ] 02 51 22 0D 10 30 6C 0B 11 2E 02 01 01 0C 0C 37 00 50 26 00 D0 A0 3C 32 C9 Sun 12/14/2014 08:58:20 PM : [Ext-Direct ] 22.0D.10-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sun 12/14/2014 08:58:20 PM : [D2D EVENT ] Event [22 D 10 1] [CLISPC] [160] uom=0 prec=-1 Sun 12/14/2014 08:58:20 PM : [ 22 D 10 1] CLISPC 160 Sun 12/14/2014 08:58:20 PM : [D2D EVENT ] Event [22 D 10 1] [CLISPH] [120] uom=0 prec=-1 Sun 12/14/2014 08:58:20 PM : [ 22 D 10 1] CLISPH 120 Sun 12/14/2014 08:58:20 PM : [D2D EVENT ] Event [22 D 10 1] [CLIHUM] [38] uom=0 prec=-1 Sun 12/14/2014 08:58:20 PM : [ 22 D 10 1] CLIHUM 38 Sun 12/14/2014 08:58:20 PM : [iNST-TX-I2CS] 02 62 22 0D 10 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 Sun 12/14/2014 08:58:20 PM : [iNST-ACK ] 02 62 22.0D.10 1F 2E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 D2 06 (00) Sun 12/14/2014 08:58:21 PM : [iNST-SRX ] 02 50 22.0D.10 30.6C.0B 2B 2E 00 (00) Sun 12/14/2014 08:58:21 PM : [std-Direct Ack] 22.0D.10-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/14/2014 08:58:21 PM : [iNST-ERX ] 02 51 22 0D 10 30 6C 0B 11 2E 00 00 01 00 D0 26 F8 EB 00 00 0A 05 04 00 00 Sun 12/14/2014 08:58:21 PM : [Ext-Direct ] 22.0D.10-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sun 12/14/2014 08:58:21 PM : [iNST-TX-I1 ] 02 62 1F C3 DD 0F 19 01 Sun 12/14/2014 08:58:22 PM : [iNST-ACK ] 02 62 1F.C3.DD 0F 19 01 06 LTSREQ (01) Sun 12/14/2014 08:58:22 PM : [iNST-ERX ] 02 51 22 0D 10 30 6C 0B 12 D1 C0 00 01 00 D0 26 F8 EB 00 00 0A 05 04 00 00 Sun 12/14/2014 08:58:22 PM : [Ext-Direct ] 22.0D.10-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Sun 12/14/2014 08:58:22 PM : [iNST-SRX ] 02 50 1F.C3.DD 30.6C.0B 2F 03 00 (00) Sun 12/14/2014 08:58:22 PM : [std-Direct Ack] 1F.C3.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Sun 12/14/2014 08:58:22 PM : [iNST-TX-I1 ] 02 62 1F C3 DD 0F 19 00 Sun 12/14/2014 08:58:22 PM : [iNST-ACK ] 02 62 1F.C3.DD 0F 19 00 06 LTSREQ (LIGHT) Sun 12/14/2014 08:58:23 PM : [iNST-SRX ] 02 50 1F.C3.DD 30.6C.0B 2B 03 00 (00) Sun 12/14/2014 08:58:23 PM : [std-Direct Ack] 1F.C3.DD-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 12/14/2014 08:58:23 PM : [D2D EVENT ] Event [22 D 10 1] [CLIMD] [0] uom=0 prec=-1 Sun 12/14/2014 08:58:23 PM : [ 22 D 10 1] CLIMD 0 Sun 12/14/2014 08:58:23 PM : [D2D EVENT ] Event [22 D 10 1] [CLIFS] [8] uom=0 prec=-1 Sun 12/14/2014 08:58:23 PM : [ 22 D 10 1] CLIFS 8 Sun 12/14/2014 08:58:23 PM : [D2D EVENT ] Event [22 D 10 1] [uOM] [2] uom=0 prec=-1 Sun 12/14/2014 08:58:23 PM : [ 22 D 10 1] UOM 2 Sun 12/14/2014 08:58:23 PM : [D2D EVENT ] Event [1F C3 DD 1] [sT] [0] uom=0 prec=-1 Sun 12/14/2014 08:58:23 PM : [ 1F C3 DD 1] ST 0 Sun 12/14/2014 08:58:23 PM : [D2D-CMP 00B7] STS [1F C3 DD 1] ST op=1 Event(val=0 uom=0 prec=-1) is Condition(val=0 uom=0 prec=-1) --> true

Techman, I'd be happy if it updated when it changed and I blew hot air on it several times yesterday to test. The problem is it does not update itself for changes or when queried. Btw it does return humidity when queried.

Lee, thanks for extra effort. I'm still wondering if section from page 13 of user manual indicates it can do more with a different software link mode. Funny thing is it has reported temp on its own. Just not sure cause. From page 13 including footnote. INSTEON ProgrammingAdd INSTEON Wireless Thermostat as a ControllerINSTEON Wireless Thermostat can be set up to control other INSTEON devices or trigger software events when there is a change. The following INSTEON Wireless Thermostat changes can be configured as a controller (note that when linked to an INSTEON Thermostat, these commands will not function):• Group 1 - Cooling mode change (scene control)• Group 2 - Heating mode change (scene control)• Group 3 - Dehumidification, high humidity setpoint (scene control)• Group 4 - Humidification, low humidity setpoint (scene control)• Group EF - Broadcast on any change (notification group for linked software controllers)1 1 Group EF is a hexadecimal representation of Group 254 and can only be configured using software

I read full user manual and it speaks of link mode type EF on page 13 of manual. Footnote says can only be set by software and I don't see this in ISY interface. Is this what I'm missing?