FullyKiosk media player entity stays in state 'playing' forever

[bcutter]

The problem

Once the media player entity switches to playing, it keeps that state like forever. That's a problem as it is used massively for notifications (so no one is clicking "stop" regularly) and therefore renders the usage of the media player entity a bit useless.

In detail: once the media player entity switches to playing, it won't resume from that state until

• a) HA has been restarted
• b) the integration has been reloaded
• c) the stop button has been pressed

What version of Home Assistant Core has the issue?

core-2022.9.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

fully_kiosk

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

https://github.com/cgarwood/homeassistant-fullykiosk/issues/118#issuecomment-1336502513

[home-assistant[bot]]

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

Code owner commands

Code owners of fully_kiosk can trigger bot actions by commenting:

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

_{^{(message by CodeOwnersMention)}}

---

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

[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.

[bcutter]

No one ever took a look at this in 3 months.

So let's keep this open and wait another 3 months. Thanks bot.

[TheAlphaLaw]

No one ever took a look at this in 3 months.

So let's keep this open and wait another 3 months. Thanks bot.

I am seeing the same issue here.

[mheath]

While FKB has an API to play sound media, it does not have an API to say if it has finished. Given the limitations of the FKB API, I don't see a way to resolve this issue.

[erkr]

Same issue, will ask FKB support to extend the API 🤞

[bcutter]

Same issue, will ask FKB support to extend the API 🤞

Thank you. Feel free to link it here.

[erkr]

I sent an email, but will report back on their response

[erkr]

Hi @mheath, @bcutter

In got a response from FKB support. Please help me with an answer, as this is bestond my knowledge:

Hello Eric,

without knowing anything about HA I could read this on one of the threads:

> While FKB has an API to play sound media, it does not have an API to say if it has finished.

Which Fully Kiosk API is used exactly to play sound media?

Alexey

--
Fully Kiosk Solutions for Android
https://www.fully-kiosk.com

[mheath]

We use the REST API /?cmd=playSound.

[erkr]

Forwarded you answer. Thanks!

[erkr]

@mheath got this answer. Sounds promising:

Hello Eric,

adding these information to the cmd=getDeviceInfo&type=json REST API was not a big deal. You can test or let the developers test with the latest beta version.

https://www.fully-kiosk.com/files/2023/05/Fully-Kiosk-Browser-v1.51-beta-1.apk

The new fields are audioVolumes and soundUrlPlaying

Alexey 

[mheath]

Thanks for reaching out to Fully Kiosk @erkr. Very cool that they're so responsive. Adding soundUrlPlaying to device info should make fixing this issue fairly simple.

Adding MQTT events for sound start/stop will allow us to make the media control more responsive for those with MQTT enabled. (There are already MQTT volume events.)

[TheAlphaLaw]

Thanks for reaching out to Fully Kiosk @erkr. Very cool that they're so responsive. Adding soundUrlPlaying to device info should make fixing this issue fairly simple.

Adding MQTT events for sound start/stop will allow us to make the media control more responsive for those with MQTT enabled. (There are already MQTT volume events.)

I have MQTT enabled but can't figure out how to send media to any device with Fully Kiosk. I'm able to use the media player through home assistant, but it can have a major delay. Any tips on how to config?

[kernelpanic85]

I'm also having this issue. Did Fully Kiosk implement the change needed? Does the HA side just need an update at this point?

[mheath]

The HA side still needs to be updated to see when the media has stopped playing, volume, and MQTT support still hasn't been added. There aren't any MQTT features in FKB that will significantly help with the media player.

I don't think the changes we talked about previously will fix the "major delay" issue.

[erkr]

@mheath thanks for the heads up. Looking forward to have the stopped playing and volume added👍

[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.

[kernelpanic85]

Still an issue for sure. Anybody have luck looking into this?

[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.

[bcutter]

https://github.com/home-assistant/core/issues/83261#issuecomment-1803843506

[erkr]

Still the case

[sophof]

It sounds like @mheath knows how to fix this, is that correct? Reading this back (as I just ran into this issue) it appears that is what everyone assumes at least? If not I could try digging in (but I'd rather not)

[cgarwood]

There is a PR open to fix, just waiting for review: https://github.com/home-assistant/core/pull/105762

[erkr]

Great, thanks! I really hope it gets merged in soon😊

[bcutter]

Great! Hopefully https://github.com/home-assistant/core/pull/105762 will make it to a stable release soon. Really looking forward to read about this in the release notes :-)

[erkr]

@cgarwood thanks for picking this up and looking forward to have it released 😊