hart2hart

I have a 2 zone HVAC system controlled by a Honeywell HZ322 zone panel including a DAT sensor (DATS). If the DATS (or potentially the HZ322) goes bad, the system may indicate heating (or cooling) but the temperature will continue to fall (or rise with cooling). This just happened to me in the very cold weather as my DATS failed after we went to bed, and it just got colder until the shivering woke me up I knew a little bit about how to troubleshoot the HVAC system and was able to disable the DATS through the HZ322 panel. The system has been running for almost a week and a half just fine. The major issue was the internal temperatures dropped several degrees quickly as the outside temp was around -10 F. It took the HVAC system many hours to catch up and replace the heat in the air, floors, walls, and materials. It would have been so much better to have caught it sooner. I wrote the following programs that would work in conjunction with the VenstarCT node server to catch situations of Heating but inside temperature is falling and Cooling but inside temperature is rising. It feels like it was too easy so can great forum members provide insights of what I've missed. Heat programs. First one should trigger when heat comes on and grab current temperature (may also INIT variable too for possible mid cycle restarts) and enable the Heat Monitor program to see if temperature falls any way (realize I may have to give one degree leeway to prevent false alerts but will start here). When the state is no longer heating it disables the monitor program. I will add a run at startup program for reboots to ensure the monitor program is in proper enabled state. Great Room:Heat On If 'Great / Great Thermostat' Heat/Cool State is Heating Then $HVAC_GreatRoom_Start_Tempature_I = 'Great / Great Thermostat' Temperature °F Enable Program 'Great Room:Heat Monitor_NE' Else Disable Program 'Great Room:Heat Monitor_NE' Great Room:Heat Monitor_NE - [Not Enabled] If 'Great / Great Thermostat' Temperature <= '$HVAC_GreatRoom_Start_Tempature_I Fahrenheit' Then Send Notification to 'JPaulText' content 'Heat On But Temperature Is Falling' Else - No Actions - (To add one, press 'Action') Cool Programs. Same construct but obviously opposite direction. Great Room:Cool On If 'Great / Great Thermostat' Heat/Cool State is Cooling Then $HVAC_GreatRoom_Start_Tempature_I = 'Great / Great Thermostat' Temperature °F Enable Program 'Great Room:Cool Monitor_NE' Else Disable Program 'Great Room:Cool Monitor_NE' Great Room:Cool Monitor_NE - [Not Enabled] If 'Great / Great Thermostat' Temperature >= '$HVAC_GreatRoom_Start_Tempature_I Fahrenheit' Then Send Notification to 'JPaulText' content 'Cool On But Temperature Is Rising' Else - No Actions - (To add one, press 'Action')

@Goose66 It was my garage based access point rebooting.

I opened and closed both doors. Doors listed as Closed and Lights On then Off. Less than 20 minutes later, all status are Unknown.

Thanks. Do you think they’re going offline as in WiFi dropped or power lost? Suggestion on how can I monitor?

@Goose66 After some amount time the Garage Door Opener Door State and Lockout Status are becoming Unknown. The Light Module Status is doing the same.

I just installed and discovered two ratgdos on Chamberlin Security 2.0+ doors. I can control both doors and lights. However, I was very surprised that I didn't have to learn the ratgdo as a controller in the rolling code scheme -- they just worked first try. How did this happen? The value of Obstruction is "Clear" for one door and "Unknown" for other door after multiple open/close cycles. Does this mean I've not got good contact on the black sensor wire?

Upgraded to 13.2p9. Thanks Michel and UDI team!

When I disarmed the security system this morning, I could see something was not right. I have an 8 button insteon keypad by the alarm panel and the Hot Water recirculating pump button did not light up. I turn the pump off when security is armed away and security stay. Disarming the alarm should have turned it on. On rare occasions the Insteon message would get lost, but I had created the program with automatic resends to the keypad about 15 seconds apart. Also created a program that looks at status every 30 minutes as a fail-safe. Walked to counter and picked up my phone to see texts that devices can't communicate to cloud (Flume, Ring, and Envisalink among them). Turns out the cable modem lost connection last night. I rebooted it and saw texts for things being back online and confirmed it was good. With that fixed, I looked at the Hot Water Pump issue. First thing I looked at was the Envisalink node server which was showing online for about 17 minutes which is about the time since I left the equipment rack from restarting cable modem. Could it be that even though the Envisalink device is local control that if the sidekick cellular backup is invoked that the Envisalink will stop communicating locally via wired IP? I'll likely enter an issue with them but wanted to seek any knowledge and advice from other users using same tech as me.

Mine has been great but I’ll always tak better. [emoji6]How long does the update run?

I’m sorry. I should have been clearer that you were describing something in option 2 that was parallel to Ring node server which works very well for me. I should have just said here’s my vote for option 2. Again, thank you.

I looked at my Ring Camera NS devices where I can detect their motion actions. Each camera is virtualized as a Light and a Motion Node: http://d2z8ydsemzif1x.cloudfront.net/monthly_2024_01/image.jpeg.fbd961bd3a3d70bc0e082e532297193c.jpeg and the node values for Motion are: http://d2z8ydsemzif1x.cloudfront.net/monthly_2024_01/image.thumb.jpeg.1415b311bd0859ac5b990ab38c0f9c11.jpeg In programs to detect motion, you code as: http://d2z8ydsemzif1x.cloudfront.net/monthly_2024_01/image.jpeg.7589c1d10585a4b56f2018a5f55ae33e.jpeg and that translates to: If 'Ring / Ring / Back Porch (Motion)' is switched Motion This scheme works well for 4 Ring cameras on outside of my house. Given that The Ring Motion node has Motion action and not a status of Motion, it appears to be similar to what we have with ratgdo. How opposed are you to adding the node and having it say "None" for those without a motion capable keypad? Thanks again, @Goose66. My two ratdgo arrive Tuesday!

Motion detection would be a bonus and if the work arounds get us there — great. If it’s not a big lift, it feels like getting in on ratgdo issues list and seeing if author thinks it’s worthwhile is reasonable. Personally, I’m good either way since it’s already fantastic solution. Thanks

Thanks. My ratgdo devices have not arrived yet so I’m doing a bit of preparatory planning. Can I do the mqtt clear after say 2 minutes within a iox program? Could motion be detected using If Control (with logic to prevent continuous issues) vs If Status? If not, do we ask @Goose66 if it can be done in the node server?

I have the keypads that include the motion detector and the ratgdo documentation mentions some support for them. Does the node server support their use? It would be very handy and likely replace the need for an old battery powered insteon MS.

Thank you, @Goose66 I’m looking forward to arrival ratgdo devices so I can put it all in place.

Upgraded. Thanks UDI!

@Goose66, thanks. After changing sensor type setting on the physical thermostat from Outdoor to Remote and doing testing all is working well.

I’d guess your IP setup has an issue. Specifically, your DNS server IP addresses are not set up correctly so rpi can’t resolve automationshack.com.

Adding a bit more information... The log entry about "Outdoor" has now changed to "Remote" after I changed the Sensor Type. It is updating the NS with the correct temperature. Does the CoolTouch API designate the sensor by type -- appears so from log? I'm a little surprised that they would do this as you can only have one wired sensor, but then I recall they added a WiFi sensor so maybe that's why the type is so important. I've had a WiFi sensor still in its box for a few years. If I can find it do, we want to experiment with adding it to thermostat and see what types it can be set to... To me, clearly now me changing the Sensor Type from Remote to Outdoor was the root cause of my issue but its discovery will likely add to the cause. 2023-12-28 06:53:03,643 Thread-3455 udi_interface DEBUG venstarapi:_call_api: HTTP GET http://192.168.1.183/query/sensors data: None 2023-12-28 06:53:03,653 Thread-3455 udi_interface DEBUG venstarapi:_call_api: HTTP response code: 200 data: {"sensors":[{"name":"Thermostat","temp":72.0,"hum":40},{"name":"Space Temp","temp":72.0},{"name":"Remote","temp":33.0}]} 2023-12-28 06:53:03,653 Thread-3455 udi_interface.node DEBUG node:setDriver: c0a801b7_s0:Thermostat No change in ST's value 2023-12-28 06:53:03,654 Thread-3455 udi_interface.node DEBUG node:setDriver: c0a801b7_s0:Thermostat No change in BATLVL's value 2023-12-28 06:53:03,654 Thread-3455 udi_interface.node DEBUG node:setDriver: c0a801b7_s1:Remote No change in ST's value 2023-12-28 06:53:03,654 Thread-3455 udi_interface.node DEBUG node:setDriver: c0a801b7_s1:Remote No change in BATLVL's value

You can't name it in the thermostat. All you can do is pick a type: o Outdoor o Remote o Supply o Return It's only been a little while since I made the change I mentioned so should have recalled it better. Anyways, thinking it was originally set to Remote at the time of discovery and I "corrected it" and set it to Outdoor which is where the sensor was and is located. I just reset it to sensor type of Remote and the NS appears to be getting the correct temp now -- I'll have to wait to see if it changes with as temp changes to be sure. Is there any way to confirm it was originally Remote at time of discovery and that my changing it to Outdoors created this issue. The thermostat shows the Outside Temp at a nearby weather reporting station unless the sensor is set to Outdoor. When set to Outdoor, the thermostat displays the sensor reading as outside in climate displays which is why I adjusted it. The point was so I could quickly see the outside reading on thermostat face very easy to confirm some programming actions based on outdoor temp. Additionally, and in some cases more important is that my true local temp is usally 2-4 degrees off from distant official weather stations like at the Nashville Airport. I'm wondering if there is an issue when selecting the sensor type of Outside instead of Remote in that it does something different with the NS. I renamed two other remote sensors on the other thermostats, and they continue to register correctly. I just reviewed my topology listings that I save after all changes and the name always shows Outdoor Temp Sensor. Again, I think, I changed the type and not the name. Again, Thanks for looking at this and hoping it means new knowledge of the NS related to the wired sensor.

@Goose66 sorry but I’m lost again. All the names for the node in IOx AC and PG3x Nodes are showing as Outdoor Temp Sensor. Where are you seeing Outdoor? In retrospect, I do recall trying to give it that name in AC and then going back to the original name in same session. I see the following in the log but can't find a place to rename it. 2023-12-27 18:20:24,517 Thread-44 udi_interface DEBUG venstarapi:getThermostatState: in API getThermostatState()... 2023-12-27 18:20:24,518 Thread-44 udi_interface DEBUG venstarapi:_call_api: HTTP GET http://192.168.1.183/query/info data: None 2023-12-27 18:20:24,521 Thread-43 udi_interface DEBUG venstarapi:_call_api: HTTP response code: 200 data: {"sensors":[{"name":"Thermostat","temp":71.0,"hum":47},{"name":"Space Temp","temp":71.0},{"name":"Outdoor","temp":49.0}]} 2023-12-27 18:20:24,522 Thread-43 udi_interface DEBUG venstarapi:getRuntimes: in API getSensorState()... 2023-12-27 18:20:24,522 Thread-43 udi_interface DEBUG venstarapi:_call_api: HTTP GET http://192.168.1.183/query/runtimes data: None 2023-12-27 18:20:24,545 Thread-44 udi_interface DEBUG venstarapi:_call_api: HTTP response code: 200 data: {"name":"Great Room","mode":1,"state":0,"fan":0,"fanstate":1,"tempunits":0,"schedule":0,"schedulepart":255,"away":0,"spacetemp":71.0,"heattemp":71.0,"cooltemp":73.0,"cooltempmin":35.0,"cooltempmax":99.0,"heattempmin":35.0,"heattempmax":99.0,"activestage":0,"hum_active":1,"hum":47,"hum_setpoint":48,"dehum_setpoint":99,"setpointdelta":2.0,"availablemodes":0} 2023-12-27 18:20:24,546 Thread-43 udi_interface DEBUG venstarapi:_call_api: HTTP response code: 200 data: {"runtimes":[{"ts":1703203200,"heat1":351,"heat2":0,"cool1":0,"cool2":0,"aux1":0,"aux2":0,"fc":0},{"ts":1703289600,"heat1":300,"heat2":0,"cool1":0,"cool2":0,"aux1":0,"aux2":0,"fc":0},{"ts":1703376000,"heat1":162,"heat2":0,"cool1":0,"cool2":0,"aux1":0,"aux2":0,"fc":0},{"ts":1703462400,"heat1":68,"heat2":0,"cool1":70,"cool2":0,"aux1":0,"aux2":0,"fc":0},{"ts":1703548800,"heat1":9,"heat2":0,"cool1":0,"cool2":0,"aux1":0,"aux2":0,"fc":0},{"ts":1703635200,"heat1":191,"heat2":0,"cool1":0,"cool2":0,"aux1":0,"aux2":0,"fc":0},{"ts":1703701223,"heat1":361,"heat2":0,"cool1":0,"cool2":0,"aux1":0,"aux2":0,"fc":0}]} 2023-12-27 18:20:24,546 MQTT udi_interface.interface INFO interface:_message: Successfully set c0a801b7 :: GV11 to 0 UOM 25 2023-12-27 18:20:24,547 Thread-44 udi_interface.node DEBUG node:setDriver: c0a801b7:Great Thermostat No change in GV0's value Only thing I see in nodes is: Node Name 3 Address NodeDef Primary Node Hint Enabled Is Primary Delete Outdoor Temp Sensor c0a801b7_s1 SENSOR c0a801b7 16974592 true false Name Driver UOM Value Variable BATLVL 51 0 ${sys.node.n015_c0a801b7_s1.BATLVL} ST 17 79.0 ${sys.node.n015_c0a801b7_s1.ST} From AC:

@Goose66 , thanks so much for figuring that out and sorry as it appears I caused the issue. I’ll simply rename it back to original name.

Isylink is NodeLink and is not managed inside PG3x. You can remove it from AC Nodeservers if you’re not longer using it. I think ISY portal was original integration to Alexa. Can delete it at same way if not using.

After all, I’ve decided to install with USB wall wort. I located and 3D printed a ratgdo case on printables.com which will keep it all tidy and on top of GDO. Now just waiting for boards. Again,thanks for NS and letting me hijack this thread. Happy Holidays.

Thanks, I don’t mind soldering and will likely use the auto adapter. The ratgdo has a 3.3V port but using it appears to require 2 other wires and I only saw an example of it with a version 1.0 as documented in the designers “Solder Method”.