Probably nothing to worry about, but the log on the main page of Nodelink is showing lots of these errors:

...
2018-01-05 09:34:35 - Subscription Error: ISY Decode Error: <Event seqnum="19562" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="1" id="59"><init>2520</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:34:35 - Subscription Error: ISY Decode Error: <Event seqnum="19564" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="2" id="39"><init>2520</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:34:38 - Subscription Error: ISY Decode Error: <Event seqnum="19572" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="2" id="59"><init>318</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:34:38 - Subscription Error: ISY Decode Error: <Event seqnum="19573" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="2" id="60"><init>318</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:35:36 - Subscription Error: ISY Decode Error: <Event seqnum="19611" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="1" id="59"><init>2529</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:35:36 - Subscription Error: ISY Decode Error: <Event seqnum="19613" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="2" id="39"><init>2529</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:36:37 - Subscription Error: ISY Decode Error: <Event seqnum="19655" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="1" id="59"><init>2536</init><prec>0</prec></var></eventInfo></Event>
2018-01-05 09:36:37 - Subscription Error: ISY Decode Error: <Event seqnum="19657" sid="uuid:48"><control>_1</control><action>7</action><node></node><eventInfo><var type="2" id="39"><init>2536</init><prec>0</prec></var></eventInfo></Event>
...

I'm on v5.0.11B firmware with NodeLink v0.8.11 running on Synology Docker container.  I just migrated to Docker yesterday but these errors were present on my RPi2 Debian installation as well.

 

Is this something to do with a changed syntax in the output from the ISY that's not being parsed correctly?  I notice an underscore before the 1 between <control>_1</control>

I switched to a proper a xml parser vs. the old brute force method a couple versions back so there are some growing pains.

 

These appear to be changes to the init value of variables, which I don't have support for (never did) but now they crap out.  I'll fix it in the next version, it won't hurt anything with the exception of a nuisance error.

Thanks io_guy.  That makes sense.  In some of my programs, I periodically set the init value for variables.

 

Great work on NodeLink, by the way.  Very much appreciated!

I switched to a proper a xml parser vs. the old brute force method a couple versions back so there are some growing pains.

 

These appear to be changes to the init value of variables, which I don't have support for (never did) but now they crap out.  I'll fix it in the next version, it won't hurt anything with the exception of a nuisance error.

I hate to even suggest it (in view of so much hard work by your lately) but a three level logging enable may benefit sleuthing, after the event.

• Verbose Off (clear box)
• Verbose on errors only (grey box?)
• Verbose On ("X"ed box)

Larry,

The issue there is that all the verbose data that you'd be looking for would need to be logged prior to the error, so you wouldn't catch it with the "verbose on errors only".

Larry,

The issue there is that all the verbose data that you'd be looking for would need to be logged prior to the error, so you wouldn't catch it with the "verbose on errors only".

Yeah, there may be no point in that then. You've been doing the troubleshooting.

V0.8.12 fixed the errors. Thanks!

 

 

Sent from my iPhone using Tapatalk