Updated NodeLink from v0.10.6 to v0.11.3 - Encountering Issues!

[GDavis01]

Today I decided to update NodeLink from v0.10.6 to v0.11.3.

I am running v5.0.16C on my ISY.

I have NodeLink running on my Raspberry pi.

I have 2 Venstar stats and therefore 2 nodes; a DSC alarm node; Network Monitor; and ISY Data nodes.

The nodes that seem to be giving me issues are the 2 Venstar and the DSC nodes.

The issue is that the ISY is not updating and the heartbeat is not changing.

Note that after installing the new version on the pi, I ran the command to update the Venstar nodes (http://ISY/rest/ns/1/nodes/n001_ven1/change/Venstar?nls=140V)

I am attaching the log file after I set both of the Venstars and the DSC to debug.

Any thoughts on what is wrong?

logfile_2022-02-27.txt

[hart2hart]

Today I decided to update NodeLink from v0.10.6 to v0.11.3.
I am running v5.0.16C on my ISY.
I have NodeLink running on my Raspberry pi.
I have 2 Venstar stats and therefore 2 nodes; a DSC alarm node; Network Monitor; and ISY Data nodes.
The nodes that seem to be giving me issues are the 2 Venstar and the DSC nodes.
The issue is that the ISY is not updating and the heartbeat is not changing.
Note that after installing the new version on the pi, I ran the command to update the Venstar nodes (http://ISY/rest/ns/1/nodes/n001_ven1/change/Venstar?nls=140V)
I am attaching the log file after I set both of the Venstars and the DSC to debug.
Any thoughts on what is wrong?
logfile_2022-02-27.txt

Io_guy will help you in detail but you need to run

Make sure you ran the install script as the standard update from gui does not move you to .net 5

Execute http://ISY/rest/ns/1/nodes/n001_ven2/change/Venstar?nls=140V to change the second thermostat. Hi

[GDavis01]

Thanks for the reply...

 

I did run the install script which presumably moved me to .net 5. 

I should have explained that, in fact, I had executed the rest command for each Venstar stat.

I did notice that when I ran the script on the Raspberry that it did have an error... attached is a screenshot I took of the error. Perhaps this is causing issues.