Announcements to resume previous playback after chime finishes on Google Cast

[SCBionicle]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

When using the announce feature, previous playback doesn't resume on the Google Nest Hub.

Describe the solution you'd like

It would be awesome if Chime could resume the previous playback on the Nest Hub after the announcement is finished.

Describe alternatives you've considered

I'm not exactly sure what this field means. But, it might be worth mentioning, that the google cast integration does hold the tokens, urls, media types, application, seek position, etc in the device attributes during playback.

Additional context

No response

[SixFive7]

If need be I can easily test any solution for this. Just let me know!

[nimroddolev]

Hi @SCBionicle and @SixFive7.
I don't own a Google Nest Hub so I can't do any testing on my end. Could you please provide me with debug logs in order to help me understand what's going on?

To enable debug logs:

1. Turn on debug logging:

   action: logger.set_level
   data:
     custom_components.chime_tts: debug
   

2. Call the chime_tts.say action again.

3. Check your log messages in Home Assistant:

   https://{YOUR_HOME_ASSISTANT_ADDRESS}:8123/config/logs?filter=chime_tts
   

   and click LOAD FULL LOGS

[nimroddolev]

Hi @SCBionicle and @SixFive7. Is this issue still relevant or can I close this ticket?

[SCBionicle]

I apologize, I completely forgot I posted this ticket. I moved to using Music Assistant to process Chime TTS announcements because Chime TTS does not resume previous playback on either the Spotify Player or the default media player.

[SCBionicle]

It's the end of the day over here right now, so I can explore getting those logs to you tomorrow, if that works.

[nimroddolev]

Hi @SCBionicle. No problem, please reply when you've had a chance 👍

With respect to the issue you're having with the resuming of playback after the announcement: have you read the documentation for the announce parameter? It should allow for the previously playing audio to resume after the announcement.

If you are still experiencing the issue, please provide me with your debug log messages. Without them I have no way of knowing what it going on behind the scenes on your end and can't help you further.

[SCBionicle]

I'll attach the debug logs here.

Player Device: Google Nest Hub 1st Gen
Home Assistant Hardware: Hyper-V x86_64 6GB 4 Core Home Assistant OS v12.0 Core v2024.9.3
Chime TTS: v1.1.4
filtered Chime TTS Debug.txt (Default media player playing locally based video)

[SCBionicle]

Some observations I noticed with the Google Nest Hub in Google Cast when using the Default Media Player (which Chime uses):

Entity State changes to Idle under the following conditions:

• Playback of current track ends (default media player doesn't support enqueuing) (This is distinct from the app being turned off, device gets the Entity State, off, when the app disconnects and the device returns to the default photo frame)
• Playback gets stuck buffering (Entity State doesn't switch to Buffering for some reason)

[Burbacottero]

News about this? I'm facing the same problem

[Burbacottero]

I apologize, I completely forgot I posted this ticket. I moved to using Music Assistant to process Chime TTS announcements because Chime TTS does not resume previous playback on either the Spotify Player or the default media player.

How do you did that?

[SCBionicle]

I apologize, I completely forgot I posted this ticket. I moved to using Music Assistant to process Chime TTS announcements because Chime TTS does not resume previous playback on either the Spotify Player or the default media player.

How do you did that?

I set up the music assistant server add-on and its corresponding integration.