Auto play not consistently working with fullykiosk

[Daniel-dev22]

Checklist:

• Please try updating to the latest available version.
• Please try clearing your browser cache.

[REQUIRED] Card diagnostic information:

card_version: 6.5.1
browser: >-
  Mozilla/5.0 (Linux; Android 15; SM-S938U1 Build/AP3A.240905.015.A2; wv)
  AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/132.0.6834.166
  Mobile Safari/537.36 Home Assistant/2025.1.2-14946 (Android 15; SM-S938U1)
date: 2025-02-22T20:31:22.258Z
lang: en
timezone: America/New_York
git:
  hash: 43947b4
  build_date: Sun, 02 Feb 2025 00:09:40 GMT
  commit_date: Sat, 1 Feb 2025 16:08:32 -0800
ha_version: 2025.2.4
custom_integrations:
  frigate:
    detected: true
    version: 5.8.0
    devices:
      121894675fc2447d4c58c7cbe23d8009: 5.8.0/0.16.0-0083d09
  hass_web_proxy:
    detected: false
config:
  type: custom:frigate-card
  cameras_global:
    live_provider: go2rtc
    go2rtc:
      modes:
        - webrtc
  cameras:
    - camera_entity: camera.birdseye
  live:
    auto_play:
      - visible
    auto_pause:
      - hidden
  menu:
    buttons:
      frigate:
        enabled: true

[REQUIRED] Description of problem:

[OPTIONAL] Last working release (if known):

I tried both latest and 6.5.1 and still have an issue with auto play not working all the time with fully kiosk on my galaxy tab s7.

This diagnostic isn't from that device but that's where I notice this issue.

I notice because the tablet is on all the time and the screen turns off/on via an automation. Sometimes when the screen turns on the stream starts right away other times it's stuck on paused from when the screen was off. The fact it pauses when the screen is off is great but when I turn it on and the stream is visible I would hope that it would start playing immediately.

Previously I used webrtc card with the config optionintersection 0.75 and never had this issue. I also used Birdseye and the stream was also webrtc and used go2rtc from frigate.

[OPTIONAL] Javascript errors shown in the web inspector:

[OPTIONAL] Additional information:

Interestingly I see a resource for both frigate card loaded and one for advanced camera card it seems that sometimes I noticed the card using latest version when it starts up and shows the version for a second and other times the older version. Not sure if that's related and if I should remove that frigate card resource

[tinimark]

I'm also having the exact same issue with a very similar setup with card version 7.1.0

[github-actions]

🎉 This issue has been resolved in version 7.3.2 🎉

See: GitHub release

[Daniel-dev22]

I don't think this fixed the issue I see the fully kiosk tablets are using the new version but I still have to tap the play button once to start playing on initial page load. Then it works for awhile and stops requiring pressing the play button again.

Should I open a new issue or can we reopen this? @dermotduffy

@tinimark are you seeing improvement on your end?

[dermotduffy]

@Daniel-dev22 We can re-open. Perhaps it's a different issue entirely.

One caution: Please make sure you only have a single reference to advanced-camera-card (and not frigate-hass-card) in your dashboard resources, I've had a few people struggle to get fixes to work and it turns out they were importing old code, see Steps 1-3:

https://card.camera/#/troubleshooting?id=duplicate-versions-duplicate-element-registrations-custom-element-not-found-advanced-camera-card

[Daniel-dev22]

@Daniel-dev22 We can re-open. Perhaps it's a different issue entirely.

One caution: Please make sure you only have a single reference to advanced-camera-card (and not frigate-hass-card) in your dashboard resources, I've had a few people struggle to get fixes to work and it turns out they were importing old code, see Steps 1-3:

https://card.camera/#/troubleshooting?id=duplicate-versions-duplicate-element-registrations-custom-element-not-found-advanced-camera-card

Yep I only have the advanced camera card enabled I removed the frigate card resource. when I load the page I see the version flash of 7.3.5

[dermotduffy]

@Daniel-dev22 Thanks. What's the most reliable way you've found to reproduce this? Does it only happen in fullykiosk?

[Daniel-dev22]

I only really use the auto play on my Samsung tablets running fully kiosk. I'll have to monitor this on my phone to see how it behaves.

They are running android 13. Fully kiosk is using
Chrome 129.0.668.81

My phone for context is also android. It's the S25 ultra running android 15 so that would provide another comparison for browser/os differences.

Chrome 133.0.6943.137

[tinimark]

I don't think this fixed the issue I see the fully kiosk tablets are using the new version but I still have to tap the play button once to start playing on initial page load. Then it works for awhile and stops requiring pressing the play button again.

Should I open a new issue or can we reopen this? @dermotduffy

@tinimark are you seeing improvement on your end?

I would definitely say it's improved. It works fine 90% of the time but every now and again a stream refuses to load or the stream freezes. I found things got better by scheduling the tablet to reboot every morning and also switching to webview canary (in play store) helped. Hard to troubleshoot this when it's intermittent and there's so many variables in the settings to experiment with.
I wonder if there's a more efficient way to send the stream to the tablet other than using kiosk.

[Daniel-dev22]

I don't think this fixed the issue I see the fully kiosk tablets are using the new version but I still have to tap the play button once to start playing on initial page load. Then it works for awhile and stops requiring pressing the play button again.
Should I open a new issue or can we reopen this? @dermotduffy
@tinimark are you seeing improvement on your end?

I would definitely say it's improved. It works fine 90% of the time but every now and again a stream refuses to load or the stream freezes. I found things got better by scheduling the tablet to reboot every morning and also switching to webview canary (in play store) helped. Hard to troubleshoot this when it's intermittent and there's so many variables in the settings to experiment with. I wonder if there's a more efficient way to send the stream to the tablet other than using kiosk.

Can you post your frigate card diagnostics? Curious about your device/Chrome version.

[tinimark]

Can you post your frigate card diagnostics? Curious about your device/Chrome version.

I'd be more than happy to do so if you can let me know where to find them (on the tablet itself)?

[Daniel-dev22]

Can you post your frigate card diagnostics? Curious about your device/Chrome version.

I'd be more than happy to do so if you can let me know where to find them (on the tablet itself)?

From the GitHub issue template.

On the card, hold down the Iris (default) menu button for a few seconds then paste the diagnostics *between* the pair of triple backticks below. No help can be provided without this.

[tinimark]

[Daniel-dev22]

I think this would rule out it being a Chrome version or android issue then. Will monitor how it works for me on android 15 with my phone just to be sure.

@tinimark did auto play on visible ever work for you without issues?

[tinimark]

There have always been issues going back a couple of years of doing this via various methods. I will say it's more stable now than ever before though and I've just installed camera card latest update to see how that goes.
I've never seen any issues when using a PC.

The way I have it setup is a fullscreen camera-card (panel mode) for each of 7 cameras on hidden tabs in HA.
When camera detects occupancy, nodered flow turns the tablet screen on via Kiosk API and then Browser_mod navigates to the tab with the relevant camera. This seems more reliable than having just one tab with trigger options configured.

One strange thing, I purchased a PoE charger for the tablet to connect it via LAN cable as I thought it might be wifi issues. With this connected and wifi turned off, the video stream always freezes after a couple of seconds even though speedtests result in a faster connection. Not sure what that's about. I'll monitor how it goes on the latest camera card version and report back in a few days.