There’s nothing to change when using MQTT via the UI, and nothing with MQTT changed in that regard. I suggest you create a separate support thread to figure out the problem with your installation.
No. You only need to change your MQTT yaml if you had a previously configured MQTT via yaml.
it’s not an issue with my installation, it’s a bug with the latest updates.
i do not have a fancy installation.
why not discuss it here? so that people still update without knowing the issues?
the main problem is, the stable channel is beta. obviously, if you read this thread. those problems should be discuessed in beta state, not in stable.
this leads to a never ending story of unstable installations. because how to know that exact version is real stable? should i update? when to update?
there is a fundamental issue on how updates getting rolled out.
We had over 1000 people run the beta, including myself who has MQTT set up via the UI. No one ran into this problem. This is an issue with your system, and if it leads to a problem an issue will be created. Lastly, we don’t want to bloat the release thread with support. So, if you want support, open a new thread. If you want to complain, go ahead, but that won’t fix your problems.
Are there startup errors in your logs related to MQTT in 2022.9?
Once active connection support is available in esphome.
If we are getting requests in…
I have RuuviTags. I asked the author of the custom component RuuviFriends if they would migrate to the new Bleak bluetooth platform - Plans to migrate to Bleak? · Issue #40 · ruuvi-friends/ruuvi-hass.io · GitHub but there has been no response, nor any real activity on the repo for some time in general.
Could I be a pest and request that Ruuvi just makes it officially into Home Assistant?
Same issue here, but I have mine added through the Homekit Controller
I also ran the beta with MQTT installed on my system and saw no issues as well.
What @petro is telling you is you will get much better support if you open a new thread for just your issue. If it is truly a bug with MQTT open a GitHub issue. I find the support to be outstanding for an open source project. You need to provide a lot more information for people to understand your issue and be able to help you.
Updated to 2022.9.1 and got the Update Warning about Pushover. So I commented out the information in notify.yaml because I have notify: !include notify.yaml in configuration.yaml and restarted HA. I did some test and it works fine, but I wanted to see what the GUI provided for settings. I am sure I am just over looking something, but I cannot find a Pushover setting selection anywhere. In integrations for Pushover there is no setting option.
Yes the adapter is fine, somehow HA picked up the lock overnight but now I have to figure out how to get the offline key and slot… I read the docs and don’t have a rooted android.
Does this mean that devices can be discovered but not added to HA from a proxy? Or they can be added but can’t be controlled through proxies yet?
No. I didn’t see any startup errors.
There was a message that automation configured to start HASS did not work at system startup due to the absence of the mqtt.publish service
What are you using to trigger that automation? I have the exact same automation that publishes some mqtt discovery topics. My trigger is
trigger:
- platform: homeassistant
event: start
I love the processor and memory usage along with the ability to change a ZHA coordinator without having to re-pair devices - I was always worried about what I’d do in case my Conbee failed. Also looking forward to more on BT Proxies.
However, all is not well in the automation editor. Honestly, I feel it’s a change for the sake of change. Rather than making things easier, it now mandates re-learning where the elements of the editor are. The editor has now become more unintuitive. For example, if I choose a trigger as “Device” and then decide to change it to “State”, I now need to delete the existing Device trigger and then add a new State trigger. The same goes for conditions. It is just not as intuitive as it was before. In the attempt to make things simple, the exact opposite has been achieved. I mean, in order to even rename an automation, I now need to click an overflow menu, find and then click Rename before I can actually make the change. Not very user friendly at all.
Lastly, in the automations list, I could easily enable/disable automations by toggling them. That has also been made more difficult by virtue of the overflow menu.
Love the new changes this release brings. However, changes to the automation editor are 3 setps backward IMHO. Will I learn and adapt? You bet - I love HA and how it allows me to take the smart home to a new level. Has it made the automation editor easier to use? Nope!!
Yes, it looks like your code.
alias: Start HASS
description: ""
trigger:
- platform: homeassistant
event: start
condition: []
action:
- service: mqtt.publish
data:
payload: announce
qos: "0"
retain: false
topic: shellies/command
Tomorrow I will try to install version 2022.9.1 again and check for errors in the MQTT log at system startup.
For those that are having mqtt issues, check that the old config is not lingering in your packages directory.
I have a few HHCCJCY01 and LYWSD03MMC (with ATC firmware) throughout the house.
Built the ESP as follows
After that I went back (ESP still connected via USB to the laptop I used to build), connected again and checked the log. It connected to the API but doesn’t seem to scan
[D][wifi:399]: Found networks:
[I][wifi:443]: - 'The Meier Residence' [redacted]▂▄▆█
[D][wifi:444]: Channel: 11
[D][wifi:445]: RSSI: -53 dB
[D][wifi:448]: - [redacted] [redacted]▂▄▆█
[D][wifi:448]: - [redacted] [redacted]▂▄▆█
[I][wifi:255]: WiFi Connecting to 'The Meier Residence'...
[I][wifi:516]: WiFi Connected!
[C][wifi:360]: Local MAC: AC:67:B2:34:BD:34
[C][wifi:361]: SSID: [redacted]
[C][wifi:362]: IP Address: 192.168.2.156
[C][wifi:364]: BSSID: [redacted]
[C][wifi:365]: Hostname: 'esp32-bluetooth-proxy-34bd34'
[C][wifi:367]: Signal strength: -53 dB ▂▄▆█
[C][wifi:371]: Channel: 11
[C][wifi:372]: Subnet: 255.255.255.0
[C][wifi:373]: Gateway: 192.168.2.1
[C][wifi:374]: DNS1: 192.168.2.1
[C][wifi:375]: DNS2: 0.0.0.0
[D][wifi:525]: Disabling AP...
[C][ota:085]: Over-The-Air Updates:
[C][ota:086]: Address: esp32-bluetooth-proxy.local:3232
[C][api:025]: Setting up Home Assistant API server...
[I][app:062]: setup() finished successfully!
IMPROV�
IMPROV�
[I][app:102]: ESPHome version 2022.9.0-dev compiled on Sep 8 2022, 17:49:40
[I][app:104]: Project esphome.bluetooth-proxy version 1.0
[C][wifi:502]: WiFi:
[C][wifi:360]: Local MAC: AC:67:B2:34:BD:34
[C][wifi:361]: SSID: [redacted]
[C][wifi:362]: IP Address: 192.168.2.156
[C][wifi:364]: BSSID: [redacted]
[C][wifi:365]: Hostname: 'esp32-bluetooth-proxy-34bd34'
[C][wifi:367]: Signal strength: -53 dB ▂▄▆█
[C][wifi:371]: Channel: 11
[C][wifi:372]: Subnet: 255.255.255.0
[C][wifi:373]: Gateway: 192.168.2.1
[C][wifi:374]: DNS1: 192.168.2.1
[C][wifi:375]: DNS2: 0.0.0.0
[C][logger:275]: Logger:
[C][logger:276]: Level: DEBUG
[C][logger:277]: Log Baud Rate: 115200
[C][logger:278]: Hardware UART: UART0
[C][bluetooth_proxy:053]: Bluetooth Proxy:
[C][safe_mode.button:022]: Safe Mode Button 'Safe Mode Boot'
[C][safe_mode.button:022]: Icon: 'mdi:restart-alert'
[C][esp32_ble_tracker:717]: BLE Tracker:
[C][esp32_ble_tracker:718]: Scan Duration: 300 s
[C][esp32_ble_tracker:719]: Scan Interval: 1100.0 ms
[C][esp32_ble_tracker:720]: Scan Window: 1100.0 ms
[C][esp32_ble_tracker:721]: Scan Type: ACTIVE
[C][captive_portal:088]: Captive Portal:
[C][mdns:094]: mDNS:
[C][mdns:095]: Hostname: esp32-bluetooth-proxy-34bd34
[C][ota:085]: Over-The-Air Updates:
[C][ota:086]: Address: esp32-bluetooth-proxy.local:3232
[C][api:138]: API Server:
[C][api:139]: Address: esp32-bluetooth-proxy.local:6053
[C][api:143]: Using noise encryption: NO
[C][improv_serial:032]: Improv Serial:
[D][api:102]: Accepted ::FFFF:C0A8:262
[D][api.connection:861]: Home Assistant 2022.9.1 (::FFFF:C0A8:262): Connected successfully
>
After a few minutes I see this on the log
[D][esp32.preferences:113]: Saving 1 preferences to flash...
[D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[D][esp32_ble_tracker:222]: Starting scan...
but then nothing happens. I know there are a few LYWSD03MMC (with ATC firmware) within 1 meter… but nothing shows.
Tried a second ESP32 with the same result…
Go to Developer Tools > Services and find the MQTT Publish service. If it’s not in the list then it means the MQTT integration failed to load. Check the Log for errors.