Non détection "Home-Assistant-Matter-Hub" par ALEXA => Pas de réponse mDNS

Bonjour à tous,

j’espère que vous avez bien été gaté par le père Noël cette année encore :slight_smile:

Mon problème

*Je viens de créer chez ma belle mère une Bridge Matter en utilisant ce dépôt Home-Assistant-Matter-Hub - Home-Assistant-Matter-Hub. Pas de soucis à la création, le bridge découvre bien via l’auto refresh les entités que j’ai déclaré avec le label alexa, bref jusque là pas de soucis.

Le problème est qu’Alexa ne détecte pas mon Hub Matter, du coup après avoir scanné le QR code il me demande de mettre mon hub matter en mode Appairage et fini par dire qu’il n’a pas trouvé l’appareil. Je pense donc qu’il y a un soucis avec la config réseau.

Concernant la config, dans les grandes lignes, ma belle mère a une Livebox 5, HomeAssistant installé sur un PC proxmox via une VM (script de la communauté), l’accès réseau se fait en local en http:\192.168.1.10:8123 et l’accès extérieur se fait via NGINX Proxy Manager via Wildcard du type https:\ha.NomDeDomaine.duckdns.org

  • Le PC proxmox est connecté en RJ45 à la livebox en direct à l’adresse 192.168.1.2 avec Home Assistant dessus en 192.168.1.10 ainsi que NPM en Add-on de HA.
  • L’enceinte AMAZON ECHO Dot Gen 5 est connecté en WIFI sur la bande 5GHz à l’adresse IP 192.168.1.15
  • Mon PC portable est en Windows 11 connecté en WIFI sur la bande 5GHz à l’adresse 192.168.1.18

Voilà ce que j’ai déjà vérifié depuis mon PC Windows :

PS C:\WINDOWS\system32> ping 192.168.1.10

Envoi d’une requête 'Ping'  192.168.1.10 avec 32 octets de données :
Réponse de 192.168.1.10 : octets=32 temps=5 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=5 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=5 ms TTL=64
Réponse de 192.168.1.10 : octets=32 temps=5 ms TTL=64

Statistiques Ping pour 192.168.1.10:
    Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
    Minimum = 5ms, Maximum = 5ms, Moyenne = 5ms


PS C:\WINDOWS\system32> Test-NetConnection 192.168.1.10 -Port 8123


ComputerName     : 192.168.1.10
RemoteAddress    : 192.168.1.10
RemotePort       : 8123
InterfaceAlias   : Wi-Fi
SourceAddress    : 192.168.1.18
TcpTestSucceeded : True




PS C:\WINDOWS\system32> Test-NetConnection 192.168.1.10 -Port 5540
AVERTISSEMENT : TCP connect to (192.168.1.10 : 5540) failed


ComputerName           : 192.168.1.10
RemoteAddress          : 192.168.1.10
RemotePort             : 5540
InterfaceAlias         : Wi-Fi
SourceAddress          : 192.168.1.18
PingSucceeded          : True
PingReplyDetails (RTT) : 4 ms
TcpTestSucceeded       : False

Voilà ce que donne WireShark lorsque je scanne le QR-CODE via l’application ALEXA jusqu’à ce qu’ALEXA indique qu’il ne trouve pas. En gros personne ne répond j’ai l’impression à la requête « Où es-tu ? »

Voici le log de l’Add-On de matter depuis son démarrage jusqu’à l’échec d’appairage de l’appli ALEXA. On voit visiblement qu’il reçoit les requêtes mais visiblement ne répond pas à ALEXA car non visible dans WireShark.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Home-Assistant-Matter-Hub
 Publish your entities from Home Assistant to any Matter-compatible controller like Alexa, Apple Home or Google Home.
-----------------------------------------------------------
 Add-on version: 3.0.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 16.3  (amd64 / qemux86-64)
 Home Assistant Core: 2025.12.4
 Home Assistant Supervisor: 2025.12.3
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2025-12-28 23:19:37.611 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2025-12-28 23:19:37.623 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2025-12-28 23:19:37.626 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: 0.0.0.0:5353
2025-12-28 23:19:37.629 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5353 localAddress: :::5353
2025-12-28 23:19:37.682 INFO   HomeAssistantClient  Waiting for Home Assistant to be up and running - the application will be available once a connection to Home Assistant could be established.
2025-12-28 23:19:42.689 DEBUG  HomeAssistantClient  Got an update from Home Assistant. System state is 'RUNNING'.
2025-12-28 23:19:42.690 INFO   HomeAssistantClient  Home assistant reported to be up and running
2025-12-28 23:19:42.761 INFO   ServerNodeStore      Opened 284da16b31f94ec0b303605a20e1a99a storage at /config/data/284da16b31f94ec0b303605a20e1a99a
2025-12-28 23:19:42.765 DEBUG  Crypto               Using Node.js crypto implementation for 284da16b31f94ec0b303605a20e1a99a
2025-12-28 23:19:42.966 INFO   BaseEventStore       Loaded volatile event store with next number 5001
2025-12-28 23:19:43.000 INFO   Endpoint             284da16b31f94ec0b303605a20e1a99a ready endpoint#: 0 type: RootNode (0x16) behaviors: 💤parts ✓index ✓basicInformation ✓accessControl ✓groupKeyManagement ✓generalCommissioning ✓administratorCommissioning ✓operationalCredentials ✓generalDiagnostics ✓commissioning ✓network 💤productDescription 💤subscription 💤sessions ✓events 💤controller ✓descriptor
2025-12-28 23:19:43.010 INFO   Endpoint             284da16b31f94ec0b303605a20e1a99a.aggregator ready endpoint#: 1 type: Aggregator (0xe) behaviors: 💤parts ✓index ✓descriptor
2025-12-28 23:19:43.062 DEBUG  WindowCoveringServer Operational status changed to {"global":0,"lift":0,"tilt":"undefined"} with new global status undefined
2025-12-28 23:19:43.064 DEBUG  WindowCoveringServer Syncing lift position 100.00 to 100%
2025-12-28 23:19:43.130 INFO   Endpoint             284da16b31f94ec0b303605a20e1a99a.aggregator.cover_tous_les_volets ready endpoint#: 3 type: WindowCovering (0x202) behaviors: ✓identify ✓bridgedDeviceBasicInformation ✓homeAssistantEntity ✓windowCovering ✓descriptor
2025-12-28 23:19:43.147 DEBUG  WindowCoveringServer Operational status changed to {"global":0,"lift":0,"tilt":"undefined"} with new global status undefined
2025-12-28 23:19:43.148 DEBUG  WindowCoveringServer Syncing lift position 100.00 to 100%
2025-12-28 23:19:43.212 INFO   Endpoint             284da16b31f94ec0b303605a20e1a99a.aggregator.cover_shelly_voletsalon ready endpoint#: 6 type: WindowCovering (0x202) behaviors: ✓identify ✓bridgedDeviceBasicInformation ✓homeAssistantEntity ✓windowCovering ✓descriptor
2025-12-28 23:19:43.227 DEBUG  WindowCoveringServer Operational status changed to {"global":0,"lift":0,"tilt":"undefined"} with new global status undefined
2025-12-28 23:19:43.228 DEBUG  WindowCoveringServer Syncing lift position 100.00 to 100%
2025-12-28 23:19:43.294 INFO   Endpoint             284da16b31f94ec0b303605a20e1a99a.aggregator.cover_shelly_voletterrasse ready endpoint#: 5 type: WindowCovering (0x202) behaviors: ✓identify ✓bridgedDeviceBasicInformation ✓homeAssistantEntity ✓windowCovering ✓descriptor
2025-12-28 23:19:43.299 NOTICE Node                 284da16b31f94ec0b303605a20e1a99a going online
2025-12-28 23:19:43.302 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5540 localAddress: :::5540
2025-12-28 23:19:43.304 DEBUG  NodejsChannel        Socket created and bound remoteAddress: undefined:5540 localAddress: 0.0.0.0:5540
2025-12-28 23:19:43.312 NOTICE Node                 284da16b31f94ec0b303605a20e1a99a is online
2025-12-28 23:19:43.314 DEBUG  OccurrenceManager    Recorded event #5001: {"eventId":0,"clusterId":40,"endpointId":0,"priority":2,"epochTimestamp":1766960383313,"payload":{"softwareVersion":2025}}
2025-12-28 23:19:43.317 DEBUG  OccurrenceManager    Recorded event #5002: {"eventId":3,"clusterId":51,"endpointId":0,"priority":2,"epochTimestamp":1766960383317,"payload":{"bootReason":0}}
2025-12-28 23:19:43.369 INFO   WebApi               HTTP server (API & Web App) listening on port 64344
2025-12-28 23:21:37.584 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/ 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.606 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/index-CwXqCCpI.css 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.609 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/index-BAxKd4Jc.js 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.902 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/vitesse-light-CVO1_9PV.js 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.903 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/vitesse-dark-D0r3Knsf.js 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.907 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/javascript-ySlJ1b_l.js 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.963 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/roboto-latin-400-normal-CNwBRw8h.woff2 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.965 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/roboto-latin-500-normal-CkrA1NAy.woff2 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:37.982 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges?_s=1766960497805 200 OK from ::ffff:172.30.32.2
2025-12-28 23:21:44.829 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/assets/roboto-latin-700-normal-CXeAXeti.woff2 304 Not Modified from ::ffff:172.30.32.2
2025-12-28 23:21:44.869 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:21:44.888 INFO   CertificateAuthority Loaded stored credentials with ID 0
2025-12-28 23:21:44.890 DEBUG  MdnsScanner          MDNS Scanner started listening for MDNS messages
2025-12-28 23:21:44.890 INFO   MdnsScanner          MDNS Scan targets updated : commissionable = true Targets: 
2025-12-28 23:21:54.850 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:22:04.847 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:22:14.857 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:22:24.861 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:22:34.857 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:22:44.855 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:22:54.864 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2
2025-12-28 23:23:04.866 DEBUG  WebApi / Access Log  GET /api/hassio_ingress/Z3Xr6Z3on9RLb-RILH5xhSc96fn3FxwI8d2lohO887E/api/matter/bridges/284da16b31f94ec0b303605a20e1a99a/devices 200 OK from ::ffff:172.30.32.2

System Information

version core-2025.12.4
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 2501
Downloaded Repositories 6
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 16.3
update_channel stable
supervisor_version supervisor-2025.12.3
agent_version 1.7.2
docker_version 28.3.3
disk_total 30.8 GB
disk_used 15.5 GB
nameservers 192.168.1.1, 2a01:cb10:93f3:d800:12e9:92ff:fe0f:fab0, fe80::12e9:92ff:fe0f:fab0
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 File editor (5.8.0), Samba share (12.5.4), InfluxDB (5.0.2), Grafana (12.1.0), Home Assistant Google Drive Backup (0.112.1), Nginx Proxy Manager (2.1.0), MariaDB (2.7.2), Mosquitto broker (6.5.2), Zigbee2MQTT (2.7.1-1), Duck DNS (1.26.0), Home-Assistant-Matter-Hub (3.0.3), Terminal & SSH (9.21.0)
Dashboards
dashboards 2
resources 4
views 6
mode storage
Network Configuration
adapters lo (disabled), enp0s18 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethaac57f5 (disabled), veth3f9eb1d (disabled), vethad2cabf (disabled), veth0552ef2 (disabled), vethd9ef986 (disabled), vethde61f3b (disabled), veth4978bf7 (disabled), veth6c63576 (disabled), veth42cb43c (disabled), veth3b15ef3 (disabled), vethfd8232d (disabled), vethb8a24c1 (disabled), veth573143b (disabled), vethdcd85f1 (disabled), veth2e1269a (disabled)
ipv4_addresses lo (127.0.0.1/8), enp0s18 (192.168.1.10/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethaac57f5 (), veth3f9eb1d (), vethad2cabf (), veth0552ef2 (), vethd9ef986 (), vethde61f3b (), veth4978bf7 (), veth6c63576 (), veth42cb43c (), veth3b15ef3 (), vethfd8232d (), vethb8a24c1 (), veth573143b (), vethdcd85f1 (), veth2e1269a ()
ipv6_addresses lo (::1/128), enp0s18 (2a01:cb10:93f3:d800:f63f:1316:b3d0:9cdf/64, fe80::dccd:e0d3:5ec9:e62c/64), hassio (fe80::3072:a8ff:fec0:f9f3/64), docker0 (fe80::38bf:6fff:fe58:8a8b/64), vethaac57f5 (fe80::f074:62ff:fe60:3b3e/64), veth3f9eb1d (fe80::2c1f:9eff:fe1a:8f4b/64), vethad2cabf (fe80::9cb4:aeff:fe85:8c62/64), veth0552ef2 (fe80::ac88:6aff:fe1b:346f/64), vethd9ef986 (fe80::a00d:91ff:fe30:38ec/64), vethde61f3b (fe80::74fe:e9ff:fe17:c68e/64), veth4978bf7 (fe80::7c34:76ff:fe79:190f/64), veth6c63576 (fe80::9c09:c4ff:fe2a:3345/64), veth42cb43c (fe80::7860:aeff:fed6:5924/64), veth3b15ef3 (fe80::b4dd:bcff:fe41:7db8/64), vethfd8232d (fe80::106a:d2ff:feb9:e8b0/64), vethb8a24c1 (fe80::60dc:25ff:fe3a:838/64), veth573143b (fe80::80f7:afff:fef4:2de/64), vethdcd85f1 (fe80::e028:5eff:fecf:548/64), veth2e1269a (fe80::e3:e4ff:fec7:940b/64)
announce_addresses 192.168.1.10, 2a01:cb10:93f3:d800:f63f:1316:b3d0:9cdf, fe80::dccd:e0d3:5ec9:e62c
Recorder
oldest_recorder_run 29 octobre 2025 à 19:34
current_recorder_run 28 décembre 2025 à 12:10
estimated_db_size 238.07 MiB
database_engine sqlite
database_version 3.49.2

Je me répond à moi-même en espérant que cela aidera quelqu’un un jour.

il fallait déclarer l’interface réseau dans la config de l’Add-on car visiblement il n’y arrivait pas seul. Suite à cette modification et a un redémarrage complet, l’appairage a fonctionné du premier coup :

L’interface était listée dans la description de ma configuration Home Assistant :

1 « J'aime »

Ce sujet a été automatiquement fermé après 2 jours. Aucune réponse n’est permise dorénavant.