larryllix Posted July 7, 2018 Posted July 7, 2018 Something seems to have changed with NodeLink about two weeks ago. I will try to describe. This has to do with blank fields from NodeLink, found in each node, In particular my two ecobee stats and a Venstar T7900 node setpoint fields. I have a watchdog to monitor the three stat setpoints (6 with heat and A/C) and previously it never reported setpoints too low (< 17.0C each) with ecobee, Internet, or other comm failures. Lately, they are notifying every day or so, and the setpoint temps sent are indicating blank each time. It would seem that the NodeLink reporting has failed (although I never got any heartbeat watchdog fail reports (6 min, allowances) from any of the nodes). The setpoint watchdogs are all instantaneous which could explain the race winner. I am not sure how NodeLink could affect this but nothing in my ISY v5.0.12 changed a few weeks ago. I hope I have installed a successful work-around using "> Lowest setpoint tem" ANDed with "< 17.0C", attempting to detect the ISY condition seeing a blank field as 0c.
rccoleman Posted July 7, 2018 Posted July 7, 2018 Have you tried restarting NodeLink from within the web page (System Config)? Sometimes it seems like the connection to the ISY breaks and restarting NodeLink reestablishes it. Blank fields typically indicate that NodeLink is failing to set those values.
larryllix Posted July 8, 2018 Author Posted July 8, 2018 1 hour ago, rccoleman said: Have you tried restarting NodeLink from within the web page (System Config)? Sometimes it seems like the connection to the ISY breaks and restarting NodeLink reestablishes it. Blank fields typically indicate that NodeLink is failing to set those values. Those fields are filled 99.9% of the time and the situation is always fleeting. I have never been able to get admin console running to see program statuses before it returns. I don't see how NodeLink could change how the ISY logic interprets a blanks field but I don't understand how the fields are made to be blank and since I have accumulated a screen full of ecobee server flops, it is time to clear the list anyway.
io_guy Posted July 8, 2018 Posted July 8, 2018 13 hours ago, larryllix said: Lately, they are notifying every day or so, and the setpoint temps sent are indicating blank each time. What does this mean? Not following what you're saying at all.
larryllix Posted July 8, 2018 Author Posted July 8, 2018 2 hours ago, io_guy said: What does this mean? Not following what you're saying at all. I have a program....simplified it looks like this. If stat.temp < 17.0 c AND <----work around added now. stat.temp >= 5.0c Then Notify Larry 'setpoint error' Else ------ When ecobee server would go down, or ISY would power cycle, and the stat setpoint field would be blank until updated but I was never notified. Now the program sends a notification on a regular basis, since about two weeks ago. One or more fields directly from the stat nodes are sent blank when this happens, like this. Gathering Room setpoint: 21.5c Rec Room setpoint: c Utility Room: 22c I am not sure if / how NodeLink data could possibly affect this internal logic response in ISY logic. I do not understand how ISY programs interpret a blank field as a numeric, but the interpretation logic seems to have changed about 2 weeks ago. The notifications have been happening every few days now. I have added the blue lines attempting to circumvent the problem.
io_guy Posted July 8, 2018 Posted July 8, 2018 If you enable NodeLink's system config debug you can see exactly what is being sent to the ISY and match it to when you get the ISY notification.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.