First of all, well done @Romuald_Pochet, I have some devices that were just waiting for you 
Don’t take this the wrong way, I’ll try to be as thorough as possible to be constructive and to help integrate your work 
A few remarks:
On the integration page, I find that the image is not in the right format:
(note, you need to search for « z-wave » with the dash)
If the devices list is empty, we don’t show a blue « alert » square on the other integrations; instead we usually show a text. It’s not very important, but it breaks consistency with the other services.
Display issue on a medium-sized screen:
Labeling issue with code:
Spacing and understanding issues (I’m not at all a Z-Wave expert, I don’t know whether I should fill in all the fields, or even what they mean, a small explanatory panel would be appreciated
Note, the localhost link doesn’t work because I’m using a remote server (raspberry).
So, I went with the integrated installation at first, and when clicking « Connect/Reconnect », I have some (non-blocking) errors that appear in the logs
2023-03-27T19:16:59+0200 \u003cerror\u003e installMqttContainer.js:57 (ZwaveJSUIManager.installMqttContainer) MQTT broker failed to install as Docker container: Error: (HTTP code 409) unexpected - Conflict. The container name \"/gladys-zwave-js-ui-mqtt\" is already in use by container \"f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d\". You have to remove (or rename) that container to be able to reuse that name.
at /src/server/node_modules/docker-modem/lib/modem.js:336:17
at getCause (/src/server/node_modules/docker-modem/lib/modem.js:366:7)
at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:335:5)
at IncomingMessage.\u003canonymous\u003e (/src/server/node_modules/docker-modem/lib/modem.js:303:16)
at IncomingMessage.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
reason: undefined,
statusCode: 409,
json: {
message: 'Conflict. The container name \"/gladys-zwave-js-ui-mqtt\" is already in use by container \"f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d\". You have to remove (or rename) that container to be able to reuse that name.'
}
}
2023-03-27T19:16:59+0200 \u003cerror\u003e index.js:15 (process.\u003canonymous\u003e) unhandledRejection catched: Promise {
\u003crejected\u003e Error: (HTTP code 409) unexpected - Conflict. The container name \"/gladys-zwave-js-ui-mqtt\" is already in use by container \"f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d\". You have to remove (or rename) that container to be able to reuse that name.
at /src/server/node_modules/docker-modem/lib/modem.js:336:17
at getCause (/src/server/node_modules/docker-modem/lib/modem.js:366:7)
at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:335:5)
at IncomingMessage.\u003canonymous\u003e (/src/server/node_modules/docker-modem/lib/modem.js:303:16)
at IncomingMessage.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
reason: undefined,
statusCode: 409,
json: {
message: 'Conflict. The container name \"/gladys-zwave-js-ui-mqtt\" is already in use by container \"f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d\". You have to remove (or rename) that container to be able to reuse that name.'
}
}
}
2023-03-27T19:16:59+0200 \u003cerror\u003e index.js:16 (process.\u003canonymous\u003e) Error: (HTTP code 409) unexpected - Conflict. The container name \"/gladys-zwave-js-ui-mqtt\" is already in use by container \"f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d\". You have to remove (or rename) that container to be able to reuse that name.
at /src/server/node_modules/docker-modem/lib/modem.js:336:17
at getCause (/src/server/node_modules/docker-modem/lib/modem.js:366:7)
at Modem.buildPayload (/src/server/node_modules/docker-modem/lib/modem.js:335:5)
at IncomingMessage.\u003canonymous\u003e (/src/server/node_modules/docker-modem/lib/modem.js:303:16)
at IncomingMessage.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1359:12)
at processTicksAndRejections (node:internal/process/task_queues:82:21) {
reason: undefined,
statusCode: 409,
json: {
message: 'Conflict. The container name \"/gladys-zwave-js-ui-mqtt\" is already in use by container \"f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d\". You have to remove (or rename) that container to be able to reuse that name.'
}
}
2023-03-27T19:17:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Mon, 27 Mar 2023 17:17:00 GMT
2023-03-27T19:17:03+0200 \u003cinfo\u003e installMqttContainer.js:54 (ZwaveJSUIManager.installMqttContainer) {
name: '/gladys-zwave-js-ui-mqtt',
image: 'eclipse-mosquitto:2',
state: 'created',
id: 'f36daed4ca294ad1555d79172eec835aeacf429c03c6d19bbb0bde8284125d1d',
networkMode: 'host',
created_at: 1679937418
}
Then I went to the « Discovery » page, having not yet connected any device other than the USB dongle, and the search keeps looping.
I’m afraid that this kind of active-search behavior might block other exchanges in other Gladys services.
Just after installing the container, I see this message:
Zwavejs UI version not supported: supported version 8.9.0 but current version is 8.11.1
But I didn’t do anything!!!
And to underline how incompetent I am with Z-Wave, on zwave-ui I have this error message:
Driver: Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)
at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4148:23)
at ZWaveController.identify (/usr/src/app/node_modules/zwave-js/src/lib/controller/Controller.ts:967:33)
at Driver.initializeControllerAndNodes (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1291:26)
at Immediate.\u003canonymous\u003e (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:1097:16) (ZW0100)
I hope my dongle isn’t too old…
I’ll stop here for tonight; I’ll try to get it working as soon as I have a bit more time.
Otherwise it’s still a great job, and count on us to help you fine-tune the details
