Z-Wave JS to MQTT Develo devices

Hi,

I migrated from the OpenZwave integration to Z-Wave JS to MQTT. Alot of Devolo devices are not working anymore though;

  1. Devolo Scene Switch SKU: MT2652
  2. Devolo Smoke Detector SKU: MT2651
  3. Devolo RS 014G0159 Thermostat
  4. Devolo Motion Sensor SKU: MT02647
  5. Devolo Door Window Contact SKU: MT02648

For example; Node 34 is ‘Awake’ but seems to hang in ‘ProtocolInfo’

{
  "id": 34,
  "deviceId": null,
  "manufacturer": null,
  "manufacturerId": null,
  "productType": null,
  "productId": null,
  "name": "",
  "loc": "",
  "values": [],
  "groups": [],
  "neighbors": [],
  "ready": false,
  "available": false,
  "hassDevices": {},
  "failed": false,
  "lastActive": null,
  "interviewCompleted": false,
  "firmwareVersion": null,
  "isBeaming": false,
  "isSecure": false,
  "keepAwake": false,
  "maxBaudRate": null,
  "isRouting": null,
  "isFrequentListening": false,
  "isListening": false,
  "status": "Unknown",
  "interviewStage": "ProtocolInfo",
  "_name": "NodeID_34"
}

The devices are all battery powered. I tried restarting a couple of times, and even waited a few days. Also ‘Heal node’ or ‘Re-interview node’ does nothing. If i press a button on the devices nothing gets logged in the debugging page. How can i fix this?

Edit; same happens with the Z-Wave JS integration.

I haven’t checked the default check in times but I suppose your issue is similar? Don’t restart the addon and force the devices to check in until the interview etage is completed

Unfortunately, i already let the devices wait for more dan a day now. And if i read the manual from (for example) the smoke detector, it says:
https://manual.zwave.eu/backend/make.php?lang=en&sku=DEVE9875&cert=ZC10-14080006

“To wakeup the device please perform the following action: Press program switch once, the detector will send NIF signal first and will also send Wake Up Notification after 3 seconds.”

I tried that but nothing in the logging, the status ProtocolInfo seems to be stuck here… Anyone that knows how to fix this?

Are the devices within range of powered Z-Wave devices that are working? Is there any of the Devolo sensors you can bring closer to your Z-Wave hub (stick?) to see if they communicate at that point?
Are the devices added secure or insecure? Are other devices working that are added the same way?

Good hint! But unfortunately the same result… :roll_eyes: The devices are all relatively close to the Aeon stick and moving even closer does not change it. Maybe i miss something in the whole procedure of getting info from the devices?

Is there any way we can check if there are certain devices not yet supported by Zwave JS?

Device configuration files (zwave-js.github.io)
and
node-zwave-js/packages/config/config/devices at master · zwave-js/node-zwave-js (github.com)

I believe these are the files you should be looking at/for. Have you added the nodes securely and if so, is your network key still correct/the same?

It seems the devices are in there, so they should work. But i tried everything, restarting a couple of times and waiting for the network/ pushing on devices but no luck. Almost all devices (exept the Fibaro one) are not added secure in the past. The network key is the same as with the OpenZwave integration.

In OpenZwave it was: 0xXX,0xXX,0xXX,0xXX,0x64,0x4A,0x83,0xD7,0x86,0x46,0x49,0x93,0x91,0x36,0x70,0x91 (code is a bit modified at the start for obvious reasons)
In Zwave JS to Mqtt:
XXXXXX78644A83D78646499391367091

I also now see that one of my Fibaro double-switches is not in the ‘Completed’ stage;

That one is the only secure added device. Is something wrong with my config?

It has finished reading all of the manufacturer information before, so it must have worked at some point. The last message is also probably recent, so the Fibaro devices should work I suppose. Last thing I can think of is interference on your Z-Stick, can you provide more details on your hardware and how it’s attached? For example, using a Raspberry Pi 4 with USB 2 hub, running from SSD/USB.

I run a Hassio VM on a Synology Ds918+ Nas. The USB devices are passed trough and are working. I use a ‘AEON Labs Z‐Stick Gen5 USB Controller’ Other Z-Wave devices work without issues and even quite fast. All devices are not more dan 20 meters away.

Strange thing is that after re-saving the security key it seems to get better now (after a couple of reboots). The Fibaro’s are working!

Only struggling with 2 devolo devices now;

Devolo Door Window Contact SKU: MT02648 (Node 31)
Devolo Scene Switch SKU: MT2652 (Node 34)

If i look at the logging, it seems that something is wrong:

2021-03-01 17:20:59.640 INFO ZWAVE: Calling api refreshInfo with args: [ 34, [length]: 1 ]
2021-03-01 17:20:59.688 INFO ZWAVE: Success zwave api call refreshInfo { success: true, message: 'Success zwave api call', result: undefined }
2021-03-01 17:21:02.970 INFO ZWAVE: Node 34: metadata updated: 91-0-scene-002
2021-03-01 17:21:02.985 INFO ZWAVE: Node 34: value notification: 91-0-scene-002 0
2021-03-01 17:21:05.918 INFO ZWAVE: Node 34: metadata updated: 91-0-scene-001
2021-03-01 17:21:05.926 INFO ZWAVE: Node 34: value notification: 91-0-scene-001 0
2021-03-01 17:21:07.461 ERROR ZWAVE: Interview of node 34 has failed: Attempt 1/5 failed
2021-03-01 17:21:07.486 INFO ZWAVE: Node 34 is asleep
2021-03-01 17:21:15.357 INFO ZWAVE: Node 34: value notification: 91-0-scene-002 0
2021-03-01 17:21:19.797 INFO ZWAVE: Node 34: value notification: 91-0-scene-002 0
2021-03-01 17:21:21.817 INFO ZWAVE: Node 34: value notification: 91-0-scene-001 0
2021-03-01 17:21:23.562 INFO ZWAVE: Node 34: value notification: 91-0-scene-002 0

The last value notification/ scene updates are from the device (pushes by me on the buttons), so there is communication. Only the interview fails every time.

Ok update, so I updated to version 6.0 yesterday. All devices are suddenly recognized! Finally! Except for the wall switch:


Strange is that i can see updates from this device, so it works as normal;

{
    "event_type": "zwave_js_event",
    "data": {
        "type": "value_notification",
        "domain": "zwave_js",
        "node_id": 34,
        "home_id": 3491824269,
        "endpoint": null,
        "device_id": "3d55e589d1799d7f3873e100ca670759",
        "command_class": 91,
        "command_class_name": "Central Scene",
        "label": "Scene 001",
        "property_name": "scene",
        "property_key_name": "001",
        "value": 0
    },
    *snip*

But, now it seems that open/close sensors are not updating in Home Assistant. I can see this in the logging for my garage door-sensor (the Devolo Door Window Contact SKU: MT02648);

2021-03-04 10:06:18.560 INFO ZWAVE: Node 31: value updated: 128-0-level 100 => 100
2021-03-04 10:06:18.564 INFO ZWAVE: Node 31: value updated: 128-0-isLow false => false
2021-03-04 10:06:18.566 INFO ZWAVE: Node 31: metadata updated: 48-0-Door/Window
2021-03-04 10:06:18.571 INFO ZWAVE: Node 31: value updated: 48-0-Door/Window false => true
2021-03-04 10:06:18.573 INFO ZWAVE: Node 31: metadata updated: 49-0-Illuminance
2021-03-04 10:06:18.578 INFO ZWAVE: Node 31: value updated: 49-0-Illuminance 4 => 7
2021-03-04 10:06:18.580 INFO ZWAVE: Node 31: metadata updated: 49-0-Air temperature
2021-03-04 10:06:18.584 INFO ZWAVE: Node 31: value updated: 49-0-Air temperature 56 => 56

But in Home Assistant nothing ever happens;
image
It always stays closed. Same thing happens to the motion sensor (Devolo Motion Sensor SKU: MT02647)

Any clue how to fix it? It seems as if i’m really close to getting it all running…

Hi @s4nder

I have the same problem. In my ZWave-JS log is a error message if I close / open the devolo door/windows sensor:
“DRIVER Received a command that contains multiple CommandClasses. This is not supporte
d yet! Discarding the message…”

Think that this is the reason and we have to wait till the implementation from multiple CommandClassis is done.

Or do you fix it already? If yes please tell me how.

Thanks for this pointer, that got my newly acquired MT02648 working.

Parameter 7 is a bit mask allowing various reporting settings to be changed. Bit 5 enables or disables “Multi CC” (which I assume means multiple CommandClasses) It was set to 0, so I changed it to 1 to disable multiple CC and now open/close alerts are working.

TL;DR: Add 16 to the current value of parameter 7 (mine was 20 despite the manual saying it should be 4. Changed it to 36)

2 Likes

Hello, is there a workaround. My motion detector is not working.
I have already changed parameter 7 to 22, unfortunately this does not work either.
Here my settings:
PARAMETER 2 Basic Set Level
Setting the BASIC command value to turn on the light.
255

PARAMETER 3 PIR Sensitivity
Set the sensitivity for the PIR (Passive Infrared Sensor).
80

PARAMETER 4 Light Threshold
Set the illumination threshold to turn on the light.
99

PARAMETER 5 Operation Mode
Parameter to set the Operation Mode
4

PARAMETER 6 Multi-Sensor Function Switch
Parameter to set the sensor functions.
21

PARAMETER 7 Customer Function
Parameter to set the Customer Function.
20

PARAMETER 8 PIR Re-Detect Interval Time
Setting the re-detect time after motion detected
3

PARAMETER 9 Turn Off Light Time
Setting delay time to turn off the light when no motion
4

PARAMETER 10 Auto Report Battery Time
The interval time for auto reporting the battery level.
12

PARAMETER 11 Auto Report Door/Window State Time
Interval time for auto reporting the door/window state.
12

PARAMETER 12 Auto Report Illumination Time
The Interval time for auto reporting the illumination state.
12

PARAMETER 13 Auto Report Temperature Time
The interval time for auto reporting the temperature state.
12

PARAMETER 20 Auto Report Tick Interval
The interval time for each auto report tick.
30

PARAMETER 21 Temperature Differential Report
1

PARAMETER 22 Illumination Differential Report
0

I did get my MT02648 working with Z-wave JS. These are my settings:

Now it is reporting just fine in Home Assistant. Can you review these settings?

Hey, thanks for your quick reply, can you also give me your settings for the MT02647 (motion detector), thank you.

No problem;

1 Like

Thank you for the info. Unfortunately the settings don’t work for me. I always get an error message. Which Z-Wave controller are you using? Maybe it’s because of that. I have a RaZberry Controller 2016 ZWave+.

Hi, On the devolo motion sensor, I’ve changed Parameter 5 to 12 and parameter 7 to 22, wait a few minute, then start a device rediscovery. Then the motion sensor started to work are expected.

thank you :slight_smile: