search

CircuitSetup / Split-Single-Phase-Energy-Meter

Split Single-phase Energy Meter
https://www.crowdsupply.com/circuitsetup/split-single-phase-energy-meter
MIT License
261 stars 57 forks source link

Repeated MQTT reconnects due to emon server unavailable #56

Closed chaseadam closed 3 years ago

chaseadam commented 3 years ago

This is partially for tracking some debugging or porting work, but also so others can chime in with guidance and suggestions.

I am seeing many mqtt "reconnects" (here is an example of 41 connects in 1.5 hours). At no time was mainfreeram less than 200000.

Note: my emon host is offline, so the "resets" may be related to a watchdog or timeout (just over 2 minutes?)

Aug 12 11:00:43 emon/emonesp Energy monitor connected
Aug 12 11:02:56 emon/emonesp Energy monitor connected
Aug 12 11:05:09 emon/emonesp Energy monitor connected
Aug 12 11:07:22 emon/emonesp Energy monitor connected
Aug 12 11:09:35 emon/emonesp Energy monitor connected
Aug 12 11:11:48 emon/emonesp Energy monitor connected
Aug 12 11:14:01 emon/emonesp Energy monitor connected
Aug 12 11:16:14 emon/emonesp Energy monitor connected
Aug 12 11:18:27 emon/emonesp Energy monitor connected
Aug 12 11:20:40 emon/emonesp Energy monitor connected
Aug 12 11:22:53 emon/emonesp Energy monitor connected
Aug 12 11:25:06 emon/emonesp Energy monitor connected
Aug 12 11:27:19 emon/emonesp Energy monitor connected
Aug 12 11:29:32 emon/emonesp Energy monitor connected
Aug 12 11:31:45 emon/emonesp Energy monitor connected
Aug 12 11:33:58 emon/emonesp Energy monitor connected
Aug 12 11:36:11 emon/emonesp Energy monitor connected
Aug 12 11:38:24 emon/emonesp Energy monitor connected
Aug 12 11:40:37 emon/emonesp Energy monitor connected
Aug 12 11:42:50 emon/emonesp Energy monitor connected
Aug 12 11:45:03 emon/emonesp Energy monitor connected
Aug 12 11:47:16 emon/emonesp Energy monitor connected
Aug 12 11:49:29 emon/emonesp Energy monitor connected
Aug 12 11:51:42 emon/emonesp Energy monitor connected
Aug 12 11:53:55 emon/emonesp Energy monitor connected
Aug 12 11:56:08 emon/emonesp Energy monitor connected
Aug 12 11:58:21 emon/emonesp Energy monitor connected
Aug 12 12:00:34 emon/emonesp Energy monitor connected
Aug 12 12:02:47 emon/emonesp Energy monitor connected
Aug 12 12:05:00 emon/emonesp Energy monitor connected
Aug 12 12:07:13 emon/emonesp Energy monitor connected
Aug 12 12:09:26 emon/emonesp Energy monitor connected
Aug 12 12:11:39 emon/emonesp Energy monitor connected
Aug 12 12:13:52 emon/emonesp Energy monitor connected
Aug 12 12:16:04 emon/emonesp Energy monitor connected
Aug 12 12:18:17 emon/emonesp Energy monitor connected
Aug 12 12:20:31 emon/emonesp Energy monitor connected
Aug 12 12:22:44 emon/emonesp Energy monitor connected
Aug 12 12:24:56 emon/emonesp Energy monitor connected
Aug 12 12:27:10 emon/emonesp Energy monitor connected
Aug 12 12:29:22 emon/emonesp Energy monitor connected

Config for the EmonESP is:

{"espflash":"4194304","version":"2.6","ssid":"Chasen","pass":"_DUMMY_PASSWORD","emoncms_server":"emon.827.chasen.name","emoncms_path":"","emoncms_node":"cs1","emoncms_apikey":"_DUMMY_PASSWORD","emoncms_fingerprint":"","mqtt_server":"mqtt.827.chasen.name","mqtt_topic":"emon/emonesp","mqtt_feed_prefix":"main","mqtt_user":"","mqtt_pass":"","www_username":"achasen","www_password":"_DUMMY_PASSWORD","voltage_cal":"37106","ct1_cal":"44000","ct2_cal":"44000","freq_cal":"4231","gain_cal":"0"}

mosquitto MQTT logs:

1628940651: New connection from 10.0.2.100:43548 on port 1883.
1628940651: Client esp32-98cac9d108f0 already connected, closing old connection.
1628940651: New client connected from 10.0.2.100:43548 as esp32-98cac9d108f0 (p2, c1, k60).
1628940784: New connection from 10.0.2.100:43550 on port 1883.
1628940784: Client esp32-98cac9d108f0 already connected, closing old connection.
1628940784: New client connected from 10.0.2.100:43550 as esp32-98cac9d108f0 (p2, c1, k60).
1628940917: New connection from 10.0.2.100:43552 on port 1883.
1628940917: Client esp32-98cac9d108f0 already connected, closing old connection.
1628940917: New client connected from 10.0.2.100:43552 as esp32-98cac9d108f0 (p2, c1, k60).
1628941050: New connection from 10.0.2.100:43554 on port 1883.
1628941050: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941050: New client connected from 10.0.2.100:43554 as esp32-98cac9d108f0 (p2, c1, k60).
1628941183: New connection from 10.0.2.100:43556 on port 1883.
1628941183: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941183: New client connected from 10.0.2.100:43556 as esp32-98cac9d108f0 (p2, c1, k60).
1628941316: New connection from 10.0.2.100:43558 on port 1883.
1628941316: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941316: New client connected from 10.0.2.100:43558 as esp32-98cac9d108f0 (p2, c1, k60).
1628941449: New connection from 10.0.2.100:43560 on port 1883.
1628941449: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941449: New client connected from 10.0.2.100:43560 as esp32-98cac9d108f0 (p2, c1, k60).
1628941582: New connection from 10.0.2.100:43562 on port 1883.
1628941582: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941582: New client connected from 10.0.2.100:43562 as esp32-98cac9d108f0 (p2, c1, k60).
1628941715: New connection from 10.0.2.100:43564 on port 1883.
1628941715: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941715: New client connected from 10.0.2.100:43564 as esp32-98cac9d108f0 (p2, c1, k60).
1628941848: New connection from 10.0.2.100:43566 on port 1883.
1628941848: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941848: New client connected from 10.0.2.100:43566 as esp32-98cac9d108f0 (p2, c1, k60).
1628941981: New connection from 10.0.2.100:43568 on port 1883.
1628941981: Client esp32-98cac9d108f0 already connected, closing old connection.
1628941981: New client connected from 10.0.2.100:43568 as esp32-98cac9d108f0 (p2, c1, k60).
1628942114: New connection from 10.0.2.100:43570 on port 1883.
1628942114: Client esp32-98cac9d108f0 already connected, closing old connection.
1628942114: New client connected from 10.0.2.100:43570 as esp32-98cac9d108f0 (p2, c1, k60).
1628942247: New connection from 10.0.2.100:43572 on port 1883.
1628942247: Client esp32-98cac9d108f0 already connected, closing old connection.
1628942247: New client connected from 10.0.2.100:43572 as esp32-98cac9d108f0 (p2, c1, k60).
1628942380: New connection from 10.0.2.100:43576 on port 1883.
1628942380: Client esp32-98cac9d108f0 already connected, closing old connection.
1628942380: New client connected from 10.0.2.100:43576 as esp32-98cac9d108f0 (p2, c1, k60).
1628942513: New connection from 10.0.2.100:43578 on port 1883.
1628942513: Client esp32-98cac9d108f0 already connected, closing old connection.
1628942513: New client connected from 10.0.2.100:43578 as esp32-98cac9d108f0 (p2, c1, k60).
1628942646: New connection from 10.0.2.100:43580 on port 1883.
1628942646: Client esp32-98cac9d108f0 already connected, closing old connection.
1628942646: New client connected from 10.0.2.100:43580 as esp32-98cac9d108f0 (p2, c1, k60).
1628942779: New connection from 10.0.2.100:43582 on port 1883.
1628942779: Client esp32-98cac9d108f0 already connected, closing old connection.
1628942779: New client connected from 10.0.2.100:43582 as esp32-98cac9d108f0 (p2, c1, k60).
chaseadam commented 3 years ago

The reconnects stopped for the past 24 hours since the emon server became available again. Possibly a connection timeout or failure to the emon server was triggering a full reset?

Marking closed!