WiFi Connectivity (connect/disconnect) Issues

Support
#1

Hello, I was browsing the files on the IoTaWatt today and noticed there are periods of good connectivity (e.g. 10-12 hours) but then a series of connect/disconnects for many hours. While I suspect this doesn’t really impact functionality, it does point to a problem I’d like to try and resolve.
The IoTaWatt is in the same room as the router and the IoTaWatt appears to have great/strong signal strength. I’ve attached my iotamsgs.txt file in case anyone has any ideas I could look into.
iotamsgs.txt (118.1 KB)

Also want to take a moment for a plug and to say as an aside that this is a great and amazing device. I’ve searched for a number of years for something like this and previously leaned towards TED but I’m glad I came across IoTaWatt

Heap memory has degraded below safe minimum, restarting
#2

The disconnect/connect cycles appear to be caused by channel switching. That is controlled by the router/AP. IoTaWatt cannot unilaterally change channels.

#3

Thanks @overeasy, I’ll look on the router side why it’s channel switching and update this thread.

edit(1):

It’s my router causing the disconnect/connect.
I have another router there in the same area so there might be channel conflicts. I will remove and retest.

router log (timezone is PDT / UTC-7):

Jun  3 09:47:09 acsd: acs_set_chspec: 0x1006 (6) for reason APCS_CSTIMER
Jun  3 09:47:09 acsd: eth4: selected_chspec is 1006 (6)
Jun  3 09:47:09 acsd: eth4: Adjusted channel spec: 0x1006 (6)
Jun  3 09:47:09 acsd: eth4: selected channel spec: 0x1006 (6)
Jun  3 09:47:09 acsd: eth4: txop channel select: Performing CSA on chspec 0x1006
Jun  3 09:47:13 acsd: acs_build_candidates(731): eth6: number of valid chanspec is 0
Jun  3 09:47:16 acsd: acs_set_chspec: 0xe28a (140/80) for reason APCS_CSTIMER

corresponding IoTaWatt log:

6/03/22 16:47:47z WiFi disconnected.
6/03/22 16:47:51z WiFi connected. SSID=<redacted>, IP=192.168.10.211, channel=6, RSSI -51db
#4

After turning off the second router in the same room, the connect/disconnect problems disappeared. The Message Log is clean so I’ll try hard configuring the routers to non-overlapping channels.

** Restart **

SD initialized.
6/08/22 14:59:41z Real Time Clock is running. Unix time 1654700381 
6/08/22 14:59:41z Reset Reason: Power-fail restart.
6/08/22 14:59:41z ESP8266 ID: 482274, RTC M41T81 (68)
6/08/22 14:59:41z IoTaWatt 5.0, Firmware version 02_07_05
6/08/22 14:59:41z SPIFFS mounted.
6/08/22 14:59:41z Local time zone: +0:00
6/08/22 14:59:41z device name: IotaWatt
6/08/22 14:59:44z Connecting with WiFiManager.
6/08/22 15:01:51z HTTP server started
6/08/22 15:01:51z influxDB_v2: Starting, interval:5, url:http://192.168.10.1:8086
6/08/22 15:01:51z WiFi connected. SSID=<redacted>, IP=192.168.10.233, channel=2, RSSI -39db
6/08/22 15:01:51z MDNS responder started for hostname IotaWatt
6/08/22 15:01:51z LLMNR responder started for hostname IotaWatt
6/08/22 15:01:51z timeSync: service started.
6/08/22 15:01:51z statService: started.
6/08/22 15:01:51z Updater: service started. Auto-update class is MINOR
6/08/22 15:01:52z dataLog: service started.
6/08/22 15:01:52z dataLog: Last log entry 06/08/22 14:59:35
6/08/22 15:01:53z influxDB_v2: Resume posting 06/08/22 04:30:40
6/08/22 15:01:54z Updater: Auto-update is current for class MINOR.
6/08/22 15:01:56z historyLog: service started.
6/08/22 15:01:56z historyLog: Last log entry 06/08/22 14:59:00

Thanks again, issue closed!

1 Like