2 OpenEVSEs MQTT

Ryan_S · 2019-11-15T22:47:18.022Z

So I have 2 OpenEVSE chargers and I would like to integrate them both over MQTT to the EmonCMS. I can get 1 to connect and show data, but when I bring the other one in it shows connected, but no data shows and I see no change on the inputs of EmonCMS

glyn.hudson · 2019-11-16T01:35:53.165Z

You should set the base topic to be different on the 2nd unit e.g emon/openevse2

15874×1390 63.6 KB

Ryan_S · 2019-11-16T02:29:20.339Z

I’m done that, but it never seems to show up. Wonder if I’m not waiting long enough.

borpin · 2019-11-16T12:15:01.476Z

glyn.hudson:

You should set the base topic to be different on the 2nd unit e.g emon/openevse2

@glyn.hudson, is the MQTT Client ID hardcoded? If so the MQTT broker will complain 2 devices using same ID.

Ryan_S · 2019-11-16T12:17:40.619Z

borpin:

@glyn.hudson, is the MQTT Client ID hardcoded? If so the MQTT broker will complain 2 devices using same ID.

That is something I’m wondering myself.

borpin · 2019-11-16T12:21:54.843Z

If you check the MQTT log, you will see errors (if there is an issue).

cat  /var/log/mosquitto/mosquitto.log

borpin · 2019-11-16T12:23:55.755Z

Ryan_S:

That is something I’m wondering myself.

Does the first one you start always work?

Ryan_S · 2019-11-16T12:28:29.735Z

borpin:

Does the first one you start always work?

It appeared to, yet when I brought in the 2nd OpenEVSE it never seemed to appear. Will take a look at that log.

borpin · 2019-11-16T12:29:46.041Z

Ryan_S:

It appeared to, yet when I brought in the 2nd OpenEVSE it never seemed to appear.

So If you start the first it works fine. If you stop the first and just start the second, what is happening? Do you ever see the second set of data?

Ryan_S · 2019-11-16T12:38:28.377Z

Here’s what I see with OpenEVSE2 only submitting over MQTT.

image1090×435 22.2 KB

When I bring in OpenEVSE1 over MQTT this is what it shows on the inputs.

image1088×483 22.1 KB

There is a new input of 0, but nothing else. I’m guessing they are conflicting and this is MQTTs way of handling that.

Ryan_S · 2019-11-16T12:40:39.868Z

borpin:

So If you start the first it works fine. If you stop the first and just start the second, what is happening? Do you ever see the second set of data?

Just a bit more data. Here is what it shows if I stop OpenEVSE2 MQTT and leave OpenEVSE1 MQTT running. It looks like it just adds OpenEVSE1’s inputs now and accepted them.

image1084×514 25 KB

borpin · 2019-11-16T15:18:59.556Z

Ryan_S:

Just a bit more data. Here is what it shows if I stop OpenEVSE2 MQTT and leave OpenEVSE1 MQTT running.

Ok, so the base topic for that is openevse

What if you stop that one and start the second one?

You should get a second set of inputs under openevse2

If you don’t, try using the IP address of the EmonPi as the host (generally more reliable anyway) in the settings of the openevse.

Ryan_S · 2019-11-16T21:15:42.492Z

borpin:

Ok, so the base topic for that is openevse

What if you stop that one and start the second one?

You should get a second set of inputs under openevse2

If you don’t, try using the IP address of the EmonPi as the host (generally more reliable anyway) in the settings of the openevse.

You know what. I see what the problem is. I already had an openevse2 in there for the main connection for my feeds. It was being masked under that when I put that for the base-topic. Changed it to openevse22 and sure enough there it is.

glyn.hudson · 2019-11-17T13:56:46.813Z

borpin:

@glyn.hudson, is the MQTT Client ID hardcoded? If so the MQTT broker will complain 2 devices using same ID.

Yes, it is fixed on the V2.x ESP8266 version, the new ESP32 V3.x version uses the ESP chip ID. This version is still in beta: GitHub - OpenEVSE/openevse_esp32_firmware: OpenEVSE V4 WiFi gateway using ESP32

I think my experience even through mosquitto complains in the log it doesn’t functionally make any differance if the same ID is used as long as the topics in use are different. I will need to test this again to be sure.

@Ryan_S could you post a screenshot showing your MQTT config settings on both OpenEVSE’s?

Ryan_S · 2019-11-17T13:59:46.556Z

glyn.hudson:

@Ryan_S could you post a screenshot showing your MQTT config settings on both OpenEVSE’s?

Certainly.

Here is OpenEVSE1

image446×664 26.5 KB

And here is OpenEVSE2

image432×664 26.3 KB

At this point I don’t see an advantage to the MQTT for myself as the charge shaping is based on UK data and not my local data, but I do want it connected as I am looking at putting solar on my roof after a roof replacement next year.

glyn.hudson · 2019-11-17T14:02:14.777Z

That looks correct. However, I see the data is showing up on your Emoncms Inputs page with node name “openevse” rather than “openevse3” open “openevse4” a I would expect.

Do you know where “openevse” could be coming from? Do you have a third openevse somwhere?!

borpin · 2019-11-17T16:58:52.411Z

glyn.hudson:

I think my experience even through mosquitto complains in the log it doesn’t functionally make any differance if the same ID is used as long as the topics in use are different.

My experience is the opposite. I had 2 instances of emoncms talking to the same Broker (when the client_ID was hardcoded) and it complained vociferously!

Easy enough to check in the mosquitto logs IIRC.

Ryan_S · 2019-11-17T18:50:52.915Z

glyn.hudson:

That looks correct. However, I see the data is showing up on your Emoncms Inputs page with node name “openevse” rather than “openevse3” open “openevse4” a I would expect.

Do you know where “openevse” could be coming from? Do you have a third openevse somwhere?!

That was when I was originally using emon/openevse not realizing that leaving both the same would result in them overlapping. I have since changed them to what you see above and deleted the openevse input as it is not longer needed.