Unit fails after upgrade from 02_06_06 to 02_07_05

Hi there @overeasy

Since my Iotawatt autoupdated to this release on Jan 4th 2022, it has crashed my unit and i get the Green flashing LED. I have looked at other posts and most indicate that this is related to a config txt error.

my auto update is set to minor. It has been working flawlessly until now since installation (if only everything in life was as solid as this. :rofl:)

My issue seems to be different.

I have taken a full dump of the SD card. and can provide whatever is needed from it.

My main concern, is that as it has been offline and not logging to influx for 8 days now, im assuming that the unit is still hopefully logging this and saving it to the SD, so that when i fix it and re-connect, it will update and push the data into influx. Can you please confirm this, and also provide a path forward? as i dont want to lose the data if possible. its about 1 weeks worth of data.

I will await your guidance on this before going any further.

Thanks.

Jason

Can you post the message log
/iotawatt/iotamsgs.txt

Also, is the led blinking green fast or slow?

it is a slow green blink.

the text file is 200MB. I have a truncated version below. This is from the update event, and 20 messages after.

** Restart **

SD initialized.
1/02/22 17:01:20z Real Time Clock is running. Unix time 1641142880
1/02/22 17:01:20z Reset reason: Exception
1/02/22 17:01:20z Trace: 0:0, 11:0, 11:4, 11:5, 11:5, 11:10, 11:15, 11:20, 11:20[1], 11:20[2], 11:20[3], 11:21, 11:22, 11:21, 11:22, 11:21, 11:22, 11:20[4], 11:20[5], 11:20[6], 11:20[7], 11:25, 11:30, 11:31, 11:30, 11:35, 31:100, 31:100, 31:100, 31:100, 31:101, 31:102
1/02/22 17:01:20z ESP8266 ID: 6735387, RTC PCF8523
1/02/22 17:01:20z IoTaWatt 5.0, Firmware version 02_06_06
1/02/22 17:01:20z SPIFFS mounted.
1/03/22 03:01:20 Local time zone: +10:00
1/03/22 03:01:20 device name: IotaWatt
1/03/22 03:01:20 HTTP server started
1/03/22 03:01:20 influxDB_v1: Starting, interval:10, url:http://192.168.100.19:8086
1/03/22 03:01:21 timeSync: service started.
1/03/22 03:01:21 statService: started.
1/03/22 03:01:21 dataLog: service started.
1/03/22 03:01:22 dataLog: Last log entry 01/03/22 02:58:50
1/03/22 03:01:26 historyLog: service started.
1/03/22 03:01:26 historyLog: Last log entry 01/03/22 02:58:00
1/03/22 03:01:31 WiFi connected. SSID=Two_Foos_IOT, IP=192.168.130.9, channel=6, RSSI -77db
1/03/22 03:01:31 MDNS responder started for hostname IotaWatt
1/03/22 03:01:31 LLMNR responder started for hostname IotaWatt
1/03/22 03:01:31 Updater: service started. Auto-update class is MINOR
1/03/22 03:01:34 Updater: Auto-update is current for class MINOR.
1/03/22 03:01:46 influxDB_v1: Start posting at 01/03/22 02:57:50
1/04/22 12:05:15 Updater: Update from 02_06_06 to 02_07_05
1/04/22 12:05:15 Updater: download 02_07_05
1/04/22 12:05:21 Updater: Release downloaded 6190ms, size 951104
1/04/22 12:05:35 Updater: signature verified
1/04/22 12:05:42 Updater: firmware upgraded to version 02_07_05
1/04/22 12:05:42 Updater: Firmware updated, restarting.

** Restart **

SD initialized.
1/04/22 02:05:51z Real Time Clock is running. Unix time 1641261951
1/04/22 02:05:51z Reset reason: Software/System restart
1/04/22 02:05:51z Trace: 31:0, 31:1, 31:2[3], 32:60, 32:60, 32:61, 31:1, 1:6[6], 1:1[8], 1:2[9], 9:0[9], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:3, 1:6[1], 1:6[2], 1:6[2], 1:6[2], 1:6[3], 1:5[5], 1:6[4], 5:0, 5:7
1/04/22 02:05:51z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:05:51z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:05:51z Updater: Installing update files for version 02_07_05
1/04/22 02:05:51z Updater: Installing GRAPH.HTM
1/04/22 02:05:51z Updater: Installing GRAPH.JS
1/04/22 02:05:51z Updater: Installing GRAPH2.HTM
1/04/22 02:05:52z Updater: Installing GRAPH2.JS
1/04/22 02:05:53z Updater: Installing INDEX.HTM
1/04/22 02:05:55z Updater: Installing TABLES.TXT
1/04/22 02:05:55z Updater: Installing CNFSTYLE.CSS
1/04/22 02:05:56z Updater: Installing EDIT.HTM
1/04/22 02:05:56z Updater: Installing FAVICON.ICO
1/04/22 02:05:57z Updater: Installation complete.
1/04/22 02:05:58z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:05:59z Real Time Clock is running. Unix time 1641261959
1/04/22 02:05:59z Reset reason: Exception
1/04/22 02:05:59z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:05:59z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:05:59z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:05:59z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:00z Real Time Clock is running. Unix time 1641261960
1/04/22 02:06:00z Reset reason: Exception
1/04/22 02:06:00z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:00z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:00z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:00z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:02z Real Time Clock is running. Unix time 1641261962
1/04/22 02:06:02z Reset reason: Exception
1/04/22 02:06:02z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:02z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:02z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:02z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:03z Real Time Clock is running. Unix time 1641261963
1/04/22 02:06:03z Reset reason: Exception
1/04/22 02:06:03z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:03z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:03z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:03z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:04z Real Time Clock is running. Unix time 1641261964
1/04/22 02:06:04z Reset reason: Exception
1/04/22 02:06:04z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:04z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:04z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:04z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:05z Real Time Clock is running. Unix time 1641261965
1/04/22 02:06:05z Reset reason: Exception
1/04/22 02:06:05z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:05z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:05z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:05z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:07z Real Time Clock is running. Unix time 1641261967
1/04/22 02:06:07z Reset reason: Exception
1/04/22 02:06:07z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:07z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:07z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:07z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:08z Real Time Clock is running. Unix time 1641261968
1/04/22 02:06:08z Reset reason: Exception
1/04/22 02:06:08z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:08z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:08z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:08z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:09z Real Time Clock is running. Unix time 1641261969
1/04/22 02:06:09z Reset reason: Exception
1/04/22 02:06:09z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:09z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:09z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:09z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:11z Real Time Clock is running. Unix time 1641261971
1/04/22 02:06:11z Reset reason: Exception
1/04/22 02:06:11z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:11z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:11z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:11z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:12z Real Time Clock is running. Unix time 1641261972
1/04/22 02:06:12z Reset reason: Exception
1/04/22 02:06:12z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:12z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:12z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:12z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:13z Real Time Clock is running. Unix time 1641261973
1/04/22 02:06:13z Reset reason: Exception
1/04/22 02:06:13z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:13z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:13z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:13z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:14z Real Time Clock is running. Unix time 1641261974
1/04/22 02:06:14z Reset reason: Exception
1/04/22 02:06:14z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:14z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:14z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:14z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:16z Real Time Clock is running. Unix time 1641261976
1/04/22 02:06:16z Reset reason: Exception
1/04/22 02:06:16z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:16z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:16z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:16z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:17z Real Time Clock is running. Unix time 1641261977
1/04/22 02:06:17z Reset reason: Exception
1/04/22 02:06:17z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:17z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:17z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:17z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:18z Real Time Clock is running. Unix time 1641261978
1/04/22 02:06:18z Reset reason: Exception
1/04/22 02:06:18z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:18z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:18z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:18z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:19z Real Time Clock is running. Unix time 1641261979
1/04/22 02:06:19z Reset reason: Exception
1/04/22 02:06:19z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:19z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:19z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:19z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:21z Real Time Clock is running. Unix time 1641261981
1/04/22 02:06:21z Reset reason: Exception
1/04/22 02:06:21z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:21z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:21z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:21z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:22z Real Time Clock is running. Unix time 1641261982
1/04/22 02:06:22z Reset reason: Exception
1/04/22 02:06:22z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:22z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:22z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:22z SPIFFS mounted.

** Restart **

SD initialized.
1/04/22 02:06:23z Real Time Clock is running. Unix time 1641261983
1/04/22 02:06:23z Reset reason: Exception
1/04/22 02:06:23z Trace: 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[1], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[1], 34:10[11]
1/04/22 02:06:23z ESP8266 ID: 6735387, RTC PCF8523 (68)
1/04/22 02:06:23z IoTaWatt 5.0, Firmware version 02_07_05
1/04/22 02:06:23z SPIFFS mounted.

Can you send your config.txt file in a private message please?

The bottom line is that 02_07_05 cannot digest your configuration.

Your influxDB has 103 measurements, which is well more than double anything I’ve seen before. It appears that it’s just running out of memory when trying to process the configuration and build the in-memory tables for the influx instance.

When processing the config, the unit needs enough memory to store the working json object that is the influx configuration, a json parse workspace, and heap memory to save the name, and encoded scripts for all of the measurements. It appears to have failed on about the 93rd measurement. Even if it had finished processing the influx config, I’m not sure it would have been able to run reliably.

Youu’re not the first to choke an IoTaWatt, but maybe the first to do it with just one uploader. There is no strict formula for what it can handle. Its a complex mixture of memory needed for all of the various processes and functions and it changes all the time. I could start placing limits on various configuration options, but they would all need to be very low to preclude a worst case scenario. Instead, I let users push the envelope and if it breaks, well, you need to back off.

Admittedly the failure mode here is not very user friendly, but I can say that it has been a couple of years since I’ve seen this during config processing. You will need to pare down the influx upload. Here are some recommendations:
re
Eliminate some of the metrics that are of little value like PF, VAR and VARh. I’m confident that alone would resolve this problem and would not have any effect on the remaining metrics like Watts, kWh (you should be using Wh), Amps and VA.

If you are interested in changing your schema, it would be more economical to drop the units appended to each name and either add a units tag or set the field_key to units.

I will PM a pared down config.txt with some of the measurements mentioned above removed. Once you get it restarted, you should be able to edit and fine tune.

Shorten the

1 Like

hmm… ok. sounds fair enough.

Im not sure how the whole tag thing works, and i set it up the way it is as it made sense at the time and what not.

Am i correct in understanding that all the data on the SD card in the iotalog.log is the data that has also been shipped to influx?

if im going to change my schemma, i would like it to all be the same etc… so, if it can be changed and then re-uploaded to influx that would be swell.

As it currently sits, is it still polling and recording the data to the internal memory? or is it stuck in a boot loop of sorts and is essentially doing nothing at the moment?

Happy to work on a plan forward from here.

Sorry to say it’s stuck in a boot loop since Jan 4th.

I should have the edited config in a little bit. In the meantime you will need to shut down the unit and remove the SDcard so you can replace the config.

all good.

I admit, that the VAH, VAR and PF are not something that i use, but im a ‘get all the data’ person. as you never know what you may need in the future.

but if they are an issue, im happy to drop them.

The main thing will be the swapping form KWH to WH. can you provide some info on why this should be? and, if i do, is there a simple way where i can then modify all the data in influx to match accordingly?