networking issue --- bug in gateway firmware 406?

[Tom]

Hello,

before I post a ticket, I was wondering if anyone else has seen this problem.
My TED gateway is on DHCP, gets the IP address of 192.168.8.102. I go to the footprints and enable the energy postings to a third party API with 1minute intervals.
Everything is working fine.

Now I come back after five days, and the Third party API is still working, but these things are screwed up:
- the gateway is still using this IP address, but hasn't done any recent renewals of the lease
- the gateway's web server is still listening, but it doesn't find anymore of its pages:

tom@xxxxxx:~$ wget http://192.168.8.102/Footprints.html
--2011-04-13 16:06:22--  http://192.168.8.102/Footprints.html
Connecting to 192.168.8.102:80... connected.
HTTP request sent, awaiting response... 404 Not found
2011-04-13 16:06:22 ERROR 404: Not found.


Cheers
Tom

[Tom]

BTW, a simple power cycle fixes it:


tom@d2009:~$ wget http://192.168.8.102/Footprints.html
--2011-04-13 16:26:27--  http://192.168.8.102/Footprints.html
Connecting to 192.168.8.102:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `Footprints.html'

    [ <=>                                                                                                                                                   ] 368         --.-K/s   in 0s     

2011-04-13 16:26:27 (81.5 MB/s) - `Footprints.html' saved [368]

[TedDev]

This has recently been fixed in our development tree. The fix is currently being tested and will be part of the next Beta firmware release in a few weeks.

The issue occurs when the 3rd party server being posted to is down (unresponsive) for a period of time (20-40 minutes).  The gateway is still colllecting data in this state, and will eventually reset on it own. The fix is to prevent the state to begin with.

[dannyted]

Yes I had seen the issue and posted about it last week.  It looks like they have addressed it.

[Tom]

This has recently been fixed in our development tree. The fix is currently being tested and will be part of the next Beta firmware release in a few weeks.

The issue occurs when the 3rd party server being posted to is down (unresponsive) for a period of time (20-40 minutes).  The gateway is still colllecting data in this state, and will eventually reset on it own. The fix is to prevent the state to begin with.

I have not seen "will eventually reset of its own". From all the cases I have seen, it just gets stuck in this state for as many days as you leave it without a power cycle. Very bad for an embedded system.

[dannyted]

Any idea when the new firmware will be released?

[TedDev]

We've been internally testing the release candidate for the last few weeks and everything looks good so far. If no showstopper issues pop up between now and Monday we'll post the beta early next week.

[dannyted]

Thanks!

[TedDev]

Firmware beta has been released. Info available here:

http://www.theenergydetectiveforums.com/index.php/topic,296.0.html

[dannyted]

Thanks will try tomorrow evening.