408 Request Timeout Errors

[skarragallagher]

Can you give some more context, why the local non-REST API (I am assuming you are were using their local socket connection?) doesn't work with the way your home is configured?

[kevini]

With the legacy Rainforest Eagle I noticed with Spud's Plugin and the Python script that I wrote it seems to have a memory leak when you use the Cloud API. It is fine in the beginning and then slows down and you receive these timeout's. Even the local WebUI stops working.

It looks like the cloud just proxies the API's and each call hits the eagle. After time this leak happens, eventually it stops responding all together. There are lots of reports of people using many different 3rd party apps and seeing it. The local non-REST API worked fine but I can't use it anymore due to the way my home is configured.

I gave up using the Legacy Rainforest Eagle, bought a Eagle-200 and it has been rock solid. They changed the way the cloud API works, the Rainforest cloud always gets your data and then it sends it to other clouds. The API using the data in the cloud so it does not re-query the Eagle. The Eagle seems to hum away without issues.

[skarragallagher]

I'm getting the same errors. I was at 60 seconds, I just updated the plugin to .2 and changed the value to 300, I will see if this helps. Also I notice that I didn't have any data in the homeseer energy db for this device (rainforest root) for the past 2 days

[automateme]

In version 3.0.0.2 I have set the default poll interval to 300secs, I will contact Rainforest to see what they recommend.

I will move my discussion to the new dedicated forum, Thanks!

I am curious about Rainforest's response to the timeouts - it must be something on their server-side. Even with polling at 300s, I am still getting a lot of the 408 errors randomly. Just now looking through my log - I had (1) 408 error about 1am, then none until 6:40am, then (21) between 6:40am and 7:10am.