in progress binary sensor...

[RaceNJason]

With the latest home assistant core update, my ATOM Echo voice assistant now shows this notification:

This stops working in version 2025.4. Please address before upgrading.

The ESPHome in progress binary sensor binary_sensor.atom_echo_master_bedroom_assist_in_progress is deprecated.

Migrate your configuration to use the corresponding assist_satellite entity and then click SUBMIT to disable the in progress binary sensor and fix this issue.

[daknightuk]

I have exactly the same issue, not sure whether to disable the in progress binary sensor or not?

[RaceNJason]

I would not click the 'SUBMIT' button just yet. Prefer to wait to see this fixed (in which case the message may go away on it's own). Sounds like if it isn't fixed and you click on it, it could do more than just ignore the warning (like ignore in_progress messages thinking assist_satellite messages are now coming in)??

[sanderlv]

I have the same error. Even after updating to the latest template.

https://github.com/esphome/media-players/blob/main/m5stack/m5stack-atom-echo.yaml

[dane-io]

I also have this error with a custom S3 config.

[tduzzi]

I too have this error M5Atom Echo

[Powerbless]

Same error

[Menz01]

same issue here

[jparchem]

Also same issue with both my Atom M3 Echo, VoIP, S3 Box and Wyoming satellites. The error message itself is included in a release notes screenshot: https://www.home-assistant.io/blog/2024/10/02/release-202410/#the-source-of-a-repair

[Wummeke]

I had the same issue with my RaspiAudio Muse Luxe. I solved it by removing the voice-assistant: component from my ESPHome configuration. I don't really use it to be fair. After OTA-updating my ESPHome device and a repair in Home-Assistant, the warning was gone.

If you do want to use the assistant functionality, you might wanna have a look at these configurations: https://github.com/esphome/firmware/tree/main/voice-assistant I'm not sure if those configs solve the issue, to be honest. I did try them at first, but before I got to checking the warning in Home-Assistant, I saw all kinds of buffer errors in the ESPHome Logs and (for me the most important reason) the media-player functionality of my Muse Luxe was gone.

[Nismonx]

Same here, Updating to 2024.9.2 via ESPhome seems to fix the issue.

[jmcbri]

Same here, Updating to 2024.9.2 via ESPhome seems to fix the issue.

Thanks. How do you do thank? I puttered around in various places in gui and didn't see an option. Command line?

[tduzzi]

That did not work for me as I am currently running 2024.9.2 and still have this warning:

Todd

On Saturday, October 5, 2024 at 12:05:01 PM EDT, James McBride ***@***.***> wrote:   

Same here, Updating to 2024.9.2 via ESPhome seems to fix the issue.

Thanks. How do you do thank? I puttered around in various places in gui and didn't see an option. Command line?

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

[kevvar]

When you click on 'Submit', it fixes the issue. It disables the binary sensor, and it automatically creates the assist satellite entity.

[ericvb]

When you click on 'Submit', it fixes the issue. It disables the binary sensor, and it automatically creates the assist satellite entity.

The explanatory text is then very unhappily worded : Migrate your configuration to use the corresponding assist_satellite entity and then click SUBMIT to disable the in progress binary sensor and fix this issue. ???

[kevvar]

Yes you are right.

[OzGav]

I tentatively clicked on SUBMIT and yes issue fixed for me. I also think the text should be Migrate your configuration to use the corresponding assist_satellite entity and disable the in progress binary sensor by clicking SUBMIT to fix this issue.

[deejay1]

unfortunately there is no documentation on how to migrate the config

[OzGav]

@deejay1 as explained above just click submit

[weboide]

It's also tracked in https://github.com/esphome/wake-word-voice-assistants/issues/26

[jlpouffier]

There is no config to migrate ;)

The repair is just here because you could be using the binary_sensor assist_in_progress to automate or display something in your dashboards.

If you are NOT using the binary_sensor assist_in_progress, then simply click SUBMIT on the repair. We will disable the binary_sensor assist_in_progress for you.

If you ARE using the binary_sensor assist_in_progress, then there is a new kid on the block called the assist_satelitte entity.

The assist_satelitte is great because it retains all the functionally of the old binary_sensor, and then add on top more data.

When the binary_sensor was simply

• on (When something was happening)
• off.

The assist_satelitte has now 4 states

• idle
• listening
• processing
• responding

So you can do (Automate or display things) more, and more granularly.

By the way, if you still need a binary indication that something is happening (For example, I do - I display a very small badge in my dashboard when one of my voice assistant is active), then you can easily recreate the binary_sensor with a template.

Just go to Settings > Devices and Services > Helpers > Create Helper > Template > Binary Sensor. Here is the template

{{states('assist_satellite.s3box_chambre') in ['listening','responding','processing'] }}

✌🏻 JLo