# Interrogations sur Matter et IPV6

**URL:** <https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134>\
**Category:** Configuration\
**Tags:** matter\
**Created:** [Mars 14, 2026, 10:47 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134 "2026-03-14T10:47:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\
**Post date:** [Mars 14, 2026, 10:47 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/1 "2026-03-14T10:47:17Z")

</div>

Hello,

je me pose quelques questions sur l’intégration Matter et la détection de l’IPV6 dans Gladys.  
Il y a quelques temps de cela, j’ai modifié mon réseau interne et après de mauvaises manip, j’ai dû désactiver le forward de l’IPV6 du wan vers le lan.  
Donc je n’ai plus que de l’IPV6 interne (fe80:: ).  
Ce qui a amené une erreur dans Gladys car on vérifie si l’IPV6 est une IP externe ou non :

 ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/e/9/e9f6dc9dc69383d5a8e8cce4a6abc1f71dba20d2.png)

Et depuis ce jour je n’accède plus à mes appareils Matter, ni même à matterbridge ☹  
Mais c’est uniquement avec Gladys que je n’ai plus d’accès car après quelques tests sur Apple Maison, Homey Self Hosted et HA, ça fonctionnait très bien : tout était reconnu, visible et fonctionnel.

En regardant la doc de matterbridge, j’ai vu ceci :

 ![IMG_9133](https://gladys-assistant-community.b-cdn.net/uploads/default/original/3X/9/7/97c8ca419c18021c3cd9eecce57a3ebb0f164542.jpeg)  
A l’époque des tests, j’avais remarqué que si Gladys et matterbridge n’avait pas la même configuration IPv6 (les 2 devaient être en interne et externe mais pas l’un interne et l’autre externe), il avait été décidé de bloquer les IPv6 interne sur Gladys. Je me rends compte que ce n’était pas une si bonne idée 🙄

@pierre-gilles penses-tu que l’on puisse «&nbsp;réactiver&nbsp;» l’IPv6 interne sur Gladys ?  
Je suis dispo pour les tests 😉

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Mars 16, 2026, 1:03 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/2 "2026-03-16T13:03:31Z")

</div>

Salut @mutmut 🙂

Gladys n’active rien de particulier et ne gère pas directement la configuration réseau. Tout ce qui concerne IPv6 dépend uniquement de ta machine et de ta configuration réseau. De son côté, Gladys se contente simplement d’afficher un message selon qu’il détecte ou non une adresse IPv6.

Du coup, ce message est purement informatif, et les modifications qu’on avait faites ne changent pas vraiment la situation dans ce cas 😅

J’espère que c’est plus clair ! N’hésite pas si quelque chose n’est pas évident.

---

<div class="post-metadata">

**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\
**Post date:** [Mars 16, 2026, 2:25 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/3 "2026-03-16T14:25:23Z")

</div>

> [@pierre-gilles](#):
>
> J’espère que c’est plus clair !

argh, malheureusement oui c’est plus clair et j’ai un problème avec l’intégration Matter alors 😩

Alors voici ce que j’ai :

- je ne vois plus mon matterbridge dans l’interface de configuration Matter
- j’ai toujours mes appareils issus des matterbridge mais non pilotables
- j’ajoute des appareils matter over wifi mais rien n’apparaît dans la configuration matter
- je rajouté ces mêmes appareils une seconde fois et Gladys me dit qu’ils sont déjà associés mais je les vois pas.

Tu aurais une idée par hasard pour orienter mes recherches de solutions car là je sais plus quoi faire si ce n’est pas le réseau ?

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Mars 16, 2026, 2:30 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/4 "2026-03-16T14:30:25Z")

</div>

Par hasard tu n’as pas d’erreurs dans les logs de Gladys liée à Matter ?

---

<div class="post-metadata">

**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\
**Post date:** [Mars 16, 2026, 3:57 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/5 "2026-03-16T15:57:19Z")

</div>

j’ai trouv&é pas mal d’occurence de ça :

```plaintext
2026-03-16T16:46:03+0100 <warn> errorMiddleware.js:68 (errorMiddleware) CachedClientNodeStore unavailable due to initialization error
      at crashedError (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:605:32)
      at handleRejection (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:312:69)
    Caused by: (ValidationOutOfBoundsError/135) EndpointNumber must be between 0 and 0xFFFE, got NaN
      at EndpointNumber (/src/server/services/matter/node_modules/@matter/types/src/datatype/EndpointNumber.ts:23:11)
      at CachedClientNodeStore.#loadEndpointStore (/src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:52:32)
      at /src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:46:28

```

et quand j’ai voulu ajouter mon appareil (déjà ajouté mais non visible), j’ai eu ça :

```plaintext
2026-03-16T16:47:08+0100 <info> matter.pairDevice.js:38 (MatterHandler.pairDevice) Commissioning device with options: {"commissioning":{"regulatoryLocation":0,"regulatoryCountryCode":"XX","regulatoryLocationType":0},"discovery":{"identifierData":{"shortDiscriminator":5},"discoveryCapabilities":{"ble":false}},"passcode":38085971,"commissioningTimeoutSeconds":90,"commissioningAttempts":4,"commissioningRetryDelayMs":1000}
2026-03-16 16:47:10.750 ERROR Controller~missioner Commissioning step 11.1: OperationalCredentials.Certificates failed with error: Commission error: This device is already commissioned into this fabric. You can not commission it again. ... Aborting commissioning
2026-03-16T16:47:10+0100 <error> matter.pairDevice.js:50 (MatterHandler.pairDevice) Error commissioning device: Error: Commission error: This device is already commissioned into this fabric. You can not commission it again.

```

Avec une désactivation de Matter et activation :

```plaintext
2026-03-15T22:57:20+0100 <info> index.js:36 (Object.stop) Stopping Matter service
2026-03-15T22:57:22+0100 <info> index.js:18 (Object.start) Starting Matter service
2026-03-15T22:57:22+0100 <info> index.js:24 (Object.start) Matter is enabled, starting...
2026-03-15T22:57:22+0100 <info> matter.init.js:20 (MatterHandler.init) Matter.init: storagePath: /var/lib/gladysassistant/matter
2026-03-15 22:57:22.632 WARN Commission~ontroller BLE is not supported on this platform
2026-03-15T22:58:05+0100 <warn> service.start.js:44 (Service.start) Unable to start service matter CachedClientNodeStore unavailable due to initialization error
      at crashedError (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:605:32)
      at handleRejection (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:312:69)
    Caused by: (ValidationOutOfBoundsError/135) EndpointNumber must be between 0 and 0xFFFE, got NaN
      at EndpointNumber (/src/server/services/matter/node_modules/@matter/types/src/datatype/EndpointNumber.ts:23:11)
      at CachedClientNodeStore.#loadEndpointStore (/src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:52:32)
      at /src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:46:28
2026-03-15T22:58:05+0100 <warn> errorMiddleware.js:68 (errorMiddleware) CachedClientNodeStore unavailable due to initialization error
      at crashedError (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:605:32)
      at handleRejection (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:312:69)
    Caused by: (ValidationOutOfBoundsError/135) EndpointNumber must be between 0 and 0xFFFE, got Na
      at EndpointNumber (/src/server/services/matter/node_modules/@matter/types/src/datatype/EndpointNumber.ts:23:11)
      at CachedClientNodeStore.#loadEndpointStore (/src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:52:32)
      at /src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:46:28
2026-03-15T22:58:05+0100 <warn> errorMiddleware.js:68 (errorMiddleware) CachedClientNodeStore unavailable due to initialization error
      at crashedError (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:605:32)
      at handleRejection (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:312:69)
    Caused by: (ValidationOutOfBoundsError/135) EndpointNumber must be between 0 and 0xFFFE, got NaN
      at EndpointNumber (/src/server/services/matter/node_modules/@matter/types/src/datatype/EndpointNumber.ts:23:11)
      at CachedClientNodeStore.#loadEndpointStore (/src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:52:32)
      at /src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:46:28
2026-03-15T22:58:06+0100 <warn> errorMiddleware.js:68 (errorMiddleware) CachedClientNodeStore unavailable due to initialization error
      at crashedError (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:605:32)
      at handleRejection (/src/server/services/matter/node_modules/@matter/general/src/util/Construction.ts:312:69)
    Caused by: (ValidationOutOfBoundsError/135) EndpointNumber must be between 0 and 0xFFFE, got NaN
      at EndpointNumber (/src/server/services/matter/node_modules/@matter/types/src/datatype/EndpointNumber.ts:23:11)
      at CachedClientNodeStore.#loadEndpointStore (/src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:52:32)
      at /src/server/services/matter/node_modules/@project-chip/matter.js/src/device/CachedClientNodeStore.ts:46:28

```

---

<div class="post-metadata">

**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\
**Post date:** [Mars 16, 2026, 4:03 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/6 "2026-03-16T16:03:23Z")

</div>

Ok, le souci est assez clair, il y a un bug dans la librairie matter-js qu’on utilise, l’erreur c’est `CachedClientNodeStore unavailable due to initialization error` dû à `EndpointNumber must be between 0 and 0xFFFE, got NaN`

Pour info, je travaille sur la mise à jour de cette dépendance car tu n’es pas le seul à avoir des problèmes !

> <https://github.com/GladysAssistant/Gladys/pull/2429>
>
> \### Pull Request check-list
> 
> To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items:
> 
> \- \[\] If your changes affect the code, did you write the tests?
> \- \[\] Are tests passing? (\`npm test\` on both front/server)
> \- \[\] Is the linter passing? (\`npm run eslint\` on both front/server)
> \- \[\] Did you run prettier? (\`npm run prettier\` on both front/server)
> \- \[\] If you are adding a new feature/service, did you run the integration comparator? (\`npm run compare-translations\` on front)
> \- \[\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[forum\](https://community.gladysassistant.com/)) for testing before merging.
> \- \[\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code)
> \- \[\] If you are adding a new features/services which needs explanation, did you modify the user documentation? See \[the GitHub repo\](https://github.com/GladysAssistant/v4-website) and the \[website\](https://gladysassistant.com).
> \- \[\] Did you add fake requests data for the demo mode (\`front/src/config/demo.js\`) so that the demo website is working without a backend? (if needed) See \[https://demo.gladysassistant.com\](https://demo.gladysassistant.com).
> 
> NOTE: these things are not required to open a PR and can be done afterwards / while the PR is open.
> 
> \### Description of change
> 
> Please provide a description of the change here. It's always best with screenshots, so don't hesitate to add some!
> 
> 
> 
> \## Summary by CodeRabbit
> 
> \* \*\*Chores\*\*
> \* Bumped Matter dependencies to v0.16.9 for improved compatibility and stability.
> 
> \* \*\*Refactor\*\*
> \* Device handling now uses accessor-based APIs and stricter device-data validation for more robust behavior.
> 
> \* \*\*Bug Fixes / Improvements\*\*
> \* More reliable state reporting for sensors and actuators (color, power, energy, temperature, humidity, occupancy, window covering, levels) with improved unit handling and conversions.

Je rencontre quelques soucis dû à des changements breakings dans la librairie, mais rien d’insurmontable 😉

Je te tiens au courant dès que j’ai une version testable !

---

<div class="post-metadata">

**Author:** ![mutmut](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/mutmut/32/14064_2.png) [@mutmut](https://community.gladysassistant.com/u/mutmut)\
**Post date:** [Mars 16, 2026, 4:20 UTC](https://community.gladysassistant.com/t/interrogations-sur-matter-et-ipv6/10134/7 "2026-03-16T16:20:14Z")

</div>

top, merci @pierre-gilles !

Pour info j’ai un Gladys de test qui a un autre matterbridge de visible dans la configuration et je peux piloter mes volets somfy.  
La différence est que sur ma plateforme de test, tout est en docker sur le même host (même IP partout), alors que pour ma prod, j’ai Gladys sur une IP et matterbridge sur une autre.