Firmware 02_03_02

Support
1

Hi Bob,
I had my system on the ALPHA channel (I know, living on the edge!), and a day or so ago, it updated itself to 02_03_02. At that point, it stopped posting to a local emoncms server, with endless errors in the log:
EmonService: response not ok. Retrying.
It looks like you’ve added the ability to post to both emoncms & to InfluxDB - which I would indeed like to try!
I did try reverting to the BETA channel, but I get an error:
Update file format error.

Here’s the bottom of my current log:

** Restart **

No clock yet: SD initialized.
3/27/18 15:56:24 Real Time Clock is running. Unix time: 1522166184
3/27/18 15:56:24 Version: 02_03_02
3/27/18 15:56:24 Reset reason: Software Watchdog
3/27/18 15:56:24 Trace: 3:6, 3:6, 9:4, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5, 1:6, 1:1, 9:0, 9:1, 8:4, 8:6, 8:8, 9:3, 9:4, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5, 3:0, 3:6, 3:6, 1:6, 1:3, 1:4, 1:5, 3:0
3/27/18 15:56:24 ESP8266 ChipID:2870702
3/27/18 08:56:24 device name: IotaWatt, version: 3
3/27/18 08:56:24 Local time zone: -7
3/27/18 08:56:24 MDNS responder started
3/27/18 08:56:24 You can now connect to http://IotaWatt.local
3/27/18 08:56:24 HTTP server started
3/27/18 08:56:24 dataLog: service started.
3/27/18 08:56:25 dataLog: Last log entry:1522166155
3/27/18 08:56:25 statService: started.
3/27/18 08:56:25 timeSync: service started.
3/27/18 08:56:25 WiFi connected. SSID: BLACKBURN, IP: 192.168.2.45
3/27/18 08:56:25 Updater: started.
3/27/18 08:56:25 historyLog: service started.
3/27/18 08:56:26 historyLog: Last log entry:1522166160
3/27/18 08:56:26 EmonService: started.url: 192.168.2.44:80/emoncms, node: IotaWatt, post interval: 10, unsecure GET
3/27/18 08:56:27 EmonService: Start posting at 1522049640
3/27/18 08:56:27 Updater: Update from 02_03_02 to 02_03_01
3/27/18 08:56:27 Updater: download 02_03_01
3/27/18 08:56:40 Updater: Release downloaded 12754ms, size 591460
3/27/18 08:56:42 Update file format error.
3/27/18 08:56:46 EmonService: response not ok. Retrying.
3/27/18 08:56:47 EmonService: response not ok. Retrying.
3/27/18 08:56:48 EmonService: response not ok. Retrying.
3/27/18 08:56:49 EmonService: response not ok. Retrying.
3/27/18 08:56:50 EmonService: response not ok. Retrying.
3/27/18 08:56:51 EmonService: response not ok. Retrying.
3/27/18 08:56:52 EmonService: response not ok. Retrying.

Thanks!
Sandy

2

Hello Sandy,

Livin’ on the edge. Not too bad, lets try and sort this out:

I can see the problem with retries on unsecure posting to Emoncms. That’s fixed here in my development branch. It works fine until you get an error, then the retry logic is flawed. So I don’t know what triggers the initial error, but the rest is predictable.

The firmware downgrade is another known issue. I’ve been seeing some of this intermittently since the update went async. Not sure I’m going to stay with that. It usually works after a few retries (an hour apart) so I’d say just hang in there for awhile and see if you get the downgrade. You can speed it up by doing repeated software restarts:

iotawatt.local/command?restart=yes

You should probably stop the Emoncms Service until the downgrade happens. Do that by deleting it. When you get it going again on 02_03_01 it should catch up all of the history.

3

Hi Bob,
Sure enough, after a couple of hours, it restarted itself again, reverted to 02_03_01 & uploaded all the missing data. That’s pretty resilient ya know!
I guess I’ll keep an eye out for 02_03_03 & jump more deliberately off the edge.
Thanks again,
Sandy

1 Like