Smartwings drapery - Z-Wave 800 LR not pairing

🛎️ Get Help Devices
1

I got a Smartwings Drapery rod with the Z-Wave 800 LR engine today. I am able to pair the remote which come with it an test that it works but I do not seem to be able to pair it to Hubitat.

I have a C-8 Pro controller running z-wavejs.

According to Smartwings documentation this should work well.

I am seated in Europe and the device is supposed to be EU compatible but there is no info on the device itself stating which frequency its on (it has a correct European power plug). The serial number of the device seem to be WK82T/V.

Anyone encountered the same issue?

2

I’m not showing the drapery rod is certified for the eu region. This is the official list, in case i missed something. If you also confirm what you bought is not on the certified list, i would contact smartwings support.
https://products.z-wavealliance.org/?_zwa_brand=smartwings&_zwa_region=eu&_zwa_frequency=eu

1 Like
3

I checked this with Smartwings before I bought them and they verified that it would be delivered with European z-wave frequency.

4

The exact engine for the drapery is not listed for any frequency: Z-Wave Alliance Product Catalog

The manual which come with it do state it exist for US, EU and AU.

5

Are you using SmartStart to pair?

If so, it may be trying to pair LR (SmartStart defaults to that for LR-capable devices [at least in the US here]), but Hubitat doesn't have a LR option for regions outside of the US yet.

Although I don't recall the process details, I know it's possible to tell SmartStart to pair it mesh instead... Or you could just try pairing the old way (no SmartStart).

2 Likes
6

I have tried both. First tried the old way, then SmartStart. Not much success with either.

I've contacted SmartWings customer support so we will see if they can provide more info.

7

If LR frequency is not enabled then it doesn't attempt to include over LR..

2 Likes
8

If you are on ZWave-JS there might be more information in the z-wave logs.. If something happened during the inclusion process that caused it to fail there should be a lot of information here.. If it's not being picked up due to wrong frequency/etc it won't have anything here..

Just to verify, as I didn't see it in the thread here, have you tried to run an exclude on it first? Some devices have come from the factory already included (usually a test hub at the factory)..

1 Like
9

ZWave-JS there might be more information in the z-wave logs..

Are these logs in the UI or are there other ways to access them (SSH and on the file system)? I don't see any info in the UI logs. I see that Hubitat go into inclusion mode and then there is nothing in the logs in the UI.

Just to verify, as I didn't see it in the thread here, have you tried to run an exclude on it first?

I have tried to exclude it and also did a factory reset (I found instructions for such somewhere online).

10

Found the z-wave log :slight_smile:

When I run the inclusion this is what I get in the z-wave log:

2026-03-21 12:32:54.777CNTRLR The inclusion process was stopped
2026-03-21 12:32:54.774SERIAL » [ACK] (0x06)
2026-03-21 12:32:54.772SERIAL « 0x0108004ab0060000000b (10 bytes)
2026-03-21 12:32:54.769SERIAL « [ACK] (0x06)
2026-03-21 12:32:54.767DRIVER » [REQ] [AddNodeToNetwork] - action: Stop - high power: true - network wide: true - callback id: 176
2026-03-21 12:32:54.764DRIVER one or more queues busy
2026-03-21 12:32:54.761CNTRLR stopping inclusion process...
2026-03-21 12:32:48.707SERIAL » [ACK] (0x06)
2026-03-21 12:32:48.705DRIVER « [Node 009] [REQ] [BridgeApplicationCommand] - │ type: broadcast - │ target node: 255 - │ RSSI: -76 dBm - └─[Security2CCMessageEncapsulation] [INVALID] - error: Multicast frames without MGRP extension
2026-03-21 12:32:48.703DRIVER Dropping message with invalid payload
2026-03-21 12:32:48.700SERIAL « 0x012000a81400010009129f03150054e41b5d807a97e46a7f0f04221500b400000 (34 bytes) - 012
2026-03-21 12:32:46.350DRIVER Dropping message with invalid payload
2026-03-21 12:32:46.346SERIAL « 0x012000a81400010009129f03140001b394b4cacb7060920f8d401c3b00b500000 (34 bytes) - 0b0
2026-03-21 12:32:34.621DRIVER all queues idle
2026-03-21 12:32:34.618SERIAL » [ACK] (0x06)
2026-03-21 12:32:34.617SERIAL « 0x0107013b9f9d9da3fe (9 bytes)
2026-03-21 12:32:34.614SERIAL « [ACK] (0x06)
2026-03-21 12:32:34.611SERIAL » 0x0103003bc7 (5 bytes)
2026-03-21 12:32:34.610DRIVER one or more queues busy
2026-03-21 12:32:22.199DRIVER Dropping message with invalid payload
2026-03-21 12:32:22.196SERIAL « 0x011d00a814000100090f9f031300f9e74350f54ba03fe58b8c00b4000000ac (31 bytes)
2026-03-21 12:32:19.793DRIVER Dropping message with invalid payload
2026-03-21 12:32:19.790SERIAL « 0x011e00a81400010009109f031200f44c2aa77658c4599e9139de00b500000010 (32 bytes)
2026-03-21 12:32:16.713DRIVER « [Node 009] [REQ] [BridgeApplicationCommand] - │ type: broadcast - │ target node: 255 - │ RSSI: -76 dBm - └─[Security2CCMessageEncapsulation] [INVALID] - error: Multicast frames without MGRP extension
2026-03-21 12:32:16.710DRIVER Dropping message with invalid payload
2026-03-21 12:32:16.708SERIAL « 0x011d00a814000100090f9f031100486f0f57fdb351a7ace2db00b400000032 (31 bytes)
2026-03-21 12:32:14.674DRIVER Dropping message with invalid payload
2026-03-21 12:32:14.670SERIAL « 0x012000a8140001000a129f0336006a1241f7fab57675ef77063fbea500bf00000 (34 bytes) - 057
2026-03-21 12:32:12.153DRIVER « [Node 010] [REQ] [BridgeApplicationCommand] - │ type: broadcast - │ target node: 255 - │ RSSI: -64 dBm - └─[Security2CCMessageEncapsulation] [INVALID] - error: Multicast frames without MGRP extension
2026-03-21 12:32:12.153SERIAL » [ACK] (0x06)
2026-03-21 12:32:12.149SERIAL « 0x012000a8140001000a129f033500a95697ef8b39cf39073a78cce9b800c000000 (34 bytes) - 008
2026-03-21 12:32:04.622DRIVER all queues idle
2026-03-21 12:32:04.620SERIAL » [ACK] (0x06)
2026-03-21 12:32:04.617SERIAL « 0x0107013b9f9f9fa3fe (9 bytes)
2026-03-21 12:32:04.614SERIAL « [ACK] (0x06)
2026-03-21 12:32:04.611SERIAL » 0x0103003bc7 (5 bytes)
2026-03-21 12:32:04.608DRIVER one or more queues busy
2026-03-21 12:31:40.763SERIAL » [ACK] (0x06)
2026-03-21 12:31:40.761DRIVER « [Node 010] [REQ] [BridgeApplicationCommand] - │ type: broadcast - │ target node: 255 - │ RSSI: -65 dBm - └─[Security2CCMessageEncapsulation] [INVALID] - error: Multicast frames without MGRP extension
2026-03-21 12:31:40.758SERIAL « 0x011e00a8140001000a109f0333003a8d6af0c6a4be2b386b214400bf000000ba (32 bytes)
2026-03-21 12:31:38.271SERIAL » [ACK] (0x06)
2026-03-21 12:31:38.267SERIAL « 0x011d00a8140001000a0f9f03320020c0cfc2e5d9a39004b2a800c0000000c8 (31 bytes)
2026-03-21 12:31:35.965SERIAL » [ACK] (0x06)
2026-03-21 12:31:35.963DRIVER Dropping message with invalid payload
2026-03-21 12:31:35.960SERIAL « 0x012000a8140001000a129f033100b715f076e95e1d8c3ea13867090100bf00000 (34 bytes) - 0a2
2026-03-21 12:31:34.622DRIVER « [RES] [GetBackgroundRSSI] - channel 0: -97 dBm - channel 1: -100 dBm - channel 2: -100 dBm - channel 3: -91 dBm
2026-03-21 12:31:34.621SERIAL » [ACK] (0x06)
2026-03-21 12:31:34.619SERIAL « 0x0107013b9f9c9ca5f8 (9 bytes)
2026-03-21 12:31:34.615SERIAL « [ACK] (0x06)
2026-03-21 12:31:34.610DRIVER » [REQ] [GetBackgroundRSSI]
2026-03-21 12:31:34.609DRIVER one or more queues busy
2026-03-21 12:31:25.691DRIVER « [Node 014] [REQ] [BridgeApplicationCommand] - │ type: broadcast - │ target node: 255 - │ RSSI: -54 dBm - └─[Security2CCMessageEncapsulation] [INVALID] - error: Multicast frames without MGRP extension
2026-03-21 12:31:25.690DRIVER Dropping message with invalid payload
2026-03-21 12:31:25.686SERIAL « 0x012000a8140001000e129f03dd00580dc8c493ae52c5876b68733ec700ca00000 (34 bytes) - 008
2026-03-21 12:31:07.985CNTRLR The controller is now ready to add nodes

11

Can you also post your z-wave details page in it's entirety? Use windows snip.

1 Like
12

Here you go :slight_smile:

devices
devices1675×2289 387 KB

1 Like
13

So; I've heard from Smartwings and it seems like they wrongly have sent me a non EU region engine. They are sending me a new one so lets see :slight_smile:

2 Likes
14

For the record;

I got the replacement engine for my drapes from SmartWings today and it includes easily so the first engine I got was clearly the wrong frequency.

image
image1384×65 13.4 KB

It works perfectly with the Generic Z-Wave DT Window Covering driver. The engine includes as these SmartWings engines so I assume its the same engine in the drapes as they use in the tube engines for roller curtains.

The only thing is that I could not use the button on the engine itself to include it. Using the remote which comes with the engine works perfectly.

Anyhow; thanks for all the help everyone :slight_smile:

1 Like