Mosquito MQTT update v3 broke my hassio

Installation Home Assistant OS
295

same problem for me… what a mess!!!

296

Thanks mate. This worked for me:sweat_smile:. I had to stop, uninstall and then restore it from back up as you have shown above and restarted HA and RP Pi3+ also. Now my Sonoff Pows Basics, Sensor nodes (5 sensors in each), 10 Blue Iris based cameras and etc etc are all working

I am taking it slowly with other important things. I have stopped with 0.76.2 and have 3 test benches to check new versions but my main unit I am not updating just yet. WIth this bad experience I have DISABLED all AUTO UPDATES to ADD-ONs.

Home assistant in changing a lot but things are breaking and it is not fun when you cannot take a break and do something else without tinkering with this all the time. Home Assistant is becoming pain in the butt for a person to maintain and it is not fun when your wife and kids yelling at you.

297

There’s a surprise :smile:

The old version works fine with the latest version of HA so stop upgrading and everything will be fine, there’s no must haves in the update so just wait until everything settles down.

1 Like
298

I keep getting disconnect errors:

[INFO] found esp1mqtt on Home Assistant
1541682637: New client connected from 192.168.1.192 as ledcontroller-68c63a9fb114 (c1, k15, u'esp1mqtt').
1541682787: Client ledcontroller-68c63a9fb114 has exceeded timeout, disconnecting.
1541682787: Socket error on client ledcontroller-68c63a9fb114, disconnecting.
1541682803: New connection from 192.168.1.192 on port 1883.
[INFO] found esp1mqtt on Home Assistant
1541682804: New client connected from 192.168.1.192 as ledcontroller-68c63a9fb114 (c1, k15, u'esp1mqtt').
1541682943: New connection from 192.168.1.192 on port 1883.
[INFO] found esp1mqtt on Home Assistant
1541682943: Client ledcontroller-68c63a9fb114 already connected, closing old connection.
1541682943: Client ledcontroller-68c63a9fb114 disconnected.
1541682943: New client connected from 192.168.1.192 as ledcontroller-68c63a9fb114 (c1, k15, u'esp1mqtt').
299

Hi Team,

I too seemed to have walked into problems with MQTT v3.
I run Sonoff Basic w/Tasmota and some ESP8266 (BRUH code) sensors which were hard-coded with username and password.

So I was stuck as the INO’s running on ESP8266 were hard-coded (please someone guide me on a better way).

I decided to:

  1. Check Configuration for Auth and MQTT Settings
  2. NOT change any settings within Sonoff/Tasmota as they were working a day ago
  3. Modified the MQTT username in the Add-On config (which I think did the job).

Below are my settings for Configuration.yaml and also settings for MQTT Add-On.

################################################
# Configuration.yaml Snips 
################################################
homeassistant:
    <Cut for Brevity>
  auth_providers:
    - type: homeassistant
    - type: legacy_api_password

mqtt:
  broker: xxx.xxx.xxx.xxx  #Same as my pi


################################################
# Configuration from MQTT Embedded Broker
################################################
Note that the MQTTUser, and MQTTPWD are same userid/pwd that I use on the ESP8266/BRUH Sensors.  Also use same ID on Sonoff/Tasmota.

{
  "logins": [
    {
      "username": "<MQTTUser>",
      "password": "<MQTTPWD"
    }
  ],
  "anonymous": true,
  "customize": {
    "active": false,
    "folder": "mosquitto"
  },
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem"
}

I hope this helps,
~Bryan

Kit: Hassio 0.81.6, Resin OS 2.3.0+rev1, Supervisor: v139

300

MQTT Update V3 also broke my setup, could go back to V2 with a snapshot.
Not a pleasant experience. Could not figure out to run V3.
Maybe the makes can share more details what was changed.

301

Ditto. my entire house is down

302

V4 just popped up, everything has reconnected after the update. Just rebooted and all is ok.

1 Like
303

V4 certainly has a LOT less chatter in the logs. Everything seems OK so far.

1 Like
304

Has anyone upgraded from version 2 to 4? I was on 3 temporarily then downgraded due to all the probs. I’m not updating to 4 until I hear from someone who went from 2 to 4 successfully. :slight_smile:

305

I finally got 3 working yesterday. I upgraded to 4 this afternoon. The upgrade to 4 was uneventful. So far all is quiet on the Western Front.

306

After being down for a couple of days v4 restored everything for me.

307

@quovadis Did you update from V2?

308

I just tried the direst update from V2 to V4 and now HA is dead for me on a reboot. I can get into the CLI but HA does not start.

Maybe I should have removed the integration first before the update or remove the addon completely before adding it back in.

I tried removing Mosquito from cli with

hassio addons uninstall --name “core_mosquitto”

but it still wouldn’t come back up so I am currently flashing Hassio to the card and hope to get it back up from a backup with V2 running soon.

UPDATE
It appears that an issue with Chromecast was stopping it coming back up. I have tried again but, as mentioned before, you cannot use “homeassistant” as the username. I changed it and changed 1 Sonoff and that works. Not ideal as some of my devices are standalone with no working OTA option so will need to be done manually :rage:

I made sure that the integration was removed before restarting HA then adding it under back to the “configured” section.

309

Try ssh root to your pi, go to /config/.storage and delete the file core.config_entries, then go into /config and edit out all mqtt references in your configuration.yaml

1 Like
310

From what you’ve said, as my mqtt username isn’t homeassistant, I should be able to update the add-on with no further action?

311

Yes you should be good to go but make a Snap shot first and copy it off your device.

Remove the integration, restart HA, Update Mosquito to v4, restart HA then add the integration back. This is what I did to test my Sonoff and Espeasy Wemos D1. I have several Bruh NodeMCU’s and Wemos D1’s that seem to look up when I flash them OTA. I really need to get most of them running ESPeasy so that I have a web interface to change this in the future.

Good luck and I am keeping everything crossed for you - This has taken me most of the day to get back and working as it should.

1 Like
312

Cheers, because mines a VM I cloned the whole bloody thing first :slight_smile:

Anyway, stopped the add-on, updated and restarted, everything just like it was before, still not using auth.

1 Like
313

Good to hear that its working for you.

Just making a list of all the MQTT devices I have - currently found 5 that will need to be manually update via IDE from a laptop - leaving that for another day :wink:

314

Same question…Anyone from v2->v4?