Can't Connect to IoTaWatt in AP mode

Hardware IoTaWatt
1

I have been using my IoTaWatt at home and been work OK. Decided to install at mother-in-laws for a few weeks to help her work out why her bill is so high.

Connected everything up and turned on. Saw AP screen to enter new WiFi details but I think I entered wrong password. Tried to get back in for another attempt but I can no longer access the IoTWatt AP page.

When I search for the WiFi network SSID (iotawatt + num) it does not come up on my iphone, or PC or android phone.

Any ideas ? I have power cycled a few times but problem still there.

The status light shows dull green then green then green (longer delay) then red. The docs seem to say this means it can’t connect to wifi so I should be able to connect via the AP mode.

2

I think I have resolved this now.

After removing the SD card and putting back and powering up again I finally got connected to wifi. Looks like I could not connect to the AP because it was actually connected to home wifi.

However some strange things happening with user interface so I deleted everything on SD and installed new files from GIT.

Now I think everything is working fine.

Would be good to have option to delete all old/unwanted wifi ssid and start again.

3

Iotawatt.local/command?disconnect=yes

Tools menu in next release will have a button for this. I can’t see how any of the SDcard activity should have been a factor in your experience, but not a problem either.

4

Everything has been logging well for a few days but had a power outage today and logging to Emoncms has stopped.

I have done a reset with web interface to Iotawatt, power cycled a few times but still can’t get logging to Emoncms.

The status on the Iotawatt seems to show all working OK and graphing shows data being logged locally.

Only odd thing I can see is the time is one hour wrong, probably because of DST but not sure if this adjusted correctly when everything was working. I have attached the log below, looks OK to me.

Any ideas ???

** Restart **

No clock yet: SD initialized.
1/9/18 08:32:32 Real Time Clock is running. Unix time: 1515486752
1/9/18 08:32:32 Version: 02_02_27
1/9/18 08:32:32 Reset reason: Software/System restart
1/9/18 08:32:32 Trace: 86,88,93,94,95,99,12,13,14,15,30,34,31,35,36,38,148,149,140,142,143,144,145,148,149,146,147,39,16,17,102,103
1/9/18 08:32:32 ESP8266 ChipID:2991982
1/9/18 08:32:32 device name: IotaWatt, version: 3
1/9/18 08:32:32 Local time zone: 0
1/9/18 08:32:35 Connecting with WiFiManager.
1/9/18 08:32:42 MDNS responder started
1/9/18 08:32:42 You can now connect to http://IotaWatt.local
1/9/18 08:32:42 HTTP server started
1/9/18 08:32:42 dataLog: service started.
1/9/18 08:32:42 dataLog: Last log entry:1515486750
1/9/18 08:32:43 statService: started.
1/9/18 08:32:43 timeSync: service started.
1/9/18 08:32:43 WiFi connected. SSID: Telstra4E94, IP: 192.168.0.16
1/9/18 08:32:43 historyLog: service started.
1/9/18 08:32:43 historyLog: Last log entry:1515486720
1/9/18 08:32:47 EmonService: started.url: emoncms.org:80, node: IotaWatt, post interval: 10, encrypted POST
1/9/18 08:32:47 EmonService: Start posting at 1515434630

5

Hi Paul.

Starting with the time being off, your IoTaWatt is configured to UTC (GMT). There is no local time offset. You would need to set that in the Setup/Device section.

The log you posted shows that the EmonCMS posting is about 15 hours behind, but as you say, logging locally OK.

Can you try removing the userid field in your server settings to change to unencrypted posting? If that resolves the backlog, change back and see if it stops again.

If that doesn’t resolve the problem, please post the log back to the power fail that you mention.

Update: There appear to be some ongoing problems with Emoncms that may be causing this. The symptoms appear to be consistent with what you are reporting… Emoncms accepts the data but then doesn’t post it. That would explain the lack of communications errors in your log, and why your IoTaWatt is serving you locally while unable to post remotely. Hopefully, the data is in a backlog queue and will be posted when the problem is resolved, but maybe not. To be on the safe side, I’d recommend stopping your Emoncms server (server=NONE) and restarting when the problem has been resolved. You can follow that issue in this post: 5 hours of no updating of Feeds

6

Thanks for the update, I can stop wondering what I am doing wrong.

My update is that data started to load to emoncms from the local iotawatt data but stopped again about 4 hours ago. I just checked the log when I woke up and there are extra entries as shown below that probably relate to this problem.

I plan to setup my own emoncms server but thought it easier to start with the web version.

** Restart **

No clock yet: SD initialized.
1/9/18 08:32:32 Real Time Clock is running. Unix time: 1515486752
1/9/18 08:32:32 Version: 02_02_27
1/9/18 08:32:32 Reset reason: Software/System restart
1/9/18 08:32:32 Trace: 86,88,93,94,95,99,12,13,14,15,30,34,31,35,36,38,148,149,140,142,143,144,145,148,149,146,147,39,16,17,102,103
1/9/18 08:32:32 ESP8266 ChipID:2991982
1/9/18 08:32:32 device name: IotaWatt, version: 3
1/9/18 08:32:32 Local time zone: 0
1/9/18 08:32:35 Connecting with WiFiManager.
1/9/18 08:32:42 MDNS responder started
1/9/18 08:32:42 You can now connect to http://IotaWatt.local
1/9/18 08:32:42 HTTP server started
1/9/18 08:32:42 dataLog: service started.
1/9/18 08:32:42 dataLog: Last log entry:1515486750
1/9/18 08:32:43 statService: started.
1/9/18 08:32:43 timeSync: service started.
1/9/18 08:32:43 WiFi connected. SSID: Telstra4E94, IP: 192.168.0.16
1/9/18 08:32:43 historyLog: service started.
1/9/18 08:32:43 historyLog: Last log entry:1515486720
1/9/18 08:32:47 EmonService: started.url: emoncms.org:80, node: IotaWatt, post interval: 10, encrypted POST
1/9/18 08:32:47 EmonService: Start posting at 1515434630
1/9/18 08:45:16 EmonService: POST failed. HTTP code:read Timeout
1/9/18 08:46:16 EmonService: Resending EmonCMS data:2
1/9/18 08:46:16 EmonService: Retry successful.
1/9/18 09:30:28 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:31:28 EmonService: Resending EmonCMS data:2
1/9/18 09:31:29 EmonService: Retry successful.
1/9/18 09:31:44 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:32:44 EmonService: Resending EmonCMS data:2
1/9/18 09:32:44 EmonService: Retry successful.
1/9/18 09:40:58 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:41:58 EmonService: Resending EmonCMS data:2
1/9/18 09:41:59 EmonService: Retry successful.
1/9/18 09:42:18 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:43:18 EmonService: Resending EmonCMS data:2
1/9/18 09:43:19 EmonService: Retry successful.
1/9/18 09:46:08 time=1515491160&data=[[0,“IotaWatt”,239.7,37.9,0,324.4,286.2
1/9/18 09:46:08 EmonService: Invalid response: Can’t connect to database, please verify credentials/configu
1/9/18 09:46:08 EmonService: Expectd response: XGVrGu4RvV6Fw0vmv16mCt38Z_9QX5pACRB5ttGA-QU=
1/9/18 09:47:08 EmonService: Resending EmonCMS data:2
1/9/18 09:47:09 EmonService: Retry successful.
1/9/18 09:49:19 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:50:19 EmonService: Resending EmonCMS data:2
1/9/18 09:50:20 EmonService: Retry successful.
1/9/18 09:51:28 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:52:28 EmonService: Resending EmonCMS data:2
1/9/18 09:52:30 EmonService: Retry successful.
1/9/18 09:53:08 EmonService: POST failed. HTTP code:read Timeout
1/9/18 09:54:08 EmonService: Resending EmonCMS data:2
1/9/18 09:56:10 EmonService: Resending EmonCMS data:3
1/9/18 09:56:12 EmonService: Retry successful.
1/9/18 10:16:36 time=1515492990&data=[[0,“IotaWatt”,241.6,111.9,2156.6,152.5
1/9/18 10:16:36 EmonService: Invalid response: Can’t connect to database, please verify credentials/configu
1/9/18 10:16:36 EmonService: Expectd response: j2rgN_vqReQO57iqKKeIU3dghk1_E4o9GCpx8sXgdAk=
1/9/18 10:17:36 EmonService: Resending EmonCMS data:2
1/9/18 10:17:37 EmonService: Retry successful.
1/9/18 12:19:06 EmonService: POST failed. HTTP code:read Timeout
1/9/18 12:20:06 EmonService: Resending EmonCMS data:2
1/9/18 12:20:07 EmonService: Retry successful.
1/9/18 14:21:25 time=1515507680&data=[[0,“IotaWatt”,243.5,0,0,144.4,36.4,0,3
1/9/18 14:21:25 EmonService: Invalid response: Can’t connect to database, please verify credentials/configu
1/9/18 14:21:25 EmonService: Expectd response: gbt2-70VXlmWR7XqCoHhQ8sKKO6Xo65-15FA12qXmAw=
1/9/18 14:22:25 EmonService: Resending EmonCMS data:2
1/9/18 14:22:25 EmonService: Retry successful.
1/9/18 14:51:47 EmonService: POST failed. HTTP code:read Timeout
1/9/18 14:52:47 EmonService: Resending EmonCMS data:2
1/9/18 14:52:47 EmonService: Retry successful.
1/9/18 20:51:20 EmonService: started.url: emoncms.org:80, node: IotaWatt, post interval: 10, unsecure GET
1/9/18 20:51:20 EmonService: Start posting at 1515531070