Tous mes micro modules Fibaro ont sauté les uns après les autres

Bonjour,

J’ai des modules Fibaro 222 sur mes inter de volets, et ils sont devenus indisponibles les uns après les autres au fur et à mesure de la soirée, jusqu’à que plus aucun de fonctionne.

J’ai redémarré HA et mon RPI, je ne comprends pas d’où vient le problème.

Shutting down
Closing server...
Client disconnected
Code 1000: 
Server closed
[22:50:27] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/config.sh
[23:51:04] INFO: No 'network_key' detected, setting it to 's0_legacy_key' for backwards compatibility
[23:51:04] INFO: Flushing config to disk due to creation of new key(s)...
[23:51:05] INFO: Soft-reset set to automatic
[23:51:05] INFO: Virtual Machine not detected, enabling soft-reset
cont-init: info: /etc/cont-init.d/config.sh exited 0
cont-init: info: running /etc/cont-init.d/structure.sh
cont-init: info: /etc/cont-init.d/structure.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun zwave_js (no readiness notification)
s6-rc: info: service legacy-services successfully started
[23:51:06] INFO: Successfully send discovery information to Home Assistant.
2025-01-07T22:51:07.561Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-01-07T22:51:07.563Z DRIVER   version 13.10.3
2025-01-07T22:51:07.563Z DRIVER   
2025-01-07T22:51:08.590Z CONFIG   version 13.10.3
2025-01-07T22:51:09.003Z CNTRLR   querying Serial API capabilities...
2025-01-07T22:51:09.185Z CNTRLR   received API capabilities:
                                    firmware version:    4.36
                                    manufacturer ID:     0x00
                                    product type:        0x01
                                    product ID:          0x01
                                    supported functions: 
                                    · GetSerialApiInitData (0x02)
                                    · SetApplicationNodeInformation (0x03)
                                    · ApplicationCommand (0x04)
                                    · GetControllerCapabilities (0x05)
                                    · SetSerialApiTimeouts (0x06)
                                    · GetSerialApiCapabilities (0x07)
                                    · SoftReset (0x08)
                                    · GetProtocolVersion (0x09)
                                    · SetRFReceiveMode (0x10)
                                    · UNKNOWN_FUNC_SET_SLEEP_MODE (0x11)
                                    · SendNodeInformation (0x12)
                                    · SendData (0x13)
                                    · SendDataMulticast (0x14)
                                    · GetControllerVersion (0x15)
                                    · SendDataAbort (0x16)
                                    · FUNC_ID_ZW_R_F_POWER_LEVEL_SET (0x17)
                                    · UNKNOWN_FUNC_SEND_DATA_META (0x18)
                                    · FUNC_ID_ZW_GET_RANDOM (0x1c)
                                    · GetControllerId (0x20)
                                    · UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
                                    · UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
                                    · UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
                                    · UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
                                    · EnterBootloader (0x27)
                                    · UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
                                    · GetNVMId (0x29)
                                    · ExtNVMReadLongBuffer (0x2a)
                                    · ExtNVMWriteLongBuffer (0x2b)
                                    · ExtNVMReadLongByte (0x2c)
                                    · ExtExtWriteLongByte (0x2d)
                                    · GetNodeProtocolInfo (0x41)
                                    · HardReset (0x42)
                                    · FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
                                    · FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
                                    · AssignReturnRoute (0x46)
                                    · DeleteReturnRoute (0x47)
                                    · RequestNodeNeighborUpdate (0x48)
                                    · ApplicationUpdateRequest (0x49)
                                    · AddNodeToNetwork (0x4a)
                                    · RemoveNodeFromNetwork (0x4b)
                                    · AddControllerAndAssignPrimary (0x4c)
                                    · AddPrimaryController (0x4d)
                                    · SetLearnMode (0x50)
                                    · AssignSUCReturnRoute (0x51)
                                    · RequestNetworkUpdate (0x53)
                                    · SetSUCNodeId (0x54)
                                    · DeleteSUCReturnRoute (0x55)
                                    · GetSUCNodeId (0x56)
                                    · SendSUCNodeId (0x57)
                                    · ExploreRequestInclusion (0x5e)
                                    · RequestNodeInfo (0x60)
                                    · RemoveFailedNode (0x61)
                                    · IsFailedNode (0x62)
                                    · ReplaceFailedNode (0x63)
                                    · UNKNOWN_FUNC_UNKNOWN_0x66 (0x66)
                                    · UNKNOWN_FUNC_UNKNOWN_0x67 (0x67)
                                    · FirmwareUpdateNVM (0x78)
                                    · GetRoutingInfo (0x80)
                                    · LockUnlockLastRoute (0x90)
                                    · GetPriorityRoute (0x92)
                                    · SetPriorityRoute (0x93)
                                    · UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
                                    · undefined (0xb4)
                                    · EnableWatchdog500 (0xb6)
                                    · DisableWatchdog500 (0xb7)
                                    · KickWatchdog500 (0xb8)
                                    · UNKNOWN_FUNC_UNKNOWN_0xB9 (0xb9)
                                    · UNKNOWN_FUNC_RF_POWERLEVEL_GET (0xba)
                                    · GetLibrary (0xbd)
                                    · SendTestFrame (0xbe)
                                    · GetProtocolStatus (0xbf)
                                    · StartWatchdog (0xd2)
                                    · StopWatchdog (0xd3)
                                    · SetMaximumRoutingAttempts (0xd4)
                                    · undefined (0xee)
                                    · undefined (0xef)
2025-01-07T22:51:09.186Z CNTRLR   querying additional controller information...
2025-01-07T22:51:09.289Z CNTRLR   received additional controller information:
                                    Z-Wave API version:         5 (legacy)
                                    Z-Wave chip type:           ZW050x
                                    node type                   Controller
                                    controller role:            primary
                                    controller is the SIS:      true
                                    controller supports timers: false
                                    Z-Wave Classic nodes:       1, 3, 4, 5, 6, 7, 8, 9, 10, 11
2025-01-07T22:51:09.289Z CNTRLR   querying version info...
2025-01-07T22:51:09.301Z CNTRLR   received version info:
                                    controller type: Static Controller
                                    library version: Z-Wave 4.24
2025-01-07T22:51:09.301Z CNTRLR   querying protocol version info...
2025-01-07T22:51:09.309Z CNTRLR   received protocol version info:
                                    protocol type:             Z-Wave
                                    protocol version:          4.24.0
2025-01-07T22:51:09.310Z CNTRLR   querying controller capabilities...
2025-01-07T22:51:09.319Z CNTRLR   received controller capabilities:
                                    controller role:      Primary
                                    is the SUC:           true
                                    started this network: true
                                    SIS is present:       true
                                    was real primary:     false
2025-01-07T22:51:09.320Z CNTRLR   supported Z-Wave features: 
2025-01-07T22:51:09.321Z CNTRLR   Performing soft reset...
2025-01-07T22:51:09.327Z CNTRLR   Waiting for the controller to reconnect...
2025-01-07T22:51:10.829Z CNTRLR   Re-opening serial port...
2025-01-07T22:51:11.836Z CNTRLR   Waiting for the Serial API to start...
2025-01-07T22:51:16.838Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
                                  nds...
2025-01-07T22:51:16.847Z CNTRLR   Serial API responded
2025-01-07T22:51:16.848Z CNTRLR   querying controller IDs...
2025-01-07T22:51:16.855Z CNTRLR   received controller IDs:
                                    home ID:     0xf1685206
                                    own node ID: 1
2025-01-07T22:51:16.856Z CNTRLR   finding SUC...
2025-01-07T22:51:16.863Z CNTRLR   This is the SUC
2025-01-07T22:51:16.863Z CNTRLR   setting serial API timeouts: ack = 1000 ms, byte = 150 ms
2025-01-07T22:51:16.869Z CNTRLR   serial API timeouts overwritten. The old values were: ack = 1500 ms, byte = 15
                                  0 ms
2025-01-07T22:51:16.937Z CNTRLR   [Node 001] Embedded device config loaded
2025-01-07T22:51:16.948Z CNTRLR   [Node 004] Embedded device config loaded
2025-01-07T22:51:16.955Z CNTRLR   [Node 005] Embedded device config loaded
2025-01-07T22:51:16.961Z CNTRLR   [Node 006] Embedded device config loaded
2025-01-07T22:51:16.967Z CNTRLR   [Node 008] Embedded device config loaded
2025-01-07T22:51:16.975Z CNTRLR   Interview completed
Starting server on <all interfaces>:3000
2025-01-07T22:51:16.988Z CNTRLR   [Node 001] The node is alive.
2025-01-07T22:51:16.988Z CNTRLR   [Node 001] The node is ready to be used
2025-01-07T22:51:16.989Z CNTRLR   Interviewing nodes and/or determining their status: 4, 6, 9, 8, 5, 3, 10, 11, 
                                  7
2025-01-07T22:51:16.989Z CNTRLR » [Node 004] pinging the node...
2025-01-07T22:51:17.049Z CNTRLR » [Node 006] pinging the node...
2025-01-07T22:51:17.051Z CNTRLR » [Node 009] pinging the node...
2025-01-07T22:51:17.052Z CNTRLR » [Node 008] pinging the node...
2025-01-07T22:51:17.053Z CNTRLR » [Node 005] pinging the node...
2025-01-07T22:51:17.054Z CNTRLR   [Node 003] Beginning interview - last completed stage: ProtocolInfo
2025-01-07T22:51:17.055Z CNTRLR » [Node 003] pinging the node...
2025-01-07T22:51:17.056Z CNTRLR   [Node 010] Beginning interview - last completed stage: ProtocolInfo
2025-01-07T22:51:17.056Z CNTRLR » [Node 010] pinging the node...
2025-01-07T22:51:17.057Z CNTRLR   [Node 011] Beginning interview - last completed stage: ProtocolInfo
2025-01-07T22:51:17.057Z CNTRLR » [Node 011] pinging the node...
2025-01-07T22:51:17.059Z CNTRLR   [Node 007] The node is asleep.
2025-01-07T22:51:17.059Z CNTRLR   [Node 007] Beginning interview - last completed stage: ProtocolInfo
2025-01-07T22:51:17.060Z CNTRLR » [Node 007] querying node info...
ZwaveJS server listening on <all interfaces>:3000
2025-01-07T22:51:22.639Z CNTRLR   [Node 004] The node did not respond after 1 attempts, it is presumed dead
2025-01-07T22:51:22.640Z CNTRLR   [Node 004] The node is dead.
2025-01-07T22:51:22.642Z CNTRLR   [Node 004] ping failed: The node did not acknowledge the command (ZW0204)
2025-01-07T22:51:22.719Z CNTRLR   [Node 006] The node is alive.
2025-01-07T22:51:22.720Z CNTRLR   [Node 006] The node is ready to be used
2025-01-07T22:51:22.720Z CNTRLR « [Node 006] ping successful
2025-01-07T22:51:28.943Z CNTRLR   [Node 009] The node did not respond after 1 attempts, it is presumed dead
2025-01-07T22:51:28.944Z CNTRLR   [Node 009] The node is dead.
2025-01-07T22:51:28.945Z CNTRLR   [Node 009] ping failed: The node did not acknowledge the command (ZW0204)
2025-01-07T22:51:35.414Z CNTRLR   [Node 008] The node did not respond after 1 attempts, it is presumed dead
2025-01-07T22:51:35.415Z CNTRLR   [Node 008] The node is dead.
2025-01-07T22:51:35.416Z CNTRLR   [Node 008] ping failed: The node did not acknowledge the command (ZW0204)
2025-01-07T22:51:41.919Z CNTRLR   [Node 005] The node did not respond after 1 attempts, it is presumed dead
2025-01-07T22:51:41.920Z CNTRLR   [Node 005] The node is dead.
2025-01-07T22:51:41.921Z CNTRLR   [Node 005] ping failed: The node did not acknowledge the command (ZW0204)
New client
2025-01-07T22:51:47.980Z CNTRLR   [Node 003] The node did not respond after 1 attempts, it is presumed dead
2025-01-07T22:51:47.981Z CNTRLR   [Node 003] The node is dead.
2025-01-07T22:51:47.984Z CNTRLR   [Node 003] ping failed: The node did not acknowledge the command (ZW0204)
2025-01-07T22:51:47.985Z CNTRLR   [Node 003] Interview attempt (1/5) failed, node is dead.

Merci de votre aide.

Salut
Tu as fait sauté ta configuration on dirait

No 'network_key' detected

Donc c’est pas la clé connue par les appareils lors de leur appairage

1 « J'aime »

Bonsoir,

Merci de ton retour, j’aurais fait sauter çà comment ?

Depuis parfois ils sont fonctionnels, parfois non :frowning:

Dans la paramétrage ZWAVE, tu as normalement des infos relatives aux clés de chiffrement du réseau

Là on dirait que les valeurs n’existent pas… PAr contre, c’est très étonnant que parfois ça fonctionne …
Soit ça fonctionne (et toute la config est bonne), soit ça marche pas et il manque les clés …
Si ça ballote, c’est autre chose (pertubation, alim etc), ou alors que la config a été corrigée/modifiée

Tout est config, je n’ai touché à rien.

Les micro modules vont et viennent selon si je les actionnent, reste vraiment bug 1 seul.

Là je viens d’activer l’ensemble des volets, le micro modules passent en indispo puis reviennent quelques secondes plus tard…

2025-01-12T15:04:01.918Z CNTRLR   [Node 008] The node is now alive.
2025-01-12T15:04:14.317Z CNTRLR   [Node 004] The node did not respond after 3 attempts, it is presumed dead
2025-01-12T15:04:14.317Z CNTRLR   [Node 004] The node is now dead.
Z-Wave error ZWaveError: The node did not acknowledge the command (ZW0204)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5907:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6105:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6215:29)
    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:268:24)
    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:345:17)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1194:39)
    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:27:43)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:139:100)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:60:45)
    at WebSocket.emit (node:events:517:28) {
  code: 204,
  context: SendDataRequestTransmitReport {
    host: [Driver],
    type: 0,
    functionType: 19,
    expectedResponse: undefined,
    expectedCallback: undefined,
    payload: <Buffer b9 01>,
    _callbackId: 185,
    nodeUpdateTimeout: undefined,
    prematureNodeUpdate: undefined,
    _transmissionTimestamp: undefined,
    _completedTimestamp: undefined,
    transmitStatus: 1,
    _txReport: undefined,
    txReport: undefined
  },
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5907:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6105:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6215:29)\n' +
    '    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:268:24)\n' +
    '    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:345:17)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1194:39)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:27:43)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:139:100)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:60:45)\n' +
    '    at WebSocket.emit (node:events:517:28)'
}
Z-Wave error ZWaveError: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5907:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6105:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6215:29)
    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:268:24)
    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:345:17)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1194:39)
    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:27:43)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:139:100)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:60:45)
    at WebSocket.emit (node:events:517:28) {
  code: 202,
  context: undefined,
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5907:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6105:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6215:29)\n' +
    '    at Proxy.set (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:268:24)\n' +
    '    at Proxy.<anonymous> (/usr/src/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:345:17)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:1194:39)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:27:43)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:139:100)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:60:45)\n' +
    '    at WebSocket.emit (node:events:517:28)'
}
2025-01-12T15:04:15.409Z CNTRLR   [Node 004] The node is now alive.
2025-01-12T15:04:24.262Z CNTRLR   [Node 006] Timed out while waiting for a response from the node (ZW0201)
2025-01-12T15:04:25.317Z CNTRLR   [Node 006] Timed out while waiting for a response from the node (ZW0201)

Tu as toujours le souci de clé à mon avis. Reappaires en un pour voir