The Energy Detective Forums

General Category => TED5000 Support => Topic started by: TedDev on August 04, 2011, 07:04:34 PM

Title: TED5000 Beta R469/R245
Post by: TedDev on August 04, 2011, 07:04:34 PM
The latest beta has been published. This can be used by both 20-series and 21-series gateway owners.

NOTE: Upgrading to this version of the firmware will reset your device system settings, Including Device ID #'s, and perform a “Reset Totals to Zero”, (this will reset Monthly Totals but not affect History). We recommend disabling password protection and making a backup of your system settings before upgrading. After upgrading, please find your TED5000 on the network (you can use the installation utility to do this, http://www.theenergydetective.com/install-program ) and then Restore your system settings via the “Write to Device” tab of the system settings wizard.  


Gateway R469:  http://files.theenergydetective.com/firmware/beta/gateway-g-20110922-r469.bin (http://files.theenergydetective.com/firmware/beta/gateway-g-20110922-r469.bin)
Footprints R245: http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin (http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin)


Changes since R466/R245
----
 - Fixed bug where DHCP leases were not being accepted
 - Updated weather code to pull from new weather.gov link


Changes since R465/R245
---
 - Fixed bug where the HTTP port was stuck on 80 even though it was changed in the Settings Wizard.

Changes since R454/R245
---
- Tweaked RTA code to make connection a bit more stable w/ latest firmware


Changes since R452/R240
---
-  Google PowerMeter support has been removed
-  Stats page is now linked from the help menu


Title: Re: TED5000 Beta R454/R245
Post by: altenbach on August 04, 2011, 09:49:00 PM
After upgrading, I wanted to restore the configuration but it asks for the password. For some reason my password no longer works?

Ideas?
Title: Re: TED5000 Beta R454/R245
Post by: TedDev on August 04, 2011, 10:44:53 PM
After upgrading, I wanted to restore the configuration but it asks for the password. For some reason my password no longer works?

Ideas?

The upgrade itself would have cleared out any password you have (and disabled password protection to begin with). You may need to reset to factory defaults to clear that out (note: the side reset button no longer clears history, just your system and utility settings).
Title: Re: TED5000 Beta R454/R245
Post by: altenbach on August 04, 2011, 11:02:37 PM
Thanks. Unfortunately, I am currently traveling and don't have access to the unit.

I guess I should have saved the configuration file without password before upgrading. Is there a default password perhaps?

(I wonder if there was no password after upgrading, but restoring the file caused the password prompts, maybe one for each configuration line (?). I actually got many PW prompts is rapid succession, I canceled many password dialogs before being able to get back to the home screen.)
Title: Re: TED5000 Beta R454/R245
Post by: TedDev on August 04, 2011, 11:31:28 PM
The default username/password is admin/admin.
Title: Re: TED5000 Beta R454/R245
Post by: altenbach on August 05, 2011, 12:01:54 AM
Thanks, that worked! I can now administer again.

Still, all probes read zero now since the upgrade. It seems no data is acquired.

(IDs etc. look right after restoring the configuration files and the settings have been applied and rebooted).

Is there anything else that needs to be done?
Title: Re: TED5000 Beta R454/R245
Post by: DougHo on August 05, 2011, 06:20:54 PM
To get non-zero readings, I needed to "Restart TED5000" after restoring the system/utility settings that were cleared by the firmware update (I see you say "rebooted" but I thought it worth mentioning for others).  In the past I would sometimes get a message about settings change needing a restart; I got no such message this time but when I saw no readings I decided to restart manually.  After the restart, readings came through normally.  20-series hardware updating from non-Beta firmware (gateway update, then wait a minute, then footprints update), if that matters.  P.S.  Good time to update may be few minutes after midnight, otherwise the Day History can end up low.
Title: Re: TED5000 Beta R454/R245
Post by: altenbach on August 06, 2011, 05:51:40 PM
I restarted several times, but my solar still reads zero 100% of the time. The net reading seems correct.

Once I have access to the device, I will try a reset.
Title: Re: TED5000 Beta R454/R245
Post by: stanar on August 09, 2011, 12:40:32 AM
Since the R452/R240 thread is closed, I am posting it here.

At last I found what the issue is with the R452/R240 firmware.

When using DHCP address, it expires within 60 secs even though the router has  24 hour lease. Though I assign the static IP per MAC on the router, the gateway keeps requesting new ip every minute which is causing connectivity issues.

This makes it mandatory to configure static IP on the gateway itself vs statically assigning the IP on the router.

I did not have this issue with the earlier versions. Due to this issue, I lost more than 6 months of data and had to get a replacement gateway.

Not sure if this was an intentional change. But I would keep Static IP on the gateway optional and to use dhcp address with the lease offered by the router.

Can someone comment?
Title: Re: TED5000 Beta R454/R245
Post by: TedDev on August 09, 2011, 01:10:30 AM
There has not been a change to the DHCP code or settings since the initial release of this device so the recent firmware wouldn't have caused a change.  I will check with support to see why a the gateway as replaced (even if it were a firmware issue the firmware could be downgraded). My guess is that the device itself was resetting every 60 seconds or so which would be indicative of a hardware issue. In this case, it would request a new DHCP every 60 seconds as it does it automatically upon reset/power-up.  

We still use DHCP as a default and a static IP is not required (although we do recommend it).
Title: Re: TED5000 Beta R454/R245
Post by: stanar on August 09, 2011, 01:38:29 AM
There has not been a change to the DHCP code or settings since the initial release of this device so the recent firmware wouldn't have caused a change.  I will check with support to see why a the gateway as replaced (even if it were a firmware issue the firmware could be downgraded). My guess is that the device itself was resetting every 60 seconds or so which would be indicative of a hardware issue. In this case, it would request a new DHCP every 60 seconds as it does it automatically upon reset/power-up. 

We still use DHCP as a default and a static IP is not required (although we do recommend it).


The old gateway (already returned and received by TED) was completely inaccessible. Could not hard reset, couldn’t access FP, nothing whatsoever. I found it defaulted to factory set ip 192.168.7.2 which I could ping but  not browse. (I provided the screenshots to support).

Anyway, in the above post I was  referring to the brand new gateway which came with the old firmware (think it was R406). Before I loaded the R452/R240 firmware, it was working as expected with the dhcp settings.  After I loaded the R452/R240 firmware, I found that  I couldn’t access the gateway via browser.

When I  checked the router's dhcp clients list, I found that this one keeps requesting a new IP every 60 secs when all the other devices have 24 hrs lease time. Nothing has been changed on the router between using the old and new firmware on the gateway.

I don’t think the device was resetting every 60 secs, because I did check this graph for an hour there were no indications of resetting every minute other the two while configuring.

Once I configured  the static IP on the gateway itself, everything is  back to normal.
Title: Re: TED5000 Beta R454/R245
Post by: solar_dave on August 09, 2011, 07:48:18 PM
TEDdev I looked at the down load page for this upgrade  (http://www.theenergydetective.com/ted-5000/firmware-upgrade) and it says not to use R454/R245 but to use R406/R223 on a 20XXXX gateway.  Will this one work or not?
Title: Re: TED5000 Beta R454/R245
Post by: anthonyris on August 09, 2011, 09:14:58 PM
Strike that. The web page refers to .452 firmware, while this thread is the .454 variant - which should work across the 20XXXX and 21XXXX devices. Got it.

Separately, the notes say that the DeviceIDs, etc will get wiped. Sounds like this should NOT be done remotely, correct?


Ditto. Web page says don't use this on 20XXXX gateway, but the Forum says to use it.

Clarity, pls.

.//A.

TEDdev I looked at the down load page for this upgrade  (http://www.theenergydetective.com/ted-5000/firmware-upgrade) and it says not to use R454/R245 but to use R406/R223 on a 20XXXX gateway.  Will this one work or not?
Title: Re: TED5000 Beta R454/R245
Post by: altenbach on August 10, 2011, 08:00:02 PM
OK, I physically reset the unit and hopefully things will clear up... I also cleared the browser cache.

Some problems I noticed with R454/R245:

The "second live view" works correctly only for about 10-15 seconds after selecting a new range. After that time, it reverts to a unusual display, showing only about 5 seconds (5 points) and the time axis is about two hours in the future. (currently it is 8:54 and it jumps to 10:58 after 10-15 seconds)

The "minute live view" does not display any data at all. Ever!
Title: Re: TED5000 Beta R454/R245
Post by: bobtheskutter on August 11, 2011, 09:44:50 PM
The latest beta has been published. This can be used by both 20-series and 21-series gateway owners.


Gateway R454:  http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin (http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin)
Footprints R245: http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin (http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin)



I recently upgraded my firmware and now my 20 series gateway is reporting a 210001 product ID in footprints and I cannot change it to what it really is ( 20 08 3E )

See my Footprints here:

     http://67.169.140.160:8733/Footprints.html
Title: Re: TED5000 Beta R454/R245
Post by: TedDev on August 11, 2011, 10:03:28 PM
The latest beta has been published. This can be used by both 20-series and 21-series gateway owners.


Gateway R454:  http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin (http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin)
Footprints R245: http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin (http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin)



I recently upgraded my firmware and now my 20 series gateway is reporting a 210001 product ID in footprints and I cannot change it to what it really is ( 20 08 3E )


See my Footprints here:

     http://67.169.140.160:8733/Footprints.html

Please contact support and they'll walk you through resetting the serial id number.

http://www.theenergydetective.com/support/tickets
Title: Re: TED5000 Beta R454/R245
Post by: bobtheskutter on August 12, 2011, 01:19:05 AM
The latest beta has been published. This can be used by both 20-series and 21-series gateway owners.


Gateway R454:  http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin (http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin)
Footprints R245: http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin (http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin)



I recently upgraded my firmware and now my 20 series gateway is reporting a 210001 product ID in footprints and I cannot change it to what it really is ( 20 08 3E )


See my Footprints here:

     http://67.169.140.160:8733/Footprints.html

Please contact support and they'll walk you through resetting the serial id number.

http://www.theenergydetective.com/support/tickets


I have done.  Apparently I need to ship it back to be "re-flashed"
Ticket: #1272
Posted here to see if anyone else has experienced this.
Title: Re: TED5000 Beta R454/R245
Post by: DougHo on August 12, 2011, 03:39:52 AM
I experienced the improper 210001 instead of proper 20-something when flashing an EARLIER Beta (around mid-June), was told to write a ticket for walk-through reset, told they couldn't walk me through reset and that it was okay to keep the 210001 ID, then told they needed online access, then told that I needed to ship.  I shipped around 7/11 and got it back around 7/16, with proper 20-something ID.
I did NOT have any ID problem when flashing the most recent Beta (around a week ago).
Title: Re: TED5000 Beta R454/R245
Post by: drpulis on August 13, 2011, 10:49:28 PM
I would like to see 2 minimum, maybe even 3, configurations for 3rd party Energy Posting.  I have just gone through a series of Activate, Deactivate processes to evaluate suitability for some of the available systems.  It would certainly be nice to be able to run 2 parallel, until decided which I want to permanently use.

In addition to better evaluations, I suspect I would eventually want 2 links permanently anyway.  One link for my desktop and detail tracking, while yet another to send specifically to my Smartphone.
Title: Re: TED5000 Beta R454/R245
Post by: mbisco on August 16, 2011, 02:50:10 PM
Stanar and TedDev:

I've experienced the 60 second DHCP lease life, noticed it after upgrading (R406 timeframe), but it may have been happening before the upgrade. I was just learning TED at that point, and didn't know what to expect. The unit kept "disappearing".

I do not believe TED is resetting after 60 seconds because the router lease table clearly shows the lease life as 60 seconds. This indicates that TED requested a lease of only 60 seconds, not a reset after 60 or so seconds. I had posted full details previously.

Update 8/17: Upgraded to R454/R245, I didn't see the short lease life problem. Found TED in the lease table with a 23:59 life. But I only messed around with TED a few minutes before restoring settings (with static IP). I had seen the problem with R452/R240.
Title: Re: TED5000 Beta R454/R245
Post by: stanar on August 20, 2011, 08:06:36 PM
@mbisco - Thanks for sharing your experience; so I wasnt alone.

TEDEV said they didnt change anything with the dhcp. But R450 and R452 requests IP every minute if not configured with a static address.

It wasnt a router issue as nothing changed on the router side. Just to make sure, I did test with 3 different routers with the same result.

It's good if it was fixed in R454; I havent upgraded yet from R452.
Title: Re: TED5000 Beta R454/R245
Post by: TedDev on August 21, 2011, 10:55:00 PM
We didn't change any of the networking code in that revision either; however, we did force all system settings to reset w/ that build (R452) to free up memory used by the PowerMeter code. You may want to try resetting to factory defaults to see if that's the case.
Title: Re: TED5000 Beta R454/R245
Post by: DVB on August 25, 2011, 04:18:07 AM
I just received the TED5000 3 days ago, and it is gateway series 21.  I like many others lost my connection to the TED5000 footprints software.  I see the Gateway on my router, and the standalone silver device is receiving accurate data from the gateway.
Is this R454/R245 upgrade really needed for a product that I received so recently?

Is this potentially why I can't connect with the software anymore?  A couple of times it looks like it is close, because the basic outline of the footprints startup dashboard is coming up and the address bar changes from 192.168.1.X to TED5000. 

I put in a support ticket, but haven't heard from anyone?  So, the closest I get to having software and "remote" access to TED5000 is to read the website jargon and hope.

Title: Re: TED5000 Beta R454/R245
Post by: mbisco on August 25, 2011, 09:55:34 PM
DVB:

The 'new' TED5000 you just received has undoubtedly been sitting in a warehouse somewhere for a while and the firmware is whatever was in production at the time the unit was manufactured. This Beta firmware addresses problems, offers new features, etc. So if you want/need improvements offered by the upgrade...

The description of the problem you just mentioned sounds more like a browser issue. If you are using IE or Chrome, try Firefox. Firefox is nicer for troubleshooting because it will alert you when there are wierd issues with your communications but IE will just quietly not give you what you want.

If you are still having problem and want to determine if the DHCP lease time is a potential problem for your installation, you could try the following...
   as long as you have access to your routers DHCP lease table:

 1) unplug TED ethernet connection
 2) reboot TED (power reset by unplugging for 15 seconds)
 3) reboot router (mostly to clear  out the DHCP lease table so you are starting clean)
 4) log into router - open DHCP lease table - at this point, hopefully only lease outstanding is the PC you logged into the router with.
 5) connect TED ethernet connection
 6) monitor the DHCP lease table (refresh might be required depending on your router interface software - mine has a <Refresh> button)
 7) IF the lease for TED5000 has a one minute lease period, you may be experiencing the DHCP lease timeout problem.
 8) Monitor the DHCP lease table for a few minutes to see if TED requests another lease and to see what (new) address is assigned.
 9) After a few minutes, activity from TED should settle down. At this point, try to connect to TED using the last DHCP address assigned to TED (whether it is expired or not) .
 10) Assuming you are having the lease timeout issue, once you gain access to TED, set the IP address to STATIC. Assign an address in a range that your routers DHCP service will not assign. My router is configured to give out addresses in the 192.168.1.100 - 192.168.1.150 range. All other addresses in the 192.168.1.x range can be statically assigned (other than .0, .1, and maybe .254 .255 depending on your router).

I say 'may be experiencing the problem' because as long as your network isn't active (no new devices attaching), even if the lease times out, TED will continue to answer to the last address it was assigned... And if TED requests a new address as long as the network isn't active, the router will probably assign the same address again. A duplicate address problem can occur if TED continues to use the last (expired) address and a new device is assigned the expired address TED is using.

When TED was behaving badly during my earlier testing, it would ask for an address about once a minute for a while. When my network was active, I saw TED start at address .101 and within a day or so, get to .127. Another setting that may aggrevate the problem is time sync - i turned that off at Supports suggestion. TED apparently resyncs time about every 20 minutes if it is enabled.

The 'solution' to the DHCP lease issue is to assign a static IP to TED. But you need to be able to access TED's 'System Settings Wizard' which means you need to get further than the footprints outline. Not sure any of this helps.
Title: Re: TED5000 Beta R454/R245
Post by: celblazer on September 12, 2011, 12:11:41 AM
OK So I decided to upgrade my TED5000 21 series firmware today to the latest beta.  Bad idea.   Firmware said it updated the gateway.  Then I tried to update footprints.   I used the installation program and it only got to 15% then reset counting, did the same thing again then after a while it said writing firmware and OK.   Now I can't access foot prints.  I get a "404: File not found" and my remote display is not receiving data.  I tried hitting the reset button on the gateway but no change.  The gateway is listed in my router and the installation program sees it but I can't get footprints to load from it.
Title: Re: TED5000 Beta R454/R245
Post by: kdyke on September 12, 2011, 09:00:57 PM
The earlier release notes mention the ability to backup/restore history and point to a (non-working) link to the beta install program for Windows.   I was curious if a) the link could be fixed, and b) if the format of the save/restore data is something that could be regenerated if I have historical data saved from something like google power meter.   Over the weekend I did a firmware upgrade and unfortunately it went awry and I wound up having to fully reset the device and lost all of the previous history, so it'd be nice to find a way to combine my previously saved historical data with the existing data on the device.  I don't mind doing a bit of programming if I have to in order to generate a new historical backup that could be re-uploaded to the device, but right now I don't even have a way to do the save/restore....
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 12, 2011, 11:04:33 PM
So...
I updated my TED5000 (Gateway ID = 215D93) today to Gateway firmware R465 and Footprints to R245.
I saved my system settings before the update.  In order to restore, I need a username/password.

admin/admin does NOT work (all lower case, will not work with the "A" in caps either).

I can get footprints to load, but realtime shows zero usage.  I cannot restart because the password don't work.

Any suggestions?
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 13, 2011, 12:17:33 AM
Well I've tried everything I know except the hard reset.  I guess that's next when I get the time.
Can someone summarize the procedure?

This is aggravating, I went from a perfectly working TED5K to a paperweight in just a few seconds...
What gives!
Title: Re: TED5000 Beta R454/R245
Post by: celblazer on September 13, 2011, 12:31:22 AM
Same here.   :-[
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 13, 2011, 12:37:03 AM
celblazer...admin/admin not get you into footprints either?
I've tried my old password/username and every normal default...nothing works.
Title: Re: TED5000 Beta R454/R245
Post by: TedDev on September 13, 2011, 01:07:38 AM
You'll need to do a hard reset but that no longer erases history...just system and utility settings.

Title: Re: TED5000 Beta R454/R245
Post by: celblazer on September 13, 2011, 01:25:42 AM
I've tried a hard reset.  Left it unplugged for about over an hour.  I still get the 404 error and no communications to the display.
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 13, 2011, 05:26:03 AM
Does unplugging the gateway for a span of time qualify as a "hard reset"?
I would think it would, but just want to make sure.  I am not getting any 404 errors,
I can get footprints to come up and can access the stats.htm page as well with no problem.

Even the "About" shows my firmware to have taken to the latest version and footprints did too.

I just cannot log in so that I can restore my settings.arrrrgggghhhh!

I cannot do any further troubleshooting tonight.  I will start messing with it some more tomorrow.
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 13, 2011, 10:41:30 PM
OK...I unplugged my gateway and left it for over 18 hours.  IF this qualifies as a hard reset, I'm still out of business.
I powered down my router for about half an hour...let it reboot and initialize for about 15 minutes, then plugged in my gateway.

After about 5 minutes, I opened IE and went to the footprints shortcut, and it loaded up.  I proceeded to restore my settings...good huh???

I opened the settings file and hit "restore" and once the bar graph got to 6% complete, footprints quit loading the restore file, and sit there
prompting me for a password that no one knows what the hell is.  admin/admin doesn't work.  My old password/username doesn't work.
Nothing will get me back into this thing.

OK tech support...what gives??
Title: Re: TED5000 Beta R454/R245
Post by: rotus8 on September 14, 2011, 12:04:02 AM
To do a hard reset:
Quote
While the Gateway is plugged in, use a pen/paperclip to press the reset button on the side of the Gateway and hold for about 20-30 seconds, until the LED right next to the button lights up solid amber. Let go of the button, allow the LEDs to cycle, then unplug the gateway for about 10 minutes. Then you will need to do your setup once again.
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 14, 2011, 03:59:57 AM
Thanks Rotus...I'll give this a shot tomorrow.  I'm beat at the moment, and the wife is watching TV so I can't get back there to work ;D
Title: TED5000 Beta R465/R245
Post by: paulking on September 14, 2011, 04:08:09 AM
Gateway Version 1.0.465
Daughterboard Version 1.0.88
Footprints Version 1.0.245
MTU Version 1.0.61

The beta firmware seems to ignore the "Networks Settings" entry for "HTTP Port", using the default of port 80 even when there is an override value.  It also seems not to listen even to the default "HTTPS Port" setting of 443.

If this is not the correct forum for beta issues, please advise.
Title: Re: TED5000 Beta R454/R245
Post by: PV-Skip on September 14, 2011, 06:02:04 PM
. . .
I opened the settings file and hit "restore" and once the bar graph got to 6% complete, footprints quit loading the restore file, and sit there
prompting me for a password that no one knows what the hell is.  admin/admin doesn't work.  My old password/username doesn't work.
Nothing will get me back into this thing.

OK tech support...what gives??

I had almost the same problem last week.
The green bar got stuck and was asking for a password.
Nothing worked. Rotus8 gave me a hint to try admin/admin again, what I did, but with no success at first.

Then I tried everything else and found out, that the passwords have been mixed.
Username admin now worked with my old password.
I was pretty happy until I tried to restore my old username. Same thing happened.
Logged in, put in my new username and during the update (green bar)I was asked about my user and pass. . .
Nothing worked.
So I killed the program with the task manager and after I called up TED again, my user and pass have been updated.
Very strange. . .
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 14, 2011, 06:39:03 PM
. . .
I opened the settings file and hit "restore" and once the bar graph got to 6% complete, footprints quit loading the restore file, and sit there
prompting me for a password that no one knows what the hell is.  admin/admin doesn't work.  My old password/username doesn't work.
Nothing will get me back into this thing.

OK tech support...what gives??

I had almost the same problem last week.
The green bar got stuck and was asking for a password.
Nothing worked. Rotus8 gave me a hint to try admin/admin again, what I did, but with no success at first.

Then I tried everything else and found out, that the passwords have been mixed.
Username admin now worked with my old password.
I was pretty happy until I tried to restore my old username. Same thing happened.
Logged in, put in my new username and during the update (green bar)I was asked about my user and pass. . .
Nothing worked.
So I killed the program with the task manager and after I called up TED again, my user and pass have been updated.
Very strange. . .

Strange ideed...I'll have to give this a try once I get home th is afternoon...who knows, I've tried everything else!
Title: Re: TED5000 Beta R454/R245
Post by: sparker on September 14, 2011, 08:31:12 PM
The earlier release notes mention the ability to backup/restore history and point to a (non-working) link to the beta install program for Windows.   I was curious if a) the link could be fixed, and b) if the format of the save/restore data is something that could be regenerated if I have historical data saved from something like google power meter.   Over the weekend I did a firmware upgrade and unfortunately it went awry and I wound up having to fully reset the device and lost all of the previous history, so it'd be nice to find a way to combine my previously saved historical data with the existing data on the device.  I don't mind doing a bit of programming if I have to in order to generate a new historical backup that could be re-uploaded to the device, but right now I don't even have a way to do the save/restore....

It's not quite what you're asking (how to put the data back on the gateway), but I had a problem in the past where the gateway was losing data consistently, so I wrote a script that pulls all the historical data for both the netmeter and the solar generator right off the gateway twice a week. Since I have a Unix box (Mac), I have the following cron entry which runs a "getted" script.

Yes, this results in a lot of duplicate data, but ensures that I don't lose any of the "minute-by-minute" data due to rollover. I have a separate perl script that concatenates all the entries into appropriate files and removes all duplicate lines. These "detailed history files" are fed into other scripts currently under development that show year-to-year graphed comparisons of how my solar panels are doing.

Cron entry:
Code: [Select]
0 1 * * 0,4 "/Users/sparker/Documents/TED_History/getted" > "/Users/sparker/Documents/TED_History/getted.log"
"getted" script which uses "curl" (like wget) to pull data from the gateway directly
Code: [Select]
#!/bin/bash
_time=$(date +%Y%m%d-%H%M%S)
echo "Getting values from TED : $_time"

cd "/Users/sparker/Documents/TED_History"
mkdir "CSV Files/$_time"

# the -o flag is "where to store the data" and
# the 1st parameter is the web URL to get something from
curl -o "CSV Files/$_time/Minutes-MTU0_$_time.csv" "http://<ted IP address>/history/minutehistory.csv?MTU=0&INDEX=0&U=3"
curl -o "CSV Files/$_time/Minutes-MTU1_$_time.csv" "http://<ted IP address>/history/minutehistory.csv?MTU=1&INDEX=0&U=4"

curl -o "CSV Files/$_time/Hours-MTU0_$_time.csv"   "http://<ted IP address>/history/hourlyhistory.csv?MTU=0&INDEX=0&U=5"
curl -o "CSV Files/$_time/Hours-MTU1_$_time.csv"   "http://<ted IP address>/history/hourlyhistory.csv?MTU=1&INDEX=0&U=6"

curl -o "CSV Files/$_time/Daily-MTU0_$_time.csv"   "http://<ted IP address>/history/dailyhistory.csv?MTU=0&INDEX=0&U=7"
curl -o "CSV Files/$_time/Daily-MTU1_$_time.csv"   "http://<ted IP address>/history/dailyhistory.csv?MTU=1&INDEX=0&U=8"

curl -o "CSV Files/$_time/Monthly-MTU0_$_time.csv" "http://<ted IP address>/history/monthlyhistory.csv?MTU=0&INDEX=0&U=9"
curl -o "CSV Files/$_time/Monthly-MTU1_$_time.csv" "http://<ted IP address>/history/monthlyhistory.csv?MTU=1&INDEX=0&U=10"

echo "-   tar and compress files"
cd "CSV Files"
tar -czf "$_time.tgz" "$_time"
rm -rf "$_time"

echo "-   DONE...."
Title: Re: TED5000 Beta R454/R245
Post by: gman19 on September 15, 2011, 01:11:17 AM
Finally got resolved...wierd stuff!

Following the hard reset, to the letter, did not work, but may have helped...here was my resolution: I followed the hard reset provided by tech support. After everything came back up, I tried to restore with the same result....Footprints would load the backup of my setup, but when I went to update to the gateway, the password prompt came back....I don't know why I didn't think to do it before but here's where I went... I did another hard reset as instructed. This time I loaded my backup file...and went to review it as Footprints prompted BEFORE I went to update to the gateway. On the Network Settings tab, I UNCHECKED password protection...hoping it would not prompt for a password. Well, it didn't prompt for a password and successfully updated but did something funny... When I went back into Network settings tab, somehow DHCP was turned on. I had to go back and manually enter my static IP information (which was there and correct BEFORE I updated the gateway!) Anyhow, with the password turned off, I successfully have my TED5000 working again.
Title: Re: TED5000 Beta R466/R245
Post by: paulking on September 20, 2011, 06:46:53 PM
Gateway Version 1.0.466
Daughterboard Version 1.0.88
Footprints Version 1.0.245
MTU Version 1.0.61

This new version firmware no longer ignores the "Networks Settings" entry for "HTTP Port", but now does not handle DHCP properly.  This can be worked around by setting ip address directly, which does seem to work.  Networking seems unstable in general, with the builtin web server responding very slowly or timing out.

If this is not the correct forum for beta issues, please advise.  Otherwise, a response by an admin would be appreciated.
Title: Re: TED5000 Beta R454/R245
Post by: eagleye on September 21, 2011, 01:54:39 PM
The latest beta has been published. This can be used by both 20-series and 21-series gateway owners.


Gateway R454:  http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin (http://files.theenergydetective.com/firmware/beta/gateway-g-20110727-r454.bin)
Footprints R245: http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin (http://files.theenergydetective.com/firmware/beta/Footprints-20110803-R245.bin)



I recently upgraded my firmware and now my 20 series gateway is reporting a 210001 product ID in footprints and I cannot change it to what it really is ( 20 08 3E )


See my Footprints here:

     http://67.169.140.160:8733/Footprints.html

Please contact support and they'll walk you through resetting the serial id number.

http://www.theenergydetective.com/support/tickets


I have done.  Apparently I need to ship it back to be "re-flashed"
Ticket: #1272
Posted here to see if anyone else has experienced this.

I had this same problem.   My ID was zeros.  It was working for a while like that until I started losing data and the gateway was freezing.  I had to send mine back and they reflashed it.  My memory had been scrambled somehow and it was affecting the gateway operation.  Now here's the interesting thing,  Mine begins with 20, but when they reflashed it, it came back from service with R454/R245.  It works fine now.  But I thought there was a listing here that said not to flash to a 20 gateway with this version.
Title: Re: TED5000 Beta R454/R245
Post by: eagleye on September 21, 2011, 02:35:31 PM
Nevermind, I see the "NOT to flash message online applied to R452 on a 20 unit.
Title: Re: TED5000 Beta R466/R245
Post by: TedDev on September 21, 2011, 09:18:59 PM
This new version firmware no longer ignores the "Networks Settings" entry for "HTTP Port", but now does not handle DHCP properly.  This can be worked around by setting ip address directly, which does seem to work.  Networking seems unstable in general, with the builtin web server responding very slowly or timing out.

Thanks. We will look into it.
Title: Re: TED5000 Beta R466/R245
Post by: TedDev on September 22, 2011, 10:49:08 PM
This new version firmware no longer ignores the "Networks Settings" entry for "HTTP Port", but now does not handle DHCP properly.  This can be worked around by setting ip address directly, which does seem to work.  Networking seems unstable in general, with the builtin web server responding very slowly or timing out.

Thanks. We will look into it.

Fix for DHCP is in the latest beta.