Publishing an input with MQTT from an EmonPi

bdhughes · 2021-02-21T16:33:22.504Z

I’m trying to publish an input to mqtt. The input is called Grid and shows up in my emonpi after the usual power1, power2 etc.

Screenshot 2021-02-21 at 16.23.561429×960 77.4 KB

I’ve set up an input process to publish it to MQTT. It’s not appearing at all.

Screenshot 2021-02-21 at 16.25.091346×455 40.6 KB

I’ve used MQTTLens to see if it’s there and it isn’t. Is there something I’ve missed?

Thanks
Brian

borpin · 2021-02-21T16:43:34.054Z

MQTT has a publish and subscribe mechanism.

Publish is one device sending data to the MQTT Broker
Sebscribe is one device asking the MQTT Broker for data.

Emoncms looks for any topic with the base topic emon/ and then pulls that data in as an Input.

If you want to publish data from Emoncms for other devices to use, you need to use a different base topic name else it will appear as an INput

bdhughes:

I’ve used MQTTLens to see if it’s there and it isn’t.

How is Grid created in the first place. I think you have created a loop and it keeps appearing as the retain flag is set.

bdhughes · 2021-02-21T17:28:24.267Z

Hi Brian O.

I’m not familiar with MQTT but my emonEVSE requires it. I used to have it all working but I needed to rebuild this emonPi.

Grid comes from a calculated field that I send to the emoncms on that emonPi using Python

data1 = 'http://192.168.86.88/emoncms/input/post.json?node=emonpi&json={'
data2 = 'Grid:{}'.format(grid)
data3 = '}&apikey=xxxxxxxxxxxxxxxxxxxxx'
data = data1 + data2 + data3
r = requests.get(data)

I need to make it available to the emonEVSE via MQTT. As I understand it the emonPi needs to publish the value and emonEVSE needs to subscribe to it.

I’ve tried changing the base to emonBH like this:

Screenshot 2021-02-21 at 17.16.491322×407 38.9 KB

but that doesn’t seem to work either.

So this is my emonEVSE side which (apart from me changing emon to emonBH for this test) hasn’t changed.

Screenshot 2021-02-21 at 17.20.00443×691 31.2 KB

MQTT Lens shows nothing for emonBH.

Have I misunderstood and changed the wrong thing?

Thanks
Brian H.

JJC · 2021-02-21T17:54:17.876Z

Brian,

this is how I do it, hope it helps

mod

feed1770×468 89.2 KB

John

bdhughes · 2021-02-21T19:39:03.186Z

Hi John

Yes, That’s pretty much how I had mine set up originally. I’ve tried changing the name of the MQTT feed to solarpower, just like yours in case there was some confusion with me having an input also called Grid but it’s still not working.

I’m flumoxed. My setup looks like yours and how it used to work in my old setup which would have been several years old.

I downloaded the prebuilt-card version a couple of days ago. I’m wondering if there are any problems with MQTT with it or is there some setting I should change?

Anyway, thanks for posting what your setup is.

Brian

borpin · 2021-02-21T21:13:38.338Z

JJC:

this is how I do it,

You must see solarpower as an Input as well then.

Anything on the broker under the base topic of emon/ will be processed as an input.

bdhughes:

Yes, That’s pretty much how I had mine set up originally.

Not really, as you are posting

from Python → Emoncms → MQTT → Emoncms

Because you published to the same name, that published data is then read back in as an Input and published back out - you have a loop.

bdhughes:

I’ve tried changing the base to emonBH like this:

but that doesn’t seem to work either.

What bit of that doesn’t work? Do you see it (a value published to the topic emonBHemonpi/grid) in your MQTT Lens?

Oh I see - remove the leading /

bdhughes · 2021-02-21T23:06:41.762Z

Hi Brian

D’oh! That was it. As soon as I removed that leading / it worked. And yes, Brian, you’re right I have Grid with the post to MQTT and now I see solarpower as an input as well. So it wasn’t a good idea to have the Input called Grid and to publish it to Grid.

Thanks to you and John.
Brian

Robert.Wall · 2021-06-14T14:05:27.353Z

A post was merged into an existing topic: Create topic mqtt json in emoncms