Configuration serrure Danalock

goulouche · Août 13, 2026, 8:49

Bonsoir à tous,

J’ai ce type d’erreur qui revient sans cesse dans le log Zwavejsd :

[90m2026-08-04 07:00:13.169e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-04 12:19:48.733e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-04 13:51:21.886e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-04 14:23:36.010e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-05 07:46:16.697e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-05 18:05:05.564e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-05 21:30:10.396e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 255 on 98-0-targetMode: Failed to execute controller command (ZW0202)
e[90m2026-08-05 21:30:10.398e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 255 on 98-0-targetMode: Fail
e[90m2026-08-06 07:00:42.686e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-06 18:00:36.886e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-07 18:12:46.372e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-07 18:15:25.667e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-08 11:20:22.141e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-08 12:35:56.666e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-08 13:27:07.199e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-09 00:12:11.630e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing false on 37-0-targetValue: Timeout while waiting for a callback from the controller (ZW0200)
e[90m2026-08-09 00:12:11.633e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write false on 37-0-targetValue: Fail
e[90m2026-08-09 06:55:42.027e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 0 on 38-1-targetValue: Timeout while waiting for a callback from the controller (ZW0200)
e[90m2026-08-09 06:55:42.028e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 38-1-targetValue: Fail
e[90m2026-08-09 21:30:08.616e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 255 on 98-0-targetMode: Fail
e[90m2026-08-10 12:22:19.645e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-10 12:30:36.788e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-12 16:55:11.780e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 0 on 98-0-targetMode: Fail
e[90m2026-08-13 21:32:47.581e[39m e[31mERRORe[39m e[1mAPPe[22m: Unhandled Rejection, reason: ZWaveError: Security class for node 83 is not yet known! (ZW1402)
ZWaveError: Security class for node 83 is not yet known! (ZW1402)

Peut-être le module est-il mal configuré :

Valeurs du nœud quand la serrure est verrouillée

Valeurs du nœud quand la serrure est déverrouillée

Commandes Jeedom

Traduction des valeurs du nœud

Sincèrement tout cela est assez incompréhensible pour moi.

S’il faut d’autres informations, dites le moi. Merci d’avance.

Informations Jeedom

Core : 4.6.1 (master)
DNS Jeedom : non

Plugin : Z-Wave JS
Version : 2026-07-18 01:03:31 (stable)
Statut Démon : Démarré - (2026-08-03 15:25:14)

Santé

🟢 Matériel : diy
🟢 Système à jour : OK
🟢 Cron actif : OK
🟢 Scénario actif : OK
🟢 Démarré : OK 2026-07-15 04:16:12
🟢 Date système (dernière heure enregistrée) : OK 2026-08-13 22:31:43 (2026-08-13 21:42:01)
🟢 Droits sudo : OK
🟢 Version Jeedom : 4.6.1
🟢 Version OS : debian 12.14
🟢 Version PHP : 8.2.32
🟢 Nombre de processus Apache : 14
🟢 Version OS : Linux jeedom 6.1.0-50-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.176-1 (2026-07-02) x86_64 GNU/Linux  [12.14]
🟢 Version database : 10.11.14-MariaDB-0+deb12u2
🟢 Espace disque libre : 91 %
🟢 Connexion active/max/autorisée : 13/96/151
🟢 Taille base de données : 219.34 MB
🟢 Espace disque libre tmp : 89 %
🟢 Mémoire disponible : 44 % (Total 3915 Mo)
🟢 Mémoire suffisante : 0 
🟢 Erreur I/O : 0
🟢 Swap disponible : 70 % (Total 975 Mo)
🟢 Swappiness : 10 %
🟢 Charge : 1.57 - 1.46 - 1.3
🟢 Configuration réseau interne : OK
🟢 Configuration réseau externe : OK
🟢 Node : v22.23.1 
🟢 Python 3 : Python 3.11.2 
🟢 Persistance du cache : OK
🟢 Apache private tmp : OK

Madcow · Août 14, 2026, 2:31

Bonjour,

La seule chose approchante que j’ai trouvé serait que la serrure est en limite de portée.

github.com/zwave-js/zwave-js

Crashes with "security class is not yet known"

ouvert 07:32AM - 31 Mar 25 UTC

AlCalzone

bug

Originally reported in https://github.com/home-assistant/addons/issues/3952#issu…ecomment-2765164903 ``` 2025-02-24T01:29:37.479Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] │ sequence number: 166 │ extensions: │ · type: SPAN sender EI: 0x518087a72192d4dedca14bf55b962c33 │ security class: S2_Authenticated └─[SupervisionCCGet] │ session id: 48 │ request updates: false └─[NotificationCCReport] notification type: System notification status: 255 notification event: Heartbeat 2025-02-24T01:29:37.480Z CNTRLR [Node 006] [Notification] type: System event: Heartbeat 2025-02-24T01:29:37.529Z DRIVER Dropping message with invalid payload 2025-02-24T01:29:37.529Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Duplicate command (sequence number 166) 2025-02-24T01:29:37.674Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Security2CC_CannotDecode 2025-02-24T01:29:37.675Z CNTRLR [Node 006] Message authentication failed, cannot decode command. 2025-02-24T01:29:37.710Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Security2CC_CannotDecode 2025-02-24T01:29:37.710Z CNTRLR [Node 006] Message authentication failed, cannot decode command. 2025-02-24T01:29:38.339Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Security2CC_CannotDecode 2025-02-24T01:29:38.340Z CNTRLR [Node 006] Message authentication failed, cannot decode command. 2025-02-24T01:29:38.443Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Security2CC_CannotDecode 2025-02-24T01:29:38.443Z CNTRLR [Node 006] Message authentication failed, cannot decode command. 2025-02-24T01:29:38.522Z DRIVER Dropping message with invalid payload 2025-02-24T01:29:38.522Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Duplicate command (sequence number 166) 2025-02-24T01:29:38.888Z DRIVER Dropping message with invalid payload 2025-02-24T01:29:38.888Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Duplicate command (sequence number 166) 2025-02-24T01:29:41.507Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Security2CC_CannotDecode 2025-02-24T01:29:41.507Z CNTRLR [Node 006] Message authentication failed, cannot decode command. 2025-02-24T01:29:41.566Z DRIVER Dropping message with invalid payload 2025-02-24T01:29:41.566Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Duplicate command (sequence number 167) 2025-02-24T01:29:41.688Z DRIVER Dropping message with invalid payload 2025-02-24T01:29:41.688Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Duplicate command (sequence number 167) 2025-02-24T01:29:41.698Z DRIVER « [REQ] [SendData] callback id: 80 transmit status: NoAck, took 5740 ms routing attempts: 34 protocol & route speed: Z-Wave, 40 kbit/s routing scheme: Resort to Direct TX channel no.: 1 route failed here: 11 -> 6 2025-02-24T01:29:41.703Z DRIVER » [Node 006] [REQ] [SendData] │ transmit options: 0x25 │ callback id: 81 └─[Security2CCNonceGet] sequence number: 156 2025-02-24T01:29:41.712Z DRIVER « [RES] [SendData] was sent: true 2025-02-24T01:29:42.005Z DRIVER « [Node 006] [REQ] [ApplicationCommand] └─[Security2CCMessageEncapsulation] [INVALID] error: Security2CC_NoSPAN 2025-02-24T01:29:42.005Z CNTRLR » [Node 006] No SPAN is established yet, cannot decode command. Requesting a non ce... 2025-02-24T01:29:50.836Z DRIVER « [REQ] [SendData] callback id: 81 transmit status: NoAck, took 9120 ms routing attempts: 33 protocol & route speed: Z-Wave, 40 kbit/s routing scheme: Explorer Frame TX channel no.: 1 route failed here: 15 -> 6 2025-02-24T01:29:50.839Z DRIVER » [Node 006] [REQ] [SendData] │ transmit options: 0x05 │ callback id: 82 └─[Security2CCNonceReport] sequence number: 157 SOS: true MOS: false receiver entropy: 0xc6a3086bcc4808f0fd83e435c9988163 ZWaveError: Security class for node 6 is not yet known! (ZW1402) at Driver.sendMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6059:23) at Driver.sendCommandInternal (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6259:28) at Driver.sendCommand (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:6377:29) at Proxy.sendReport (file:///usr/src/node_modules/@zwave-js/cc/src/cc/SupervisionCC.ts:102:20) at reply (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5140:9) at Driver.handleRequest (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:5185:12) at Driver.handleUnsolicitedMessage (file:///usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4689:5) [01:29:50] WARNING: �[33mHalt add-on�[0m ```

Cependant je t’encouragerais à ouvrir une issue sur le github de zwavejs (pas celui de Zwavejs-UI).

goulouche · Août 19, 2026, 7:35

Bonsoir @Madcow ,

Merci pour ta réponse. J’avoue être quelque peu surpris par la “limite de portée” parce qu’avec une soixantaine de modules z-wave j’ai un réseau plutôt bien maillé. Cependant, ma réflexion n’a peut-être aucun rapport avec le problème.

Malgré les erreurs constatées, la serrure fonctionne comme je le souhaite. Je ne vais donc rien changer pour l’instant.

Pour ce qui est d”ouvrir une issue sur Github, je tâcherai de voir ça à la rentrée parce que, pour le moment, leurs règles de fonctionnement m’échappent un peu.

Merci encore et bonne soirée.