No longer receiving inputs on emonpi from OpenEVSE

I’ve been trying to solve some new problems with my OpenEVSE which had been working for several months. I’ve solved some of the problems but I haven’t been able to restore the inputs into emonpi. Chris sent me here though I’m not convinced it’s an emonpi problem, perhaps you can give me some debugging directions to solve this.

The third EmonCMS. Sounds like you can access the OpenEVSE WiFi page, which means there is no reason the WiFi module should not be able to reach EmonCMS. We would suggest a factory reset of the WiFi module and if that does not work contact openenergymonitor support, they wrote both EmonCMS and the OpenEVSE client. - Chris

The problems started about 10 days ago when I disconnected my Tesla MY from charging, the latest data in emonpi seems to be from that moment. I’ve done several poweroff cycles of the OpenEVSE, a firmware update to OpenEVSE (Build|openevse_wifi_v1|Installed|v5.1.2|), opened up the OpenEVSE box and wiggled wires (I bought it pre-assembled so I don’t know what’s what in there).

I bought the preloaded emonpi Raspberry pi last year and it seems to be working, I have other inputs including a Tailwind garage door opener that’s in the same garage as the OpenEVSE. When I go to the OpenEVSE MQTT configuration page and try to Enable MQTT it says [Not Connected], I haven’t changed any settings there: Protocol MQTT, host emonpi, port 1883, username and password haven’t changed (but I entered them again anyway).

Here is an excerpt from OpenEVSE log, I will guess mqtt_connected:0 means it’s not connected. As it says on the configuration page.

{"evse_connected":1,"amp":0,"voltage":240,"power":0,"pilot":24,"max_current":24,"temp":321,"temp_max":321,"temp1":false,"temp2":321,"temp3":false,"temp4":false,"state":2,"status":"active","flags":1280,"vehicle":1,"colour":3,"manual_override":0,"freeram":181728,"divertmode":1,"srssi":-54,"time":"2024-10-02T13:37:30Z","local_time":"2024-10-02T09:37:30-0400","offset":"-0400","uptime":673,"session_elapsed":9210,"session_energy":14802.10148,"total_energy":243.9371015,"total_day":0,"total_week":14.80210148,"total_month":14.80210148,"total_year":14.80210148,"total_switches":8,"elapsed":9210,"wattsec":5.328756533e7,"watthour":243937.1015}
{"session_elapsed":9210,"session_energy":14802.10148,"total_energy":243.9371015,"total_day":0,"total_week":14.80210148,"total_month":14.80210148,"total_year":14.80210148,"total_switches":8}
{"mqtt_connected":0,"mqtt_close_code":-1,"mqtt_close_reason":""}
{"mqtt_connected":0,"mqtt_close_code":-1,"mqtt_close_reason":""}
{"mqtt_connected":0,"mqtt_close_code":-1,"mqtt_close_reason":""}

Adding some detail of my emonpi:

Model Raspberry Pi 4 Model B Rev 1.2 - 4GB (Sony UK)
Serial num. 10000000B5164639
emonpiRelease emonSD-10Nov22

MQTT Server
Version Mosquitto 2.0.11

I heard again from Chris and solved this by using Energy Monitoring configuration instead of the MQTT, he said that’s more reliable. So this seems resolved.