Is there a published or easy method to upgrade an existing installation of NodeLink?

 

 

Thanks!

Install new zip file in ISY and reboot it, overwrite NodeLink.exe (or let it auto-update).

 

Eventually NodeLink will auto-update the ISY but right now that appears to be broken in V5.

 

I was debating creating some sort of zip version tracking to alert user if the zip needs updating but I have no idea what UDI are planning on their side.

Install new zip file in ISY and reboot it, overwrite NodeLink.exe (or let it auto-update).

 

Eventually NodeLink will auto-update the ISY but right now that appears to be broken in V5.

 

I was debating creating some sort of zip version tracking to alert user if the zip needs updating but I have no idea what UDI are planning on their side.

Thanks!

 

I had the "NodeLink AutoUpdate" turned on and it was already updated to v3.0.

 

I found the nodesetup.zip file (could be a little easier to locate and version number could help the user's "confirmed feeling"), loaded the new profile via  ISY Node menu pulldown, and rebooted.

 

IIRC, when doing the initial install a reboot didn't get it  and a power cycle seemed to be necessary.

I can't detect any version change etc. How do I know if ISY was successful installing anything different?

 

Thanks again for great stuff.

Can't help ya, that's all ISY related. Right now there's no way.

Hi io_guy,

I just updated my nodelink to 0.8.8 version. After successfully updating the profile and nodelink, i started seeing this error log from the Nodelink.

2017-12-27 20:27:30 - Subscription Error: ISY Decode Error: <Event seqnum="1" sid="uuid:29"><control>_4</control><action>6</action><node></node><eventInfo><status>1</status></eventInfo></Event>8
2017-12-27 20:27:31 - DSC: System Status - Disarmed (Set By Status Request - Partition 1) [dsc1]
2017-12-27 20:27:31 - Subscription Error: ISY Decode Error: <Event seqnum="113" sid="uuid:29"><control>_4</control><action>6</action><node></node><eventInfo><status>1</status></eventInfo></Event><

Do you have any idea why I am getting this error?

 

Thanks,

Yea,

NodeLink used to decode the subscription using brute force on text strings.  I've switched to using proper XML parsing, meaning if the incoming packet is corrupt you'll see the errors above.

 

You can see for example, an extra "8" at the end of your first string - not supposed to be there.  I've added additional clean-up to the next version to clear any extra crap at the end of strings prior to sending it to the parser, that'll fix your examples above.  You may still see some of these errors if the extra characters are in the middle of the packet - nothing I can do there.