Paulus Schoutsen
Paulus Schoutsen
The problem here that this is working around the fact that our services do not have return values. We shouldn't implement work arounds for this. We have had some explorative...
Yes, but the voice assistant events are not fired over the event bus and not accessible for automations.
Make sure you use the correct charger for your Raspberry Pi: https://www.home-assistant.io/integrations/rpi_power/ A lack of power can impact writes to SD card. Also make sure you use a high quality...
All write access is sequential. Unless you have a custom component that has issues. 2/3 of the log you posted is with a custom component package `pymultimatic`. Try disabling all...
Fixed in #88797
You should really write your beacon template as a custom integration in Python and don't use jinja2 for this.
The OpenAI prompt is a Jinja2 template that we render as input, and somehow your situation is not working. ```jinja2 {%- for area in areas %} {%- set area_info =...
ok, will be fixed in next hot fix release. Thanks for verifying!
This issue is about OpenAI. Yours is about Google. Also, Home Assistant only supports a single conversation agent at the moment. So if you don't want to use Google, disable...
You can already call `decode` and `encode` on strings to turn it back into bytes so I don't see how this is a useful addition.