Bonjour,
Sur mon profil utilisateur , j’ai un message d’erreur lorsque je veux visualiser le flux vidéo de ma sonnette. Sur n’importe quel autre profil le flux fonctionne.
Sur mon profil voici le message :
Quelqu’un pourrait il me dire vers quoi m’orienter pour résoudre mon problème.
Merci d’avance
System Information
| version |
core-2025.12.5 |
| installation_type |
Home Assistant OS |
| dev |
false |
| hassio |
true |
| docker |
true |
| container_arch |
amd64 |
| user |
root |
| virtualenv |
false |
| python_version |
3.13.9 |
| os_name |
Linux |
| os_version |
6.12.51-haos |
| arch |
x86_64 |
| timezone |
Europe/Paris |
| config_dir |
/config |
Home Assistant Community Store
| GitHub API |
ok |
| GitHub Content |
ok |
| GitHub Web |
ok |
| HACS Data |
ok |
| GitHub API Calls Remaining |
5000 |
| Installed Version |
2.0.5 |
| Stage |
running |
| Available Repositories |
2500 |
| Downloaded Repositories |
11 |
Home Assistant Cloud
| logged_in |
true |
| subscription_expiration |
6 novembre 2026 à 01:00 |
| relayer_connected |
true |
| relayer_region |
eu-central-1 |
| remote_enabled |
true |
| remote_connected |
true |
| alexa_enabled |
true |
| google_enabled |
true |
| cloud_ice_servers_enabled |
true |
| remote_server |
eu-central-1-29.ui.nabu.casa |
| certificate_status |
ready |
| instance_id |
6a61d3ea779a433989d6aa5ec6a7db89 |
| can_reach_cert_server |
ok |
| can_reach_cloud_auth |
ok |
| can_reach_cloud |
ok |
Home Assistant Supervisor
| host_os |
Home Assistant OS 16.3 |
| update_channel |
stable |
| supervisor_version |
supervisor-2025.12.3 |
| agent_version |
1.7.2 |
| docker_version |
28.3.3 |
| disk_total |
58.0 GB |
| disk_used |
11.2 GB |
| nameservers |
8.8.4.4, 8.8.8.8, 192.168.1.1 |
| healthy |
true |
| supported |
true |
| host_connectivity |
true |
| supervisor_connectivity |
true |
| ntp_synchronized |
true |
| virtualization |
|
| board |
generic-x86-64 |
| supervisor_api |
ok |
| version_api |
ok |
| installed_addons |
Zigbee2MQTT (2.7.2-1), go2rtc (1.9.13), Get HACS (1.3.1), Mosquitto broker (6.5.2), Node-RED (20.2.4), Music Assistant (2.7.2), File editor (5.8.0), Domovra (1.4.2), IAction (1.8), IAction (1.8), Z-Wave JS (0.27.0) |
Dashboards
| dashboards |
5 |
| resources |
9 |
| views |
9 |
| mode |
storage |
Network Configuration
| adapters |
lo (disabled), enp2s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth092435d (disabled), veth9d453a7 (disabled), veth2213a27 (disabled), veth29065e1 (disabled), veth5501ec3 (disabled), vetha000461 (disabled), veth1e7302c (disabled), veth7c8203e (disabled), vethab5bd9e (disabled) |
| ipv4_addresses |
lo (127.0.0.1/8), enp2s0 (192.168.1.50/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth092435d (), veth9d453a7 (), veth2213a27 (), veth29065e1 (), veth5501ec3 (), vetha000461 (), veth1e7302c (), veth7c8203e (), vethab5bd9e () |
| ipv6_addresses |
lo (::1/128), enp2s0 (fe80::d368:32e5:f2c2:544a/64), docker0 (fe80::78da:9dff:fe8f:6261/64), hassio (fe80::a49d:85ff:feb0:1ada/64), veth092435d (fe80::14a5:5cff:fe36:fe01/64), veth9d453a7 (fe80::1856:64ff:fe22:a4cb/64), veth2213a27 (fe80::a027:21ff:fe49:b7be/64), veth29065e1 (fe80::e46e:83ff:fe1d:b5d8/64), veth5501ec3 (fe80::c8e8:a0ff:fe3e:23b2/64), vetha000461 (fe80::208f:22ff:fea0:60b2/64), veth1e7302c (fe80::ccdb:f2ff:fe6e:583/64), veth7c8203e (fe80::8415:22ff:fedf:746a/64), vethab5bd9e (fe80::1028:bcff:fe19:8d/64) |
| announce_addresses |
192.168.1.50, fe80::d368:32e5:f2c2:544a |
Recorder
| oldest_recorder_run |
21 décembre 2025 à 08:46 |
| current_recorder_run |
2 janvier 2026 à 18:33 |
| estimated_db_size |
52.73 MiB |
| database_engine |
sqlite |
| database_version |
3.49.2 |
Spotify
| api_endpoint_reachable |
ok |
Réponse trouvé à mon problème. Bug sur Android, en baissant la résolution cela fonctionne de nouveau
