Connexion à Matterbridge

J’ai fait un test avec un plugin SMAPPEE (ma borne de recharge de voiture electrique), mais je ne sais pas si je dois parler de mon résultat au plugin ou ici ^^

En fait le plugin a bien été créé, je l’ai bien installé dans matterbridge.
Mais lorque j’essaie de l’ajouter dans GLadys j’ai cette erreur.

Est-ce que cela vient de ma configuration ?

Salut :slight_smile: effectivement c’est ta configuration, il faut que Gladys et Matterbridge puisse se parler en ipv6 !

Pourtant cela semble bon de ce coté là..

Ok en fait j’avais 2 containers Matterbridge qui tournaient en même temps avec une concurrence de ports, ça n’aidait pas.
J’ai pu faire le ménage !

Lorsque j’ai voulu appairer mon device, seul le Matterbridge lui meme est remonté (commutateurs).
Le plugin lui ne veut toujours pas être ajouté à Gladys.

Pourtant il tourne bien coté MatterBridge

On voit que tu as un device sur le plugin mais il y a quoi dans l’onglet Devices ?
Et les logs matterbridge te racontent des choses ?

Et l’IPv6 est ok dans matterbridge (2a01:…), il faut peut-être que tu ajoutes enp0s25 dans l’interface mdns dans l’onglet Settings.

Coté Matterbridge j’ai ça :

J’ai rajouté enp0s25 dans les settings.

Les logs de Matterbridge sont ceux là :

info[14:18:13.738][InteractionServer]Invoke « @2:0•8e73⇵1978 invokes: RootNode:0x0.GeneralCommissioning:0x30.armFailSafe:0x0
info[14:18:13.739][ProtocolService]Invoke « matterbridge-ai-factory-smappee-ev-wall-home.generalCommissioning.armFailSafe @2:0•8e73⇵1978✉0e06cf91 expiryLengthSeconds: 314 breadcrumb: 1
info[14:18:13.740][ProtocolService]Invoke » matterbridge-ai-factory-smappee-ev-wall-home.generalCommissioning.armFailSafe @2:0•8e73⇵1978✉0e06cf91 errorCode: 0 debugText:
info[14:18:13.742][SystemCheck]System check succeeded
info[14:18:13.747][CaseServer]Received pairing request « udp://[fe80::5644:b10:d213:e3b5%enp0s25]:59361
notice[14:18:13.765][Matterbridge]Session opened on server node for matterbridge-ai-factory-smappee-ev-wall-home: { name: '@2:b59ba12b37d80423•8e74', nodeId: 3261996172427324781, peerNodeId: 13086230349247677475, fabric: { fabricIndex: 2, fabricId: 1, nodeId: 3261996172427324781, rootNodeId: 13086230349247677475, rootVendorId: 65521, label: '' }, isPeerActive: true, lastInteractionTimestamp: 1780237093763, lastActiveTimestamp: 1780237093763, numberOfActiveSubscriptions: 0 }
info[14:18:13.767][CaseServer]@2:b59ba12b37d80423•8e74 New session with @2:b59ba12b37d80423 2↔1 address: udp://[fe80::5644:b10:d213:e3b5%enp0s25]:59361 fabric: 7dd378d18fa83e2c (#2) SII: 500ms SAI: 300ms SAT: 4s DMRev: 19 IMRev: 13 spec: 0x1040200 maxPaths: 10 CATs:
info[14:18:13.775][InteractionServer]Invoke « @2:b59ba12b37d80423•8e74⇵197a invokes: RootNode:0x0.GeneralCommissioning:0x30.commissioningComplete:0x4
info[14:18:13.776][ProtocolService]Invoke « matterbridge-ai-factory-smappee-ev-wall-home.generalCommissioning.commissioningComplete @2:b59ba12b37d80423•8e74⇵197a✉0975e87e (no payload)
info[14:18:13.781][Session]•unsecured#86eb25f03fafc4af Session ended
info[14:18:13.787][MdnsAdvertisement]Unpublishing kind: commissionable service: mdns:EF8BCAC32661B03E._matterc._udp.local time: 1m 57s
info[14:18:13.907][Session]@2:0•8e73 Session ended
notice[14:18:13.911][Matterbridge]Server node for matterbridge-ai-factory-smappee-ev-wall-home commissioned successfully!
notice[14:18:13.913][Matterbridge]Commissioned fabric index 2 added on server node for matterbridge-ai-factory-smappee-ev-wall-home: { fabricIndex: 2, fabricId: 1, nodeId: 3261996172427324781, rootNodeId: 13086230349247677475, rootVendorId: 65521, label: '' }
info[14:18:13.914][GeneralCommissioningClusterHandler]Commissioned fabric: 7dd378d18fa83e2c (#2) node: 2d44f03c6c36ed6d
info[14:18:13.915][ProtocolService]Invoke » matterbridge-ai-factory-smappee-ev-wall-home.generalCommissioning.commissioningComplete @2:b59ba12b37d80423•8e74⇵197a✉0975e87e errorCode: 0 debugText:
info[14:18:13.935][InteractionServer]Invoke « @2:b59ba12b37d80423•8e74⇵197b invokes: RootNode:0x0.OperationalCredentials:0x3e.updateFabricLabel:0x9
info[14:18:13.936][ProtocolService]Invoke « matterbridge-ai-factory-smappee-ev-wall-home.operationalCredentials.updateFabricLabel @2:b59ba12b37d80423•8e74⇵197b✉0975e880 label: Gladys Assistant fabricIndex: 2
info[14:18:13.945][FabricAccessControl]ACL List updated privilege: 5 authMode: 2 subjects: 13086230349247677475 targets: null fabricIndex: 2
info[14:18:13.947][Transaction]Tx ◦reactor<matterbridg ... dleUpdatedFabric>#43 waiting on @2:b59ba12b37d80423•8e74⇵197b✉0975e880
info[14:18:13.948][ProtocolService]Invoke » matterbridge-ai-factory-smappee-ev-wall-home.operationalCredentials.updateFabricLabel @2:b59ba12b37d80423•8e74⇵197b✉0975e880 statusCode: 0 fabricIndex: 2
notice[14:18:13.956][Matterbridge]Commissioned fabric index 2 updated on server node for matterbridge-ai-factory-smappee-ev-wall-home: { fabricIndex: 2, fabricId: 1, nodeId: 3261996172427324781, rootNodeId: 13086230349247677475, rootVendorId: 65521, label: 'Gladys Assistant' }
info[14:18:14.339][InteractionServer]Subscribe « @2:b59ba12b37d80423•8e74⇵197d fabricFiltered attributePaths: 1 eventPaths: 1
info[14:18:14.359][InteractionServer]Subscribe successful » @2:b59ba12b37d80423•8e74⇵197d 2↔1 sub#: 5badc555 timing: 1s - 1m => 1m sendInterval: 48.1s
notice[14:18:14.365][Matterbridge]Session subscriptions changed on server node for matterbridge-ai-factory-smappee-ev-wall-home: { name: '@2:b59ba12b37d80423•8e74', nodeId: 3261996172427324781, peerNodeId: 13086230349247677475, fabric: { fabricIndex: 2, fabricId: 1, nodeId: 3261996172427324781, rootNodeId: 13086230349247677475, rootVendorId: 65521, label: '' }, isPeerActive: true, lastInteractionTimestamp: 1780237093763, lastActiveTimestamp: 1780237093763, numberOfActiveSubscriptions: 1 }
warn[14:18:20.953][ExchangeManager]Ignoring message for unknown session 8e73 from node 0000000000000000

J’ai l’impression sur ton screenshot que le plugin a son propre code Matter à ajouter à Gladys ! Pour certains types d’appareils, c’est le cas

Oui tu as raison, en fait c’est parce que pour tester j’ai passé MatterBridge du mode Bridge au mode ChildBridge.

Ceci dit dans un sens comme dans l’autre, que je mette un code d’appairage global, ou celui spécifique du plugin, le device n’est pas ajouté à Gladys.
Ce qui se passe c’est :

  • je mets le code d’appairage, je vois le spinner un quart de seconde… puis retour aux appareils (vide)
  • si je réessaie, je vois le spinner pendant un moment, puis j’ai les messages d’erreur.

Est-il possible qu’en fait l’apparaige soit fait, mais le device pas reconnu / autre subtilité ?

Il faut voir dans les logs si tu as un message spécial, après ça ressemble juste à un problème lié à ta configuration

Tu as le container Matterbridge et Gladys sur la même machine ? Ils peuvent se parler ? Network=host ?

Ben je ne trouve aucun message qui m’aide (ni qui aide Gemini).
Les 2 containers sont sur mon NUC où tourne Gladys, ils peuvent se parler oui, le network mode est le bon.

Je sèche ^^

Il me manque de l’information pour t’aider :grinning_face_with_smiling_eyes:

On voit bien ton Matterbridge connecté dans les paramètres, donc on est d’accord que l’appairage a bien marché ?

Et du coup, qu’est ce qui ne marche pas ? Quel est le symptôme ? Un message d’erreur dans l’interface ?

Coté Matter, je vois ça :

Ca me parait étrange.

Je vais donc repartir de zéro pour être à peu près certain de ce que je fais / ce que je vous dit.

Merci pour votre aide en tout cas

Je suis donc reparti de zéro, tout désactivé, tout réinitialisé.

Lorsque je remets tout en place, j’ajoute le code d’appairage dans gladys et j’obtiens ceci :

Pas de traces de mon device, qui est dans Matterbridge :

Logs Gladys :

2026-05-31T18:14:21+0200 <info> index.js:18 (Object.start) Starting Matter service
2026-05-31T18:14:21+0200 <info> index.js:24 (Object.start) Matter is enabled, starting...
2026-05-31T18:14:21+0200 <info> matter.init.js:20 (MatterHandler.init) Matter.init: storagePath: /var/lib/gladysassistant/matter
2026-05-31 18:14:21.098 WARN   BasicInfor~ionServer Using development values for some BasicInformation attributes: vendorId: 65521 vendorName: Matter.js Test Vendor productId: 32768 productName: Matter.js Test Product hardwareVersion: 0 softwareVersion: 0
2026-05-31 18:14:21.202 WARN   FabricAuthority      Using test vendor ID 0xfff1 for controller fabric
2026-05-31 18:14:21.218 WARN   Commission~ontroller BLE is not enabled on this platform
2026-05-31 18:14:21.219 NOTICE Node                  matter-controller-data going online
2026-05-31 18:14:21.232 NOTICE Node                  matter-controller-data is online
2026-05-31T18:14:21+0200 <info> matter.init.js:55 (MatterHandler.init) Matter controller started
2026-05-31T18:14:21+0200 <info> index.js:26 (Object.start) Matter started
2026-05-31T18:14:54+0200 <info> matter.pairDevice.js:38 (MatterHandler.pairDevice) Commissioning device with options: {"commissioning":{"regulatoryLocation":0,"regulatoryCountryCode":"XX","regulatoryLocationType":0},"discovery":{"identifierData":{"shortDiscriminator":4},"discoveryCapabilities":{"ble":false}},"passcode":57949520,"commissioningTimeoutSeconds":90,"commissioningAttempts":4,"commissioningRetryDelayMs":1000}

2026-05-31T18:15:24+0200 <error> matter.pairDevice.js:50 (MatterHandler.pairDevice) Error commissioning device: Error: No device discovered using identifier {"shortDiscriminator":4}! Please check that the relevant device is online.

2026-05-31T18:15:30+0200 <info> matter.reset.js:14 (MatterHandler.reset) Matter: resetting integration...
2026-05-31 18:15:30.272 NOTICE Node                  matter-controller-data going offline
2026-05-31 18:15:30.414 NOTICE Node                  matter-controller-data is offline
2026-05-31T18:15:30+0200 <info> matter.reset.js:21 (MatterHandler.reset) Matter: backup variable deleted
2026-05-31T18:15:30+0200 <info> matter.reset.js:25 (MatterHandler.reset) Matter: MATTER_ENABLED set to false
2026-05-31T18:15:30+0200 <info> matter.reset.js:30 (MatterHandler.reset) Matter: folder deleted successfully
2026-05-31T18:15:30+0200 <info> matter.reset.js:38 (MatterHandler.reset) Matter: integration reset complete

2026-05-31T18:15:53+0200 <info> system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker.
2026-05-31T18:15:53+0200 <info> checkForContainerUpdates.js:13 (MatterbridgeManager.checkForContainerUpdates) Matterbridge: Checking for current installed versions and required updates...
2026-05-31T18:15:53+0200 <info> system.isDocker.js:13 (System.isDocker) System.isDocker: This system is running inside Docker.
2026-05-31T18:15:53+0200 <info> installContainer.js:48 (MatterbridgeManager.installContainer) Matterbridge: is being installed as Docker container...
2026-05-31T18:15:53+0200 <info> installContainer.js:49 (MatterbridgeManager.installContainer) Pulling luligu/matterbridge:latest image...
2026-05-31T18:15:54+0200 <info> installContainer.js:53 (MatterbridgeManager.installContainer) Matterbridge: Preparing environment...
2026-05-31T18:15:54+0200 <info> configureContainer.js:13 (MatterbridgeManager.configureContainer) Matterbridge: Docker container is being configured...
2026-05-31T18:15:54+0200 <info> configureContainer.js:37 (MatterbridgeManager.configureContainer) Matterbridge: configuration directories created
2026-05-31T18:15:54+0200 <info> installContainer.js:56 (MatterbridgeManager.installContainer) Creation of container...
2026-05-31T18:15:54+0200 <info> installContainer.js:70 (MatterbridgeManager.installContainer) Matterbridge: successfully installed and configured as Docker container
2026-05-31T18:15:54+0200 <info> configureContainer.js:13 (MatterbridgeManager.configureContainer) Matterbridge: Docker container is being configured...
2026-05-31T18:15:54+0200 <info> configureContainer.js:37 (MatterbridgeManager.configureContainer) Matterbridge: configuration directories created
2026-05-31T18:15:54+0200 <info> installContainer.js:93 (MatterbridgeManager.installContainer) Matterbridge: container is (re)starting...
2026-05-31T18:15:59+0200 <info> installContainer.js:99 (MatterbridgeManager.installContainer) Matterbridge: container successfully started

2026-05-31T18:19:04+0200 <info> index.js:18 (Object.start) Starting Matter service
2026-05-31T18:19:04+0200 <info> index.js:24 (Object.start) Matter is enabled, starting...
2026-05-31T18:19:04+0200 <info> matter.init.js:20 (MatterHandler.init) Matter.init: storagePath: /var/lib/gladysassistant/matter
2026-05-31 18:19:04.581 WARN   BasicInfor~ionServer Using development values for some BasicInformation attributes: vendorId: 65521 vendorName: Matter.js Test Vendor productId: 32768 productName: Matter.js Test Product hardwareVersion: 0 softwareVersion: 0
2026-05-31 18:19:04.689 WARN   FabricAuthority      Using test vendor ID 0xfff1 for controller fabric
2026-05-31 18:19:04.705 WARN   Commission~ontroller BLE is not enabled on this platform
2026-05-31 18:19:04.706 NOTICE Node                  matter-controller-data going online
2026-05-31 18:19:04.717 NOTICE Node                  matter-controller-data is online
2026-05-31T18:19:04+0200 <info> matter.init.js:55 (MatterHandler.init) Matter controller started
2026-05-31T18:19:04+0200 <info> index.js:26 (Object.start) Matter started

2026-05-31T18:19:54+0200 <info> matter.pairDevice.js:38 (MatterHandler.pairDevice) Commissioning device with options: {"commissioning":{"regulatoryLocation":0,"regulatoryCountryCode":"XX","regulatoryLocationType":0},"discovery":{"identifierData":{"shortDiscriminator":2},"discoveryCapabilities":{"ble":false}},"passcode":46999621,"commissioningTimeoutSeconds":90,"commissioningAttempts":4,"commissioningRetryDelayMs":1000}
2026-05-31T18:19:56+0200 <info> matter.pairDevice.js:42 (MatterHandler.pairDevice) Successfully commissioned device with nodeId 1910614006600401468

Logs Mattebridge :

WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketConnected to WebSocket: ws://192.168.100.190:8283/
info[16:16:08.319][Frontend]WebSocketServer client "::ffff:192.168.100.191" connected to Matterbridge
info[16:16:08.585][DockerVersion]Starting docker version check...
info[16:16:08.586][DockerVersion]Docker build config: version=3.7.10 dev=false
info[16:16:08.592][CheckUpdates]Starting check updates...
info[16:16:08.908][CheckUpdates]Check updates succeeded
info[16:16:10.179][DockerVersion]Docker version check succeeded: latest=3.7.10, dev=3.8.0, current=3.7.10
info[16:16:28.783][Matterbridge]shutting down...
notice[16:16:28.784][Matterbridge]Stopping matter server nodes in bridge mode...
notice[16:16:29.787][Matterbridge]Closing Matterbridge server node
notice[16:16:29.789][Node]Matterbridge going offline
info[16:16:29.796][MdnsAdvertisement]Unpublishing kind: commissionable service: mdns:F1249CDD82661569._matterc._udp.local time: 30s
notice[16:16:29.944][Node]Matterbridge is offline
notice[16:16:29.946][Matterbridge]Server node for Matterbridge is offline
info[16:16:29.986][ServerNodeStore]Closed Matterbridge storage at /root/.matterbridge/matterstorage/Matterbridge
info[16:16:29.987][Matterbridge]Closed Matterbridge server node
notice[16:16:29.987][Matterbridge]Stopped matter server nodes
info[16:16:29.988][Matterbridge]Closing matter node storage...
info[16:16:29.988][Matterbridge]Matter node storage closed
WebSocketDisconnected from WebSocket: ws://192.168.100.190:8283/
WebSocketReconnecting (attempt 1 of 100) to WebSocket: ws://192.168.100.190:8283/
WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketWebSocket error connecting to ws://192.168.100.190:8283/
WebSocketDisconnected from WebSocket: ws://192.168.100.190:8283/
WebSocketReconnecting (attempt 2 of 100) to WebSocket: ws://192.168.100.190:8283/
WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketWebSocket error connecting to ws://192.168.100.190:8283/
WebSocketDisconnected from WebSocket: ws://192.168.100.190:8283/
WebSocketReconnecting (attempt 3 of 100) to WebSocket: ws://192.168.100.190:8283/
WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketConnected to WebSocket: ws://192.168.100.190:8283/
info[16:16:35.041][Frontend]WebSocketServer client "::ffff:192.168.100.191" connected to Matterbridge
notice[16:16:35.055][Matterbridge]Starting Matterbridge server node
notice[16:16:35.057][Matterbridge]Matterbridge bridge started successfully
notice[16:16:35.060][Node]Matterbridge going online
notice[16:16:35.104][Node]Matterbridge is online
info[16:16:35.254][MdnsAdvertisement]Publishing kind: commissionable service: mdns:4D3836E90A56CED8._matterc._udp.local
notice[16:16:35.258][Matterbridge]Server node for Matterbridge is online
notice[16:16:35.258][Matterbridge]Server node for Matterbridge is not commissioned. Pair to commission.
notice[16:16:35.259][Matterbridge]QR Code URL: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT:Y.K90AFN00EC7K2S.00
notice[16:16:35.259][Matterbridge]Manual pairing code 04307728683 discriminator 656 short discriminator 2 passcode 46999621
info[16:16:35.428][DockerVersion]Starting docker version check...
info[16:16:35.430][DockerVersion]Docker build config: version=3.7.10 dev=false
info[16:16:35.450][CheckUpdates]Starting check updates...
info[16:16:35.781][CheckUpdates]Check updates succeeded
info[16:16:36.994][DockerVersion]Docker version check succeeded: latest=3.7.10, dev=3.8.0, current=3.7.10
PluginsUploading package matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz
info[16:17:00.727][Frontend]File matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz uploaded successfully
PluginsServer response: File matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz uploaded successfully
info[16:17:00.855][SpawnCommand]Starting spawn command npm with args install -g /root/.matterbridge/uploads/matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz --omit=dev --verbose and package command install for package matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz...
spawn[16:17:00.859][Matterbridge:spawn-init]Installing matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz
spawn[16:17:01.022][Matterbridge:spawn]npm verbose cli /usr/local/bin/node /usr/local/bin/npm
spawn[16:17:01.023][Matterbridge:spawn]npm info using npm@11.13.0
spawn[16:17:01.023][Matterbridge:spawn]npm info using node@v24.16.0
spawn[16:17:01.028][Matterbridge:spawn]npm verbose title npm install /root/.matterbridge/uploads/matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz
spawn[16:17:01.028][Matterbridge:spawn]npm verbose argv "install" "--global" "/root/.matterbridge/uploads/matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz" "--omit" "dev" "--loglevel" "verbose"
spawn[16:17:01.029][Matterbridge:spawn]npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2026-05-31T16_17_00_974Z-
spawn[16:17:01.032][Matterbridge:spawn]npm verbose logfile /root/.npm/_logs/2026-05-31T16_17_00_974Z-debug-0.log
spawn[16:17:01.921][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/npm 228ms
spawn[16:17:02.015][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/node-persist-manager 170ms (cache miss)
spawn[16:17:02.020][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/node-ansi-logger 186ms (cache miss)
spawn[16:17:02.081][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/node-persist 47ms (cache miss)
spawn[16:17:02.115][Matterbridge:spawn]npm http cache node-persist-manager@https://registry.npmjs.org/node-persist-manager/-/node-persist-manager-2.0.2.tgz 0ms (cache hit)
spawn[16:17:02.118][Matterbridge:spawn]npm http cache node-ansi-logger@https://registry.npmjs.org/node-ansi-logger/-/node-ansi-logger-3.2.1.tgz 0ms (cache hit)
spawn[16:17:02.201][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/node-persist-manager/-/node-persist-manager-2.0.2.tgz 80ms (cache miss)
spawn[16:17:02.214][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/node-ansi-logger/-/node-ansi-logger-3.2.1.tgz 91ms (cache miss)
spawn[16:17:02.239][Matterbridge:spawn]npm http cache matterbridge-ai-factory-smappee-ev-wall-home@file:/root/.matterbridge/uploads/matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz 1ms (cache hit)
spawn[16:17:02.240][Matterbridge:spawn]npm http cache yocto-queue@https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz 0ms (cache hit)
spawn[16:17:02.241][Matterbridge:spawn]npm http cache p-limit@https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz 0ms (cache hit)
spawn[16:17:02.242][Matterbridge:spawn]npm http cache node-persist@https://registry.npmjs.org/node-persist/-/node-persist-4.0.4.tgz 0ms (cache hit)
spawn[16:17:02.307][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz 63ms (cache miss)
spawn[16:17:02.310][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/p-limit/-/p-limit-3.1.0.tgz 63ms (cache miss)
spawn[16:17:02.315][Matterbridge:spawn]npm http fetch GET 200 https://registry.npmjs.org/node-persist/-/node-persist-4.0.4.tgz 67ms (cache miss)
spawn[16:17:02.324][Matterbridge:spawn]added 6 packages in 1s
spawn[16:17:02.325][Matterbridge:spawn]5 packages are looking for funding
spawn[16:17:02.325][Matterbridge:spawn] run `npm fund` for details
spawn[16:17:02.328][Matterbridge:spawn]npm verbose cwd /matterbridge
spawn[16:17:02.329][Matterbridge:spawn]npm verbose os Linux 6.8.0-106-generic
spawn[16:17:02.329][Matterbridge:spawn]npm verbose node v24.16.0
spawn[16:17:02.329][Matterbridge:spawn]npm verbose npm v11.13.0
spawn[16:17:02.331][Matterbridge:spawn]npm notice
spawn[16:17:02.331][Matterbridge:spawn]npm notice New minor version of npm available! 11.13.0 -> 11.16.0
spawn[16:17:02.331][Matterbridge:spawn]npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.16.0
spawn[16:17:02.331][Matterbridge:spawn]npm notice To update run: npm install -g npm@11.16.0
spawn[16:17:02.331][Matterbridge:spawn]npm notice
spawn[16:17:02.331][Matterbridge:spawn]npm verbose exit 0
spawn[16:17:02.331][Matterbridge:spawn]npm info ok
spawn[16:17:02.406][Matterbridge:spawn-exit-success]Child process exited
spawn[16:17:02.406][Matterbridge:spawn-exit-success]Child process closed
info[16:17:02.407][SpawnCommand]Spawn command npm with args install -g /root/.matterbridge/uploads/matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz --omit=dev --verbose executed successfully
info[16:17:02.408][PluginManager]Installed package matterbridge-ai-factory-smappee-ev-wall-home from matterbridge-ai-factory-smappee-ev-wall-home-1.0.0.tgz successfully
info[16:17:02.417][PluginManager]Added plugin matterbridge-ai-factory-smappee-ev-wall-home
info[16:17:02.422][PluginManager]Loading plugin matterbridge-ai-factory-smappee-ev-wall-home type AnyPlatform
info[16:17:02.488][Matterbridge plugin for Smappee EV Wall Home (actuators, switch/sensor/electricity metering)]Initializing Smappee platform...
notice[16:17:02.490][PluginManager]Loaded plugin matterbridge-ai-factory-smappee-ev-wall-home type DynamicPlatform (entrypoint /usr/local/lib/node_modules/matterbridge-ai-factory-smappee-ev-wall-home/dist/module.js)
info[16:17:35.058][Matterbridge]Setting reachability to true for Matterbridge
info[16:18:02.353][Frontend]Saving config for plugin matterbridge-ai-factory-smappee-ev-wall-home...
info[16:18:06.555][Matterbridge]shutting down...
notice[16:18:06.557][Matterbridge]Stopping matter server nodes in bridge mode...
notice[16:18:07.560][Matterbridge]Closing Matterbridge server node
notice[16:18:07.563][Node]Matterbridge going offline
info[16:18:07.569][MdnsAdvertisement]Unpublishing kind: commissionable service: mdns:4D3836E90A56CED8._matterc._udp.local time: 1m 32s
notice[16:18:07.620][Node]Matterbridge is offline
notice[16:18:07.621][Matterbridge]Server node for Matterbridge is offline
info[16:18:07.660][ServerNodeStore]Closed Matterbridge storage at /root/.matterbridge/matterstorage/Matterbridge
info[16:18:07.660][Matterbridge]Closed Matterbridge server node
notice[16:18:07.661][Matterbridge]Stopped matter server nodes
info[16:18:07.662][Matterbridge]Closing matter node storage...
info[16:18:07.662][Matterbridge]Matter node storage closed
WebSocketDisconnected from WebSocket: ws://192.168.100.190:8283/
WebSocketReconnecting (attempt 1 of 100) to WebSocket: ws://192.168.100.190:8283/
WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketWebSocket error connecting to ws://192.168.100.190:8283/
WebSocketDisconnected from WebSocket: ws://192.168.100.190:8283/
WebSocketReconnecting (attempt 2 of 100) to WebSocket: ws://192.168.100.190:8283/
WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketWebSocket error connecting to ws://192.168.100.190:8283/
WebSocketDisconnected from WebSocket: ws://192.168.100.190:8283/
WebSocketReconnecting (attempt 3 of 100) to WebSocket: ws://192.168.100.190:8283/
WebSocketConnecting to WebSocket: ws://192.168.100.190:8283/
WebSocketConnected to WebSocket: ws://192.168.100.190:8283/
info[16:18:12.992][Frontend]WebSocketServer client "::ffff:192.168.100.191" connected to Matterbridge
info[16:18:13.252][DockerVersion]Starting docker version check...
info[16:18:13.254][DockerVersion]Docker build config: version=3.7.10 dev=false
info[16:18:13.265][CheckUpdates]Starting check updates...
info[16:18:13.662][CheckUpdates]Check updates succeeded
info[16:18:14.799][DockerVersion]Docker version check succeeded: latest=3.7.10, dev=3.8.0, current=3.7.10
info[16:18:42.801][PluginManager]Configuring plugin matterbridge-ai-factory-smappee-ev-wall-home type DynamicPlatform
info[16:18:42.815][Matterbridge plugin for Smappee EV Wall Home (actuators, switch/sensor/electricity metering)]onConfigure called
notice[16:18:42.978][PluginManager]Configured plugin matterbridge-ai-factory-smappee-ev-wall-home type DynamicPlatform
info[16:19:12.800][Matterbridge]Setting reachability to true for Matterbridge
info[16:19:54.634][PaseServer]Received pairing request « udp://[fe80::5644:b10:d213:e3b5%enp0s25]:33019
info[16:19:55.009][PaseServer]@0:0•b73a New session with udp://[fe80::5644:b10:d213:e3b5%enp0s25]:33019 3↔2
info[16:19:55.019][Session]•unsecured#9dbc9c855b26c806 Channel detached
info[16:19:55.082][InteractionServer]Invoke « @0:0•b73a⇵2c2e invokes: RootNode:0x0.GeneralCommissioning:0x30.armFailSafe:0x0
info[16:19:55.089][ProtocolService]Invoke « Matterbridge.generalCommissioning.armFailSafe @0:0•b73a⇵2c2e✉085634c7 expiryLengthSeconds: 60 breadcrumb: 1
info[16:19:55.091][ProtocolService]Invoke » Matterbridge.generalCommissioning.armFailSafe @0:0•b73a⇵2c2e✉085634c7 errorCode: 0 debugText:
info[16:19:55.112][InteractionServer]Invoke « @0:0•b73a⇵2c2f invokes: RootNode:0x0.OperationalCredentials:0x3e.certificateChainRequest:0x2
info[16:19:55.113][ProtocolService]Invoke « Matterbridge.operationalCredentials.certificateChainRequest @0:0•b73a⇵2c2f✉085634c9 certificateType: 1
info[16:19:55.149][ProtocolService]Invoke » Matterbridge.operationalCredentials.certificateChainRequest @0:0•b73a⇵2c2f✉085634c9 certificate: 308201ea3082018fa003 ... 350bd246f2fcd036ca17
info[16:19:55.163][InteractionServer]Invoke « @0:0•b73a⇵2c30 invokes: RootNode:0x0.OperationalCredentials:0x3e.certificateChainRequest:0x2
info[16:19:55.164][ProtocolService]Invoke « Matterbridge.operationalCredentials.certificateChainRequest @0:0•b73a⇵2c30✉085634cb certificateType: 2
info[16:19:55.166][ProtocolService]Invoke » Matterbridge.operationalCredentials.certificateChainRequest @0:0•b73a⇵2c30✉085634cb certificate: 308201b130820157a003 ... ca17a89212d82260057a
info[16:19:55.178][InteractionServer]Invoke « @0:0•b73a⇵2c31 invokes: RootNode:0x0.OperationalCredentials:0x3e.attestationRequest:0x0
info[16:19:55.181][ProtocolService]Invoke « Matterbridge.operationalCredentials.attestationRequest @0:0•b73a⇵2c31✉085634cd attestationNonce: 6ebf9d42bdeea854320dda1fef3e7ede7d9655b110a7944c6a16288ceb0fcd9c
info[16:19:55.184][ProtocolService]Invoke » Matterbridge.operationalCredentials.attestationRequest @0:0•b73a⇵2c31✉085634cd attestationElements: 153001eb3081e806092a ... 288ceb0fcd9c24030018 attestationSignature: de97591c7c17ffef9443 ... 155296b7bac4cc722fed
info[16:19:55.198][InteractionServer]Invoke « @0:0•b73a⇵2c32 invokes: RootNode:0x0.OperationalCredentials:0x3e.csrRequest:0x4
info[16:19:55.200][ProtocolService]Invoke « Matterbridge.operationalCredentials.csrRequest @0:0•b73a⇵2c32✉085634cf csrNonce: 32d8d5a6625daf142542b908e51a3bad935896a3de3634ae82d3683f25905949
info[16:19:55.203][ProtocolService]Invoke » Matterbridge.operationalCredentials.csrRequest @0:0•b73a⇵2c32✉085634cf nocsrElements: 153001cc3081c9307002 ... ae82d3683f2590594918 attestationSignature: 89d926851e0c827cb0bf ... 9709e2259b0cae1de7b2
info[16:19:55.217][InteractionServer]Invoke « @0:0•b73a⇵2c33 invokes: RootNode:0x0.OperationalCredentials:0x3e.addTrustedRootCertificate:0xb
info[16:19:55.219][ProtocolService]Invoke « Matterbridge.operationalCredentials.addTrustedRootCertificate @0:0•b73a⇵2c33✉085634d1 rootCaCertificate: 15300101002402013703 ... 70eb8030ea5dfe041518
info[16:19:55.245][InteractionServer]Invoke « @0:0•b73a⇵2c34 invokes: RootNode:0x0.OperationalCredentials:0x3e.addNoc:0x6
info[16:19:55.247][ProtocolService]Invoke « Matterbridge.operationalCredentials.addNoc @0:0•b73a⇵2c34✉085634d3 nocValue: 15300101022402013703 ... acc2c6687155ae383818 icacValue: ipkValue: 2cd8ef371569c5ecde4b5082d04092f4 caseAdminSubject: 11181304605732249382 adminVendorId: 65521
info[16:19:55.261][FabricAccessControl]ACL List updated
info[16:19:55.267][FabricAccessControl]ACL List updated privilege: 5 authMode: 2 subjects: 11181304605732249382 targets: null fabricIndex: 1
info[16:19:55.269][Transaction]Tx ◦reactor<Matterbridge.operationalCredentials.#handleAddedFabric>#66 waiting on @0:0•b73a⇵2c34✉085634d3
info[16:19:55.270][MdnsAdvertisement]Publishing kind: operational service: mdns:B77B5B408CFD8854-1A83DD50EE4D823C._matter._tcp.local
info[16:19:55.282][FabricAccessControl]ACL List updated privilege: 5 authMode: 2 subjects: 11181304605732249382 targets: null fabricIndex: 1
info[16:19:55.283][OperationalCredentials]addNoc success, adminVendorId 65521, caseAdminSubject 9b2bf94c3e1c1f26
info[16:19:55.283][ProtocolService]Invoke » Matterbridge.operationalCredentials.addNoc @0:0•b73a⇵2c34✉085634d3 statusCode: 0 fabricIndex: 1
info[16:19:55.302][InteractionServer]Invoke « @1:0•b73a⇵2c35 invokes: RootNode:0x0.GeneralCommissioning:0x30.armFailSafe:0x0
info[16:19:55.303][ProtocolService]Invoke « Matterbridge.generalCommissioning.armFailSafe @1:0•b73a⇵2c35✉085634d5 expiryLengthSeconds: 60 breadcrumb: 1
info[16:19:55.304][ProtocolService]Invoke » Matterbridge.generalCommissioning.armFailSafe @1:0•b73a⇵2c35✉085634d5 errorCode: 0 debugText:
info[16:19:55.321][InteractionServer]Invoke « @1:0•b73a⇵2c36 invokes: RootNode:0x0.GeneralCommissioning:0x30.armFailSafe:0x0
info[16:19:55.322][ProtocolService]Invoke « Matterbridge.generalCommissioning.armFailSafe @1:0•b73a⇵2c36✉085634d7 expiryLengthSeconds: 314 breadcrumb: 1
info[16:19:55.324][ProtocolService]Invoke » Matterbridge.generalCommissioning.armFailSafe @1:0•b73a⇵2c36✉085634d7 errorCode: 0 debugText:
info[16:19:55.332][CaseServer]Received pairing request « udp://[fe80::5644:b10:d213:e3b5%enp0s25]:33019
notice[16:19:55.350][Matterbridge]Session opened on server node for Matterbridge: { name: '@1:9b2bf94c3e1c1f26•b73b', nodeId: 1910614006600401468, peerNodeId: 11181304605732249382, fabric: { fabricIndex: 1, fabricId: 6767716289488547961, nodeId: 1910614006600401468, rootNodeId: 11181304605732249382, rootVendorId: 65521, label: '' }, isPeerActive: true, lastInteractionTimestamp: 1780244395348, lastActiveTimestamp: 1780244395348, numberOfActiveSubscriptions: 0 }
info[16:19:55.352][CaseServer]@1:9b2bf94c3e1c1f26•b73b New session with @1:9b2bf94c3e1c1f26 2↔1 address: udp://[fe80::5644:b10:d213:e3b5%enp0s25]:33019 fabric: b77b5b408cfd8854 (#1) SII: 500ms SAI: 300ms SAT: 4s DMRev: 19 IMRev: 13 spec: 0x1040200 maxPaths: 10 CATs:
info[16:19:55.361][InteractionServer]Invoke « @1:9b2bf94c3e1c1f26•b73b⇵2c38 invokes: RootNode:0x0.GeneralCommissioning:0x30.commissioningComplete:0x4
info[16:19:55.362][ProtocolService]Invoke « Matterbridge.generalCommissioning.commissioningComplete @1:9b2bf94c3e1c1f26•b73b⇵2c38✉029f5805 (no payload)
info[16:19:55.367][Session]•unsecured#77fad7d15f9fbcd Session ended
info[16:19:55.372][MdnsAdvertisement]Unpublishing kind: commissionable service: mdns:431ECDF6042C0832._matterc._udp.local time: 1m 42s
info[16:19:55.397][Session]@1:0•b73a Session ended
notice[16:19:55.401][Matterbridge]Server node for Matterbridge commissioned successfully!
notice[16:19:55.402][Matterbridge]Commissioned fabric index 1 added on server node for Matterbridge: { fabricIndex: 1, fabricId: 6767716289488547961, nodeId: 1910614006600401468, rootNodeId: 11181304605732249382, rootVendorId: 65521, label: '' }
info[16:19:55.403][GeneralCommissioningClusterHandler]Commissioned fabric: b77b5b408cfd8854 (#1) node: 1a83dd50ee4d823c
info[16:19:55.404][ProtocolService]Invoke » Matterbridge.generalCommissioning.commissioningComplete @1:9b2bf94c3e1c1f26•b73b⇵2c38✉029f5805 errorCode: 0 debugText:
info[16:19:55.417][InteractionServer]Invoke « @1:9b2bf94c3e1c1f26•b73b⇵2c39 invokes: RootNode:0x0.OperationalCredentials:0x3e.updateFabricLabel:0x9
info[16:19:55.418][ProtocolService]Invoke « Matterbridge.operationalCredentials.updateFabricLabel @1:9b2bf94c3e1c1f26•b73b⇵2c39✉029f5807 label: Gladys Assistant fabricIndex: 1
info[16:19:55.426][FabricAccessControl]ACL List updated privilege: 5 authMode: 2 subjects: 11181304605732249382 targets: null fabricIndex: 1
info[16:19:55.427][Transaction]Tx ◦reactor<Matterbridge.operationalCredentials.#handleUpdatedFabric>#71 waiting on @1:9b2bf94c3e1c1f26•b73b⇵2c39✉029f5807
info[16:19:55.428][ProtocolService]Invoke » Matterbridge.operationalCredentials.updateFabricLabel @1:9b2bf94c3e1c1f26•b73b⇵2c39✉029f5807 statusCode: 0 fabricIndex: 1
notice[16:19:55.434][Matterbridge]Commissioned fabric index 1 updated on server node for Matterbridge: { fabricIndex: 1, fabricId: 6767716289488547961, nodeId: 1910614006600401468, rootNodeId: 11181304605732249382, rootVendorId: 65521, label: 'Gladys Assistant' }
info[16:19:56.050][InteractionServer]Subscribe « @1:9b2bf94c3e1c1f26•b73b⇵2c3b fabricFiltered attributePaths: 1 eventPaths: 1
info[16:19:56.075][InteractionServer]Subscribe successful » @1:9b2bf94c3e1c1f26•b73b⇵2c3b 2↔1 sub#: f2b32c2f timing: 1s - 1m => 1m 1s sendInterval: 48.9s
notice[16:19:56.081][Matterbridge]Session subscriptions changed on server node for Matterbridge: { name: '@1:9b2bf94c3e1c1f26•b73b', nodeId: 1910614006600401468, peerNodeId: 11181304605732249382, fabric: { fabricIndex: 1, fabricId: 6767716289488547961, nodeId: 1910614006600401468, rootNodeId: 11181304605732249382, rootVendorId: 65521, label: '' }, isPeerActive: true, lastInteractionTimestamp: 1780244395348, lastActiveTimestamp: 1780244395348, numberOfActiveSubscriptions: 1 }
warn[16:20:02.538][ExchangeManager]Ignoring message for unknown session b73a from node 0000000000000000
info[16:20:11.614][SystemCheck]Starting system check...
info[16:20:11.649][SystemCheck]System check succeeded
info[16:23:11.629][CheckUpdates]Starting check updates...
info[16:23:11.631][DockerVersion]Starting docker version check...
info[16:23:11.631][DockerVersion]Docker build config: version=3.7.10 dev=false
info[16:23:11.948][CheckUpdates]Check updates succeeded
info[16:23:13.171][DockerVersion]Docker version check succeeded: latest=3.7.10, dev=3.8.0, current=3.7.10

Et si tu ouvres le device « MA-Aggregator » dans les paramètres de l’intégration Matter, tu ne vois rien ? Dans Matterbridge, tous les appareils apparaitront sous cet appareil

L’autre question, c’est qu’est-ce qu’expose le plugin ?

Deux possibilités :

  • L’usine à plugin s’est trompée et le plugin n’expose rien ou a eu un souci (auquel cas, il faut revenir vers l’usine avec un commentaire qui explique le souci)
  • Le plugin expose une fonctionnalité Matter que Gladys ne gère pas (ça arrive souvent), et là dans ce cas-là il faut faire une demande d’évolution côté Gladys pour qu’on le rajoute :slight_smile:

Ok je comprends l’idée :slight_smile: merci pour les explications.

Quand j’ouvre le noeud MA-aggregator dans l’intégration Mattebridge j’ai toute une liste de trucs auxquels je ne comprends pas grand chose : [ { "node_id": "1910614006600401468", "is_connected": true, "d - Pastebin.com

Je ne sais pas comment vérifier ce qu’expose le plugin afin de savoir s’il expose bien quelque chose / si c’est Gladys qui ne prend pas en charge la fonctionnalité :thinking:

Merci pour le JSON, je pencherais plus pour un bug du plugin en état, je vois bien un appareil qui expose « PowerSource », sauf que c’est une erreur, ce n’est pas le bon cluster à implémenter.

Si ton objectif est de suivre la consommation de ta borne de recharge de véhicule électrique, il faut implémenter le cluster ElectricalEnergyMeasurement et ElectricalPowerMeasurement !

Fais un retour sur Github à l’usine et Claude Code corrigera :slight_smile:

J’ai ajouté un message sur github :slight_smile: merci de m’avoir guidé !! On croise les doigts !