#Cannot add Shelly Wave Motion EU LR

1 messages · Page 1 of 1 (latest)

proven forge
#

It started to display incorrectly in Z-Wave JS UI, so I removed it, did a factory reset and try to include it with Smart Start. I use Home Assistant Connect ZWA-2. Tried to add a few times, logs:

2026-01-24 16:09:41.292 INFO Z-WAVE: Controller status: Secure inclusion started
2026-01-24 16:09:46.366 INFO Z-WAVE: Controller status: Inclusion failed
2026-01-24 16:09:46.389 INFO Z-WAVE: Controller status: Inclusion stopped

2026-01-24 16:13:02.972 INFO Z-WAVE: Controller status: Secure inclusion started
2026-01-24 16:13:07.126 INFO Z-WAVE: Controller status: Inclusion stopped
2026-01-24 16:13:07.127 INFO Z-WAVE: [Node 272] Found
2026-01-24 16:13:07.127 DEBUG MQTT: Publishing to zwave/nodeID_272/status: { time: 1769271187127, value: false, status: 'Unknown', nodeId: 272 } with options { qos: 1, retain: true }
2026-01-24 16:13:17.694 INFO Z-WAVE: [Node 272] Removed, reason: SmartStartFailed
2026-01-24 16:13:17.715 INFO Z-WAVE-SERVER: Client disconnected
2026-01-24 16:13:17.715 DEBUG Z-WAVE-SERVER: Code 1000: 
2026-01-24 16:13:17.719 DEBUG Z-WAVE-SERVER: New client
distant arrow
#

Try excluding it once more. Even though it already is

proven forge
#

I tried it, enabled exlusion on Shelly with S button, but JS-UI said no devices to exclude found. But after 2 more Shelly factory resets it was found and added, but JS-UI said "Node 276 added with security None (Unknown)". Now I see it in JS-UI as Unknown manufacturer 0xXXXX. In Smart Start I added it as LR, S2 Access Control off, S2 Authenticated on and DSK (the same when I added first time after it worked for 2 months). Inclusion log:

2026-01-25 09:09:05.661 INFO Z-WAVE: Controller status: Secure inclusion started
2026-01-25 09:09:10.292 INFO Z-WAVE: Controller status: Inclusion stopped
2026-01-25 09:09:10.294 INFO Z-WAVE: [Node 276] Found
2026-01-25 09:09:10.295 DEBUG MQTT: Publishing to zwave/nodeID_276/status: { time: 1769332150295, value: false, status: 'Unknown', nodeId: 276 } with options { qos: 1, retain: true }
2026-01-25 09:09:15.360 DEBUG Z-WAVE: [Node 276] Binding to node events
2026-01-25 09:09:15.363 DEBUG MQTT: Publishing to zwave/nodeID_276/status: { time: 1769332155363, value: true, status: 'Alive', nodeId: 276 } with options { qos: 1, retain: true }
2026-01-25 09:09:15.363 DEBUG Z-WAVE: [Node 276] Has been added to nodes array
2026-01-25 09:09:15.363 INFO Z-WAVE: [Node 276] Added with security None
2026-01-25 09:09:15.571 DEBUG MQTT: Publishing to zwave/nodeID_276/lastActive: { time: 1769332155571, value: 1769332155359 } with options { qos: 1, retain: true }
#

I tried it to exlude, reset and add one more time - failed.

paper vector
proven forge
paper vector
#

In that instance looks like the failure is somewhere in the controller, doesn't even make it far enough for Z-Wave JS to do anything. You might try unplugging/re-plugging the controller.

2026-01-25 08:26:06.800 SERIAL « 0x0108004a3d0701100096                                              (10 bytes)
2026-01-25 08:26:06.801 SERIAL » [ACK]                                                                   (0x06)
2026-01-25 08:26:06.802 DRIVER « [REQ] [AddNodeToNetwork]
                                   status:      Failed
                                   callback id: 61
2026-01-25 08:26:06.802 CNTRLR   Adding the node failed
2026-01-25 08:26:06.803 CNTRLR   stopping inclusion process...
proven forge
#

tried it, but will try once more. Did not help. I use wifi firmware for the ZWA-2. - could it be the problem?

#

I used standard firmware when I added Shelly device the first time.

proven forge
#

tried with another Power adapter - did not help.

distant arrow
#

Same error?

proven forge
#

yes, similar, I can upload new debug logs if needed

#

will probably try with standard firmware if there are no more suggestions

proven forge
distant arrow
#

seems to have timed out: The page you requested was not found.

proven forge
distant arrow
#

Not sure what's going on in your house, but this is significant noise:

measured noise floor:                  -65 dBm
measured noise floor by destination:   -67 dBm
#

like significant SIGNIFICANT

#

that's around 45 dBm higher than it should be, or over 30000x

#

and even right before you started joining the device it was already bad:

channel 0: -87 dBm
channel 1: -89 dBm
channel 2: -89 dBm
channel 3: -82 dBm
proven forge
#

There is ambulance station about 500m away, which caused problems before - could be it?

proven forge
distant arrow
#

A few spot checks tell me it's still not great:

measured noise floor by destination:   -72 dBm
measured noise floor:                  -75 dBm
channel 0: -106 dBm
channel 1: -108 dBm
channel 2: -108 dBm
channel 3: -82 dBm