Is that what you need?
Most of the warnings seem to relate to mqtt. Try removing that from the config.
Are you running hassbian? Remove also the http stuff.
These are just for sake of tests.
Thanks.
I’m not sure about hassabian. I just installed Hassio to an SD card and went from there.
I originally had Mosquitto MQTT but that was removed and I followed the instructions for the Integrated MQTT. And it worked.
I then installed the IDE update, restarted and lost access.
Aa okay, you’re on hassio. I haven’t familiarized myself with the special aspects for that. Hope someone else have more tips.
Thank you.
try removing mqtt from config.yaml. That’s what i did prior to reboot. Follow these steps if you can get your front-end backup. Have you got a backup you can recover from?
if you use themes then remove frontend: from your configuration.yaml. That caused an error after I upgraded to 0.81. Also remove the mqtt: from your configuration.yaml
I removed mqtt: from config.yaml and I’m back in! Phew!
However, when attempting to configure MQTT in Integrations I get ‘cannot connect to broker’.
What should I be entering here?
What user name and password?
I read this post but I’m not clear how to set the MQTT user and password in users.
I have three users there: me and two Homeassistant users (sys generated), that can’t be removed.
If I create another ‘fictitious’ user, how does it link through to being the MQTT user and password?
All of my devices use my home assistant user name and password as the MQTT password (which previously matched the Mosquitto username and password) but that doesn’t work with configuring MQTT in Integrations.
Almost there. I just need a final nudge in the right direction from you guys.
nah just put your user from the addon config in the integration mqtt menu. worked for me
You mean the Mosquitto addon config?
I thought MQTT was integrated and the addon wasn’t required now.
Yeah it works for me. Try it out. I still get “Socket error on client <unknown>, disconnecting” but I can switch stuff from the frontend like it used to be so I’m happy with that.
OK. Thanks.
I still get ‘cannot connect to broker’.
username and password should be in quotations “”
{
"logins": [
{"username": "local-user", "password": "mypw"}
],
"anonymous": false,
"customize": {
"active": false,
"folder": "mosquitto"
},
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
}
The Socket error on client <unknown>, disconnecting comes from devices where you have to set the new username and password because homeassistant as username isn’t allowed anymore. Just found that out
Here’s what I now see in the overview:
The MQTT broker can’t be found when I attempt to configure it in integrations, either from the one-click top pane or the config panel from the lower pane.
Here’s and excerpt from the MQTT log:
1541617394: Socket error on client <unknown>, disconnecting. [WARN] Not found homeassistant on local database 1541617396: Socket error on client <unknown>, disconnecting. [WARN] Not found homeassistant on local database 1541617399: Socket error on client <unknown>, disconnecting. [WARN] Not found homeassistant on local database 1541617402: Socket error on client <unknown>, disconnecting. [WARN] Not found homeassistant on local database 1541617405: Socket error on client <unknown>, disconnecting. [INFO] found ashscott on local database
Which suggests to me that Mosquitto MQTT can’t find homeassistant, and vice versa!
There are two options in integration for mqtt. One I think just called mqtt and one called mqtt broker
You have to use the one which requires ip, port user and password.
Maybe try to set anonymous to true in the mqtt add on options and then restart hassio
Thanks, Chris. I already tried those options.
Stumped.
Did you read the addon description https://www.home-assistant.io/addons/mosquitto/ ? It’s pretty good explained there too.
You didn’t use “addons” or “homeassistant” as your mqtt username right?
Yes, I read all of that, and no, I’m not using those usernames.
Mosquitto is seeing my devices but home assistant doesn’t see Mosquitto.
1541618717: New connection from 10.0.1.59 on port 1883.
1541618717: New connection from 10.0.1.8 on port 1883.
1541618717: New connection from 10.0.1.62 on port 1883.
1541618717: New connection from 10.0.1.157 on port 1883.
1541618717: New connection from 10.0.1.11 on port 1883.
1541618717: New connection from 10.0.1.174 on port 1883.
1541618717: New connection from 10.0.1.53 on port 1883.
1541618717: New connection from 10.0.1.123 on port 1883.
1541618717: New connection from 10.0.1.14 on port 1883.
1541618717: New connection from 10.0.1.60 on port 1883.
1541618717: New connection from 10.0.1.28 on port 1883.
1541618717: New connection from 10.0.1.131 on port 1883.
1541618717: New connection from 10.0.1.58 on port 1883.
1541618717: New connection from 10.0.1.154 on port 1883.
1541618717: New connection from 10.0.1.8 on port 1883.
1541618717: New connection from 10.0.1.62 on port 1883.
1541618717: New connection from 10.0.1.59 on port 1883.
1541618717: New connection from 10.0.1.157 on port 1883.
1541618717: New connection from 10.0.1.11 on port 1883.
1541618717: New connection from 10.0.1.174 on port 1883.
1541618717: New connection from 10.0.1.53 on port 1883.
1541618717: New connection from 10.0.1.14 on port 1883.
1541618717: New connection from 10.0.1.123 on port 1883.
1541618717: New connection from 10.0.1.60 on port 1883.
1541618717: New connection from 10.0.1.58 on port 1883.
1541618717: New connection from 10.0.1.28 on port 1883.
1541618717: New connection from 10.0.1.131 on port 1883.
1541618717: New connection from 10.0.1.154 on port 1883.
1541618717: New connection from 10.0.1.8 on port 1883.
1541618717: New connection from 10.0.1.62 on port 1883.
1541618717: New connection from 10.0.1.59 on port 1883.
1541618717: New connection from 172.30.32.1 on port 1883.
1541618717: New connection from 10.0.1.157 on port 1883.
1541618717: New connection from 10.0.1.11 on port 1883.
1541618717: New connection from 10.0.1.174 on port 1883.
1541618717: New connection from 10.0.1.53 on port 1883.
1541618717: New connection from 10.0.1.14 on port 1883.
1541618717: New connection from 10.0.1.60 on port 1883.
1541618717: New connection from 10.0.1.58 on port 1883.
1541618717: New connection from 10.0.1.123 on port 1883.
1541618717: New connection from 10.0.1.28 on port 1883.
1541618717: New connection from 10.0.1.131 on port 1883.
1541618717: New connection from 10.0.1.154 on port 1883.
1541618717: New connection from 10.0.1.8 on port 1883.
1541618717: New connection from 10.0.1.62 on port 1883.
1541618717: New connection from 10.0.1.59 on port 1883.
1541618717: New connection from 10.0.1.157 on port 1883.
1541618717: New connection from 10.0.1.11 on port 1883.
1541618717: New connection from 10.0.1.174 on port 1883.
1541618717: New connection from 10.0.1.53 on port 1883.
1541618717: New connection from 10.0.1.14 on port 1883.
1541618717: New connection from 10.0.1.60 on port 1883.
1541618717: New connection from 10.0.1.58 on port 1883.
1541618717: New connection from 10.0.1.123 on port 1883.
1541618717: New connection from 10.0.1.131 on port 1883.
1541618717: New connection from 10.0.1.28 on port 1883.
1541618717: New connection from 10.0.1.154 on port 1883.
1541618717: New connection from 10.0.1.8 on port 1883.
1541618717: New connection from 10.0.1.62 on port 1883.
1541618717: New connection from 10.0.1.157 on port 1883.
1541618717: New connection from 10.0.1.59 on port 1883.
1541618717: New connection from 10.0.1.11 on port 1883.
1541618717: New connection from 10.0.1.174 on port 1883.
1541618717: New connection from 10.0.1.28 on port 1883.
Thanks for all of your help. Chris.
I’m going to start a new thread as we’ve resolved access the front end and it’s just the MQTT broker issue now.