Cannot include new z-wave devices

[McFcologne]

When i start inclusion i get the following dialog:

It is a bit confusing like Schroedingers dialog... "Inclusion starting..." and "Inclusion stopped." at the same time. When i run debug logging inparallel, i can see the attempt:

2024-03-01 12:03:53.758 INFO APP: GET /health/zwave 301 1.199 ms - 191
2024-03-01 12:03:56.880 INFO Z-WAVE: [Node 012] Is now awake
2024-03-01 12:03:57.167 INFO Z-WAVE: [Node 012] Is now asleep
2024-03-01 12:04:16.034 INFO Z-WAVE: Calling api startInclusion with args: [ 2, { forceSecurity: false, name: ‘’, location: ‘’ }, [length]: 2 ]
2024-03-01 12:04:16.038 INFO Z-WAVE: Success zwave api call startInclusion false
2024-03-01 12:04:23.854 INFO APP: GET /health/zwave 301 0.953 ms - 191
2024-03-01 12:04:53.952 INFO APP: GET /health/zwave 301 0.900 ms - 191
2024-03-01 12:05:10.345 INFO Z-WAVE: Calling api startInclusion with args: [ 0, { forceSecurity: false, name: ‘ab’, location: ‘’ }, [length]: 2 ]
2024-03-01 12:05:10.350 INFO Z-WAVE: Success zwave api call startInclusion false
2024-03-01 12:05:24.078 INFO APP: GET /health/zwave 301 0.955 ms - 191
2024-03-01 12:05:31.185 INFO Z-WAVE: [Node 025] Value updated: 128-0-level 69 => 69
2024-03-01 12:05:31.192 INFO Z-WAVE: [Node 025] Value updated: 128-0-isLow false => false
2024-03-01 12:05:31.250 INFO Z-WAVE: [Node 025] Value updated: 67-0-setpoint-1 18.5 => 18.5

But there is nothing in the logs (logs/zwave_current.log)

[McFcologne]

No idea what happened.. i already startet anything yesterday with no success. Today, out of the blue it was working. Sometimes, doing the same again and again can cause different results:

It would anyway be interesting, why it did not work before without any error message.

[robertsLando]

Hi @McFcologne, unfortunately I cannot say much from your logs and I tried to reproduce this without success. If you can find a reliable way to reproduce this let me know.

The only thing I see is that startInclusion returns false and that means that the inclusion was already running on backend, I think that's the problem