You are correct. It was a faulty rx-tx wire to the esp. And I did update to the latest esp-wifi firmware
So the good news is RAPI commands are working through the webapp. Able to disable , enable and set current.
Unfortunately, even though MQTT says connected and on the base “openevse” the intial connected, disconnected msg are showing up on my mobile mqtt client. The actual RAPI commands are not working over mqtt
These are my client publication and subscription
In an unreleated suggestion, it would be grest if the webserver can be hosted in the cloud so it can be accessed from anywhere outside the home network without messing around with router ip exposing or rever tunneling. Apologies if this is already possible.
And looking at the schematic, is the Atmega328 needed with the esp there? I realize openevse was build before without wifi and the wifi was added after. But if it was built again an esp alone is enough I would think.
Page 4 prerequisites says “MQTT Broker on the network”
. My broker is hivemq not local.
“If the power is removed from the OpenEVSE I would expect it to disconnect from MQTT since the WiFi module in the OpenEVSE would not have any power and therefore not able to maintain the WiFi & MQTT connection. Is this what you mean?”
Blizzard the only mqtt msg are connect and disconected …