Problème de Zwave HS après mise à jour

Entraide Home Assistant
1

Bonjour,
J’ai un soucis après la mise de ZWave JS d’aujourd’hui, je n’ai plus d’informations de mes modules qui remontent.
Je ne sais pas si mon installation est au top mais j’ai 2 modules complémentaire qui tournent pour ZWave : Zwave JS et Zwave JS UI.
N’ayant plus besoin d’envoyer ls information sur Jeedom en parallèle de HA, je n’ai plus besoin de MQTT, donc plus besoin théoriquement de Zwave JS UI. Mais j’ai peur de tout foutre en l’air si je le désinstalle.

Je vous mets les logs de Zwave UI, dans la configuration, mon dongle Zwave est bien renseigné. Il y a des erreurs, mais cela est normalement dû à des modules en panne.

2025-04-11T11:41:27.345Z CNTRLR   [Node 020] The node is ready to be used
2025-04-11T11:41:27.345Z CNTRLR   [Node 051] The node is asleep.
2025-04-11T11:41:27.347Z CNTRLR   [Node 051] The node is ready to be used
2025-04-11T11:41:27.348Z CNTRLR   [Node 009] The node is asleep.
2025-04-11T11:41:27.348Z CNTRLR   [Node 009] The node is ready to be used
2025-04-11T11:41:27.348Z CNTRLR   [Node 042] The node is asleep.
2025-04-11T11:41:27.349Z CNTRLR   [Node 042] The node is ready to be used
2025-04-11T11:41:27.350Z CNTRLR   [Node 021] The node is asleep.
2025-04-11T11:41:27.351Z CNTRLR   [Node 021] Beginning interview - last completed stage: NodeInfo
ZwaveJS server listening on <all interfaces>:3000
2025-04-11T11:41:27.367Z CNTRLR   [Node 021] Embedded device config loaded
2025-04-11T11:41:27.372Z CNTRLR   [Node 021] Interviewing Configuration...
2025-04-11T11:41:27.372Z CNTRLR   [Node 021] ConfigurationCC: Loading configuration parameters from device confi
                                  g
2025-04-11T11:41:27.379Z CNTRLR » [Node 021] querying parameter #1 value...
2025-04-11T11:41:27.512Z CNTRLR   [Node 028] The node is alive.
2025-04-11T11:41:27.512Z CNTRLR   [Node 028] The node is ready to be used
2025-04-11T11:41:27.515Z CNTRLR « [Node 028] ping successful
2025-04-11T11:41:27.553Z CNTRLR   [Node 047] The node is alive.
2025-04-11T11:41:27.553Z CNTRLR   [Node 047] The node is ready to be used
2025-04-11T11:41:27.554Z CNTRLR « [Node 047] ping successful
2025-04-11T11:41:27.702Z CNTRLR   [Node 012] The node is alive.
2025-04-11T11:41:27.703Z CNTRLR   [Node 012] The node is ready to be used
2025-04-11T11:41:27.703Z CNTRLR « [Node 012] ping successful
2025-04-11T11:41:27.744Z CNTRLR   [Node 014] The node is alive.
2025-04-11T11:41:27.744Z CNTRLR   [Node 014] The node is ready to be used
2025-04-11T11:41:27.745Z CNTRLR « [Node 014] ping successful
2025-04-11T11:41:27.770Z CNTRLR   [Node 018] The node is alive.
2025-04-11T11:41:27.771Z CNTRLR   [Node 018] The node is ready to be used
2025-04-11T11:41:27.772Z CNTRLR « [Node 018] ping successful
2025-04-11T11:41:27.801Z CNTRLR   [Node 019] The node is alive.
2025-04-11T11:41:27.801Z CNTRLR   [Node 019] The node is ready to be used
2025-04-11T11:41:27.801Z CNTRLR « [Node 019] ping successful
2025-04-11T11:41:36.067Z CNTRLR   [Node 037] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:41:36.067Z CNTRLR   [Node 037] The node is dead.
2025-04-11T11:41:36.068Z CNTRLR   [Node 037] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:41:43.697Z CNTRLR   [Node 055] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:41:43.697Z CNTRLR   [Node 055] The node is dead.
2025-04-11T11:41:43.697Z CNTRLR   [Node 055] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:41:54.505Z CNTRLR   [Node 011] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:41:54.505Z CNTRLR   [Node 011] The node is dead.
2025-04-11T11:41:54.506Z CNTRLR   [Node 011] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:42:02.177Z CNTRLR   [Node 044] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:42:02.185Z CNTRLR   [Node 044] The node is dead.
2025-04-11T11:42:02.186Z CNTRLR   [Node 044] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:42:10.339Z CNTRLR   [Node 036] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:42:10.342Z CNTRLR   [Node 036] The node is dead.
2025-04-11T11:42:10.343Z CNTRLR   [Node 036] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:42:18.626Z CNTRLR   [Node 035] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:42:18.626Z CNTRLR   [Node 035] The node is dead.
2025-04-11T11:42:18.626Z CNTRLR   [Node 035] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:42:25.959Z CNTRLR   [Node 043] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:42:25.960Z CNTRLR   [Node 043] The node is dead.
2025-04-11T11:42:25.960Z CNTRLR   [Node 043] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:42:31.759Z CNTRLR   [Node 045] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:42:31.760Z CNTRLR   [Node 045] The node is dead.
2025-04-11T11:42:31.760Z CNTRLR   [Node 045] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:42:35.842Z CNTRLR   [Node 046] The node did not respond after 1 attempts, it is presumed dead
2025-04-11T11:42:35.843Z CNTRLR   [Node 046] The node is dead.
2025-04-11T11:42:35.844Z CNTRLR   [Node 046] ping failed: The node did not acknowledge the command (ZW0204)
2025-04-11T11:46:08.715Z CNTRLR « [Node 052] received wakeup notification
2025-04-11T11:46:08.715Z CNTRLR   [Node 052] The node is now awake.
2025-04-11T11:46:08.716Z CNTRLR   [Node 052] expects some queries after wake up, so it shall receive
2025-04-11T11:46:08.716Z CNTRLR   [Node 052] compat query "Battery"::get()
2025-04-11T11:46:09.069Z CNTRLR   [Node 052] API call successful
2025-04-11T11:46:09.069Z CNTRLR   [Node 052] compat query "Thermostat Setpoint"::get(1)
2025-04-11T11:46:09.421Z CNTRLR   [Node 052] API call successful
2025-04-11T11:46:09.672Z CNTRLR » [Node 052] Sending node back to sleep...
2025-04-11T11:46:09.698Z CNTRLR   [Node 052] The node is now asleep.
2025-04-11T11:51:05.366Z CNTRLR « [Node 052] received wakeup notification
2025-04-11T11:51:05.366Z CNTRLR   [Node 052] The node is now awake.
2025-04-11T11:51:05.366Z CNTRLR   [Node 052] expects some queries after wake up, so it shall receive
2025-04-11T11:51:05.366Z CNTRLR   [Node 052] compat query "Battery"::get()
2025-04-11T11:51:05.720Z CNTRLR   [Node 052] API call successful
2025-04-11T11:51:05.721Z CNTRLR   [Node 052] compat query "Thermostat Setpoint"::get(1)
2025-04-11T11:51:06.064Z CNTRLR   [Node 052] API call successful
2025-04-11T11:51:06.316Z CNTRLR » [Node 052] Sending node back to sleep...
2025-04-11T11:51:06.327Z CNTRLR   [Node 052] The node is now asleep.
2025-04-11T11:56:02.068Z CNTRLR « [Node 052] received wakeup notification
2025-04-11T11:56:02.069Z CNTRLR   [Node 052] The node is now awake.
2025-04-11T11:56:02.070Z CNTRLR   [Node 052] expects some queries after wake up, so it shall receive
2025-04-11T11:56:02.070Z CNTRLR   [Node 052] compat query "Battery"::get()
2025-04-11T11:56:02.418Z CNTRLR   [Node 052] API call successful
2025-04-11T11:56:02.418Z CNTRLR   [Node 052] compat query "Thermostat Setpoint"::get(1)
2025-04-11T11:56:02.770Z CNTRLR   [Node 052] API call successful
2025-04-11T11:56:03.020Z CNTRLR » [Node 052] Sending node back to sleep...
2025-04-11T11:56:03.033Z CNTRLR   [Node 052] The node is now asleep.
2025-04-11T11:59:50.378Z CNTRLR « [Node 032] received wakeup notification
2025-04-11T11:59:50.379Z CNTRLR   [Node 032] The node is now awake.
2025-04-11T11:59:50.629Z CNTRLR » [Node 032] Sending node back to sleep...
2025-04-11T11:59:50.641Z CNTRLR   [Node 032] The node is now asleep.
2025-04-11T12:00:58.784Z CNTRLR « [Node 052] received wakeup notification
2025-04-11T12:00:58.785Z CNTRLR   [Node 052] The node is now awake.
2025-04-11T12:00:58.785Z CNTRLR   [Node 052] expects some queries after wake up, so it shall receive
2025-04-11T12:00:58.785Z CNTRLR   [Node 052] compat query "Battery"::get()
2025-04-11T12:00:59.132Z CNTRLR   [Node 052] API call successful
2025-04-11T12:00:59.133Z CNTRLR   [Node 052] compat query "Thermostat Setpoint"::get(1)
2025-04-11T12:00:59.488Z CNTRLR   [Node 052] API call successful
2025-04-11T12:00:59.739Z CNTRLR » [Node 052] Sending node back to sleep...
2025-04-11T12:00:59.751Z CNTRLR   [Node 052] The node is now asleep.

Et ensuite les logs de Zwave UI JS :

2025-04-11T12:07:43.747Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:07:43.747 INFO Z-WAVE: Restarting client in 15 seconds, retry 67
2025-04-11 14:07:51.820 INFO APP: GET /health/zwave 301 0.491 ms - 162
2025-04-11 14:07:58.754 INFO Z-WAVE: Client closed
2025-04-11 14:07:58.755 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:07:58.757Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:07:58.758Z DRIVER   version 15.0.5
2025-04-11T12:07:58.758Z DRIVER   
2025-04-11T12:08:07.777Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:08:07.777 INFO Z-WAVE: Restarting client in 15 seconds, retry 68
2025-04-11 14:08:21.879 INFO APP: GET /health/zwave 301 0.565 ms - 162
2025-04-11 14:08:22.778 INFO Z-WAVE: Client closed
2025-04-11 14:08:22.779 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:08:22.780Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:08:22.781Z DRIVER   version 15.0.5
2025-04-11T12:08:22.781Z DRIVER   
2025-04-11T12:08:32.117Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:08:32.117 INFO Z-WAVE: Restarting client in 15 seconds, retry 69
2025-04-11 14:08:47.125 INFO Z-WAVE: Client closed
2025-04-11 14:08:47.127 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:08:47.128Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:08:47.128Z DRIVER   version 15.0.5
2025-04-11T12:08:47.129Z DRIVER   
2025-04-11 14:08:51.924 INFO APP: GET /health/zwave 301 0.435 ms - 162
2025-04-11T12:08:56.146Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:08:56.147 INFO Z-WAVE: Restarting client in 15 seconds, retry 70
2025-04-11 14:09:11.160 INFO Z-WAVE: Client closed
2025-04-11 14:09:11.162 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:09:11.163Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:09:11.163Z DRIVER   version 15.0.5
2025-04-11T12:09:11.163Z DRIVER   
2025-04-11T12:09:20.181Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:09:20.181 INFO Z-WAVE: Restarting client in 15 seconds, retry 71
2025-04-11 14:09:21.964 INFO APP: GET /health/zwave 301 0.513 ms - 162
2025-04-11 14:09:35.193 INFO Z-WAVE: Client closed
2025-04-11 14:09:35.195 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:09:35.197Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:09:35.198Z DRIVER   version 15.0.5
2025-04-11T12:09:35.199Z DRIVER   
2025-04-11T12:09:44.219Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:09:44.219 INFO Z-WAVE: Restarting client in 15 seconds, retry 72
2025-04-11 14:09:52.013 INFO APP: GET /health/zwave 301 0.647 ms - 162
2025-04-11 14:09:59.222 INFO Z-WAVE: Client closed
2025-04-11 14:09:59.226 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:09:59.229Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:09:59.231Z DRIVER   version 15.0.5
2025-04-11T12:09:59.231Z DRIVER   
2025-04-11T12:10:08.253Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:10:08.254 INFO Z-WAVE: Restarting client in 15 seconds, retry 73
2025-04-11 14:10:22.063 INFO APP: GET /health/zwave 301 0.422 ms - 162
2025-04-11 14:10:23.255 INFO Z-WAVE: Client closed
2025-04-11 14:10:23.258 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:10:23.261Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:10:23.263Z DRIVER   version 15.0.5
2025-04-11T12:10:23.264Z DRIVER   
2025-04-11T12:10:32.284Z DRIVER   Failed to open the serial port: Error Resource temporarily unavailable Cannot 
                                  lock port
2025-04-11 14:10:32.285 INFO Z-WAVE: Restarting client in 15 seconds, retry 74
2025-04-11 14:10:47.300 INFO Z-WAVE: Client closed
2025-04-11 14:10:47.301 INFO Z-WAVE: Connecting to /dev/serial/by-id/usb-0658_0200-if00
2025-04-11T12:10:47.303Z DRIVER   ███████╗        ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗          ██╗ ███████╗
                                  ╚══███╔╝        ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝          ██║ ██╔════╝
                                    ███╔╝  █████╗ ██║ █╗ ██║ ███████║ ██║   ██║ █████╗            ██║ ███████╗
                                   ███╔╝   ╚════╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝       ██   ██║ ╚════██║
                                  ███████╗        ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗     ╚█████╔╝ ███████║
                                  ╚══════╝         ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝      ╚════╝  ╚══════╝
2025-04-11T12:10:47.303Z DRIVER   version 15.0.5
2025-04-11T12:10:47.303Z DRIVER

Espérant que vous puissiez m’aider
Stéphane

2

Tu peux préciser ton instalation parce que c’est pas clair :

Tu parles bien des add-on si oui tu n’as plus besoin de zwave JS si tu as la version UI et vice versa mais je comprends pas comment ça a pu fonctionner depuis…

Si le systeme en lui même fonctionne sous MQTT

Tu es sûr que ta clef n’as pas changé de port ? En tout cas il faut virer un des deux addon si tu a les deux. Au vu des log le serveur tourne donc c’est un problème de configuration. Il faut après brancher l’intégration HA zwave sur le serveur restant (ce que tu ne dois aps avoir fait).

3

Désolé de ma réponse très tardive, mais je suis totalement passé à côté de la réponse de @Idaho947.
Les 2 modules complémentaires sont ceux-ci :

image
image1162×150 19.4 KB

Au début, je n’en avais qu’un seul et cela ne fonctionnait pas, j’ai donc mis les 2 est cela fonctionne de façon intermittente : après plusieurs redémarrage des 2 modules, j’arrive à avoir les infos arriver, mais en cas de mise à jour ou redémarrage du système, cela ne fonctionne plus jusqu’à faire plusieurs redémarrage des 2 modules.
J’aimerai désinstaller un des 2 modules pour avoir un système stable mais j’ai peur de faire pire ;).
Merci pour votre aide.

4

Pire que pas stable ou pas fonctionnel sur la durée ?? ça devrait pas pouvoir être plus pénible

5

Oui aussi :wink:
J’essaie de ne démarrer qu’un seul module et cela ne fonctionne pas.
Si je ne démarrer que ZWave JS UI, je vois bien mes modules mais ils n’apparaissent pas dans MQTT.

image
image2555×1391 376 KB

6

@Idaho947 t’indique tout les pistes :

Donc les logs => corriger la clé, et remettre/vérifier mqtt

7

Merci @Pulpy-Luke pour ton aide

Je commence par le premier point, en regardant dans « système », je trouve ma clé ici :
image
Dans le module Zwave JS, dans la configuration, j’ai ceci :

image
image1578×240 6.12 KB

Dons, je suppose que la clé n’a pas changé de port.

8

Je me rends compte d’un truc bizarre : je viens d’arrêter les 2 modules, et je ne vois plus ma clé ZWave.
Idem dans Système : il n’y est pas non plus

9

A condition que ce soit bien la clé zwave, oui on dirait que c’est la même chose.
Par contre, plus haut, ça indiquait une erreur

Donc soit c’est la résultante de tes 2 trucs qui se piquent la clé réciproquement, soit c’est pas la bonne clé

10

La clé est la normalement bonne.
Je n’ai pas cette erreur quand je démarrer seulement Zwave JS UI.
Elle apparait quand j’ai démarré Zwave JS avant, le port doit être occupé.

1 « J'aime »
11

C’est normal ils sont dans zwave.

Supprime laddon zwavejs tout simple.

12

J’ai un autre soucis, je ne trouve plus ma clé… elle a disparu lors des démarrages… bizzare…

13

Tu as fixée le port ?

14

Comment ca?
Je suis sur un système sous Proxmox, qui est bien configuré pour le passthrough.
Après, je ne vois ,pas comment fixer le port …

15

Déjà vire zwavejs et redémarre ha.

16

Bon… après un redémarrage de la VM, je viens de retrouver mon module Zwave :

image
image876×193 8.02 KB

17

On est bien d’accord qui s’agit de Zwve JS et non ZWave JS UI ?

18

Oui c’est l’un ou l’autre.

19

Ok, je souhaite ne garder que le plus récent, je vais donc supprimer ZWave JS

20

Je viens de désinstaller ZWave JS, l’addon ZWave JS UI tourne et trouve bien mes modules

image
image2146×1258 252 KB

Mais mon intégration Zwave m’indique une erreur que je ne comprends pas

image
image1514×634 50.8 KB