hart2hart

Teken: I may try 1-wire out but was just thinking I still have Venstar T1800 thermostats (thought I'd find them a good home with need for full HVAC control) with later version adapters. Am I missing something or could they be used with a 24VAC? power supply and all other leads unconnected? Paul Edit. Already have video recording PC (Run io_guys great xxxLink programs there) so going to focus on adding 1-wire since he already has program in place.

No, Just new version of PLM attached to ISY. I've switched back to using local scenes but in future knowing the cool set point has been reached is not enough. I need to be able to track critical temperature which are higher. I will install SH power supplies so it's not first issue of discussion.. For background, ... I've got a small av closet. When cool set point is reached a scene turns on extra airflow. If temperature continues to rise and gets toward critical., I will turn entire rack off with on/0ff module. I've been off for holidays and putting in HA investment time since I Don't have time to work on this at other times of year. Thanks for you help. At this point I'm concerned this is not right solution. It looked like when plugged in 2441zth reported temp at some rate of change or worst case I could have started querying every 15 minutes once it got to cool set point. At this point current temp is almost never there.

I can't get consistent results so I'm going to contact SH. After installing their specified power supply. Their Doc states that in wired mode it should not be providing these results.

As suspected (but can't confirm why), the current temp was blank this morning with only known activity being 3am query all. In addition, couple more tests show after power cycle of thermostat revealed that ISY was somethimes not seeing Mode of OFF so I added a Wait and Query as seen above in green.

Cant believe I'm working on this tonight. Thank god wife is binge watching a new program on DVR Finally got something that appears to work with one big caveat (maybe specific to my case) -- RF range of Thermostat to Access Point must be in inches once the batteries are removed and running on AC power supply. I've measure voltage at 5.11 vdc on power supply so should be good. Also, only tested a few times so looking for insights. One more note -- I'll be curious what happens at 3am query all. Does anyone think ISY is aware the device is swapping from battery to powered device which could have implications with the way it is handled? Program enabled to run at startup If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'HVAC:Basement Sync Thermostat With ISY' (Then Path) Else - No Actions - (To add one, press 'Action') 'HVAC:Basement Sync Thermostat With ISY' If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Basement / Basement:TStat Power Supply' Off Wait 20 seconds Set 'Basement / Basement:TStat Power Supply' On Wait 10 Seconds Set 'Basement / Basement:Thermostat' Query Else - No Actions - (To add one, press 'Action') Program that runs to force thermostat into Heat Mode If $Thermostat_Basement_Mode_Manual_Set is 1 And Status 'Basement / Basement:Thermostat' is not Mode Heat Then Wait 30 seconds Set 'Basement / Basement:Thermostat' Mode Heat Wait 5 Seconds Set 'Basement / Basement:Thermostat' Query --- Query command required to get mode change above to reflect on ISY and trigger next program and stop this program Wait 10 seconds Send Notification to 'JPaulText' content 'HVAC Wireless Issue' Else - No Actions - (To add one, press 'Action') Program to set Heat Mode Set Point If Status 'Basement / Basement:Thermostat' is Mode Heat Then Wait 10 seconds Set 'Basement / Basement:Thermostat' 68° (Heat Setpoint) Wait 5 seconds Set 'Basement / Basement:Thermostat' Query Else - No Actions - (To add one, press 'Action') Program to attempt to correct not responding and report it if still bad If Status 'Basement / Basement:Thermostat' is not Responding Then Wait 15 seconds Run Program 'HVAC:Basement Sync Thermostat With ISY' (Then Path) Wait 1 minute Send Notification to 'JPaulText' content 'HVAC Wireless Issue' Else - No Actions - (To add one, press 'Action')

It is a state variable. I guess smokegrub and I think alike. I had gone extra step of controlling tstat mode via MobiLinc or ISY Console and that I did not trust command to arrive so had included repeats. The point is that after a power failure tstat resumes in correct mode instead of confirmed (mode of off) and if someone changes mode locally it reverts to controlled mode. I did steal the locked in set point from smokegrub's program. Documentation says all settings are stored in eeprom but I don't want to take chance.. Confirmed set points are not stored in eeprom.

I implemented very similar housekeeping programs to keep thermostat and ISY in sync for each mode (Heat/Cool/Off) so in effect thermostat mode is controlled by variable and not thermostat button. The only timing issue I've not fully considered is full power outage -- Thermostat will come online first and send information before ISY has rebooted and can process messages. I think ISY display would be off but thermostat would be in correct mode.This is all brute force and I want thermostat to do correct function by responding to a query fully but so be it I guess. Great idea StusViews --- I've got couple ApplianceLincs that I will put on thermostat power supplies and remove their batteries. With proper wait after startup, I will power them off and then back on so thermostat is synchronized with ISY. What does all think? ---Programs now---- Not in Heat Mode as directed by variable contents If $Thermostat_Basement_Mode_Manual_Set is 1 And Status 'Basement / Basement:Thermostat' is not Mode Heat Then Wait 5 minutes Set 'Basement / Basement:Thermostat' Mode Heat Wait 20 seconds Set 'Basement / Basement:Thermostat' 68° (Heat Setpoint) Wait 30 seconds Set 'Basement / Basement:Thermostat' Mode Heat Wait 20 seconds Set 'Basement / Basement:Thermostat' 68° (Heat Setpoint) Wait 1 minute Send Notification to 'JPaulText' content 'HVAC Wireless Issue' Else - No Actions - (To add one, press 'Action') Missed Heat Off If Status 'Basement / Basement:HVAC Heat Controller' is not Off And ( Status 'Basement / Basement:Thermostat - Heat' is Off ) Then Wait 10 seconds Send Notification to 'JPaulText' content 'HVAC Wireless Issue' Else - No Actions - (To add one, press 'Action') Missed Heat On If Status 'Basement / Basement:HVAC Heat Controller' is not On And ( Status 'Basement / Basement:Thermostat - Heat' is On ) Then Wait 10 seconds Send Notification to 'JPaulText' content 'HVAC Wireless Issue' Else - No Actions - (To add one, press 'Action') Thermostat not Responding (but we know query fails so I'll embed the power off/on method) If Status 'Basement / Basement:Thermostat' is not Responding Then Wait 10 minutes Set 'Basement / Basement:Thermostat' Query Wait 1 minute Set 'Basement / Basement:Thermostat' Query Wait 1 minute Send Notification to 'JPaulText' content 'HVAC Wireless Issue' Else - No Actions - (To add one, press 'Action')

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.