Some routers can be a bit unreliable with host names, it may be on http://openevse without the .local. If that does not work, try scanning your home network with an app called ‘fing’ to see if it can find it on your network.
@TrystanLea thanks for suggesting ‘Fing’. Great little app. I was able to find the charger ip and connect to it.
@glyn.hudson I was able to connect to the mqtt. Whenever the charger power on or off my mqtt client msg shows “connect” and “disconnected”
However when i send a RAPI command over mqtt such as reset, changed lcd color,
or set chargre rate, I do not see the charger performing those commands. I do see the command show up in my openevse/rapi/in suscription though.
I am getting a mqtt msg saying connected when the charger boots up & connects to wifi. When I unplug the power to the charger I get “disconnected” on my mqtt client. I assume this is coming from the websever or emoncms and not the actual device?
Here is the messages my mqtt client get from the suscription
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?
the OpenEVSE is obviously successfully connected to your network since it has Internet access. It looks to me like the Wifi module is not able to communicate with the OpenEVSE EV controller. This would explain why the values in Emoncms are zero and RAPI commands are not working. I would recommend checking the serial connection between the OpenEVSE WiFi module and the controller, see Services - EmonCMS - OpenEVSE
When the WiFi module is correctly connected you should see “OpenEVSE Wifi” and IP address displayed on the LCD at startup.
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
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 …
The ATmega328 is required to handle the communication with the EV, this is safety critical and required analogue inputs from CT sensors. Isolating the safety critical EV communication from the WiFi gateway is a design decision.
Thanks, that looks correct. Do you see “MQTT Connected: Yes” on the Services page?
Does MQTT dashboard not require a username / password?
What is the reason for using MQTT dashboard? I would recommend using local MQTT broker if possible since it’s not very secure to us an unencrypted cloud server. Do you have an emonPi? If so it has an integrated MQTT server. If not a MQTT server could be setup on a RasPi.
What is your goal with this setup? Do you want to get the data into Emoncms or do you have other uses for MQTT data?