TESTERS REQUIRED - ESPHome 2025.2.x - removed esp ADF Components

[BigBobbas]

hi everyone, I have added the new ESPHome media player and removed the ADF external component. It is working for me... but if anyone would like to test and find the bugs, then we can take it from there
I've put a sensor and no sensor dock version here https://github.com/BigBobbas/ESP32-S3-Box3-Custom-ESPHome/tree/dev
The best place to get involved and give feedback, report issues etc is on Discord https://discord.gg/U3SRYCG6Kp

Many Thanks as always for your support 👍

[smartmatic]

Hi @BigBobbas
I've installed the dev branch which worked without issues. Thank you.
Then i've configured a light in the lights page but the light does not switch on.

I see only this in the logs

08:45:10][D][binary_sensor:036]: 'lights1': Sending state ON
[08:45:10][D][script:077]: Script 'saver_enabled' restarting (mode: restart)
[08:45:10][D][light:036]: 'LCD Backlight' Setting:
[08:45:10][D][light:051]:   Brightness: 100%
[08:45:10][D][light:085]:   Transition length: 0.1s
[08:45:10][D][binary_sensor:036]: 'lights1': Sending state OFF

This is my configuration:

#### lights page #####  
  - platform: touchscreen
    page_id: lights_page
    id: lights1
    internal: true
    x_min: 5
    x_max: 105
    y_min: 90
    y_max: 170
          #### make sure that the following 4 lines are uncommented by removing the prefixed '#' ###
    on_click:
      min_length: 10ms
      max_length: 500ms
      then: 
        - homeassistant.service:
            service: light.toggle
            data:
              entity_id: light.schlafzimmer_deckenlicht
 
        - component.update: s3_box_lcd

Do i made something wrong?

[BigBobbas]

if you go into HA devices and services, then click the right arrow on the ESPHome icon it should list all the ESPHome devices. Then click on the 'configure' button and make sure that the box is ticked to allow the device to call actions.

[smartmatic]

The permission is granted to allow actions. Meantime i found out that the configuration is working. So the light turns on / off. But the state does not change in HA. And the tested light was in a different room why i did not see immediately that it is working. The Icon on the ESP does also not change the colour to get a visual feedback that the light is on or off.

Is that a missing configuration and where can i change it?

[BigBobbas]

if you read further down this section https://github.com/BigBobbas/ESP32-S3-Box3-Custom-ESPHome/blob/main/instructions/make%20it%20your%20own.md#the-display
it will give details on how to add a text_sensor to retrieve the state, and then how to display that state

[BigBobbas]

The code block wasn’t rendering properly in the docs, I’ve edited now and it should appear below the text_sensor: example From: smartlivenet ***@***.***> Sent: 22 February 2025 15:00 To: BigBobbas/ESP32-S3-Box3-Custom-ESPHome ***@***.***> Cc: BigBobbas ***@***.***>; Mention ***@***.***> Subject: Re: [BigBobbas/ESP32-S3-Box3-Custom-ESPHome] TESTERS REQUIRED - ESPHome 2025.2.x - removed esp ADF Components (Discussion #128) On question to the text sensor part. I've added the text sensor. Now i would like to add the print part. This parts need to be added manually as there is no copy paste of an example possible or is this part already in the code? I can't find this part. — Reply to this email directly, view it on GitHub <#128 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD4EBKNBVUCMLIK5YHNF4Q32RCGGXAVCNFSM6AAAAABXSL4TNSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRYGYZTQMI> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/BD4EBKLUJMLKYXEOICW4G3L2RCGGXA5CNFSM6AAAAABXSL4TNSWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAXN422.gif> Message ID: ***@***.*** ***@***.***> >

[smartmatic]

Sorry for my deleted post. After my posting i understood the code and deleted the post. However thank you for the update docs. Now code rendered correctly.

One question: Where i struggle a little bit is to find the right position for the icons. Is there a trick to determine the position easily?

[smartmatic]

You mention in the docs in the touch section this:
"It is important whne defining touch areas that the co-ordintates don't overlap as this will result in 2 buttons being pressed simultaneously."

This means in a consequence when adding a text sensor with his own print i need to delete the original print in the lights page section?
For example this line for the case i have defined a new print changing the colors of the first defined light?

it.printf(20, 75, id(icon_font_80), light_blue,"\U000F0335");

[BigBobbas]

so yes, if that is the location of the light you wish to change then you would add the lines with the 2 colours and the if statement and overwrite that line.

With regards to your previous question.
The screen is 320 pixels accross and 240 pixels from top to bottom.
for example the line in your comment above will start drawing on the dispay at the 20th pixel from the left (x axis) and the 75th pixel from the top (y axis) and the coordinates are always x,y , you also have to take into account the size of the font.

[jantznick]

Add me to the list of people that got this up and running. Took a bit because I'm running HA docker so I had to make a new container for esphome and the directions were slightly different. Might look at adding to them for us docker folks.

Off to set up a second one now...

[BigBobbas]

Hi, glad you managed to get up and running. With regards to docker installs , unfortunatley I have zero knowledge of using docker. I did link to the ESPHome docs in the readme here >>> https://github.com/BigBobbas/ESP32-S3-Box3-Custom-ESPHome/blob/main/README.md#requirements for those that wish to use ESPHome in docker. But without the knowledge myself I wouldn't be able to write further instructions and don't have the time to do so.

Cheers
Rob

If anyone would like to elaborate and write a more detailed guide for setup with Docker, contributions are always welcomed. 👍

[pinelesss]

Hi BigBobbas.
thank you for your hard work!
I use version: "2025.02.01". Yellow errors occur during compilation:
i2s_audio (#warning "This set of I2S APIs has been deprecated),
i2s_audio_mcrophone (#warning "This set of I2S APIs has been deprecated),
i2s_audio_speaker (#warning "This set of I2S APIs has been deprecated),
streaming_model (from src/esphome/components/micro_wake_word/streaming_model.h:7:
/data/cache/platformio/packages/toolchain-xtensa-esp32s3/xtensa-esp32s3-elf/include/c++/12.2.0/type_traits:757:5: note: declared here
757 | is_pod), adc_sensor ("legacy adc calibration driver is deprecated, please migrate to use esp_adc/adc_cali.h and esp_adc/adc_cali_scheme.h").

logs_esp32-s3box-3_run.txt
After compilation, S32-S3-Box3 starts and accepts commands, but then resets itself, and so on.

[BigBobbas]

Hi there, the yellow warning can be ignored these are just warnings, and shouldn't be the cause of any issues.

If you have wake sound switched on, could you try switching it off and see if you still experience restarts.
This is a known issue and I am currrently working to resolve this

Cheers
Rob

[pinelesss]

hello, thank you very much for your quick response.

As you wrote, after turning off "wake sound" the problem with restarting disappeared.
I found another problem regarding sending sound from Music Assistant, the sound quality e.g. from Spotify is tragic, there are interferences. If I play the radio directly from Media with Home Assistant, it is ok. I think it may be a Music Assistant problem

[TheSerapher]

Finally got around to test this new version - it was quite some effort since I took the idea of "make it your own" quite literal and had removed a lot of things I didn't need and added even more stuff. Took a while to get the yaml back on track with your upstream version.

After quite some trial and error I got everything to compile. Besides a couple of deprecation warnings it worked fine and flashed my device, no issues so far.

[BigBobbas]

update configs to fix wake sound causing restarts - feedback welcomed.

please note:-
This will not be the final update and will not be the version that is merged to main branch. This is currently purley for testing.

[badnetmask]

I would like to report that the updates are partially working for me. However I'm not sure where the problem is.

I have a highly customized version of your project, so instead of a copy and paste, I looked at the branch diff and applied the necessary changes.

A few things are happening:

1 - At the beginning of the build process, I see an error. It builds and runs fine, but I'm not sure what this could cause in the future.

INFO ESPHome 2025.2.0
INFO Reading configuration custom.yaml...
WARNING GPIO46 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO45 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Generating C++ source...

2 - Sometimes I say "Hey Jarvis" and the device thinks that was the question (I can see "Hey Jarvis?" on the screen), so it responds with "I can't understand the question". Trying again a couple of times makes it listen and it works just fine.

3 - I saw a couple of random crashes, a few seconds after I got a response, the screen goes to the idle page, then blinks orange, and I see this in the log:

[22:48:30][D][voice_assistant:642]: Event Type: 12
[22:48:30][D][voice_assistant:809]: STT by VAD end
[22:48:30][D][voice_assistant:505]: State changed from STREAMING_MICROPHONE to STOP_MICROPHONE
[22:48:30][D][voice_assistant:512]: Desired state set to AWAITING_RESPONSE
[22:48:30][D][voice_assistant:505]: State changed from STOP_MICROPHONE to STOPPING_MICROPHONE
[22:48:31][D][voice_assistant:642]: Event Type: 0
[22:48:31][E][voice_assistant:777]: Error: stt-no-text-recognized - No text recognized
[22:48:31][D][voice_assistant:624]: Signaling stop...
[22:48:31][D][voice_assistant:505]: State changed from STOPPING_MICROPHONE to STOP_MICROPHONE
[22:48:31][D][voice_assistant:512]: Desired state set to IDLE
[22:48:31][D][voice_assistant:505]: State changed from STOP_MICROPHONE to IDLE
[22:48:31][D][voice_assistant:642]: Event Type: 2
[22:48:31][D][voice_assistant:736]: Assist Pipeline ended
[22:48:31][D][micro_wake_word:399]: Resetting buffers and probabilities
[22:48:31][D][micro_wake_word:194]: State changed from IDLE to START_MICROPHONE
[22:48:31][W][micro_wake_word:173]: Wake word is already running
[22:48:31][D][micro_wake_word:107]: Starting Microphone

Let me know if you need further information.

Thank you.

[BigBobbas]

I will be uploading a new test version hopefully this morning... it is not complete as the timer function is not playing repeated audio on timer finishing, when used with "home assistant" wake word but works fine with "on device"

Hopefully this will sort the errors/crashing that have been reported.

I will look more into this when I return home next friday/saturday

As always , thank you for your feedback and continued support

Rob

[BigBobbas]

now uploaded

[RunningDroid]

I tested the dev config on my no-sensors variant briefly and it was throwing vague errors when I told MusicAssistant to play music on it:

[03:16:42][D][media_player:073]: 'Mini VA' - Setting
[03:16:42][D][media_player:080]:   Media URL: http://192.168.4.148:8097/single/media_player.mini_va_mini_va/8156b56b054b4dd4bc0c7a42da29ff43.flac
[03:16:42][D][speaker_media_player:420]: State changed to PLAYING
[03:16:42][D][ring_buffer:034][ann_read]: Created ring buffer with size 40000
[03:16:42][D][speaker_media_player.pipeline:114]: Reading FLAC file type
[03:16:44][D][ring_buffer:034]: Created ring buffer with size 19200
[03:16:44][D][speaker_media_player.pipeline:124]: Decoded audio has 2 channels, 48000 Hz sample rate, and 16 bits per sample
[03:16:44][D][ring_buffer:034][speaker_task]: Created ring buffer with size 9600
[03:16:44][D][speaker_mixer:306]: Starting speaker mixer
[03:16:44][D][speaker_mixer:314]: Started speaker mixer
[03:16:44][D][i2s_audio.speaker:111]: Starting Speaker
[03:16:44][D][i2s_audio.speaker:129]: Stopped Speaker
[03:16:44][W][i2s_audio.speaker:143]: Error writing to I2S: ESP_ERR_INVALID_STATE
[03:16:44][D][ring_buffer:034][speaker_task]: Created ring buffer with size 9600
[03:16:44][D][i2s_audio.speaker:111]: Starting Speaker
[03:16:44][D][i2s_audio.speaker:129]: Stopped Speaker
[03:16:44][W][i2s_audio.speaker:143]: Error writing to I2S: ESP_ERR_INVALID_STATE
[03:16:44][D][ring_buffer:034][speaker_task]: Created ring buffer with size 9600
[03:16:44][D][i2s_audio.speaker:111]: Starting Speaker
[03:16:44][D][i2s_audio.speaker:129]: Stopped Speaker
[03:16:44][W][i2s_audio.speaker:143]: Error writing to I2S: ESP_ERR_INVALID_STATE
[03:16:44][D][ring_buffer:034][speaker_task]: Created ring buffer with size 9600
[03:16:44][D][i2s_audio.speaker:111]: Starting Speaker
[03:16:44][D][i2s_audio.speaker:129]: Stopped Speaker

[BigBobbas]

There is still some work to do with the media player. I am away on vacation currently so may not get chance until I return next weekend

[RunningDroid]

No problem, I just wanted to make sure you're aware

[Taomyn]

Hi, I thought I would try to see if I could get this working on my non-sensor version and I've had success in getting it to compile and upload with ESPHome v2025.7.2 and the one thing I mostly use, voice, isn't completely working - it wakes, makes a sound then immediately stops listening. There could be more not working, but I've not go that far in setting things up. My latest attempt was merging some later changes I saw in a some pulls into the latest s3b_no_sensor.yaml but it's still not working. But at least it compiles. Any ideas?

s3b_no_sensor.yaml.txt

This was from an earlier log, not sure if it shows what's happening:

logs_esb3-0b7374_run.txt

I'm happy to try out any later code.

[BigBobbas]

if it wakes then stops , it sounds like it isn't talking to HA ... try deleting from the HA integration (not device builder) The device should then be automatically detected , re-add. if it doesnt detect then re-power the S3 and it should.

[Taomyn]

Strange, I do see much logging on the HA side when I check the device, but when I get home later I'll try what you suggest.

[Taomyn]

So I did as you suggested, after deleting it from the HA integration it popped back up as available very quickly but I left it for a few minutes to allow HA to catch up on the deletion. I added it back and it still behaves the same. I did discover that by muting the wake sound I also see the sad-face screen then it's back to the main screen, whereas before the happy-face appears and almost immediately it's back to the main screen again. Not sure what that means.

I then enabled very_verbose logging in case that shows anything new:
logs_esb3-0b7374_run.txt

[Taomyn]

Just tried to rebuild after upgrading to ESPHome 2025.8.0 and it fails:

Compiling .pioenvs/esb3-0b7374/components/esp-tflite-micro/tensorflow/lite/micro/recording_micro_allocator.cc.o
xtensa-esp-elf-g++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
*** [.pioenvs/esb3-0b7374/src/main.cpp.o] Error 1

logs_esb3-0b7374_run.txt

[Taomyn]

Looks like 2025.8.1 fixed the problem as it compiles fully now - won't be able to test the result until later.