Fibaro Z-Wave Motion Sensor

I just got some logs through on both sensors looks similar to Johns

guys, thats great i can work with that. leave it with me and i will update my device type. can you also knocking the sensor from behind without triggering PIR and give me the logs of that

With pleasure!:

[code]

e8e0328b-a3d8-4903-a7ee-1b7f27e89df8 ‎12‎:‎37‎:‎28: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Detector]]

e8e0328b-a3d8-4903-a7ee-1b7f27e89df8 ‎12‎:‎37‎:‎28: debug Catchall reached for cmd: NotificationReport(event: 3, eventParameter: [], eventParametersLength: 0, notificationStatus: 255, notificationType: 7, reserved61: 0, sequence: false, v1AlarmLevel: 0, v1AlarmType: 0, zensorNetSourceNodeId: 0)}

e8e0328b-a3d8-4903-a7ee-1b7f27e89df8 ‎12‎:‎37‎:‎28: debug encapsulated: NotificationReport(event: 3, eventParameter: [], eventParametersLength: 0, notificationStatus: 255, notificationType: 7, reserved61: 0, sequence: false, v1AlarmLevel: 0, v1AlarmType: 0, zensorNetSourceNodeId: 0) [/code]

Edit: In fact given that that’s identical, I probably inadvertently triggered the motion sensor.

This is probably right:

[code]e8e0328b-a3d8-4903-a7ee-1b7f27e89df8 ‎12‎:‎43‎:‎49: debug Parse returned [[isStateChange:false, displayed:false, linkText:Fibaro Motion Detector]]

e8e0328b-a3d8-4903-a7ee-1b7f27e89df8 ‎12‎:‎43‎:‎49: debug Catchall reached for cmd: NotificationReport(event: 8, eventParameter: [], eventParametersLength: 0, notificationStatus: 255, notificationType: 7, reserved61: 0, sequence: false, v1AlarmLevel: 0, v1AlarmType: 0, zensorNetSourceNodeId: 0)}

e8e0328b-a3d8-4903-a7ee-1b7f27e89df8 ‎12‎:‎43‎:‎49: debug encapsulated: NotificationReport(event: 8, eventParameter: [], eventParametersLength: 0, notificationStatus: 255, notificationType: 7, reserved61: 0, sequence: false, v1AlarmLevel: 0, v1AlarmType: 0, zensorNetSourceNodeId: 0) [/code]

ok cool thanks, it all makes sense really, they are now using notification reports of type 7 which is Burglar…

anyway i have added the code for notification reports so i am hoping provided the bit from the logs are accurate, this should send the events for motion and acceleration. please check to see if both are triggered, they may be the wrong way around i.e you get vibration for Motion and vice versa. and i am not 100% sure that the alarm frame cancellation will work either so if motion triggers wait to see if it goes back to no motion etc…

if not let me know and i will do more verbose logging

P.S. i’m using a completely made up fingerprint below, can someone get me the correct fingerprint reported by the device, if so then when you install any new devices it will use my device handler by default (maybe!?)

fingerprint deviceId: “0x2001”, inClusters: “0x30,0x84,0x85,0x80,0x8F,0x56,0x72,0x86,0x70,0x8E,0x31,0x9C,0xEF,0x30,0x31,0x9C,0x98,0x71”

1 Like

Really happy to see this being worked on. Kind of disappointing now that I got an old model. Probably move that into the kitchen and get a new one for the living room when the time comes.

That one’s a no go. Happily I now have a phone with ST installed.

Changing the device handler and rejoining/config button didn’t work.
Removing the device and handler completely, reinstalling/recreating with the new handler gave exactly the same result, constant motion and constant vibration.

Ok Basic question here… how can I get the device fingerprint? is there anyway of picking it up in the IDE?

Also same results as John I may be misreading this but it appears to me that the fibaro device is not reading the configuration message

you now don’t need to use the config every update, thats a onetime thing, the device is now associated to groups 1-5 so that doesn’t need done.

can i ask what you see in the logs now?

based on the output you put in place i would expect you to now see debug entries stating one or more of the below

Motion Detected
Motion No Longer Detected
Vibration Detected
Vibration No Longer Detected

forget about what the tiles say at the moment, just check the logs, as these entries are part of the notificationreport parsing based on the log extract you sent for Vibration/Motion when it hit the catch all block previously.

i have just added some additional debug logging to the device type. please use the new code and forget about the tiles for the moment just look at the IDE logs when you wave at the sensor and also knock it.

@Silverpawn when the device joins the zwave network if you goto locations and show events you will see the join event and the fingerprint is contained in that…if someone wants to exclude the device and re-include you will get the fingerprint from there

OK First things first I think this is the signature you’re looking for

deviceTypeId 1eb4e7da-099c-46be-a74e-6e916af7a982

If it isn’t let me know

johns definitely got the configure block as he got notification reports for motion and vibration which are set to Association Group 2 & 3 respectively. i just need what is in the logs at the mo, don’t care about the tiles displaying the values yet.

also the is the devices GUID not the fingerint, will look something like
0x2001", inClusters: 0x30,0x84,0x85,0x80,0x8F,0x56,0x72,0x86,0x70,0x8E,0x31,0x9C,0xEF,0x30,0x31,0x9C,0x98,0x71"

this is where we could really do with being able to create temp accounts with limited role based access, just so you could give me access to just that device and i could work on it…for you to do it with your account now would be like giving me root access to your IOT…not advised…ST are you listening?

1 Like

Thanks Stuart

I’m not getting motion or vibration on the Logs

Which makes me think resetting the device via the rest button pulled the config for John.

When I get home tonight I’ll do a exclude and re-add for my sensors and then a manual pull on the config via the reset button

(by default it appears to pull the smoke detector config).I’ll keep an eye out for the signature while I’m at it in the logs.

We’ll see if that helps. Thanks for the work so far

Reading the ST Docs the fingerprint is in the Raw description field.

Mine reads Device Id 0X0701
In Clusters 0x5E 0x20 0x86 0x72 0x5A 0x59 0x85 0x73 0x84 0x80 0x71 0x56 0x70 0x31 0x8E 0x22 0x30 0x9C 0x98 0x7A

I’m Assuming that doesn’t get changed when you change device type.

Ok - so I had 5 minutes to go back and look at the sim.

Motion gives: [code]

1d197a3b-45d3-4160-af0b-7289d1e37381 ‎15‎:‎44‎:‎14: debug Vibration Detected

1d197a3b-45d3-4160-af0b-7289d1e37381 ‎15‎:‎44‎:‎14: debug encapsulated: NotificationReport(event: 8, eventParameter: [], eventParametersLength: 0, notificationStatus: 255, notificationType: 7, reserved61: 0, sequence: false, v1AlarmLevel: 0, v1AlarmType: 0, zensorNetSourceNodeId: 0) [/code]

So it looks like the two are switched. But it also looks like it’s working to an extent!

ok grab the latest code from below and try that

Oops… doesn’t compile

Same here
groovy.lang.MissingMethodException: No signature of method: java.util.ArrayList.inClusters() is applicable for argument types: (java.lang.String) values: [0x5E,0x20,0x86,0x72,0x5A,0x59,0x85,0x73,0x84,0x80,0x71,0x56,0x70,0x31,0x8E,0x22,0x30,0x9C,0x98,0x7A] @ line 49

lol whoops, missed a comma out, should be good now, get updated code from github

Hah, oh yes I see it. I was just about to put the old fingerprint back in.

Testing…

Edit: you missed a semi colon as well!