Mosquito MQTT update v3 broke my hassio

Installation Home Assistant OS
48

Thanks for the tip.
Unfortunately doesn’t work for me.
I’ve changed mqtt config to:

{
  "logins": [
    {
      "username": "DVES_USER",
      "password": "DVES_PASS"
    }
  ],
  "anonymous": false,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

These creds are default Sonoff Tasmota creds. I dont care about sequrity since it is local network.
I also changed main config to

mqtt:
  broker: 192.168.1.116

and configured integration.

The addon log is:

1541430941: Opening ipv4 listen socket on port 1883.
1541430941: Opening ipv6 listen socket on port 1883.
1541430941: Opening websockets listen socket on port 1884.
1541430941: Opening ipv4 listen socket on port 8883.
1541430941: Opening ipv6 listen socket on port 8883.
1541430941: Opening websockets listen socket on port 8884.
1541430941: Warning: Mosquitto should not be run as root/administrator.
1541430944: New connection from 192.168.1.104 on port 1883.
[INFO] found DVES_USER on local database
1541430945: New client connected from 192.168.1.104 as DVES_0F6870 (c1, k15, u'DVES_USER').
1541430945: New connection from 192.168.1.124 on port 1883.
1541430945: New connection from 192.168.1.122 on port 1883.
[INFO] found DVES_USER on local database
1541430946: New client connected from 192.168.1.124 as DVES_029D3D (c1, k15, u'DVES_USER').
[INFO] found DVES_USER on local database
1541430948: New client connected from 192.168.1.122 as DVES_0E3B9B (c1, k15, u'DVES_USER').
1541430948: New connection from 192.168.1.119 on port 1883.
1541430948: New connection from 192.168.1.115 on port 1883.
1541430948: New connection from 192.168.1.121 on port 1883.
[INFO] found DVES_USER on local database
1541430951: New client connected from 192.168.1.119 as DVES_B2E718 (c1, k15, u'DVES_USER').
[INFO] found DVES_USER on local database
1541430953: New client connected from 192.168.1.115 as DVES_AC8937 (c1, k15, u'DVES_USER').
[INFO] found DVES_USER on local database
1541430955: New client connected from 192.168.1.121 as DVES_9126AB (c1, k15, u'DVES_USER').

It looks like some devices are connected successfully. But none of them alive:

830×759 30 KB

49

Stupid question but @deviant have you restarted?

50

Try changing anonymous: to true. My understanding is that by having anonymous true and a login set, it will allow anonymous clients in a read only mode. (the client can send stuff but can’t read other stuff)

1 Like
51

Well, I’m glad I’m not the only one who has been spending a couple of hours today to find this problem.
I have recreated the issue a couple of times (reflash, install, install Samba, copy back backup, restore backup, etc) before I found the problem being the MQTT update. After each iteration I lose all connectivity except ping (so no Samba, no SSH)
What is the recommended way to test here? Every time I break my HA-instance now I have to redo the whole procedure again, not a very nice way to quickly test some options…

1 Like
52

yes. today i beat my own record. restarted 1000 times :slight_smile:

3 Likes
53

no luck with anonymous mode. i see that my mqtt devices connected to the broker, but there is no healthy items in the UI.

16:34:17 MQT: Attempting connection...
16:34:19 MQT: Connected
16:34:19 MQT: tele/siren/LWT = Online (retained)
16:34:19 MQT: cmnd/siren/POWER =
54

There is an update for Supervisor to fix the mqtt reboot problem. Version 139.

If you can’t get to the UI, delete discovery.json (/mnt/data/supervisor in hassos) and restart.

55

How can I do that? My SSH_connection is also refused. Removing the SD-card and mounting it somehow in my Mac?

56

ok. something new

980×571 27.1 KB

i even haven’t changed anything in the config. are there another breaking changes beside credentials system?

1 Like
57

I don’t think I can help except to (maybe) reassure you that I also had that at some point so it is probably not anything ‘extra’!

I think I got it when I had removed my whole mqtt: section form configuration.yaml - something to do with using Integrations. Don’t ask! :wink:

58

I did not understand if this is a way to make money or a security update. anyway they made me lose an afternoon and at the end I solved, at least for the moment.
I installed mosquitto on nas sinology and now everything works regularly.
Thank you so much for making me lose an afternoon:rage::rage::rage::face_with_symbols_over_mouth::face_with_symbols_over_mouth::face_with_symbols_over_mouth::face_with_symbols_over_mouth::face_with_symbols_over_mouth::face_with_symbols_over_mouth::rage::rage::rage::angry::angry::angry::angry:

1 Like
59

Finally i found the reason of all my fails:

DISABLED discovery: feature in the config!!!

So mqtt would NOT work if you removed/commented discovery

And i don’t even have mqtt: in the config. It works out of the box. But i had to add user/password to the addon configuration

60

I’m having issues, but I am a bit confused as to where I am going now with the numerous posts on here

I’ve got the DVES_USER issue

1 Like
61

Try these steps:
Addon config:

{
  "logins": [
    {
      "username": "DVES_USER",
      "password": "DVES_PASS"
    }
  ],
  "anonymous": false,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

Configure mqtt in the Configuration -> Integrations

Make sure all your mqtt devices have correct creds (DVES_USER/DVES_PASS in case of Tasmota)

Make sure you included discovery: and GOT RID of mqtt: in the main config

Restart the hassio

PS: if you need to reboot the whole machine, make sure your hass supervisor is updated to v139. In other case you will get the docker container boot loop. To fix the loop remove discovery.json in the config folder (via ssh or direct access to the os file system)

PS2: make sure you disabled autoupdate for ALL addons. To save some time in the future :slight_smile:

4 Likes
62

this work for me… now sonoff login into mqtt broker

1 Like
63

Broken Mosquitto, 100% SD Card Usage…what a lovely monday!
Now struggling to make the integration accept the broker…

1 Like
64

my SD card is going mental too, dont want to shut it down by pulling lead out. Ive been waiting for page to load for 30 minutes now

65

What if i don’t have v. 139. I don’t have such version. The latest is 138!
MQTT is not working. And now i got this message :slight_smile:

image
image1239×494 42.6 KB

image
image1080×399 31.6 KB

It is a total mess… HASSIO made M(a)yday

66

They (home assistant or supervisor) don’t appear to be loaded/running yet. Refresh the page repeatedly or clear browser cache?

67

Samba v8 is not starting (it is not working).
SSH is closing my connection.

In other words I don’t have tools to control it. Now I will try with hard rest.