But what’s all the GUI shenanigans for, then? There are so many configuration options under MQTT devices in the GUI, but nowhere to enter an actual MQTT topic. I wonder what it’s for.
- 2 Posts
- 4 Comments
- 3 months
How to add weather station
I still have trouble understanding how to add an MQTT device without YAML. It seems there’s an elaborate GUI flow made to deal with this, so why is this so complicated?
I have MQTT messages coming in. Their topics are e.g.
wx/temperature wx/humidity wx/light_lux wx/rain_mm wx/wind_dir_deg
How do I tell Home Assistant to just add the bloody device, and let me configure units afterwards and not type out 600 lines of YAML manually?
I don’t think they will bother. They will end up in a landfill, and the school will buy new Windows computers.
Update policy?
I used to just update stuff when I could see an update was available. This changed dramatically when a few months ago, I updated Zigbee2mqtt to version 2 and my whole house stopped working. That marked the moment when the other inhabitants in my house decided that the home automation project had gone too far.
Since then, when I saw an update was available, I’ve waited - preferably until I had seen other people reporting that stuff still worked. But now I’ve realised, that if I wait too long with an update, another update just comes along…
Can I somehow configure HA to always automatically install e.g. update 2.1.3 once update 2.1.4 becomes available? Or is that a nogo too? I realise that the only sure-fire way to do this is with a staging environment, where everything is tested out before updating the production environment. But how many of us has that kind of a setup?



Yes, with a Raspberry Pi, and sending data to the MQTT server directly with rtl_433 and the MQTT option.