Intégration Ring-MQTT

Entraide Home Assistant
, ,
1

Bonjour,

Je suis nouveau sur home asistant je profite de quelques jours pour migrer tranquillement de jeedom sur HA

Mon problème

J’ai installé l’addon ring-mqtt connexion à MQTT ok, par contre quand je la démarre j’ai ceci, auriez vous une idée

2025-02-12T16:31:47.021Z ring-mqtt MQTT connection established, processing Ring locations...
2025-02-12T16:31:49.129Z ring-mqtt WARNING - Unhandled Promise Rejection
2025-02-12T16:31:49.129Z ring-mqtt The Ring account which you used to generate a refresh token does not have any associated locations.  Please use an account that has access to at least one location.
2025-02-12T16:31:49.130Z ring-mqtt Error: The Ring account which you used to generate a refresh token does not have any associated locations.  Please use an account that has access to at least one location.

Ma configuration

System Information

version core-2025.2.2
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.73-haos
arch x86_64
timezone Europe/Paris
config_dir /config
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.2
update_channel stable
supervisor_version supervisor-2025.02.0
agent_version 1.6.0
docker_version 27.2.0
disk_total 30.8 GB
disk_used 4.5 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons Ring-MQTT with Video Streaming (5.8.0)
Dashboards
dashboards 1
resources 0
mode auto-gen
Network Configuration
adapters lo (disabled), enp0s18 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth33128af (disabled), vethf4f9a2c (disabled), vetheec5a07 (disabled), vethe0d9e9f (disabled), veth6e2a2e5 (disabled), vethe84a40a (disabled)
ipv4_addresses lo (127.0.0.1/8), enp0s18 (192.168.1.4/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth33128af (), vethf4f9a2c (), vetheec5a07 (), vethe0d9e9f (), veth6e2a2e5 (), vethe84a40a ()
ipv6_addresses lo (::1/128), enp0s18 (2a01:e0a:db8:40f0:5cb:caac:b1a4:fa4a/64, fe80::ecf4:d731:8136:69ba/64), docker0 (fe80::42:61ff:fe75:99f1/64), hassio (fe80::42:a7ff:fed3:5861/64), veth33128af (fe80::282a:1ff:feea:5c9c/64), vethf4f9a2c (fe80::e0ff:cdff:fe20:d85e/64), vetheec5a07 (fe80::e81c:caff:fe31:f136/64), vethe0d9e9f (fe80::30d0:83ff:fe3d:f438/64), veth6e2a2e5 (fe80::eccd:32ff:fe33:2bed/64), vethe84a40a (fe80::a096:20ff:fee7:d182/64)
announce_addresses 192.168.1.4, 2a01:e0a:db8:40f0:5cb:caac:b1a4:fa4a, fe80::ecf4:d731:8136:69ba
Recorder
oldest_recorder_run 11 février 2025 à 09:21
current_recorder_run 12 février 2025 à 14:39
estimated_db_size 1.17 MiB
database_engine sqlite
database_version 3.47.1

Merci

2

Salut,

Si j’en crois ce genre de message, tu n’as pas le bon compte (plusieurs ?) dans la config

3

Malheureusement, j’ai essayé avec les 2 comptes dont le propriétaire et j’ai toujours le même résultat, bizarrre