ESP32 S3 Box3

m4v3r1ck · January 15, 2024, 9:45pm

Found another set of “Panasonic” NCR18650B unprotected (without the [+] button) that fit the case like a glove.

Screenshot 2024-01-15 at 22.43.25

Thanks HJM for your guidance.

HJM · January 16, 2024, 6:55am

You’re most welcome Maverick. It is interesting to see your new battery % topping out at 97%. I may adjust the calculation if I can get one more sample of a new battery charging. I’d like to adjust it so that it tops out at 100% for new batteries.

Can you also give a sample graph of the battery discharging until power off?

Cheers,
John

m4v3r1ck · January 16, 2024, 12:43pm

Hi John, working on discharging the battery.

Strange that the SOC lifted a bit upwards at ~ 11H00. May be the mute switched on?

Screenshot 2024-01-16 at 13.37.19

Keep you posted when the battery is fully discharged.
Cheers

HJM · January 16, 2024, 8:23pm

The SOC is calculated from the voltage which in turn is dependent on the current draw. If the current drops a bit (such as if it goes into power save from radar absence detected, or other reason) then the voltage will increase a bit and SOC too.

That is also why there is a dip when it is still plugged in, but the battery stops charging. The charging voltage is 4.2V and battery voltage will keep climbing toward that level until the current going in drops below 500mA (set by a 2k ohm resistor on the board) at which point the charging/protection chip disconnects the charging voltage and the apparent battery voltage drops down a bit to its internal level.

m4v3r1ck · January 17, 2024, 11:28am

Hi HJM,

This is the discharge statistic from the moment I pulled the USB charger from the BOX-3 at 01/16 at 10H09, until he BOX-3 turned itself off.

Recharging it again.

HJM · January 17, 2024, 7:09pm

That’s great work Maverick. What are the values for

The level plateau before unplugging the power supply (95%?)
The point just before it sharply drops down near the end (35%?)

Even better would be the voltages, but I can approximate the voltage from the %.

Cheers, J

m4v3r1ck · January 17, 2024, 7:51pm

Your welcome HJM.

As per your request:

Cheers

stu247 · January 18, 2024, 3:37pm

I updated one of my ESP32 S3 Box3s from ESPHome version 2023.12.5 to 2023.12.7 and now my wake word detection does not work. Has anyone else seen this? I tried deleting the build directory and rebuilding everything, but that did not help. Here is the logs:

[09:28:37][D][voice_assistant:183]: VAD detected speech
[09:28:37][D][voice_assistant:410]: State changed from WAITING_FOR_VAD to START_PIPELINE
[09:28:37][D][voice_assistant:416]: Desired state set to STREAMING_MICROPHONE
[09:28:37][D][voice_assistant:200]: Requesting start...
[09:28:37][D][voice_assistant:410]: State changed from START_PIPELINE to STARTING_PIPELINE
[09:28:37][D][voice_assistant:431]: Client started, streaming microphone
[09:28:37][D][voice_assistant:410]: State changed from STARTING_PIPELINE to STREAMING_MICROPHONE
[09:28:37][D][voice_assistant:416]: Desired state set to STREAMING_MICROPHONE
[09:28:37][D][voice_assistant:517]: Event Type: 0
[09:28:37][E][voice_assistant:644]: Error: no_wake_word - No wake word detected
[09:28:37][D][voice_assistant:510]: Signaling stop...
[09:28:37][D][voice_assistant:410]: State changed from STREAMING_MICROPHONE to STOP_MICROPHONE
[09:28:37][D][voice_assistant:416]: Desired state set to IDLE
[09:28:37][D][esp_adf.microphone:234]: Stopping microphone
[09:28:37][D][voice_assistant:410]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE
[09:28:37][D][esp-idf:000]: W (44889) AUDIO_ELEMENT: IN-[filter] AEL_IO_ABORT

[09:28:37][D][esp-idf:000]: E (44893) AUDIO_ELEMENT: [filter] Element already stopped

[09:28:37][D][esp-idf:000]: W (44923) AUDIO_PIPELINE: There are no listener registered

[09:28:37][D][esp-idf:000]: I (44926) AUDIO_PIPELINE: audio_pipeline_unlinked

[09:28:37][D][esp-idf:000]: W (44933) AUDIO_ELEMENT: [i2s] Element has not create when AUDIO_ELEMENT_TERMINATE

[09:28:37][D][esp-idf:000]: I (44938) I2S: DMA queue destroyed

[09:28:37][D][esp-idf:000]: W (44944) AUDIO_ELEMENT: [filter] Element has not create when AUDIO_ELEMENT_TERMINATE

[09:28:37][D][esp-idf:000]: W (44950) AUDIO_ELEMENT: [raw] Element has not create when AUDIO_ELEMENT_TERMINATE

[09:28:37][W][component:214]: Component voice_assistant took a long time for an operation (0.22 s).
[09:28:37][W][component:215]: Components should block for at most 20-30ms.
[09:28:37][D][voice_assistant:517]: Event Type: 2
[09:28:37][D][voice_assistant:607]: Assist Pipeline ended
[09:28:37][D][voice_assistant:517]: Event Type: 1
[09:28:37][D][voice_assistant:520]: Assist Pipeline running
[09:28:37][D][voice_assistant:517]: Event Type: 9
[09:28:37][D][esp_adf.microphone:285]: Microphone stopped
[09:28:37][D][voice_assistant:517]: Event Type: 0
[09:28:37][E][voice_assistant:644]: Error: wake-stream-failed - Unexpected error during wake-word-detection
[09:28:37][D][voice_assistant:510]: Signaling stop...
[09:28:37][D][voice_assistant:410]: State changed from STOPPING_MICROPHONE to STOP_MICROPHONE
[09:28:37][D][voice_assistant:416]: Desired state set to IDLE
[09:28:37][D][voice_assistant:410]: State changed from STOP_MICROPHONE to IDLE
[09:28:37][W][component:214]: Component voice_assistant took a long time for an operation (0.21 s).
[09:28:37][W][component:215]: Components should block for at most 20-30ms.
[09:28:37][D][voice_assistant:517]: Event Type: 2
[09:28:37][D][voice_assistant:607]: Assist Pipeline ended
[09:28:37][D][voice_assistant:410]: State changed from IDLE to START_MICROPHONE
[09:28:37][D][voice_assistant:416]: Desired state set to WAIT_FOR_VAD
[09:28:37][D][voice_assistant:153]: Starting Microphone
[09:28:37][D][voice_assistant:410]: State changed from START_MICROPHONE to STARTING_MICROPHONE
[09:28:37][D][esp-idf:000]: I (45371) I2S: DMA Malloc info, datalen=blocksize=512, dma_buf_count=8

[09:28:37][D][esp-idf:000]: I (45378) I2S: I2S0, MCLK output by GPIO2

[09:28:37][D][esp-idf:000]: I (45388) AUDIO_PIPELINE: link el->rb, el:0x3d0435ec, tag:i2s, rb:0x3d043a00

[09:28:37][D][esp-idf:000]: I (45395) AUDIO_PIPELINE: link el->rb, el:0x3d043760, tag:filter, rb:0x3d045a40

[09:28:37][D][esp-idf:000]: I (45402) AUDIO_ELEMENT: [i2s-0x3d0435ec] Element task created

[09:28:37][D][esp-idf:000]: I (45410) AUDIO_THREAD: The filter task allocate stack on external memory

[09:28:37][D][esp-idf:000]: I (45417) AUDIO_ELEMENT: [filter-0x3d043760] Element task created

[09:28:37][D][esp-idf:000]: I (45423) AUDIO_ELEMENT: [raw-0x3d043890] Element task created

[09:28:37][D][esp-idf:000]: I (45429) AUDIO_PIPELINE: Func:audio_pipeline_run, Line:359, MEM Total:16584599 Bytes, Inter:100872 Bytes, Dram:100872 Bytes


[09:28:37][D][esp-idf:000]: I (45437) AUDIO_ELEMENT: [i2s] AEL_MSG_CMD_RESUME,state:1

[09:28:37][D][esp-idf:000]: I (45443) AUDIO_ELEMENT: [filter] AEL_MSG_CMD_RESUME,state:1

[09:28:37][D][esp-idf:000]: I (45451) RSP_FILTER: sample rate of source data : 16000, channel of source data : 2, sample rate of destination data : 16000, channel of destination data : 1

[09:28:37][D][esp-idf:000]: I (45456) AUDIO_PIPELINE: Pipeline started

[09:28:37][D][esp_adf.microphone:273]: Microphone started
[09:28:37][D][voice_assistant:410]: State changed from STARTING_MICROPHONE to WAIT_FOR_VAD
[09:28:37][D][voice_assistant:170]: Waiting for speech...
[09:28:37][D][voice_assistant:410]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD
[09:28:38][W][component:214]: Component voice_assistant took a long time for an operation (0.21 s).
[09:28:38][W][component:215]: Components should block for at most 20-30ms.
[09:28:38][W][component:214]: Component voice_assistant took a long time for an operation (0.21 s).
[09:28:38][W][component:215]: Components should block for at most 20-30ms.

gbutters · January 18, 2024, 4:11pm

I am seeing the same thing here.

m4v3r1ck · January 18, 2024, 5:31pm

Yes, count me in.

gbutters · January 18, 2024, 7:38pm

Also unable to rollback to 12.6 as produces an error on compile stating microphone component requires v2023.12.7

IWShady · January 18, 2024, 9:01pm

Seeing the same here as well.

HJM · January 18, 2024, 11:17pm

It’s affecting me too. The correct place to report issues with esphome is Issues · home-assistant/core · GitHub rather than here.

I have opened an issue on this matter here:

github.com/home-assistant/core

Wake word in pipeline stops working after upgrading to esphome 2023.12.7

opened 11:14PM - 18 Jan 24 UTC

jaymunro

integration: esphome integration: assist_pipeline

### The problem As mentioned here https://community.home-assistant.io/t/esp32-s…3-box3/638287/191?u=hjm, the pipeline starts up with: ``` [voice_assistant:644]: Error: no_wake_word - No wake word detected ``` As noted in that thread, this is reported by many people and in related to Esp32-s3-box3 but may be more general with other hardware affect too (just a postulation). ### What version of Home Assistant Core has the issue? 2024.1.3 ### What was the last working version of Home Assistant Core? Was noticed after an upgrade to esphome 2023.12.7 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Esphome ### Link to integration documentation on our website https://www.home-assistant.io/integrations/esphome ### Diagnostics information Log details (ERROR) Logger: homeassistant.components.assist_pipeline.pipeline Source: components/assist_pipeline/pipeline.py:714 Integration: Assist pipeline ([documentation](https://www.home-assistant.io/integrations/assist_pipeline), [issues](https://github.com/home-assistant/core/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+assist_pipeline%22)) First occurred: 11:00:18 AM (5 occurrences) Last logged: 11:21:40 AM Unexpected error during wake-word-detection Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 714, in wake_word_detection result = await self.wake_word_entity.async_process_audio_stream( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/wake_word/__init__.py", line 112, in async_process_audio_stream result = await self._async_process_audio_stream(stream, wake_word_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/wyoming/wake_word.py", line 153, in _async_process_audio_stream chunk_info = audio_task.result() ^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/wyoming/wake_word.py", line 83, in next_chunk async for chunk_bytes in stream: File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 798, in _wake_word_audio_stream async for chunk in audio_stream: File "/usr/src/homeassistant/homeassistant/components/assist_pipeline/pipeline.py", line 1225, in process_enhance_audio async for dirty_samples in audio_stream: File "/usr/src/homeassistant/homeassistant/components/esphome/voice_assistant.py", line 158, in _iterate_packets raise RuntimeError("Not running") RuntimeError: Not running ### Example YAML snippet ```yaml substitutions: name: esp32-s3-box-3-5ad0fc friendly_name: Jarvis packages: esphome.voice-assistant: github://esphome/firmware/voice-assistant/esp32-s3-box-3.yaml@main esphome: name: ${name} name_add_mac_suffix: false friendly_name: ${friendly_name} api: encryption: key: rTJvoot5F8Z3gFEQHtaEFjXYV05tFMJ2TLON6zReaGc= wifi: ssid: !secret wifi_ssid password: !secret wifi_password # i2c: # - id: bus_a # sda: GPIO08 # scl: GPIO18 # scan: false # - id: bus_b # sda: GPIO41 # scl: GPIO40 sensor: - platform: adc pin: GPIO10 name: "Battery voltage" id: battery_voltage unit_of_measurement: "V" accuracy_decimals: 3 device_class: "voltage" entity_category: "diagnostic" disabled_by_default: true update_interval: 30s attenuation: auto filters: - multiply: 4.01 - platform: copy source_id: battery_voltage name: "Battery level" unit_of_measurement: "%" accuracy_decimals: 1 device_class: "battery" entity_category: "diagnostic" filters: - lambda: return (x - 2.5) / (4.2 - 2.5) * 100; - clamp: min_value: 0 max_value: 100 ignore_out_of_range: true # - platform: aht10 # i2c_id: bus_b # variant: AHT20 # temperature: # name: "Temperature" # accuracy_decimals: 2 # humidity: # name: "Humidity" # accuracy_decimals: 1 # update_interval: 60s switch: - platform: template name: "Mute when absent" id: mute_when_absent icon: mdi:account-right-arrow optimistic: true entity_category: config restore_mode: RESTORE_DEFAULT_OFF number: - platform: template name: "Presence duration" id: radar_delayed_off icon: mdi:account-clock optimistic: true restore_value: true initial_value: 60 min_value: 0 step: 5 max_value: 300 unit_of_measurement: s entity_category: config mode: box binary_sensor: - platform: gpio pin: number: GPIO21 name: "Presence detect" disabled_by_default: false device_class: "occupancy" filters: - delayed_off: !lambda return id(radar_delayed_off).state * 1000; on_release: then: - if: condition: switch.is_on: mute_when_absent then: - switch.turn_on: mute - light.turn_off: led on_press: then: - if: condition: switch.is_on: mute_when_absent then: - switch.turn_off: mute - light.turn_on: led ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

Feel free to add helpful comments, but avoid adding “me too” clutter.

m4v3r1ck · January 19, 2024, 7:53am

Great comment. Will provide additional context.

daywalker03 · January 19, 2024, 9:35am

Does anyone know where I can buy one of these?

Gregkg · January 19, 2024, 5:29pm

Same here. If I press ‘Factory Reset’ in the ESP’s devices/integration page, it works once but not again. After doing so, I sometimes see the following error messages in the devices’s ESPHome Logs:

[E][voice_assistant:644]: Error: wake-stream-failed - Unexpected error during wake-word-detection

[E][esp32.preferences:146]: Error saving 1 preferences to flash. Last error=ESP_ERR_NVS_INVALID_HANDLE for key=233825507

stu247 · January 19, 2024, 5:53pm

A new version of ESPHome has been published: esphome-2023.12.8. This version fixes the issue with not detecting the wake word.

stu247 · January 19, 2024, 6:08pm

Update: This post is only relevant for people that use the ESPHome command line. The HA OS ESPHome Add-on already supports this functionality.

I created a way for Home Assistant to track new versions of ESPHome. In case anyone is interested, I am documenting it below.

I picked one ESPHome device (in the example below orange_box_3) to report the ESPHome version to Home Assistant by adding the following to the ESPHome YAML:

text_sensor:
  - platform: version
    name: version
    hide_timestamp: true

In HA configuration.yaml, I created a REST sensor to track the latest version of ESPHome:

rest:
  - resource: https://api.github.com/repos/esphome/esphome/releases/latest
    scan_interval: 21600  # 6 hrs
    sensor:
      - name: "ESPHome Latest Version"
        value_template: "{{ value_json.tag_name }}"

An HA automation will send a notification if the latest ESPHome version is different from the version on the device:

- id: updateAvailEsphome
  alias: Esphome Update Available Notification
  trigger:
    - platform: state
      entity_id: sensor.esphome_latest_version
    - platform: state
      entity_id: sensor.orange_box_3_version
  condition:
    - condition: template
      value_template: "{{ states('sensor.orange_box_3_version') != states('sensor.esphome_latest_version') }}"
    - condition: template
      value_template: "{{ trigger.to_state.state != 'unavailable' }}"
    - condition: template
      value_template: "{{ trigger.from_state.state != 'unavailable' }}"
    - condition: template
      value_template: "{{ trigger.to_state.state != '' }}"
    - condition: template
      value_template: "{{ trigger.from_state.state != '' }}"
  action:
    - service: persistent_notification.create
      data_template:
        title: "New Version Esphome"
        message: "Esphome {{ states('sensor.esphome_latest_version') }} is available (current version is {{ states('sensor.orange_box_3_version') }})."
        notification_id: updateAvailEsphome

RT1080 · January 19, 2024, 6:31pm

Each esphome device has an “update.devicename” entity built in which does this out of the box. At least on ha os using the esphome addon. Or are you solving for something else?

stu247 · January 19, 2024, 6:50pm

I have “update.devicename” entities for Z-wave and WLED, but none for ESPHome. I am using HA docker and esphome CLI, so maybe that is the difference.