Wyoming successfully integrates whisper, but the entity is immediately and forever unavailable

[jds11111]

The problem

I have whisper running in a docker container on another machine. The logs show only INFO:__main__:Ready. I have uninstalled and reinstalled several times. I have deleted and reinstalled the wyoming integration for whisper several times. Each time wyoming recognizes and integrates my whisper installation. However, it then immediately reports the entity as unavailable, and it never returns. I have piper running on the same machine without any integration problems.

I have set the integration to debug logs, but no error shows up. The problem showed up on the preceding HA version (2023.05) and persists after updating to the latest (2023.06).

What version of Home Assistant Core has the issue?

core-2023.6.1

What was the last working version of Home Assistant Core?

core-2023.5

What type of installation are you running?

Home Assistant Container

Integration causing the issue

wyoming

Link to integration documentation on our website

https://www.home-assistant.io/integrations/wyoming

Diagnostics information

The only entry for wyoming is to show that the integration started up.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @balloob, @synesthesiam, mind taking a look at this issue as it has been labeled with an integration (wyoming) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of wyoming can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign wyoming Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

wyoming documentation wyoming source _{^{(message by IssueLinks)}}

[guarddog13]

Having similar issue using HA Container and Whisper in Docker. It's not Unavaible though. The state shows as "Unknown."

[paulius2k]

In my HA OS installation stt.faster_whisper entity is always unknown.

[bsamarketing]

I am seeing this issue too Installation is Hassio on a Pi4

[jds11111]

I deleted everything, reinstalled the docker containers, and re-integrated in HA. It worked for a few days, and now fails again. I deleted the integration and tried to do it again, but no luck. I don't think that this thing is at all stable.

[declan-wade]

Same issue using the offical whisper add-on, HASSOS x86/x64 bare metal install. Has been like this forever, just always 'unknown'. Piper seems fine?

[extant1]

I was looking into this and the best I can tell is when piper is called through homeassistant.components.wyoming.tts.WyomingTtsProvider.async_get_tts_audio the class WyomingTtsProvider has a base class of TextToSpeechEntity from homeassistant.components.tts which bounces around a few functions but inevitably calls internal_async_get_tts_audio which updates the state.

However, when faster-whisper is called through wyoming at homeassistant.components.wyoming.stt.WyomingSttProvider.async_process_audio_stream nothing is run from the inherited class SpeechToTextEntity from homeassistant.components.stt and the function internal_async_process_audio_stream is never run so no update takes place.

[edurenye]

This is still an issue that prevents all the voice workflow from working, I would say this is a critical issue.

[koalabamu]

any updates ?

[vexter0944]

@balloob @synesthesiam - Still seeing this - exactly as op described. Running docker with latest HA. Have tried putting whisper and piper on another host running docker to make sure this was not some kind of loopback/docker networking issue. Still the same. Add the integration and boom, immediately unavailable even though it added the whisper integration.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.