Venstar: Nodelink ssl to venstar issue

[paulbates]

Hi io_guy

 

You added SSL to venstar from Nodelink a few versions ago. After settling in on the wifi temp sensors, I started using SSL recently. The issue I'm having is that it runs fine on SSL for 10 to 15 minutes, and then it start posting these errors in the log:

2018-01-06 15:09:25 - Venstar Web Error: The request timed out [venstarfr]
2018-01-06 15:09:54 - Venstar Web Error: The request timed out [venstarus]

These keep picking up in frequency over time until my heartbeat programs start throwing exceptions. This keeps building up.  Things I've tried or noticed.

• SSL communication between nodelink and the ISY is fine (logged in, I can see query attempts from AC showing up right away, but they error out getting the value (example at the end of today's log)
• SSL communication between nodelink and the thermostats is where it happens. The nodelink page for the thermostat and thermostat values are different.. what nodelink shows is what the ISY shows
• I'm typically very close to 30 seconds for poll rate. I moved that around.. up to 60 and down into the 20s, but that doesn't change anything that I can tell.
• Thermostat operations are normal otherwise, and other network comms including to the venstar wifi temps sensors, skyport and local rest calls. that all works fine / normal
• When I restart nodelink, (and don't touch the thermostats) it behaves as expected for both stats for that 10 - 15 minute perioed..all the way back to the AC. Then the errors come and build up. See the last 3 lines:
   

2018-01-06 15:34:56 - ISY NodeLink Server v0.8.12 started
2018-01-06 15:34:56 - Mono version: 3.2.8 (Debian 3.2.8+dfsg-4+rpi1)
2018-01-06 15:34:56 - Web config server started (http://192.168.0.102:8090)
2018-01-06 15:34:57 - ISY resolved to 192.168.0.99
2018-01-06 15:34:59 - ISY Node Server config detected (profile 1)
2018-01-06 15:34:59 - Auto-Update: Checking for program update...
2018-01-06 15:35:00 - Auto-Update: No web update available
2018-01-06 15:35:02 - ISY Warning: Duplicate node names exist on the ISY (Couch Lamp)
2018-01-06 15:35:02 - ISY Warning: Duplicate node names exist on the ISY (Sink)
2018-01-06 15:35:02 - ISY Warning: Duplicate node names exist on the ISY (Table Lamp)
2018-01-06 15:35:02 - ISY Warning: Duplicate node names exist on the ISY (Recessed)
2018-01-06 15:35:10 - Relay Server: Started on port 2405
2018-01-06 15:43:55 - Venstar Web Error: The request timed out [venstarfr]
2018-01-06 15:53:00 - Venstar Web Error: The request timed out [venstarfr]

There's some recreates int the logs with / without verbose logging to from ISY and to from the thermostat. I opened one stat up via ssl and sent you the address, port and credentials via pm. 

 

Paul 

[io_guy]

Connected and running now.  May take some time (if I get anything) since it appears to be a normal web timeout.

 

If it's just because the Venstar gets bogged down then I can looks at a settable timeout.  If it's something else we may be out luck.  The https on the Venstar is a little sketchy.  It didn't work at all for the first few firmwares it was added.  It uses digest auth which is a little more complicated (and more overhead) than standard so it could be something on their side.

 

Update:

Timed out here after 25min.  Let's see if I can find a band-aid.

[paulbates]

Thanks for looking. I'd like to use it, but agree its tough to know where the problem actually is. The latency between Detroit and Ottowa probably isn't helping.

 

Would it help if I exposed my nodelink page temporarily?

 

If there isn't confidence that stat feature, I can switch back to non SSL and don't spend a lot of time on it

 

Paul

[io_guy]

After my last post I changed the https timeout to 10s and it's been running with zero errors since.

 

I'll make the timeout configurable in the next NodeLink release, we'll see if that does the trick for you.

[paulbates]

Wonderful! Thanks io_guy!

 

I'll shut that port down on my router if you're good

 

Paul

[io_guy]

Yep, kill it.

[paulbates]

io_guy. That got it.

 

I initially set it for 10s as you described. After running it for 50 minutes it threw one message for one of 2 stats. I've watched the heartbeat in the AC and it does go above the poll rate a little from time to time, but its always varied a little. I was expecting that. I bumped the time out to 15. I'll watch it a little more, data is reliably getting back to the ISY.

 

Thank you 

 

Paul