IotaWatt becoming unavailable

I’ve noticed some odd behaviour recently (couple of months), which I kind of ignored… however I set out to try and fix over the last week. I noticed a few other topics people have posted which might be connected, and all the feedback seemed to be regarding poor wifi signal, however considering they happened at similar times, I’m wondering if an update has caused an issue.

While everything was working fine… I noticed that the problem is first in my pvoutput uploads around 26/09… it was working fine before. I was getting no data uploaded for one or both of the iotawatt at random times during the day for periods between 5 minutes and an hour.

The way I have my home assistant set up basically means if the iotawatt isn’t reporting data, zero value is uploaded. When I did notice it happening live, if I tried to check the iotawatt webserver, it wasn’t aviaable. I coudln’t ping the device. A restart fixed it… or waiting enough time fixed it.

I assumed that it was my wifi… it not the greatest signal (around 70 +/- 3). I recently found a work around, which is to get my server to constantly ping the iotawatts. As soon as they don’t respond, I get my AP (unifi wifi 6 lr) to reconnect the device. They always respond immediately and come back. I would have assumed that if there was signal issues reconnecting the device via the AP would fail sometimes. I had the server log everytime it happened, and it seemed to be happening a lot more regualrly that I thought… I wasn’t losing stats this often, so sometimes it was fixing itself… and sometimes, it just stayed disconnected for those 5-60 minute periods. This is just today so far…

Thu 17 Nov 2022 00:33:37 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 00:34:37 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 00:37:04 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 01:20:22 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 02:29:37 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 03:04:52 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 03:27:31 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 04:18:11 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 04:20:16 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 05:18:52 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 05:53:17 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 06:55:47 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 07:00:11 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 08:26:32 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 08:55:11 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 09:35:41 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 11:02:11 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 11:25:32 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 11:48:21 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 11:51:21 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 12:48:27 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 12:49:57 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 12:50:32 AEST ==== Reconnecting IotaWatt1
Thu 17 Nov 2022 13:25:16 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 13:31:17 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 13:45:36 AEST ==== Reconnecting IotaWatt2
Thu 17 Nov 2022 13:46:26 AEST ==== Reconnecting IotaWatt2

Again this isn’t an issue for me right now, because of my work around. And since I had been reconnecting the iotawatts automatically I haven’t missed data in 4 days now. However others might be having similar issues… and thought maybe some further investigation is required, or at least a workaround if you have the ability to reconnect clients remotely.

I know the easy blame is wifi signal… however consdering that:

I never had wifi signal issues before 26/09
I can always connect the iotawatts immedately by forcing a reconnect via the AP
Other people seem to have similar issues starting at similar timelines
It seemed to be getting worse with time

I want to say this isn’t a wifi signal issue, but maybe something that has only recently changed, or something that starts happening after a while. I would assume that most people that use pvoutput are using the inbuilt uploaded, which would upload missed data automatically (I think)… and so its an issue only experianced by those using 3rd party uploaders.

I also could be way off and talking rubbish… otherwise I have zero complaints about my iotawatt… I can’t wait to get my battery installed and log even more data!

There are many thousands of installed IoTaWatt and currently I believe three outstanding reports of problems suspected to be caused by WiFi problems. None of them appear to have started with the latest release of firmware. I’m having trouble understanding the relationship between your connectivity issues and an update. Can you clarify when your system was last updated and show the message logs before and after?

I don’t know an update even occured, I’m just saying this problem started randomly, and I found a couple of others which happened at a similar time, so I assumed, probably incorrectly.

I realise there are thousands of users with no issues, but if uploaders automatically fix any missing data when communicatoins are restored, they wouldn’t know there are issues? So its only users that don’t use the uploaders that notice problems.

SD initialized.
11/01/22 23:11:07z Real Time Clock is running. Unix time 1667344267
11/01/22 23:11:07z Reset Reason: Power-fail restart.
11/01/22 23:11:07z ESP8266 ID: 565612, RTC M41T81 (68)
11/01/22 23:11:07z IoTaWatt 5.0, Firmware version 02_07_05
11/01/22 23:11:07z SPIFFS mounted.
11/02/22 09:11:07 Local time zone: +10:00
11/02/22 09:11:07 device name: IotaWat1
11/02/22 09:11:10 Connecting with WiFiManager.
11/02/22 09:11:14 HTTP server started
11/02/22 09:11:15 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -72db
11/02/22 09:11:15 MDNS responder started for hostname IotaWat1
11/02/22 09:11:15 LLMNR responder started for hostname IotaWat1
11/02/22 09:11:15 timeSync: service started.
11/02/22 09:11:15 statService: started.
11/02/22 09:11:15 Updater: service started. Auto-update class is MINOR
11/02/22 09:11:15 dataLog: service started.
11/02/22 09:11:16 dataLog: Last log entry 11/02/22 09:11:00
11/02/22 09:11:16 Updater: Auto-update is current for class MINOR.
11/02/22 09:11:20 historyLog: service started.
11/02/22 09:11:20 historyLog: Last log entry 11/02/22 09:11:00
11/02/22 09:11:25 PVoutput: started
11/02/22 09:11:25 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode
11/02/22 09:11:26 PVoutput: Start status beginning 11/02/22 09:15:00

** Restart **

SD initialized.
11/04/22 04:51:23z Real Time Clock is running. Unix time 1667537483
11/04/22 04:51:23z Reset Reason: Power-fail restart.
11/04/22 04:51:23z ESP8266 ID: 565612, RTC M41T81 (68)
11/04/22 04:51:23z IoTaWatt 5.0, Firmware version 02_07_05
11/04/22 04:51:23z SPIFFS mounted.
11/04/22 14:51:23 Local time zone: +10:00
11/04/22 14:51:23 device name: IotaWat1
11/04/22 14:51:26 Connecting with WiFiManager.
11/04/22 14:53:39 Did not connect after power-fail. Restarting to reset WiFi.

** Restart **

SD initialized.
11/04/22 04:53:40z Real Time Clock is running. Unix time 1667537620
11/04/22 04:53:40z Reset reason: Software/System restart
11/04/22 04:53:40z Trace:  34:30, 34:10[9], 34:30, 34:10[10], 34:5, 34:5, 34:5, 34:6[1], 34:10[11], 34:5, 34:5, 34:5, 34:6[10], 34:30, 34:10[1], 34:30, 34:10[2], 34:30, 34:10[3], 34:30, 34>
11/04/22 04:53:40z ESP8266 ID: 565612, RTC M41T81 (68)
11/04/22 04:53:40z IoTaWatt 5.0, Firmware version 02_07_05
11/04/22 04:53:40z SPIFFS mounted.
11/04/22 14:53:40 Local time zone: +10:00
11/04/22 14:53:40 device name: IotaWat1
11/04/22 14:53:40 HTTP server started
11/04/22 14:53:40 timeSync: service started.
11/04/22 14:53:40 statService: started.
11/04/22 14:53:40 dataLog: service started.
11/04/22 14:53:41 dataLog: Last log entry 11/04/22 14:51:00
11/04/22 14:53:58 historyLog: service started.
11/04/22 14:53:58 historyLog: Last log entry 11/04/22 14:51:00
11/04/22 14:53:58 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -69db
11/04/22 14:53:58 MDNS responder started for hostname IotaWat1
11/04/22 14:53:58 LLMNR responder started for hostname IotaWat1
11/04/22 14:53:58 Updater: service started. Auto-update class is MINOR
11/04/22 14:53:58 PVoutput: started
11/04/22 14:54:08 Updater: Auto-update is current for class MINOR.
11/04/22 14:54:08 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode
11/04/22 14:54:09 PVoutput: Start status beginning 11/04/22 14:55:00
11/10/22 03:07:29 Updater: Invalid response from server. HTTPcode: -4


** Restart **

SD initialized.
11/13/22 03:47:47z Real Time Clock is running. Unix time 1668311267
11/13/22 03:47:47z Reset Reason: Power-fail restart.
11/13/22 03:47:47z ESP8266 ID: 565612, RTC M41T81 (68)
11/13/22 03:47:47z IoTaWatt 5.0, Firmware version 02_07_05
11/13/22 03:47:47z SPIFFS mounted.
11/13/22 13:47:47 Local time zone: +10:00
11/13/22 13:47:47 device name: IotaWat1
11/13/22 13:47:50 HTTP server started
11/13/22 13:47:50 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -66db
11/13/22 13:47:50 MDNS responder started for hostname IotaWat1
11/13/22 13:47:50 LLMNR responder started for hostname IotaWat1
11/13/22 13:47:50 timeSync: service started.
11/13/22 13:47:50 statService: started.
11/13/22 13:47:50 Updater: service started. Auto-update class is MINOR
11/13/22 13:47:51 Updater: Auto-update is current for class MINOR.
11/13/22 13:47:51 dataLog: service started.
11/13/22 13:47:52 dataLog: Last log entry 11/13/22 13:47:40
11/13/22 13:47:55 historyLog: service started.
11/13/22 13:47:56 historyLog: Last log entry 11/13/22 13:47:00
11/13/22 13:48:00 PVoutput: started
11/13/22 13:48:00 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode
11/13/22 13:48:01 PVoutput: Start status beginning 11/13/22 13:50:00
11/13/22 14:21:05 WiFi disconnected.
11/13/22 14:21:06 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -68db
11/13/22 16:21:20 WiFi disconnected.
11/13/22 16:21:57 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -65db
11/13/22 17:22:39 WiFi disconnected.
11/13/22 17:22:40 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -70db
11/13/22 18:23:28 WiFi disconnected.

So the disconnections at the end of the logs is where I’m forcing a reconnection to the AP. There are now many reconnections, but not actually an issue as I can always get the data and connect / ping. However there is no indication that disconnections have been happening at times when pvoutput record zero data. I’ve confirmed at times when zero data is being recorded that iotawatt has not been available, not responding to pings, webserver not avaialble, and no data can be accessed via home assistant. It will always fix itself over an hour or so.


|02/11/22|8:10PM|0W|0W|0W|0W|209W|0W|
|---|---|---|---|---|---|---|---|
|02/11/22|8:05PM|0W|0W|0W|0W|209W|0W|
|02/11/22|8:00PM|0W|0W|0W|0W|209W|0W|
|02/11/22|7:55PM|0W|0W|0W|0W|208W|0W|
|02/11/22|7:50PM|0W|0W|0W|0W|208W|0W|
|02/11/22|7:45PM|0W|0W|0W|0W|208W|0W|
|02/11/22|7:40PM|0W|0W|0W|0W|214W|0W|
|02/11/22|7:35PM|0W|0W|0W|0W|215W|0W|
|02/11/22|7:30PM|0W|0W|0W|0W|192W|1W|
|02/11/22|7:25PM|0W|0W|0W|0W|191W|1W|
|02/11/22|7:20PM|0W|0W|0W|0W|191W|1W|
|02/11/22|7:15PM|0W|0W|0W|0W|191W|1W|
|03/11/22|10:10PM|0W|0W|0W|0W|125W|0W|
|---|---|---|---|---|---|---|---|
|03/11/22|10:05PM|0W|0W|0W|0W|127W|1W|
|03/11/22|10:00PM|0W|0W|0W|0W|60W|0W|
|03/11/22|9:55PM|0W|0W|0W|0W|85W|0W|
|03/11/22|9:50PM|0W|0W|0W|0W|99W|0W|
|03/11/22|9:45PM|0W|0W|0W|0W|99W|0W|
|03/11/22|9:40PM|0W|0W|0W|0W|99W|0W|
|03/11/22|8:10PM|0W|0W|0W|0W|0W|0W|
|---|---|---|---|---|---|---|---|
|03/11/22|8:05PM|0W|0W|0W|0W|0W|0W|
|03/11/22|8:00PM|0W|0W|0W|0W|0W|0W|
|03/11/22|7:55PM|0W|0W|0W|0W|0W|0W|
|03/11/22|7:50PM|0W|0W|0W|0W|0W|0W|
|03/11/22|7:45PM|0W|0W|0W|0W|108W|0W|
|03/11/22|7:40PM|0W|0W|0W|0W|104W|0W|
|03/11/22|7:35PM|0W|0W|0W|0W|99W|0W|
|03/11/22|6:10PM|20W|1W|534W|4W|0W|0W|
|---|---|---|---|---|---|---|---|
|03/11/22|6:05PM|20W|1W|436W|3W|0W|0W|
|03/11/22|6:00PM|20W|1W|295W|3W|0W|0W|
|03/11/22|5:55PM|20W|0W|380W|3W|0W|0W|
|03/11/22|5:50PM|20W|1W|609W|3W|0W|0W|
|03/11/22|5:45PM|21W|1W|593W|3W|0W|0W|
|03/11/22|5:40PM|21W|1W|712W|3W|0W|0W|
|03/11/22|5:35PM|20W|1W|770W|3W|0W|0W|
|04/11/22|2:50PM|0W|0W|0W|0W|19W|2W|
|---|---|---|---|---|---|---|---|
|04/11/22|2:45PM|0W|0W|0W|0W|19W|1W|
|04/11/22|2:40PM|0W|0W|0W|0W|19W|2W|

Theses are times when data was not being received that matched times on the iotawatt log.

I’m sorry, I’m not trying to be difficult.

Your unit has not updated recently. Release 02_07_05 has been auto-update MINOR since January 3, 2022.

When it rains it pours. It’s very common for folks to read about one user’s problem, associate one aspect of that with their experience, and then pile on to the thread. In some instances, it’s justified and helps to resolve a new issue. Most of the time the problems end up being unrelated. Except of course for WiFi problems.

So, I’m trying to sort out exactly what you are experiencing and determine what might be the issue. So far, we’ve ruled out firmware update.

What is this? Where does it come from, and why does it start out in descending chronological order and then switch to ascending?

I’ve looked at your PVoutput live updates and from what I can see, there are random outages of the voltage metric only that, as you say, stop around Nov 14. That’s hard to do with one IoTaWatt. Are you uploading to PVoutput from two different IoTaWatt units? Can I see the PVoutput setup(s)?

Can you plot voltage and total power for both of your units for Nov 2 using Graph+ and post those please?

Is the message log that you posted for IotaWat1 contiguous from Nov 4 to Nov 13 or is that edited?

Can I see the message log for the other unit over that same period?

Finally, what are you using for VTs?

What is this? Where does it come from, and why does it start out in descending chronological order and then switch to ascending?

I’m not sure if you can see it on my pvoutput… but its the extended data. I just copied the parts where it was showing 0W on those 2 days. But if you can see it, it has random outages, much like the voltage, that start around 26/09 and end 14/11.

The columns are:
Air Con - Iotawatt #1 - 3 phase
Hot Water - Iotawatt #1
GPO - Iotawatt #1 - 4 circuits added together
Oven - Iotawatt #1
Lights - Iotawatt #2 - 3 circuits added together
Waste Treatment + Spa - - Iotawatt #2

The voltage is coming fom Iotawatt #1, so you will notice its missing voltage on 2/11/22 at the same time 4 values are missing from the extended data.

I’ve looked at your PVoutput live updates and from what I can see, there are random outages of the voltage metric only that, as you say, stop around Nov 14. That’s hard to do with one IoTaWatt. Are you uploading to PVoutput from two different IoTaWatt units? Can I see the PVoutput setup(s)?

Yes, I have 2 Iotawatts, but I am not using the iotawatt to upload to pvoutput. I am using home assistant integration to get all the data from the iotawatts into home assistant. Then I was using a statistic sensor to average 5 minutes of data, and upload all the data from iotawatt1, iotawatt2 and inverter (total power used, and solar generated) in one single go every 5 minutes instead of having the iotawatts upload seperately, plus a 3rd upload from my inverter. (And I know I could, and maybe should use the iotawatt data for total power usage and solar, but when I initally set it up, I think I did choose to use the inverter data for some reason)

Can you plot voltage and total power for both of your units for Nov 2 using Graph+ and post those please?

Iotawatt 1 - I don’t have total power on iotawatt 1, I only monitor the total on iotawatt 2, and have half the circuits, I included the solar generation. I also monitor all 3 phases voltage (something again, you don’t nessesarily recommend or say is required)

Iotawatt 2

Is the message log that you posted for IotaWat1 contiguous from Nov 4 to Nov 13 or is that edited?

Its contiguous from 1st to 13th, it was just truncated from where it I started forcing disconnections around 2pm on the 13th, as its just repeated messages about disconnections.

Can I see the message log for the other unit over that same period?

I must have reset both units on the 1st for some reason, or had a power outage, as they both


** Restart **

SD initialized.
11/01/22 23:11:09z Real Time Clock is running. Unix time 1667344269 
11/01/22 23:11:09z Reset Reason: Power-fail restart.
11/01/22 23:11:09z ESP8266 ID: 562617, RTC M41T81 (68)
11/01/22 23:11:09z IoTaWatt 5.0, Firmware version 02_07_05
11/01/22 23:11:09z SPIFFS mounted.
11/02/22 09:11:09 Local time zone: +10:00
11/02/22 09:11:09 device name: IotaWat2
11/02/22 09:11:12 Connecting with WiFiManager.
11/02/22 09:11:17 HTTP server started
11/02/22 09:11:17 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -71db
11/02/22 09:11:17 MDNS responder started for hostname IotaWat2
11/02/22 09:11:17 LLMNR responder started for hostname IotaWat2
11/02/22 09:11:17 timeSync: service started.
11/02/22 09:11:17 statService: started.
11/02/22 09:11:17 Updater: service started. Auto-update class is MINOR
11/02/22 09:11:18 Updater: Auto-update is current for class MINOR.
11/02/22 09:11:18 dataLog: service started.
11/02/22 09:11:18 dataLog: Last log entry 11/02/22 09:11:00
11/02/22 09:11:22 historyLog: service started.
11/02/22 09:11:22 historyLog: Last log entry 11/02/22 09:10:00
11/02/22 09:11:27 PVoutput: started
11/02/22 09:11:27 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode  
11/02/22 09:11:28 PVoutput: Start status beginning 11/02/22 09:15:00

** Restart **

SD initialized.
11/04/22 04:51:23z Real Time Clock is running. Unix time 1667537483 
11/04/22 04:51:23z Reset Reason: Power-fail restart.
11/04/22 04:51:23z ESP8266 ID: 562617, RTC M41T81 (68)
11/04/22 04:51:23z IoTaWatt 5.0, Firmware version 02_07_05
11/04/22 04:51:23z SPIFFS mounted.
11/04/22 14:51:23 Local time zone: +10:00
11/04/22 14:51:23 device name: IotaWat2
11/04/22 14:51:26 Connecting with WiFiManager.
11/04/22 14:51:37 HTTP server started
11/04/22 14:51:37 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -68db
11/04/22 14:51:37 MDNS responder started for hostname IotaWat2
11/04/22 14:51:37 LLMNR responder started for hostname IotaWat2
11/04/22 14:51:37 timeSync: service started.
11/04/22 14:51:50 statService: started.
11/04/22 14:51:50 Updater: service started. Auto-update class is MINOR
11/04/22 14:51:51 dataLog: service started.
11/04/22 14:51:51 dataLog: Last log entry 11/04/22 14:51:00
11/04/22 14:51:56 historyLog: service started.
11/04/22 14:51:56 historyLog: Last log entry 11/04/22 14:50:00
11/04/22 14:52:01 PVoutput: started
11/04/22 14:52:05 Updater: Invalid response from server. HTTPcode: -4
11/04/22 14:54:09 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode  
11/04/22 14:54:13 PVoutput: Start status beginning 11/04/22 14:55:00
11/04/22 15:51:56 Updater: Auto-update is current for class MINOR.

** Restart **

SD initialized.
11/13/22 03:47:50z Real Time Clock is running. Unix time 1668311270 
11/13/22 03:47:50z Reset Reason: Power-fail restart.
11/13/22 03:47:50z ESP8266 ID: 562617, RTC M41T81 (68)
11/13/22 03:47:50z IoTaWatt 5.0, Firmware version 02_07_05
11/13/22 03:47:50z SPIFFS mounted.
11/13/22 13:47:50 Local time zone: +10:00
11/13/22 13:47:50 device name: IotaWat2
11/13/22 13:47:53 HTTP server started
11/13/22 13:47:53 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -70db
11/13/22 13:47:53 MDNS responder started for hostname IotaWat2
11/13/22 13:47:53 LLMNR responder started for hostname IotaWat2
11/13/22 13:47:53 timeSync: service started.
11/13/22 13:47:53 statService: started.
11/13/22 13:47:53 Updater: service started. Auto-update class is MINOR
11/13/22 13:47:53 dataLog: service started.
11/13/22 13:47:54 dataLog: Last log entry 11/13/22 13:47:35
11/13/22 13:47:54 Updater: Auto-update is current for class MINOR.
11/13/22 13:47:58 historyLog: service started.
11/13/22 13:47:58 historyLog: Last log entry 11/13/22 13:47:00
11/13/22 13:48:02 PVoutput: started
11/13/22 13:48:04 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode  
11/13/22 13:48:04 PVoutput: Start status beginning 11/13/22 13:50:00
11/13/22 15:16:52 WiFi disconnected.
11/13/22 15:16:53 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -71db
11/13/22 15:28:14 WiFi disconnected.
11/13/22 15:29:13 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -70db
11/13/22 15:38:00 WiFi disconnected.
11/13/22 15:38:33 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -68db
11/13/22 15:51:14 WiFi disconnected.
11/13/22 15:51:43 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -66db
11/13/22 20:03:28 WiFi disconnected.
11/13/22 20:03:29 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -66db
11/13/22 21:09:59 WiFi disconnected.

Finally, what are you using for VTs?

Using 3x the recommended ones from jaycar,
VT
, Powertech MP-3027(Aus)

They are split and fed into both iotawatt…

Iotawatt #1

0 PhaseA VT, Powertech MP-3027(Aus)
1 Solar_1 CT, AcuCT-H040-50
2 Solar_2 CT, AcuCT-H040-50, Vref:13
3 Solar_3 CT, AcuCT-H040-50, Vref:14
4 AC_1 CT, AcuCT-H040-50
5 AC_2 CT, AcuCT-H040-50, Vref:13
6 AC_3 CT, AcuCT-H040-50, Vref:14
7 GPO1 CT, AcuCT-H040-50, Vref:14
8 GPO2 CT, AcuCT-H040-50, Vref:13
9 GPO3 CT, AcuCT-H040-50, Vref:14
10 GPO4 CT, AcuCT-H040-50
11 Oven CT, AcuCT-H040-50
12 Hot_Water CT, AcuCT-H040-50, Vref:13
13 PhaseB VT, Powertech MP-3027(Aus)
14 PhaseC VT, Powertech MP-3027(Aus)

Iotawatt #2

0 PhaseA VT, Powertech MP-3027(Aus)
1 Main_1 CT, AcuCT-H063-100
2 Main_2 CT, AcuCT-H063-100, Vref:13
3 Main_3 CT, AcuCT-H063-100, Vref:14
4 Lights_1 CT, AcuCT-H040-50
5 Lights_2 CT, AcuCT-H040-50, Vref:13
6 Lights_3_Smokes CT, AcuCT-H040-50, Vref:14
7 Waste_Treat CT, AcuCT-H040-50
8 Spa CT, AcuCT-H040-50, Vref:13
9 Solar_1 CT, AcuCT-H040-50
10 Solar_2 CT, AcuCT-H040-50, Vref:13
11 Solar_3 CT, AcuCT-H040-50, Vref:14
12
13 PhaseB VT, Powertech MP-3027(Aus)
14 PhaseC VT, Powertech MP-3027(Aus)

Both IoTaWatt show a PVoutput uploader starting. Can I see the PVoutput setup for each of the IoTaWatt?

That’s fine. I don’t recommend it because most folks get very accurate results with just one and it’s complicated to provide the three plugs. What you are doing is better.

Just want to make sure you are preserving polarity in the splitters, and that each IoTaWatt has a separate USB power supply. This is important.

I can’t address the basic problem until I understand what the IoTaWatt are uploading to PVoutput. This is starting to sound like it could be a race condition.

If you are using HA Energy, I would recommend you look at setting up an integrator as described here in IoTaWatt Docs.

Both IoTaWatt show a PVoutput uploader starting. Can I see the PVoutput setup for each of the IoTaWatt?

I had them setup before, but both are stopped via the UI. I will grab the setup and confirm they are stopped when I’m home. I can delete the settings entirely as I no longer use them too.

Just want to make sure you are preserving polarity in the splitters, and that each IoTaWatt has a separate USB power supply. This is important.

Not sure about preserving the polarity, I’m using these to split the VT’s…

And they have a seperate USB power supply.

If you are using HA Energy, I would recommend you look at setting up an integrator as described here in IoTaWatt Docs.

I’ll look into that.


SD initialized.
11/13/22 03:47:47z Real Time Clock is running. Unix time 1668311267
11/13/22 03:47:47z Reset Reason: Power-fail restart.
11/13/22 03:47:47z ESP8266 ID: 565612, RTC M41T81 (68)
11/13/22 03:47:47z IoTaWatt 5.0, Firmware version 02_07_05
11/13/22 03:47:47z SPIFFS mounted.
11/13/22 13:47:47 Local time zone: +10:00
11/13/22 13:47:47 device name: IotaWat1
11/13/22 13:47:50 HTTP server started
11/13/22 13:47:50 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.20, channel=6, RSSI -66db
11/13/22 13:47:50 MDNS responder started for hostname IotaWat1
11/13/22 13:47:50 LLMNR responder started for hostname IotaWat1
11/13/22 13:47:50 timeSync: service started.
11/13/22 13:47:50 statService: started.
11/13/22 13:47:50 Updater: service started. Auto-update class is MINOR
11/13/22 13:47:51 Updater: Auto-update is current for class MINOR.
11/13/22 13:47:51 dataLog: service started.
11/13/22 13:47:52 dataLog: Last log entry 11/13/22 13:47:40
11/13/22 13:47:55 historyLog: service started.
11/13/22 13:47:56 historyLog: Last log entry 11/13/22 13:47:00
11/13/22 13:48:00 PVoutput: started
11/13/22 13:48:00 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode
11/13/22 13:48:01 PVoutput: Start status beginning 11/13/22 13:50:00


SD initialized.
11/13/22 03:47:50z Real Time Clock is running. Unix time 1668311270
11/13/22 03:47:50z Reset Reason: Power-fail restart.
11/13/22 03:47:50z ESP8266 ID: 562617, RTC M41T81 (68)
11/13/22 03:47:50z IoTaWatt 5.0, Firmware version 02_07_05
11/13/22 03:47:50z SPIFFS mounted.
11/13/22 13:47:50 Local time zone: +10:00
11/13/22 13:47:50 device name: IotaWat2
11/13/22 13:47:53 HTTP server started
11/13/22 13:47:53 WiFi connected. SSID=mnm_iot_garage, IP=192.168.2.21, channel=6, RSSI -70db
11/13/22 13:47:53 MDNS responder started for hostname IotaWat2
11/13/22 13:47:53 LLMNR responder started for hostname IotaWat2
11/13/22 13:47:53 timeSync: service started.
11/13/22 13:47:53 statService: started.
11/13/22 13:47:53 Updater: service started. Auto-update class is MINOR
11/13/22 13:47:53 dataLog: service started.
11/13/22 13:47:54 dataLog: Last log entry 11/13/22 13:47:35
11/13/22 13:47:54 Updater: Auto-update is current for class MINOR.
11/13/22 13:47:58 historyLog: service started.
11/13/22 13:47:58 historyLog: Last log entry 11/13/22 13:47:00
11/13/22 13:48:02 PVoutput: started
11/13/22 13:48:04 PVoutput: System 10kw Woodcrest Estate, interval 5, donator mode
11/13/22 13:48:04 PVoutput: Start status beginning 11/13/22 13:50:00

So I’m fairly confident they haven’t been running for 6+ months… I think I only used iotawatt to upload to pvoutput when I had 1 iotawatt. When I got the 2nd around feb this year I found it frustrating to have both uploading different stats, so I came up with the home assistant solution to do everything.

I can delete the pvoutput settings and see if it changes anything though.

OK, it was not clear to me that the PVoutput uploaders were stopped, and the uploading was being done by HA.

So, the basic problem appears to be that since Sept 26, IotaWat1 occasionally becomes incommunicado. As a result, when HA queries it, it does not get the data it needs to upload to PVoutput. The condition appeared to resolve spontaneously within a relatively short period of time of several minutes to an hour. No disconnects are logged that correspond to those WiFi outages. The IoTaWatt does not suffer any lapse of sampling and logging data. You setup a remedial system on Nov 13 that pings the IoTaWatt and sends the AP a command to initiate reconnect when the ping is not satisfied. The problem appears to be remediated.

Is that correct?

If so, couple of things:

There is no evidence that IotaWat2 sustained any such outages, yet the ping/reset log shows about the same number of reconnect events for IotaWat2.

There should be some messages in HA when the IoTaWatt integration queries fail. Did you observe any such messages?

Yet there were no changes to IoTaWatt either. Are you suggesting a hardware failure?

And that doesn’t indicate a WiFi issue?

Users have had issues with WiFi for years. I did not recognize any significant change in frequency or symptoms in September.

From what I can see looking at the voltage lapses in your PVoutput live data, it had bad days and good days.

Is that correct?

Correct

If so, couple of things:

There is no evidence that IotaWat2 sustained any such outages, yet the ping/reset log shows about the same number of reconnect events for IotaWat2.

There is evidence that IotaWat2 does the same thing… and it started happening at the same time as IotaWat1.

Can you see the extended data on my pvoutput? Showing the Aircon, Hot Water, GPO, Oven, Lights, Waste Treament? I’m not sure if that data is only visable to me or the public.

This is a screenshot from 29/09.

The 4 columns on the left is data from IotaWat1. Aircon, Hotwater, GPO, Oven.
The 2 on the right are from IotaWat2. Lights, Waste Treatment

So they both went down, at different times during that day. The evidence you can see with the voltage also comes from IotaWat1. Happening at the same time suggests that it is a problem on my end, I must admit that… but I’m pretty positive nothing changed this side with regards to the network. Possibilty I did something different with home assistant, but at this stage I cannot remember, I don’t think I changed anything.

There should be some messages in HA when the IoTaWatt integration queries fail. Did you observe any such messages?

There has been, but they have dropped off the log. I will grab them if it happens again.

Yet there were no changes to IoTaWatt either. Are you suggesting a hardware failure?

Unlikely as its happening to both at the same time.

And that doesn’t indicate a WiFi issue?

I’m no expert on networking, but that was just my theory based on it just started happening but was fine before 26/09. And while I cannot right now for certain say I didn’t change something on home assistant (not that I should think that would matter, unless home assistant queries are breaking iotawatt). Nothing has changed in relation to my network or access points.

I ran a temporary cable and moved my access point to improve signal. RSSI is now between -45 and -50 on both. I disabled the automatic reconnection on the IotaWat2, but it will still monitor the ping. And will monitor over the next couple of days to see if anything has changed. Unfortunately because of the way I am now handling the drop in communication with home assistant, I don’t think it will log it correctly unless its down for more than 5 minutes.

Not a expert on WiFi but it’s not unusual for users to say they didn’t change anything with WiFi yet the problem eventually is resolved with WiFi changes. Unless you live in a very rural environment, there may be others competing for bandwidth on the same channels that you use. Moreover there are more and more 2.4GHz devices in the IOT and other markets, some that potentially are not FCC approved and/or misbehave. I’m not saying you have such devices, only that they be in the vicinity. Radio waves do not respect property boundaries.

Improving the signal is a start, but it may also involve experimenting with alternate channels.

I understand. And I’m not overly concerned as I have a work around that seems to work without issue. But I’ll try check the channel later on, I don’t think the AP is automatically changing channels, when it was setup the channel was fairly clear, but that may have changed since I initially set up.

So far checking remotely for the last few hours, its still missing pings randomly. But considering its not reconnecting the device anymore, the iotawatt is responding again within a minute so far. I was definitely kicking the connection more than I needed to, I just have to wait for a longer period to get logged on pvoutput when I know its been down for over 5 minutes.

So in reality its was only doing it a few times a day, not the 25+ reconnections I had been forcing and logging, as its seems most of them solve themselves within a few seconds.

1 Like