[solved] Mqtt over internet? aka: "How to set up cloudMQTT bridge with Hassio mosquitto broker"

Configuration
6

So i have set up a free account on cloud MQTT,
Connected with the off-site tasmota using the username/password given by cloudMQTT
Everything works, tasmota publishes stuff on the cloudMQTT

Question1: I created an extra user on cloudmqtt and connected the tasmota under the new credentials. Although it connects id doesnt publish anything, what should i tweak?
Nevermind, had to give read and write access to the user on a topic using a the box under user management.

Question2: How do i bridge / read the published messages on the cloud server from my HA mosquito broker? I see the option to make a bridge on the cloudmqtt website but it requires an uri in the form of mqtt://user:pass@host:port. That would require me to expose my local mosuitto on the internet right? Am i not supposed to want to avoid this?

7

What about getting Node Red to Read the CloudMQTT

something like

https://support.industry.siemens.com/tf/WW/en/posts/connect-node-red-to-cloudmqtt/186131?page=0&pageSize=10

hope this Help

8

I have not worked with NodeRed at all, but i figured it out without it.
Here is how i did it, by compiling info from all around the community forums:

  • Register CloudMQTT free account.
  • Ignore the initial un/pw and create two (in my case) new users with their own passwords.
  • In the users page of cloudMQTT, scroll down after creating the users and click topic, select the user, add # (in case you want them in on everything) in the pattern box, then tick read/write access accordingly and add them twice (for muy two users).
  • Then set up the sonoff with the new user/password and ip/port settings to connect to the cloud mqtt.
  • Go check the logs on the mqtt website, to see that the user connected and open the websocket UI to see if its publishing the messages (having teleperiod 10 on the sonoff helps a lot)

Now we need to set up the Hassio mosquitto broker to connect to the cloudmqtt as a bridge:

  • Assuming you already have set up samba share, go to your hassio/share folder and create a new folder called mosquitto.
  • In there, add a new text file and save it as cloudmqtt.conf (any filename should work i think, the important part is the .conf extention)
  • In there, i pasted the following text:
connection cloudmqtt
address cloudmqttIPaddress:PORT #you get these from the details page on cloudMQTT
remote_username HA-USER
remote_password HA-PASS #whatever un/pass you set up for HA above on the cloudmqtt users 
clientid HomeAssistant
try_private false
start_type automatic
topic # in
  • Go to Hass.io addons page on your HA (this usually does not load for me for some reason, i found that selecting the address bar and forcing it by hitting enter speeds up things)
  • Open your Mosquitto Broker addon and change this part from false to true:
  "customize": {
    "active": true,
    "folder": "mosquitto"
  • No fire up your favorite mqtt client app and connect to your HA broker to subscribing to # topic.
  • You should see the messages there.
  • From there, go create your mqtt sensors in the mqtt conf files.

Hope this helps someone looking for the same thing.
It’s just a compilation of information i found on the community forums that worked for me.
Kudos to all the users of the forums who i cant cite for obvious reasons :slight_smile:

12 Likes
9

10 out 10 didn’t know you could just create a Folder and Add a .conf file to it

here a :beer:

1 Like
10

Me neither, found the info spread in the forums :slight_smile:

Cheers!

11

Thanks for the tutorial! I set it up tonight and my Own Tracks says connected but I am not seeing location info for either device_tracker entity. They both show as router only for location tracking.

On the part where it says “topic # in”… should we leave that as is or just do “topic #”?

12

Full as it is:
“topic # in”

13

@krash

Where exactly do you mean? Because I tried this and got the following error log:

starting version 3.2.2
Error: Unable to open include_dir '/share/mosquitto'.
Error found at /etc/mosquitto.conf:19.
Error: Unable to open configuration file.
14

Can you paste the settings in your mosquito addon configuration? From within hassio

15

Here it is

{
  "plain": true,
  "ssl": false,
  "anonymous": false,
  "logins": [
    {
      "username": "xxxx",
      "password": "xxxx"
    },
  ],
  "customize": {
    "active": true,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

and here is where I put the config file

image

16

Seems identical to mine.
Your error message sounds like there’s an error to the code and does not let it go further.
Wanna recheck all the code and .conf files in case you are missing some typo?

Btw in no means am i an expert, just consolidated all the info and the steps i followed hoping to help someone out :slight_smile: So any input from other friends here would be very welcome :slight_smile:

1 Like
17

Update:
I created the above example when i was in need to just receive information from clients connected to the mqttcloud.
This filter topic # in enables all published topics from every client to cross the bridge to your mqtt broker but only in that direction

Later when i connected new sonoff devices on the cloud that i needed to control i needed to let the bridge know to let some messages cross the bridge in the oposite direction broker -> bridge -> remote client

If you want all your topics to be published both to the local broker and the cloud mqtt you should change that line to topic # both meaning that it enables all messages (# wildcard) on both directions.

In my case, i didnt want all my home topics and devices to be published online. So i formated the selected topics in this way cmnd/remote_location_name/device_name/rest_of_command (where cmnd is the syntax that tasmota sonoffs use) and i wanted all the topics that contain ***/remote_location_name/*** to be published to the cloudmqtt server.

*The mqtt topics on the remote devices were changed too to reflect this syntax

So i added a new filter to the end of the file and my new mosquitto.conf file is something like this:

connection cloudmqtt
address cloudmqttIPaddress:PORT #you get these from the details page on cloudMQTT
remote_username HA-USER
remote_password HA-PASS #whatever un/pass you set up for HA above on the cloudmqtt users 
clientid HomeAssistant
try_private false
start_type automatic
topic # in
topic +/remote_location_name/# out

The + symbol is a wild card for only one part of the topic (that would be cmnd usually) and the # symbol is a wildcard for multiple topic parts so, a topic cmnd/remote_location_name/device_name/power/on would fit the profile, pass through the filter and get published to the cloudmqtt server for the remote devices to read.

More documentation about configuring your mosquitto.conf file here

Hope this helps.
k.

edit: At some point i had the need to connect more than 5 remote devices which is the maximum allowed per mqtt instance. In that case i just created a second instance and i split my devices between the two:

image
image1182×207 4.5 KB

Had to change my mosquitto.conf to connect to two bridges:

connection cloudmqtt
address cloudmqttIPaddress_1:PORT
remote_username HAUN
remote_password HAPASS
clientid HomeAssistant
try_private false
start_type automatic
topic # in 0
topic +/topic_of_instance_1/# out 0

connection cloudmqtt2
address cloudmqttIPaddress_2:PORT
remote_username HAUN
remote_password HAPASS
clientid HomeAssistant2
try_private false
start_type automatic
topic # in 0
topic +/topic_of_instance_2/# out 0

I found that i need to use different topics between the two bridges, or else it gets messy :slight_smile:

2 Likes
18

@krash i get this error on the log will you help me please ?

Connecting bridge cloudmqtt (xxx.cloudmqtt.com:xxx)
1537255477: Connection Refused: not authorised

19

If you are getting this message, double check your CloudMQTT Username and password.

20

i have checked it it matches

in my cloudmqtt bridges page i see this

image
image935×408 12.4 KB

this might be the issue ?

21

That should not be an issue as the bridge is being setup in MosQuiTTo not on CloudMQTT.

I use the free plan on CloudMQTT also.

I know this is the basics and you have likely checked, but did you check the server address and port number?
I know I messed up and put m11.cloudmqtt.com instead of my actual server the first time.
I should know better than to do it on a mobile device :slight_smile:

22

yes i have checked that if i’m not wrong i have to create a new user in my cloudmqtt and use that user name and password in hassio mqttconfig file? and i used port from cloudmqtt not ssl port or websockets port…

this is how my config file looks

connection cloudmqtt

address xxx.cloudmqtt.com:xxxxx
remote_username xxxx
remote_password xxxx
clientid rgtegerhsgtjtegggshtukk
try_private false
start_type automatic
topic # in
topic +/remote_cloudmqtt/# out

23

That looks about right. I don’t use an out on mine as I only use it for OwnTracks at the moment.
This is my conf file

connection cloudmqtt
address xxxx.cloudmqtt.com:xxxxx
remote_username xxxx
remote_password xxxxx
clientid xxxxxx
try_private false
start_type automatic
topic owntracks/# in

I setup a brand new user in Users and ACL section of CloudMQTT for the bridge.

I am stuck as to why you have auth issues now :confused:

25

this is how my cloudmqtt log looks like

2018-09-18 08:47:58: New connection from 51.xxx .190.xxx on port xxxx.
2018-09-18 08:48:29: New connection from 51.xxx .190.xxx on port xxxx.
2018-09-18 08:49:04: New connection from 51.xxx .190.xxx on port xxxx.
2018-09-18 08:49:40: New connection from 51.xxx .190.xxx on port xxxx.

i don’t know what else to try

26

Have you used a MQTT client like MQTTfx or something similar to see whether topics from CloudMQTT are hitting your Mosquitto server?

Also, if you are using HASSIO (as I am) your “Config” file in the plugin section should look similar to this:

{
  "plain": true,
  "plain_websockets": false,
  "ssl": false,
  "ssl_websockets": false,
  "anonymous": true,
  "logins": [],
  "customize": {
    "active": true,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

I use anonymous login for the local MosQuiTTo Broker, but it can be setup with local users as well.

The other config, as pasted earlier, is in the \\hassio\share\mosquitto\cloudmqtt.conf file.

I will be honest, I am running out of ideas as well. Maybe try copy and paste to copy your password set in your conf file into CloudMQTT so it is absolutely certain it is identical, other than that I am a bit lost now

1 Like