I’m trying to capture some temp/humidity data through a Helium end device talking to the Mosquitto mqtt add-on. I can figure out the correct “Endpoint” syntax to connect the Helium server to the Mosquitto add-on (see example below). I can see the data getting to the Helium server and it’s ok. The example they give below doesn’t help. Any ideas?
I think this tutorial should be able to point you in the right direction. It’s using the MQTT integration on the helium console. I’d give you a more definitive answer but I haven’t actually used this tutorial yet, I’m still waiting on my T-BEAM to arrive. Good Luck
Thanks for this. I’ll look it over.
I took the time to go through this tutorial with no luck. I’m still interested in have the helium console talk to HA. If you have any success let me know.
I also worked on it over the weekend and figured it out. Because I had an extra RPi 3b, I decided to build an external Mosquitto broker. Then I bridged it to the internal broker (mosquito add-on) in HA. Once I got the external and internal MQTT brokers talking, I pointed Helium to my external broker and added a mosquitto.config file to the internal HA broker pointing to the external broker as follows:
# External MQTT Broker - create and change HA mosquitto.cong file:
connection external-bridge
address <external_ip_address_broker>
topic # in
remote_username <username> (optional)
remote_password <password> (optional)
This link helped: https://selfhostedhome.com/using-two-mqtt-brokers-with-mqtt-broker-bridging/. They used a VM version of MQTT broker which I’m sure will also work.
It’s easiest to get the two brokers taking with MQTT Explorer, then use Node-Red to see what is coming from your HA broker.
Just created two flows to watch both external and internal (HA) brokers:
I’ll be writing the whole process up when I have time, so check back with me in a couple of weeks if you’re still having trouble.
1 Like
That’s great I’m glad you got it working. Seems like a weird work around though, there must be some limitation to the version of MQTT that we install through supervisor? Regardless, I do have an extra RPi laying around so I guess I’ll give it a shot once you complete your write up. Thank you
I eventually got the tutorial working that I mentioned above without have to use an external Mosquitto broker. I only mention it in case someone comes across this forum post. The supervisor’s install of Mosquitto, NodeRed and Grafana work just fine.
Great! How did you address the Home assistant MQTT Broker? I tried mqtt://username:password@HA IP address:1883 but didn’t work with any nodes outside of my network. I do use DuckDNS, Let’s Encrypt, and NGINX for HA. Maybe that’s what’s hanging me up.
First I had to ensure the helium would have it’s own username and password to login from.
In the Supervisor/Misquitto Broker/Configuration edit the yaml and add a user.
- username: heliumuser
password: heliumpassword
Then I ensured that I opened port 1883 on my router and directed it to my HA local IP address.
One really easy way to check it was working was with MQTT Explorer. http://mqtt-explorer.com
Once I could login via MQTT Explorer I knew it was accessible from the internet and my username and password were working. The explorer also let me instantly see the results of what helium was pushing to HA.
Lastly, in the helium console MQTT integration I edited my endpoint to
mqtt://username:password@internet IP Address:1883
topics remained default
and I had to customize the template body, in my case, for the T-Beam to push the lat/log ect
1 Like
Thanks! I’m still waiting for my first Bobcat Miner. Just playing around with nodes now. Located in Vancouver, WA
I saw where you posted the following on Discord:
“I know my HomeAssistant Broker is remotely accessible but the helium console has never attempted to connect to it. A part of me feels like i’m using the wrong JSON. (This is becoming an email) In trying to troubleshoot the console it says 1 warning above my MQTT integration - The Integration is unsuccessful. Check the Integration for details. – no matter where i look i can’t find the “details” of what the error is.”
I’m getting that same error on my MQTT integration on Helium Console. I can connect to the broker using MQTT Explorer, and I’m sure I have the endpoint correct. Did you resolve this issue by changing your JSON Template? or what did you do to get a successful integration?
TIA
I believe this was resolved when I provided the helium console it’s own login to my MQTT broker