MichaelMKKelly

@matt335672 - yeah that was my point, not supporting udp is fine but if a client tries to use it and it causes server side issues then that is obviously...

@matt335672 without any evidence to back it up I imagined that it worked in such a way: client: talk to me on udp://xyz instead of: client: talk to me on...

@akarl10 kde did indeed have some issues at the same time. I assumed it was because it was trying to look at my home directory and was hanging in the...

I spent some time on it today and I have resolved the issue on my EQ14: The problem: when proxmox boots it loads the BT drivers which puts the BT...

> Did something change in HASOS recently. I see [home-assistant/operating-system#4060](https://github.com/home-assistant/operating-system/issues/4060) that suggests blacklisting, but I didn't have to previously? But thanks, this blacklisting does the trick for me :-) I...

spoke with @SergeantPup on discord about this: I was able to replicate this with ``` alias: long press test description: "" triggers: - trigger: state entity_id: - event.mk_room_voice_button_press conditions: -...

This has cropped up a few times on home assistant discord. It appears that whilst using the arduino framework the player is not reporting that its finished playing so gets...

I think you should be fine to switch esp-idf framework and use i2s_audio - speaker - media_player without the voice assistant component and may solve the issue

@comet424 can try this: ``` ############## ### Bedroom ### ############## esphome: name: speaker-1 friendly_name: "Speaker #1" esp32: board: esp32dev framework: type: esp-idf # Enable logging logger: # Enable Home Assistant...

they are just warnings dont worry about them