search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
4.85k stars 966 forks source link

Multi media progress bar and time remaining updates on volume changes #3462

Closed d13g0m0nt3s closed 3 months ago

d13g0m0nt3s commented 3 months ago

Describe the issue you are experiencing

Hi, I found some strange behavior, when I change the volume up and down, the progress bars of the media player resets… can’t find why. I tried with the default media player, mini media player and with a custom progress bar

If i turn the volume up or down, the progress bar reset and the remaining time increase.

I can only try with home pods and I do know if happened with other devices but happends with home pod second gen and home pod minis

What operating system image do you use?

rpi4-64 (Raspberry Pi 4/400 64-bit OS)

What version of Home Assistant Operating System is installed?

6.6.31-haos-raspi

Did the problem occur after upgrading the Operating System?

No

Hardware details

Home Assistant Supervisor

Host operating system | Home Assistant OS 12.4 -- | -- Update channel | stable Supervisor version | supervisor-2024.06.2 Agent version | 1.6.0 Docker version | 26.1.4 Disk total | 219.4 GB Disk used | 12.9 GB Saludable | true Soportado | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization |   Placa | rpi4-64 API del Supervisor | ok Versión de la API | ok Installed add-ons | File editor (5.8.0), Advanced SSH & Web Terminal (18.0.0), Cloudflared (5.1.14), Mosquitto broker (6.4.1), Govee to MQTT Bridge (2024.04.29-30cf7732), HassOS I2C Configurator (0.14), ArgonOne Active Cooling (30a), Home Assistant Google Drive Backup (0.112.1), Samba NAS (12.2.0-nas2) ### Steps to reproduce the issue 1. Play something in any media player 2. Turn up or down the volume during playback 3. See the progress bar move down and the remaining time change. 4. Repeat from step 2 and you will see the progress bar move ... ### Anything in the Supervisor logs that might be useful for us? ```txt 2024-07-07 09:23:59.302 INFO (MainThread) [supervisor.api.middleware.security] /backups access from cebe7a76_hassio_google_drive_backup 2024-07-07 09:38:45.498 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running 2024-07-07 09:38:45.499 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system 2024-07-07 09:38:45.501 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system 2024-07-07 09:38:45.501 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server 2024-07-07 09:38:45.587 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core 2024-07-07 09:38:45.590 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system 2024-07-07 09:38:45.590 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system 2024-07-07 09:38:45.591 INFO (MainThread) [supervisor.resolution.checks.base] Run check for disabled_data_disk/system 2024-07-07 09:38:45.591 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_server 2024-07-07 09:38:45.592 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addon 2024-07-07 09:38:45.594 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisor 2024-07-07 09:38:45.609 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/system 2024-07-07 09:38:45.609 INFO (MainThread) [supervisor.resolution.check] System checks complete 2024-07-07 09:38:45.609 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state running 2024-07-07 09:38:45.824 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete 2024-07-07 09:38:45.825 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state running 2024-07-07 09:38:45.825 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete 2024-07-07 09:42:29.079 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2024-07-07 10:12:29.395 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token 2024-07-07 10:37:46.173 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json 2024-07-07 10:38:45.827 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state running 2024-07-07 10:38:45.827 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/system 2024-07-07 10:38:45.829 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/system 2024-07-07 10:38:45.830 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_server 2024-07-07 10:38:45.831 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/core 2024-07-07 10:38:45.834 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/system 2024-07-07 10:38:45.834 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/system ``` ### Anything in the Host logs that might be useful for us? ```txt 2024-07-07 02:17:42.001 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-9241ddfbe9e93f5015ffad2ab6e7e3faac06263d4cdb406e972d1b0deb88d11d-runc.M3UvTX.mount: Deactivated successfully. 2024-07-07 02:36:48.840 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-9241ddfbe9e93f5015ffad2ab6e7e3faac06263d4cdb406e972d1b0deb88d11d-runc.TBTgky.mount: Deactivated successfully. 2024-07-07 02:59:49.459 homeassistant kernel: audit: type=1334 audit(1720321189.454:2893): prog-id=1357 op=LOAD 2024-07-07 02:59:49.459 homeassistant kernel: audit: type=1334 audit(1720321189.454:2894): prog-id=1358 op=LOAD 2024-07-07 02:59:49.459 homeassistant kernel: audit: type=1334 audit(1720321189.454:2895): prog-id=1359 op=LOAD 2024-07-07 02:59:49.488 homeassistant systemd[1]: Starting Hostname Service... 2024-07-07 02:59:49.865 homeassistant systemd[1]: Started Hostname Service. 2024-07-07 02:59:49.887 homeassistant kernel: audit: type=1334 audit(1720321189.882:2896): prog-id=1360 op=LOAD 2024-07-07 02:59:49.887 homeassistant kernel: audit: type=1334 audit(1720321189.882:2897): prog-id=1361 op=LOAD 2024-07-07 02:59:49.887 homeassistant kernel: audit: type=1334 audit(1720321189.882:2898): prog-id=1362 op=LOAD 2024-07-07 02:59:49.913 homeassistant systemd[1]: Starting Time & Date Service... 2024-07-07 02:59:50.249 homeassistant systemd[1]: Started Time & Date Service. 2024-07-07 03:00:19.902 homeassistant systemd[1]: systemd-hostnamed.service: Deactivated successfully. 2024-07-07 03:00:20.023 homeassistant kernel: audit: type=1334 audit(1720321220.017:2899): prog-id=1359 op=UNLOAD 2024-07-07 03:00:20.023 homeassistant kernel: audit: type=1334 audit(1720321220.017:2900): prog-id=1358 op=UNLOAD 2024-07-07 03:00:20.023 homeassistant kernel: audit: type=1334 audit(1720321220.017:2901): prog-id=1357 op=UNLOAD 2024-07-07 03:00:20.290 homeassistant systemd[1]: systemd-timedated.service: Deactivated successfully. 2024-07-07 03:00:20.307 homeassistant kernel: audit: type=1334 audit(1720321220.301:2902): prog-id=1362 op=UNLOAD 2024-07-07 03:00:20.307 homeassistant kernel: audit: type=1334 audit(1720321220.301:2903): prog-id=1361 op=UNLOAD 2024-07-07 03:00:20.307 homeassistant kernel: audit: type=1334 audit(1720321220.301:2904): prog-id=1360 op=UNLOAD 2024-07-07 03:05:29.275 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-9241ddfbe9e93f5015ffad2ab6e7e3faac06263d4cdb406e972d1b0deb88d11d-runc.1Ph2Bc.mount: Deactivated successfully. 2024-07-07 03:07:30.006 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-9241ddfbe9e93f5015ffad2ab6e7e3faac06263d4cdb406e972d1b0deb88d11d-runc.oNGltD.mount: Deactivated successfully. 2024-07-07 04:07:05.760 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-883e7946de7a21cc9bf92c3126862212cf75806681ae521ebac6e6a1b3a3d94f-runc.RSGS9x.mount: Deactivated successfully. 2024-07-07 04:29:10.823 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-883e7946de7a21cc9bf92c3126862212cf75806681ae521ebac6e6a1b3a3d94f-runc.yJglbE.mount: Deactivated successfully. 2024-07-07 05:06:30.695 homeassistant kernel: audit: type=1334 audit(1720328790.690:2905): prog-id=1363 op=LOAD 2024-07-07 05:06:30.695 homeassistant kernel: audit: type=1334 audit(1720328790.694:2906): prog-id=1364 ``` ### System information Versión | core-2024.7.1 -- | -- Installation type | Home Assistant OS Desarrollo | false Supervisor | true Docker | true Usuario | root Virtual environment | false Python version | 3.12.4 Operating system family | Linux Operating system version | 6.6.31-haos-raspi CPU architecture | aarch64 Zona horaria | Europe/Madrid Configuration directory | /config ### Additional information _No response_
github-actions[bot] commented 3 months ago

:wave: @d13g0m0nt3s, thanks for reporting an issue!

It looks like this issue is related to Home Assistant Core. Please check the Home Assistant Core repository, the issue might have been reported already. Open a new issue in that repository if you can't find a matching issue.