New Version

[hart2hart]

I just installed the new version and nodelink no longer responds to browser.  Maybe getting ahead of myself I just used the scripts you devloped to install it again and it responded to the browser with what looked to be my nodes.  Thought I would restart nodelink to confirm all is well and it will not respond via browser.

 

EDIT.  I reinstalled again and rebooted RPi and its now running v0.10.6 and forced me to update nodedefs.  Don't think it changed any definitions.

[hart2hart]

Getting the following error from web console.  I compared the config.xml before and after update and definition are the same

 

2020-08-07 19:22:22 - ISY Error: Error setting node value - Failed to compare two elements in the array.
2020-08-07 19:26:06 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_flow1_air08549/report/status/GV1/99.27000000000001/31)
2020-08-07 19:26:36 - ISY Error: Web Error (FAILED) - NotFound (ns/1/nodes/n001_flow1_air08549/report/status/GV1/99.27000000000001/31)
 

 

Log file and screen capture of that node showing in ISY console attached.

logfile_2020-08-07.txt

[io_guy]

You may not see changes when a nodedef file is updated, the changes may be for a device you don't have installed.

Do you have WeatherFlow set to metric or US on the NodeLink config page?  If US can you give me a debug log to see the data?

[hart2hart]

28 minutes ago, io_guy said:

You may not see changes when a nodedef file is updated, the changes may be for a device you don't have installed.

Do you have WeatherFlow set to metric or US on the NodeLink config page?  If US can you give me a debug log to see the data?

io_guy,   it is so great to hear from you. It is set to US.  Just before reading your reply, I deleted the WeatherFlow node and added it back and it appears to be working.  All the node references to items remained the same verified by looking at programs.

[io_guy]

OK, I asked because that was changed in this version (you wouldn't see it in the nodedef file).

Personally I'm not a fan of the static units defined in the nodedef files (US vs. metric schemes).  It's done this was as this was the recommended path by UDI.  However there is the ability to switch these on the fly and not mess up the nodedef.  I do this on my newer devices.  Unfortunately this would be a breaking change for nodes already installed in the ISY.  So I plan to do this when I move NodeLink to NET 5 later in this year.

[hart2hart]

1 hour ago, io_guy said:

OK, I asked because that was changed in this version (you wouldn't see it in the nodedef file).

Personally I'm not a fan of the static units defined in the nodedef files (US vs. metric schemes).  It's done this was as this was the recommended path by UDI.  However there is the ability to switch these on the fly and not mess up the nodedef.  I do this on my newer devices.  Unfortunately this would be a breaking change for nodes already installed in the ISY.  So I plan to do this when I move NodeLink to NET 5 later in this year.

As always you were correct  I spoke too soon because the issue is still there.  The debug log file has serial numbers so  I've attached it to a private message

[hart2hart]

Also, ISY heartbeat programs for each node is failing.

[io_guy]

The heartbeat will fail because the other send fails.  NodeLink uses a single queue for all sends to avoid flooding the ISY.  On failure the queue just builds and continues to retry the current step.

[hart2hart]

The heartbeat will fail because the other send fails.  NodeLink uses a single queue for all sends to avoid flooding the ISY.  On failure the queue just builds and continues to retry the current step.

Thanks. I could see that heartbeat cleared up with test build. Thanks for everything. My Home Automation environment is vastly more integrated and improved via original xxxLink programs and then NodeLink.