NodeLink 0.9.17 errors

[larryllix]

Getting some new Venstar errors in this version.  Venstar errors have been very rare the last few months.

2018-07-26 23:52:09 - ISY NodeLink Server v0.9.17 started
2018-07-26 23:52:09 - OS: Linux rpi3 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux
2018-07-26 23:52:09 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-07-26 23:52:09 - Web config server started (http://192.168.0.175:8090)
2018-07-27 00:28:18 - Venstar Poll Error - There was an error deserializing the object of type NodeLink.Venstar+VInfo. Encountered an unexpected character 'H' in JSON. [ven1]
2018-07-27 00:28:18 - Venstar Poll Error (Data) - HTTP/1.1 200 OK
Cache-Control: max-age=300
ST: venstar:thermostat:ecp
Location: http://192.168.0.171/
USN: colortouch:ecp:90:B6:86:A7:8B:11:name:UTILITY:type:residential

"activestage":1,"hum_active":0,"hum":54,"hum_setpoint":38,"dehum_setpoint":44,"setpointdelta":1.0,"availablemodes":2}

[io_guy]

Can't think of anything different on the Venstar side.  Away for the weekend, will look when i get back.  

Let me know if you see any other oddities, I changed a lot of code this release to get closer to .NET Core compliant.  

[larryllix]

Thanks.
I enabled Debug mode logging again for this and see if it happens again. The comms are weak to that stat.

[dwengrovitz]

Seeing a new error from my DSC alarm upon Nodelink startup.  I'll continue to monitor and will post any other oddities.

------------------------------------------------------------------

2018-07-28 09:36:51 - ISY NodeLink Server v0.9.17 started

2018-07-28 09:36:51 - OS: Darwin Mac-Mini.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64

2018-07-28 09:36:51 - Mono version: 5.10.0.160 (2017-12/f3ac8fdeb37 Tue Mar  6 14:07:30 EST 2018)

2018-07-28 09:36:52 - Web config server started (http://192.168.1.15:8095)

2018-07-28 09:36:52 - ISY resolved to 192.168.1.6

2018-07-28 09:36:53 - ISY Node Server config detected (profile 1)

2018-07-28 09:36:54 - DSC: Repeater started on port 2402 [dsc1]

2018-07-28 09:36:54 - Relay Server: Started on port 2405

2018-07-28 09:36:54 - DSC: DataArrival Error - Index and length must refer to a location within the string.

Parameter name: length [dsc1]

[kohai]

My system seems to be working.  I've had one error for awhile.  I post this since @dwengrovitz mentioned DSC I thought I would show you what my log looks like with DSC.

2018-07-27 04:00:02 - ISY NodeLink Server v0.9.17 started
2018-07-27 04:00:02 - OS: Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
2018-07-27 04:00:02 - Mono version: 5.12.0.226 (tarball Thu May  3 11:57:48 UTC 2018)
2018-07-27 04:00:03 - Web config server started (http://192.168.1.249:8090)
2018-07-27 04:00:03 - ISY resolved to 192.168.1.250
2018-07-27 04:00:04 - ISY Error: Input string was not in a correct format. (profiles/ns/0/connection)
2018-07-27 04:00:04 - ISY Error: Error getting Node Server list - Root element is missing.
2018-07-27 04:00:04 - ISY Node Server profile set to 1
2018-07-27 04:24:31 - DSC: System Status - Exit Delay In Progress (Partition 1) [dsc]
2018-07-27 04:28:29 - DSC: System Status - Armed Stay (Partition 1) [dsc]
2018-07-27 14:05:02 - DSC: System Status - Panel Disarmed By User 40 [dsc]
2018-07-27 14:05:02 - DSC: System Status - Disarmed (Partition 1) [dsc]
2018-07-28 04:38:09 - DSC: System Status - Exit Delay In Progress (Partition 1) [dsc]
2018-07-28 04:42:08 - DSC: System Status - Armed Stay (Partition 1) [dsc]
 

[io_guy]

50 minutes ago, kohai said:

My system seems to be working.  I've had one error for awhile.  I post this since @dwengrovitz mentioned DSC I thought I would show you what my log looks like with DSC.

2018-07-27 04:00:02 - ISY NodeLink Server v0.9.17 started
2018-07-27 04:00:02 - OS: Linux raspberrypi 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
2018-07-27 04:00:02 - Mono version: 5.12.0.226 (tarball Thu May  3 11:57:48 UTC 2018)
2018-07-27 04:00:03 - Web config server started (http://192.168.1.249:8090)
2018-07-27 04:00:03 - ISY resolved to 192.168.1.250
2018-07-27 04:00:04 - ISY Error: Input string was not in a correct format. (profiles/ns/0/connection)
2018-07-27 04:00:04 - ISY Error: Error getting Node Server list - Root element is missing.
2018-07-27 04:00:04 - ISY Node Server profile set to 1
2018-07-27 04:24:31 - DSC: System Status - Exit Delay In Progress (Partition 1) [dsc]
2018-07-27 04:28:29 - DSC: System Status - Armed Stay (Partition 1) [dsc]
2018-07-27 14:05:02 - DSC: System Status - Panel Disarmed By User 40 [dsc]
2018-07-27 14:05:02 - DSC: System Status - Disarmed (Partition 1) [dsc]
2018-07-28 04:38:09 - DSC: System Status - Exit Delay In Progress (Partition 1) [dsc]
2018-07-28 04:42:08 - DSC: System Status - Armed Stay (Partition 1) [dsc]
 

Ok for this one give me the output of rest/profiles/ns/0/connection

Or enable the debug for System Config and paste it here.  

[io_guy]

1 hour ago, dwengrovitz said:

Seeing a new error from my DSC alarm upon Nodelink startup.  I'll continue to monitor and will post any other oddities.

------------------------------------------------------------------

2018-07-28 09:36:51 - ISY NodeLink Server v0.9.17 started

2018-07-28 09:36:51 - OS: Darwin Mac-Mini.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64

2018-07-28 09:36:51 - Mono version: 5.10.0.160 (2017-12/f3ac8fdeb37 Tue Mar  6 14:07:30 EST 2018)

2018-07-28 09:36:52 - Web config server started (http://192.168.1.15:8095)

2018-07-28 09:36:52 - ISY resolved to 192.168.1.6

2018-07-28 09:36:53 - ISY Node Server config detected (profile 1)

2018-07-28 09:36:54 - DSC: Repeater started on port 2402 [dsc1]

2018-07-28 09:36:54 - Relay Server: Started on port 2405

2018-07-28 09:36:54 - DSC: DataArrival Error - Index and length must refer to a location within the string.

Parameter name: length [dsc1]

This one is most likely caused by my code changes.  Enable debug for dsc and paste me the code you see for the error. 

[kohai]

9 minutes ago, io_guy said:

Ok for this one give me the output of rest/profiles/ns/0/connection

Or enable the debug for System Config and paste it here.  

see attached

kohai-isy-log.txt

kohai-isy-profile.txt

[dwengrovitz]

1 hour ago, io_guy said:

This one is most likely caused by my code changes.  Enable debug for dsc and paste me the code you see for the error. 

Turned on Debug for the DSC and restarted Nodelink.  Attached is the log.  Not quite sure which part is of most interest to you so I am attaching the full file, but the error occurs about 39 lines from the bottom of the file.

Log with DSC Debug On.txt

[io_guy]

Thanks guys, I'll sort it out later in the week.  Camping and then away for work for a few days.    

[larryllix]

59 minutes ago, io_guy said:

Thanks guys, I'll sort it out later in the week.  Camping and then away for work for a few days.    

Happy camping! I hope you get some better weather. Looks cool and damp from here if you are going north.

[io_guy]

On 7/28/2018 at 12:33 PM, dwengrovitz said:

Turned on Debug for the DSC and restarted Nodelink.  Attached is the log.  Not quite sure which part is of most interest to you so I am attaching the full file, but the error occurs about 39 lines from the bottom of the file.

Log with DSC Debug On.txt

Wrong log.  Don't enable debug under System Config, enable it under the DSC tab.

[larryllix]

Ecobee weather forecasts seem not related to the ecobee web app-site. V0.9.17

The temperatures all seem to agree with the ecobee app-site but the sky conditions seem incorrect.  The next few days are predicting overcast and rain but the interpreted (and NodeLink node tab) show almost opposite skies.

Ecobee Overcast is showing mostly sunny in ISY (2).
Ecobee Rain is showing Mostly Clear in ISY (6)
Ecobee Partly Cloudy is showing Sunny in ISY (1)

Of course I am only going by picture icons in the ecobee forecast so they interpretation may be off slightly. Hi/Lo temperatures all seem to match.

 

Thanks io_guy!!

[dwengrovitz]

On 7/30/2018 at 3:41 PM, io_guy said:

Wrong log.  Don't enable debug under System Config, enable it under the DSC tab.

Apologies, I thought that's what I had done but apparently not.  In any event, it appears the issue has been resolved in V0.9.18 and I now get a clean set of messages upon startup.  Thanks!