Open cvwillegen opened 6 months ago
Same issue here.
i started having this issue yesterday. if i restart the atom echo a few times it starts to behave properly. not a solution but a temp fix.
v2024.5.3 also broke my Atom with this problem - reverted ESPHome to 2024.5.2 to fix it.
Same issue here, also reverted back to 2025.5.2 for the time being. Since this was the only change merged for 2024.5.3, it must have been broken by this:
https://github.com/esphome/esphome/pull/6800
@jesserockz?
Same issue here, started happening with 2024.5.3
M5 Echo, Same issue, #6800 solved the BLE Bootloop error, but gettin "Could not allocate speaker buffer"
same.
Exactly the same behavior:
10:07:40][D][voice_assistant:220]: Starting Microphone [10:07:40][W][voice_assistant:086]: Could not allocate speaker buffer
HA version: 2024.5.5
Commenting to add another confirmation of the same issue. Unfortunately though when the error starts it hangs up my ESPHome page so I can't get back to the logs to grab and paste here.
could you try to use pr#6718
external_components:
- source: github://pr#6718
components:
- voice_assistant
- i2s_audio
- speaker
could you try to use pr#6718
external_components: - source: github://pr#6718 components: - voice_assistant - i2s_audio - speaker
Where now do you need me to put that? I'm not yet a wiz at this.
You can put it everywhere you want in your yaml file.
using pr#6718 and it works again.
I got it sorted where to put it. Receive a new error but voice assistant still worked.
[20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][component:157]: Component i2s_audio.speaker set Warning flag: unspecified [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:39][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:40][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:41][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:42][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:43][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:44][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:44][W][i2s_audio.speaker:207]: Error writing to I2S: ESP_OK [20:24:44][W][component:170]: Component i2s_audio.speaker cleared Warning flag
can you show your Yaml code?
@gnumpi could you have a look above, this is an issue i saw as well using the rtttl component as well after closing.
can you show your Yaml code?
@gnumpi could you have a look above, this is an issue i saw as well using the rtttl component as well after closing.
substitutions:
name: m5stack-atom-echo-30ed84
friendly_name: Dev Atom
packages:
m5stack.atom-echo-voice-assistant: github://esphome/firmware/voice-assistant/m5stack-atom-echo.yaml@main
esphome:
name: ${name}
name_add_mac_suffix: false
friendly_name: ${friendly_name}
external_components:
- source: github://pr#6718
components:
- voice_assistant
- i2s_audio
- speaker
api:
encryption:
key: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
I have the same issue with 2024.5.4 as well.
The latest update solved the issue for me. m5stack-atom-echo is working again like expected.
Thanks to the developers who fixed this so fast for us.
On 28 May 2024, at 11:33, Sam Dassanayake @.***> wrote:
I have the same issue with 2024.5.4 as well.
— Reply to this email directly, view it on GitHubhttps://github.com/esphome/issues/issues/5849#issuecomment-2134764625, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOYKTNL7J7SXZG3ZXZJDQQLZERFPZAVCNFSM6AAAAABIIWN2R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUG43DINRSGU. You are receiving this because you commented.Message ID: @.***>
@gnumpi could you have a look above, this is an issue i saw as well using the rtttl component as well after closing.
Regarding pr#6718: This warning is triggered when the the speaker has been started but it didn't receive any input for more than 100ms. The warning message itself is nonsense though, I will try to change it. Probably it is also necessary to increase the threshold value a bit.
I resent the firmware with PR#6718 to 2 of my Atom's. and I'm getting mixed results. One is working fine but logging stops after it initially coming online (no constant activity logging as it normally does). The other results in the log entry below.
[09:04:40][I][app:100]: ESPHome version 2024.5.4 compiled on May 28 2024, 08:54:55
[09:04:40][I][app:102]: Project m5stack.atom-echo-voice-assistant version 1.0
[09:04:40][C][wifi:580]: WiFi:
[09:04:40][C][esp32_rmt_led_strip:175]: ESP32 RMT LED Strip:
[09:04:40][C][esp32_rmt_led_strip:176]: Pin: 27
[09:04:41][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Button'
[09:04:41][C][gpio.binary_sensor:016]: Pin: GPIO39
[09:04:41][C][esp32_ble:374]: ESP32 BLE:
[09:04:42][D][api:102]: Accepted X.X.X.X
[09:04:42][W][component:237]: Component api took a long time for an operation (53 ms).
[09:04:42][D][api.connection:1321]: Home Assistant 2024.5.5 (X.X.X.X): Connected successfully
[09:04:42][D][voice_assistant:447]: State changed from IDLE to START_MICROPHONE
[09:04:42][W][component:237]: Component i2s_audio.microphone took a long time for an operation (51 ms).
[09:04:42][W][component:238]: Components should block for at most 30 ms.
[09:04:45][D][esp32_ble:255]: Disabling BLE...
[09:04:46][D][esp-idf:000][BTC_TASK]: E (11683) BT_OSI: config_save, err_code: 0x1
[09:04:46][W][component:237]: Component esp32_ble took a long time for an operation (232 ms).
[09:04:46][W][component:238]: Components should block for at most 30 ms.
If I try the pr#6718 :
external_components:
- source: github://pr#6718
components:
- voice_assistant
- i2s_audio
- speaker
esp_adf:
I cant compile
esp_adf: [source /config/atom-echo.yaml:275]
Component not found: esp_adf.
If I change it to
external_components:
- source: github://pr#6718
components:
- voice_assistant
- i2s_audio
- speaker
I get
Failed config
voice_assistant: [source /config/atom-echo.yaml:89]
id: va
microphone: echo_microphone
speaker: echo_speaker
noise_suppression_level: 2
auto_gain: 31dBFS
volume_multiplier: 2.0
This option requires component esp_adf.
Ok the following works:
external_components:
- source: github://pr#5230
components:
- esp_adf
refresh: 0s
- source: github://pr#6718
components:
- voice_assistant
- i2s_audio
- speaker
esp_adf:
Only getting the „ Error writing to I2S: ESP_OK“
Just for my own sanity, we're leaving
external_components:
- source: github://pr#6718
components:
- voice_assistant
- i2s_audio
- speaker
In the build yaml for now since I don't see this issue assigned or in progress yet?
Any solution? Seeing the same error, cannot compil toe above suggestions.
Still the same problem here, on esphome 2024.11.1
The problem
After update to 2024.5.3, M5Stack Atom Echo devices fail to allocate a microphone buffer. This causes the device to not function as intended.
Which version of ESPHome has the issue?
2024.5.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.5.5
What platform are you using?
ESP8266
Board
m5stack.atom-echo
Component causing the issue
Microphone / Voice Assistant
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response