I hope & expect both (the yaml files and UI) will be long time around. The elegance, for example in UI of “Automations”, is that one can do easy things with enough information in the UI, and it is then integrated in the corresponding yaml. But that one can do more elaborate things in the yaml files. The visaversa between UI and yaml is the difficult part.
Back to “Integrations”: I suspect that this is also the direction for the integrations. But IMHO the Integrations structure is a construction in progress and the MQTT is sent too early in that construction.
they should let both ways to coexist. there are lots of people that chose Home Assistant because the ability of editing the yaml [I know it’s not perfect, but it is, and that’s important for me].
making something clickable-only makes it less home/amateur-dev-friendly in my opinion. you know - if I wanted the easy way of click-n-go, I would go to something “nice and pretty” that someone did the hard work for me already 
yeah, somebody driven by a successful #hacktoberfest just pressed “send to production” button too early 
1 Like
Fixing the issue will always be the preferred way.
With the statement regarding the community mqtt addon, I have some comments.
The next version (will probably be released later this week) the NGINX proxy you open when using the web client will be authenticated by using Home Assistant.
The mosquitto broker (MQTT) that runs in that addon will not have that anytime soon, I have not (yet) looked into how much work that will require.
1 Like
Is anyone struggling with a binary sensors no longer functioning in HA? While i can see it on the network, see it establishes a connection to the broker it isn’t displaying a senor change state or toggling the relay when clicked.
(HA Garage door controller)
1 Like
Yes - I do see the same problem with my garage door magnetic sensor.
I was. But that problem has now been overtaken by this. Until I sort that I can’t look at the binary sensors.
I’m really stuck with it.
My garage door sensor is now working after a restart of HA. No explanation yet.
I tried the old on/off routine without success. Glad yours is working though. I’ll have another play with it this evening once i’ve got some spare time.
Actually i have another problem and that’s with state changes not being updated in HA after reboot. My automations do still seem to work though. I think that’s more of an espurna and tasmota issue that i need to address rather than HA or MQTT broker issue.
I finally managed to bring my system back online.
Here are the steps:
- remove mqtt: section under configuration.yaml (but leave your mqtt lights/switches/sensors untouched!)
- update to 0.81. My frontend wouldn’t start in the beginning because I had some old themes which weren’t compatible with 0.81. Just uncomment the frontend: part in configuration.yaml
- My mqtt username was “homeassistant”. This isn’t allowed anymore. You have to change all your tasmota etc. devices to a new username. Maybe you can use TasmoAdmin for that.
- Go to “Configuration” and then click on Integrations. Under “Set up a new integration” choose MQTT put your brokers ip adress in (which is the same as your hassio ip adress if you use the addon) put in your new user name and password.
- Restart Hassio
- All working again. That was a real pain in the ass to get that working again.
edit: set anonymous: true in the mqtt config (of course only if your mqtt port isn’t forwarded and only accessible from local network).
2 Likes
I’ve tried every single solution that seems to work for others, but somehow every option still fails for me…I’ve tried creating users in HASS, in the addon and in the configuration file. Tried almost every combination with old and newly created users, but…still no luck. So far I’ve spend 3 evenings/nights on this, but now I’m totally out of options…anyone else having the same issue as me?
I did pretty much the same as @chris1 has done and it worked for me. To get a working system initially, I flashed my Rpi SD card with a fresh HassOS hassio image and reverted to my last working snapshot. I left everything ticked when restoring the snapshot and chose wipe and restore.
I believe everything will need auto in the future.
Yes I ended up with random sensor names as the so off friendly name was not the detected name - my own fault I guess.
Restoring my old configuration is working every time, but as soon as I upgrade to V3 Mosquitto, it gets broken…no tasmota device can connect, even if I create new accounts etc. etc. For the very first time I have no clue what I should do to upgrade to the latest verions…
I followed the steps from people above, it works only for a while. I rebooted my pi and my devices started to connect. After a while I start getting the following warning:
WARNING (Thread-2) [homeassistant.components.mqtt] Disconnected from MQTT (1). Trying to reconnect in 1 s
And all my sensors and switches are unavailable again. It never connects again. Help please
Got MQTT running again, but my Xiaomi window sensors connected via zigbee2mqtt get no state updates any more.
Seems, that other users have similar problems with binary sensors.
The state does not change within MQTT. Since there was no change to zigbee2mqtt I think this is a problem of Mosquitto.
How does someone just insert this ““feature”” down our throats… Like COME ON,
I am wasting my time away from work… with work… on something that was functional.
Nobody on a local network cares if they have SSL and SHA289182 encryption.
If such a BREAKING change is implemented, users shall be warned. Better yet: Enable new features or changes WITH A KEY FLAG, maintaining backwards compatibility. THANK YOU.
I am literally pissed right now.
3 Likes
Or at least keep it in Beta until it’s functionality is proven.
Try without username and without password in mosquitto configuration
same problem for me… what a mess!!!
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.