Jump to content

v0.9.13 - ecobee hicough


larryllix

Recommended Posts

Been running quite well for sometime now until I got this one.

ISY notified me of heartbeats missed so it lasted for many minutes. Knocked out my two ecobees and one Venstar T7900, that I monitor but it seems centered around ISY baulking at something it got sent.

2018-05-10 08:57:28 - ISY NodeLink Server v0.9.13 started
2018-05-10 08:57:28 - OS: Linux rpi3 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux
2018-05-10 08:57:28 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-05-10 08:57:28 - Web config server started (http://192.168.0.175:8090)
2018-05-10 08:57:28 - ISY resolved to 192.168.0.161
2018-05-10 08:57:28 - ISY Node Server config detected (profile 1)
2018-05-10 09:59:20 - Venstar Get Error: Timeout [ven1]
2018-05-11 02:30:41 - Ecobee Get Error - Timeout [ecobee1]
2018-05-14 13:13:15 - Venstar Runtime Poll Error - Exception has been thrown by the target of an invocation. [ven1]
2018-05-14 18:19:45 - ISY Error: Send timer error - Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Trimmed logfile

logfile_2018-05-14.txt

 

Thanks!  I don't know if this helps you or just something that cannot be prevented.  First time I have ever encountered this error. AFAICT

 

Link to comment
Share on other sites

Oh I should have mentioned that my Ecobee4 (first NodeLink listed unit) started babbling (out of service type reports) a few hours before this data crash. When I look at the connect time in my router is showed approximately the same time the Alexa complaining happened.

Putting it all together I am guessing that the ecobee4 may have done  an automatic firmware update of some kind. This could have triggered some erroneous data but IIRC the NodeLink error was an hour or so after.

Link to comment
Share on other sites

  • 2 weeks later...

This appeared to be the same event happening again. I immediately went to the ecobee online access website but it seemed to be fully up and running for me.

Again NodeLink v0.9.13 would not resume operations after the heartbeats stopped for ecobee1,  ecobee2  and my Venstar nodes. After about 40 minutes I rebooted NodeLink and   ecobee heartbeats resumed after about 2 minutes, (Venstar heartbeat resumed almost immediately).

 

My Venstar is back on my main router and the distance is too far for the density of construction between the router and stat.

2018-05-25 08:17:15 - ISY NodeLink Server v0.9.13 started
2018-05-25 08:17:15 - OS: Linux rpi3 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux
2018-05-25 08:17:15 - Mono version: 5.8.0.108 (tarball Fri Jan 19 18:55:10 UTC 2018)
2018-05-25 08:17:16 - Web config server started (http://192.168.0.175:8090)
2018-05-25 08:17:16 - ISY resolved to 192.168.0.161
2018-05-25 08:17:16 - ISY Node Server config detected (profile 1)
2018-05-25 14:56:22 - Venstar Get Error: Timeout [ven1]
2018-05-25 14:58:02 - Venstar Get Error: Timeout [ven1]
2018-05-25 18:10:27 - Venstar Get Error: Timeout [ven1]
2018-05-25 18:12:07 - Venstar Get Error: Timeout [ven1]
2018-05-25 23:59:40 - Ecobee Timer Error - Index was outside the bounds of the array. [ecobee1]
2018-05-25 23:59:40 - Ecobee Timer Error - Index was outside the bounds of the array. [ecobee2]
2018-05-26 01:44:44 - Venstar Get Error: Timeout [ven1]
2018-05-26 01:44:54 - Venstar Get Error: Timeout [ven1]
2018-05-26 01:46:34 - Venstar Get Error: Timeout [ven1]
2018-05-26 01:48:15 - Venstar Get Error: Timeout [ven1]
2018-05-26 11:47:58 - Venstar Get Error: Timeout [ven1]
2018-05-26 11:49:39 - Venstar Get Error: Timeout [ven1]
2018-05-26 12:27:26 - Venstar Get Error: Timeout [ven1]
2018-05-26 12:29:06 - Venstar Get Error: Timeout [ven1]
2018-05-26 12:29:09 - Venstar Get Error: No route to host [ven1]
2018-05-26 22:06:20 - Venstar Get Error: Timeout [ven1]
2018-05-26 22:06:30 - Venstar Get Error: Timeout [ven1]
2018-05-26 22:08:10 - Venstar Get Error: Timeout [ven1]
2018-05-27 03:41:48 - Venstar Get Error: Timeout [ven1]
2018-05-27 03:43:28 - Venstar Get Error: Timeout [ven1]
2018-05-27 03:43:31 - Venstar Get Error: No route to host [ven1]
2018-05-27 12:02:21 - Venstar Runtime Poll Error - Expecting state 'Element'.. Encountered 'Text'  with name '', namespace ''. [ven1]
2018-05-27 15:22:08 - ISY Error: Send timer error - Index was out of range. Must be non-negative and less than the size of the collection.

 

logfile_2018-05-27.txt

 

Link to comment
Share on other sites

  • 1 month later...

Larry,

Had this happen to me last night.  Can't recreate (send timer error) but I think I know the culprit.  Will handle this in the next release.  With this error NodeLink stops sending to the ISY (devices to NodeLink still update).  It happened to me during the update process/reboot for 5.0.13.

Link to comment
Share on other sites

3 hours ago, io_guy said:

Larry,

Had this happen to me last night.  Can't recreate (send timer error) but I think I know the culprit.  Will handle this in the next release.  With this error NodeLink stops sending to the ISY (devices to NodeLink still update).  It happened to me during the update process/reboot for 5.0.13.

I haven't seen this type of thing for quite some time now but then I don't get many errors anymorewith NodeLink. Before it seemed if there was a few errors with one device eventually the other nodes started throwing errors.

This made me suspect the Ethernet system between RPi/Raspbian/Mono/Nodelink somewhere. If errors happened, the system would get messed up and usually NodeLink  would need to be rebooted to stop the more frequent errors. This could take days to escalate to that level, most times.
A month or so back, you mentioned a change in the http system and it all seemed to go away.  I figured you had found that obscure one.

 

Now other than the odd comm eror for any device node, I get now,   the one that is still happening is the 11:59:45 PM, every few nights, on the ecobee nodes.

2018-05-25 23:59:40 - Ecobee Timer Error - Index was outside the bounds of the array. [ecobee1

The errors don't seem to affect any operations so I figured they are  just some logfile switchover glitch. I turned off the debug level and haven't seen them since.

I hope you really like ecobee stats. They are the best I have used of a few differnt brands, but you have spent a lot of time on their crappy API.
Much appreciated.

I hope your A/C has been working well! :)

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...