Well, or perhaps time to throw it out. Too many sensors, too many parameters…that do not work.
I think the errors with 22 are related to the Multi CC (bit 5), which is probably unsupported. It still works though (for me). Try setting the log level higher, to see if it does anything at all.
I’ve been at the point of throwing it out many times myself. Perhaps even z-wave altogether 
…
1 Like
Log Level changed to: Verbose
2021-09-01T12:00:51.108Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultiCommandCCCommandEncapsulation]
2021-09-01T12:00:51.113Z DRIVER Received a command that contains multiple CommandClasses. This is not supporte
d yet! Discarding the message…
2021-09-01T12:00:51.115Z CNTRLR « [Node 006] TODO: no handler for application command
2021-09-01T12:00:55.050Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultiCommandCCCommandEncapsulation]
2021-09-01T12:00:55.054Z DRIVER Received a command that contains multiple CommandClasses. This is not supporte
d yet! Discarding the message…
2021-09-01T12:00:55.056Z CNTRLR « [Node 006] TODO: no handler for application command
DEBUG level
2021-09-01T12:05:42.743Z SERIAL « 0x011f00040006198f010403800364043003ff0c05310503011c063105010a004c0 (33 bytes)
b
2021-09-01T12:05:42.746Z CNTRLR [Node 006] [~] [Battery] level: 100 => 100 [Endpoint 0]
2021-09-01T12:05:42.749Z CNTRLR [Node 006] [~] [Battery] isLow: false => false [Endpoint 0]
2021-09-01T12:05:42.752Z CNTRLR [Node 006] [Binary Sensor] Motion: metadata updated [Endpoint 0]
2021-09-01T12:05:42.754Z CNTRLR [Node 006] [~] [Binary Sensor] Motion: false => true [Endpoint 0]
2021-09-01T12:05:42.757Z CNTRLR [Node 006] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2021-09-01T12:05:42.759Z CNTRLR [Node 006] [~] [Multilevel Sensor] Illuminance: 28 => 28 [Endpoint 0]
2021-09-01T12:05:42.762Z CNTRLR [Node 006] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2021-09-01T12:05:42.765Z CNTRLR [Node 006] [~] [Multilevel Sensor] Air temperature: 76 => 76 [Endpoint 0]
2021-09-01T12:05:42.767Z SERIAL » [ACK] (0x06)
2021-09-01T12:05:42.775Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultiCommandCCCommandEncapsulation]
2021-09-01T12:05:42.778Z DRIVER Received a command that contains multiple CommandClasses. This is not supporte
d yet! Discarding the message…
2021-09-01T12:05:42.779Z CNTRLR « [Node 006] TODO: no handler for application command
Ah there you go: 2021-09-01T12:05:42.754Z CNTRLR [Node 006] [~] [Binary Sensor] Motion: false => true [Endpoint 0]. This should have changed one of the entities …
So here is the door opening…
2021-09-01T12:18:37.237Z SERIAL « 0x011f00040006198f010403800364043003ff0a05310503011e063105010a004c0 (33 bytes)
f
2021-09-01T12:18:37.244Z CNTRLR [Node 006] [~] [Battery] level: 100 => 100 [Endpoint 0]
2021-09-01T12:18:37.248Z CNTRLR [Node 006] [~] [Battery] isLow: false => false [Endpoint 0]
2021-09-01T12:18:37.254Z CNTRLR [Node 006] [Binary Sensor] Door/Window: metadata updated [Endpoint 0]
2021-09-01T12:18:37.258Z CNTRLR [Node 006] [~] [Binary Sensor] Door/Window: false => true [Endpoint 0]
2021-09-01T12:18:37.263Z CNTRLR [Node 006] [Multilevel Sensor] Illuminance: metadata updated [Endpoint 0]
2021-09-01T12:18:37.265Z CNTRLR [Node 006] [~] [Multilevel Sensor] Illuminance: 27 => 30 [Endpoint 0]
2021-09-01T12:18:37.271Z CNTRLR [Node 006] [Multilevel Sensor] Air temperature: metadata updated [Endpoint 0]
2021-09-01T12:18:37.274Z CNTRLR [Node 006] [~] [Multilevel Sensor] Air temperature: 76 => 76 [Endpoint 0]
2021-09-01T12:18:37.276Z SERIAL » [ACK] (0x06)
2021-09-01T12:18:37.279Z DRIVER « [Node 006] [REQ] [ApplicationCommand]
└─[MultiCommandCCCommandEncapsulation]
2021-09-01T12:18:37.283Z DRIVER Received a command that contains multiple CommandClasses. This is not supporte
d yet! Discarding the message…
2021-09-01T12:18:37.285Z CNTRLR « [Node 006] TODO: no handler for application command
this seems ok. Now all you need to do is find the right entity. You’d best enable all entities for the device and see which one corresponds … and then disable what you don’t need afterwards (at least that is what I did)
How can I tell what entity it is, at least in any reasonable manner?
I enabled all the entities and just looked at the device integration page to see which value changed with movement or open/close. I could check to see what the default names are for the entities that work for me. Will have to do that later though.
Easy peasy. Found it.
binary_sensor.door_sensor_top_floor_br_door_window
So, automation triggers now. Just did not notify me…time to go down that rabbit hole.
yeah depends on the attribute type, quite confusing. I’m not entirely sure by heart, but don’t rely on the logging. Better open the entity and see what the value is now, or better even the developer tools > states. Could be true/false, open/close, on/off, etc. If you want to try it out, i’d suggest using the template editor in development tools to see what works.
I got it working, just had to raise to priority. The only issue appears that it notifies on open and close. So I will need to put in something to put it just on open.
Thank you for all your help! One less item headed to the trash!
great to be able to help! Good luck with the finishing touch
Hi Vinx,
Could you please confirm what value you put into param 7?
I keep trying to get it working with either 22, 20, 6, 118, 102 and this doesn’t work for me…
If I go for the notification mode: it triggers once to “motion detection” and never get back to “no motion”
If I go for the binary sensor mode: the motion sensor triggers to “true” then back to “false” then back to “true”…
Strange thing is that the door/sensor is working properly
I’m struggling with this sensor for months now and I’m getting crazy…
Thanks in advance,
Hi Antoine,
It seems you’ve tried a lot already and you’re further than I’ve been for a long time 
The inability to pick up the no-motion is what I’ve seen before as well (described somewhere in my rant up here). My conclusion there , is that the notification is not recognized, probably a HA bug (but I don’t know where to report it. At least it doesn’t seem to be picked up from our conformation here). So 102 would only work for devices without motion (for now)
The true/false/true behavior I haven’t seen. At least not on this device … I’ve got that with a Neo device, see this topic. Is your problem indeed similar to that? Could it be software (HA) related?
I also added a screenshot my Excelsheet for calculating the config values, which can be confusing (you probably have that already, but perhaps for others)
Hi,
Thanks for the feedback and your time.
Regarding the no motion report, I’ve received some piece of info from the Zwave-js on github following to an issue I opened:
https://github.com/zwave-js/node-zwave-js/issues/2674
It seems to be related to Zwave-js which needs to be updated to understand the no motion state.
For the true/false/true/… behavior I have to say that I have no idea of what is going on. I tried to reduce the PIR sensitivity but even when the sensor is in put inside a box it triggers so…
The issue you linked lloks like mine excet that it never stops to trigger, which seems to be the case at a time for you.
Will try to reset it again and see what’s going to happen.
Regards,
Alright, good. Let us know if you can find out more.
Hi,
I did try to reset the sensor but no luck…
Could you let me know which version of the firwmare has your sensor?
Here is mine, I do not know if it can have an impact
Thanks and Regards,
Where do you see this? I only see this (for two seperate devices)
