[PROJECT] Drivers for Securifi Devices (Sensors, Keyfob, Click, etc...)

snell · March 1, 2020, 11:59pm

I have posted an updated driver, but I do not think it is going to solve the DWS04N_FL for tonight.

Ranchitat · March 2, 2020, 3:30am

lol That's different, the contact switch now generates:

This is after removing, resetting, discover, 0.94 SecurifiSensors drivers = no Current States contact displayed.
Load ERIA drivers, back to SecurifiSensors drivers.

Closed = Test notice
Open = Battery defect notice (Which is showing as -20%)

Summary

Current States

Version : Latest driver

battery : -20

contact : closed

tamper : clear

temperature : 20.0

Time to reset again...

Ranchitat · March 2, 2020, 3:56am

Okay, fresh start, back cover off, discovered as Generic Moisture, load SecurifiSensors drivers, select debug, Save Preferences, cover on(tamper), Reset Tamper, open contact(magnet). Need to "Refresh" to update Contact State: Open/Close.

Summary

Battery doesn't seem to be updating.

Current States

Version : Latest driver

battery : 49

contact : open

tamper : clear

temperature : 25.0

Better and better, thanks snell.

snell · March 2, 2020, 4:19am

1st screenshot: Test Notice and Battery Defect are not actually ones I came up with. Those are both in the ZigBee Cluster Library, responses for particular Zone Statuses. While I was trying to figure things out, a lot of the changes I made involved adding in additional ZigBee responses to my sets. Most I never thought would see use, but if I was making changes might as well put them in so I never need to in the future.

2nd screenshot:
Still has a lot of those irritating enroll responses sitting in the log it looks like. The battery should not update too often. I did not want battery-powered devices draining their batteries just to tell people about their batteries.
So the battery reporting is configured to be once a day, or per 1% change. Hopefully you are not doing enough to the device to see the % drop in a day.
From the log data it also looks like the attempt at reading basic data did not work for any attribute. It did not work on any of my Securifi Sensors... so I am probably going to comment that out going forward (Securifi Peanut Plugs DO respond to some, which is why I was checking these also).

More work to do obviously but I am glad SOME progress was made even if I could not see any with my DWS04N_FL... I really wish I understood why these two models seem to act so differently.

Ranchitat · March 16, 2020, 5:12am

So, all my SZ-DWS04N_SF's seem to be reporting open/closed correctly now... not sure what happened.
The tamper switch function also works correctly.
Temperature is changing in the appropriate direction, haven't tested the accuracy at all.
The battery reporting doesn't appear to be functioning correctly. Swapping batteries between two sensors, S3 at 87 and S5 at 49, resulted in S3 still reporting 87 and S5 reporting 62.
Still, pretty happy with the result so far, now I need to figure out how to get the "tamper" state on a tile.

snell · March 16, 2020, 10:17pm

Glad to hear it worked... I wish I knew WHY. Mine STILL does not work properly.

Batteries are always a pain... If you could, give them a couple days and let me know if it eventually reported something different. I keep trying to remember to set aside a couple batteries of different levels but always seem to forget about batteries until they are dead.

Ranchitat · March 17, 2020, 3:25am

Another new one, #6, "Device Discovery" result.

Summary

inClusters : 0000,0001,0003,0402,0500,0020,0B05

Ranchitat · March 17, 2020, 3:38am

It took a few tries but it seems to be working now.

Summary

snell · March 17, 2020, 11:04am

Well... that is good to hear. I still have not figured out why the moisture sensor comes up before the custom driver. There must be SOMETHING wrong with my fingerprinting but darned if I see it.

Couple little tweaks for my NEXT version on the way, but nothing substantial at this point.

Ranchitat · March 25, 2020, 4:33am

Another week, another SZ-DWS04N_SF update.
In an effort to clean up things I removed all zigbee bulbs from HE.
After which I noticed some of the sensors were offline, unfortunately I didn't think to check before. After running zigbee discovery they showed up again but there was an issue with one of them not showing open/closed.
It was instead switching between Closed = Test notice and Open = Battery defect notice, something that had happened before.

Summary

dev:3012020-03-24 09:36:18.473 pm debugDoor Securifi5 - Refresh commands = [he raw 0xEEE2 1 0x01 0x0001 {10 00 00 21 00}, delay 200, he raw 0xEEE2 1 0x01 0x0402 {10 00 00 00 00}, delay 200, he raw 0xEEE2 1 0x01 0x0500 {10 00 00 02 00}, delay 200]

dev:3012020-03-24 09:36:18.462 pm infoDoor Securifi5 - Refreshing device...

dev:3012020-03-24 09:36:18.451 pm debugDoor Securifi5 - Read basic cluster: [he raw 0xEEE2 1 0x01 0x0000 {10 00 00 00 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 01 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 02 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 03 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 04 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 05 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 06 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 07 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 10 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 11 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 12 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 13 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 14 00}, delay 200, he raw 0xEEE2 1 0x01 0x0000 {10 00 00 00 40}, delay 200, he raw 0xEEE2 1 0x01 0x0500 {10 00 00 01 00}, delay 200]

dev:3012020-03-24 09:36:18.411 pm debugDoor Securifi5 - ZigBee Reporting Commands:[zdo bind 0xEEE2 0x01 0x01 0x0402 {000D6F000B7C9B6A} {}, delay 2000, he cr 0xEEE2 0x01 1026 0 41 1 600 {0100} {}, delay 2000, zdo bind 0xEEE2 0x01 0x01 0x0500 {000D6F000B7C9B6A} {}, delay 2000, he cr 0xEEE2 0x01 1280 2 25 1 86400 {} {}, delay 2000]

After pulling the battery and running discovery it was no longer responding to the contact opening and closing.

Summary

An additional power cycle of the sensor resulted in proper open/close states again.

Summary

Switched to debug in case there's any useful info.

Summary

dev:3012020-03-24 09:50:42.563 pm debugDoor Securifi5 - Refresh commands = [he raw 0x349F 1 0x01 0x0001 {10 00 00 21 00}, delay 200, he raw 0x349F 1 0x01 0x0402 {10 00 00 00 00}, delay 200, he raw 0x349F 1 0x01 0x0500 {10 00 00 02 00}, delay 200]

dev:3012020-03-24 09:50:42.552 pm infoDoor Securifi5 - Refreshing device...

dev:3012020-03-24 09:50:42.543 pm debugDoor Securifi5 - Read basic cluster: [he raw 0x349F 1 0x01 0x0000 {10 00 00 00 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 01 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 02 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 03 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 04 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 05 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 06 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 07 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 10 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 11 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 12 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 13 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 14 00}, delay 200, he raw 0x349F 1 0x01 0x0000 {10 00 00 00 40}, delay 200, he raw 0x349F 1 0x01 0x0500 {10 00 00 01 00}, delay 200]

dev:3012020-03-24 09:50:42.502 pm debugDoor Securifi5 - ZigBee Reporting Commands:[zdo bind 0x349F 0x01 0x01 0x0402 {000D6F000B7C9B6A} {}, delay 2000, he cr 0x349F 0x01 1026 0 41 1 600 {0100} {}, delay 2000, zdo bind 0x349F 0x01 0x01 0x0500 {000D6F000B7C9B6A} {}, delay 2000, he cr 0x349F 0x01 1280 2 25 1 86400 {} {}, delay 2000]

dev:3012020-03-24 09:50:42.497 pm infoDoor Securifi5 - Configuring device...

dev:3012020-03-24 09:50:42.434 pm infoDoor Securifi5 - Reset tamper notification

dev:3012020-03-24 09:50:42.432 pm debugDoor Securifi5 - model SZ-DWS04N_SF = contact sensor

Hopefully it continues to function after the zigbee mesh rebuilds.

And, one sensor reports temp every 5 minutes even though it's set to 10(as they all are).
Battery, unchanged: 1-75, 2-86, 3-87, 4-75, 5-62, 6-75.

Not sure why but it seems like clicking on "Configure" is less effective than using "Save Preferences"

snell · March 25, 2020, 10:56am

Well... I am glad it got working again. This is that DWS04N_SF model again? I think there is something truly buggy with those and I still think it must be related to power somehow (but that does not explain why the one I have on a fixed power supply is ALSO flaky when testing).

Oddly, the updated command DOES do more than the configure does in this case... because configure is one of the commands updated calls. I am actually thinking it would be easier to get rid of configure, but people are used to that from other drivers. Most of the additional elements are around things people set in preference (reporting interval for example) and things internal to the driver NOT the device itself. The configure command is for sending the commands around ZigBee reporting back to the device itself, little to do with the driver.

Ranchitat · March 26, 2020, 11:55pm

Another SZ-DWS04N_SF dropped off.
Running discovery resulted in the same Closed = Test notice and Open = Battery defect notice.
Just for kicks tried the Generic Zigbee Contact Driver, still no open/closed just parse messages...

Open Summary

dev:3062020-03-26 05:09:07.379 pm debugparse: listResult []

dev:3062020-03-26 05:09:07.375 pm debugzigbee.parseDescriptionAsMap-read attr: [raw:1D890105000A0200192900, dni:1D89, endpoint:01, cluster:0500, size:0A, attrId:0002, encoding:19, command:0A, value:0029, clusterInt:1280, attrInt:2]

dev:3062020-03-26 05:09:07.368 pm debugparse: read attr - raw: 1D890105000A0200192900, dni: 1D89, endpoint: 01, cluster: 0500, size: 0A, attrId: 0002, encoding: 19, command: 0A, value: 2900

dev:3062020-03-26 05:09:00.189 pm warndescription logging is: true

dev:3062020-03-26 05:09:00.186 pm warndebug logging is: true

Closed Summary

dev:3062020-03-26 05:09:12.232 pm debugparse: listResult []

dev:3062020-03-26 05:09:12.229 pm debugzigbee.parseDescriptionAsMap-read attr: [raw:1D890105000A0200192800, dni:1D89, endpoint:01, cluster:0500, size:0A, attrId:0002, encoding:19, command:0A, value:0028, clusterInt:1280, attrInt:2]

dev:3062020-03-26 05:09:12.224 pm debugparse: read attr - raw: 1D890105000A0200192800, dni: 1D89, endpoint: 01, cluster: 0500, size: 0A, attrId: 0002, encoding: 19, command: 0A, value: 2800

Then the ERIA Contact Sensor Driver, open/closed works correctly.

Summary

dev:3062020-03-26 05:18:28.898 pm infoDoor Securifi6 is open

dev:3062020-03-26 05:18:28.894 pm debugparse: read attr - raw: 1D890105000A0200192900, dni: 1D89, endpoint: 01, cluster: 0500, size: 0A, attrId: 0002, encoding: 19, command: 0A, value: 2900

dev:3062020-03-26 05:18:26.949 pm infoDoor Securifi6 is closed

dev:3062020-03-26 05:18:26.945 pm debugparse: read attr - raw: 1D890105000A0200192800, dni: 1D89, endpoint: 01, cluster: 0500, size: 0A, attrId: 0002, encoding: 19, command: 0A, value: 2800

dev:3062020-03-26 05:18:24.567 pm infoDoor Securifi6 is open

dev:3062020-03-26 05:18:24.563 pm debugparse: read attr - raw: 1D890105000A0200192900, dni: 1D89, endpoint: 01, cluster: 0500, size: 0A, attrId: 0002, encoding: 19, command: 0A, value: 2900

dev:3062020-03-26 05:18:24.050 pm debugskipped: [raw:1D890104020A0000293408, dni:1D89, endpoint:01, cluster:0402, size:0A, attrId:0000, encoding:29, command:0A, value:0834, clusterInt:1026, attrInt:0]

dev:3062020-03-26 05:18:24.045 pm debugparse: read attr - raw: 1D890104020A0000293408, dni: 1D89, endpoint: 01, cluster: 0402, size: 0A, attrId: 0000, encoding: 29, command: 0A, value: 3408

dev:3062020-03-26 05:18:23.171 pm infoDoor Securifi6 is closed

dev:3062020-03-26 05:18:23.165 pm debugparse: read attr - raw: 1D890105000A0200192800, dni: 1D89, endpoint: 01, cluster: 0500, size: 0A, attrId: 0002, encoding: 19, command: 0A, value: 2800

dev:3062020-03-26 05:18:18.719 pm warndescription logging is: true

dev:3062020-03-26 05:18:18.716 pm warndebug logging is: true

dev:3062020-03-26 05:18:18.713 pm infoupdated...

Back to the Securifi Sensor Driver, and open/closed reverts to Closed = Test notice and Open = Battery defect notice.

Summary

dev:3062020-03-26 05:22:45.114 pm infoDoor Securifi6 - Test notice

dev:3062020-03-26 05:22:43.510 pm infoDoor Securifi6 - Battery defect notice

dev:3062020-03-26 05:22:38.595 pm infoDoor Securifi6 - Test notice

dev:3062020-03-26 05:22:33.890 pm infoDoor Securifi6 - Battery defect notice

dev:3062020-03-26 05:22:32.595 pm infoDoor Securifi6 - Test notice

dev:3062020-03-26 05:22:31.645 pm infoDoor Securifi6 - Battery defect notice

dev:3062020-03-26 05:22:31.626 pm infoDoor Securifi6 - Temperature is 21.0°C

dev:3062020-03-26 05:22:31.043 pm infoDoor Securifi6 - Battery defect notice

dev:3062020-03-26 05:22:26.138 pm infoDoor Securifi6 - Has latest driver

dev:3062020-03-26 05:22:25.620 pm debugDoor Securifi6 - Refresh commands = [he raw 0x1D89 1 0x01 0x0001 {10 00 00 21 00}, delay 200, he raw 0x1D89 1 0x01 0x0402 {10 00 00 00 00}, delay 200, he raw 0x1D89 1 0x01 0x0500 {10 00 00 02 00}, delay 200]

dev:3062020-03-26 05:22:25.612 pm infoDoor Securifi6 - Refreshing device...

dev:3062020-03-26 05:22:25.608 pm debugDoor Securifi6 - Read basic cluster: [he raw 0x1D89 1 0x01 0x0000 {10 00 00 00 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 01 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 02 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 03 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 04 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 05 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 06 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 07 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 10 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 11 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 12 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 13 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 14 00}, delay 200, he raw 0x1D89 1 0x01 0x0000 {10 00 00 00 40}, delay 200, he raw 0x1D89 1 0x01 0x0500 {10 00 00 01 00}, delay 200]

dev:3062020-03-26 05:22:25.564 pm debugDoor Securifi6 - ZigBee Reporting Commands:[zdo bind 0x1D89 0x01 0x01 0x0402 {000D6F000B7C97E6} {}, delay 2000, he cr 0x1D89 0x01 1026 0 41 1 60 {0100} {}, delay 2000, zdo bind 0x1D89 0x01 0x01 0x0500 {000D6F000B7C97E6} {}, delay 2000, he cr 0x1D89 0x01 1280 2 25 1 86400 {} {}, delay 2000]

dev:3062020-03-26 05:22:25.555 pm infoDoor Securifi6 - Configuring device...

dev:3062020-03-26 05:22:25.491 pm infoDoor Securifi6 - Reset tamper notification

dev:3062020-03-26 05:22:25.488 pm debugDoor Securifi6 - model SZ-DWS04N_SF = contact sensor

dev:3062020-03-26 05:22:25.479 pm infoDoor Securifi6 - Saved preferences

Pulling the battery cover off (tampered) generates this "info" message:

Summary

dev:3062020-03-26 05:25:32.921 pm infoDoor Securifi6 - IASZone descMap = [raw:1D890105000A0200192D00, dni:1D89, endpoint:01, cluster:0500, size:0A, attrId:0002, encoding:19, command:0A, value:002D, clusterInt:1280, attrInt:2]

snell · March 27, 2020, 12:50am

Looking at those parses... The cluster 0500 is the IASZone, so where you would expect security-type reports outside of the ZoneStatus.
The attrId 0002 is an actual report of "something" happening. Per the specs, a value of 0028 should be a "Test" and 0029 should be a "Battery Defect". Basically what you see with mine or the Generic. The ERIA is treating them differently...

Let me build these in specifically for that model.
EDITED: Version 0.95 is now posted with code to specifically deal with those ONLY if it is that model. Of course when I went to try it all out with my one... the stupid thing had forgotten everything. Re-paired it and it started working perfectly, acting the same as my normal DWS04 models and will not report those commands.

That to me says "take a break" for the evening.

spudz · July 22, 2020, 1:55pm

I have found a source locally to purchase a bunch of the SZ-DWSx04 door/window sensors for under $5 but wondering if they are reliable? I have been reading about some issues so just wanted to ask here. Should I pull the trigger or pass?

snell · July 22, 2020, 2:09pm

The trouble mostly seems to be with the 04_SF model, so it depends on what you found. $5 is a really good price though.

Ranchitat · August 14, 2020, 2:45am

Back again. The contact sensors have been more or less stable. Thanks for all your help.
This time it's my motion sensors that are acting up. Turns out they are also _SF versions. They were working fine but one dropped off when I was moving some stuff around and now it doesn't want to pair the same. Before it was fine using the driver and would detect motion, but now instead of motion it's coming up with the battery defect/test notice messages.
The Tamper switch isn't reporting.
And the temperature isn't reporting but maybe it's not supposed to.

Not sure if this is enough data but if you can tweak the driver that would be fantastic.

SZ-PIR02_SF Device info

dev:112020-08-06 04:45:07.841 am infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,0402,0500,0B05", outClusters:"0003", model:"SZ-PIR02_SF", manufacturer:"Sercomm Corp."

dev:112020-08-06 04:45:07.332 am traceZCL version:01

dev:112020-08-06 04:45:07.319 am traceSoftware Build Id:unknown

dev:112020-08-06 04:45:07.315 am traceModel:SZ-PIR02_SF

dev:112020-08-06 04:45:07.305 am traceManufacturer:Sercomm Corp.

dev:112020-08-06 04:45:06.949 am debuggetting info for unknown Zigbee device...

dev:112020-08-06 04:45:03.380 am infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,0402,0500,0B05", outClusters:"0003", model:"SZ-PIR02_SF", manufacturer:"Sercomm Corp."

dev:112020-08-06 04:45:02.861 am traceZCL version:01

dev:112020-08-06 04:45:02.846 am traceSoftware Build Id:unknown

dev:112020-08-06 04:45:02.842 am traceModel:SZ-PIR02_SF

Current States

Version : Latest driver
battery : 86
contact : closed
motion : inactive
tamper : clear
temperature : 0.0

Data

endpointId: 01
application: 13
softwareBuild:
inClusters: 0000,0001,0003,0020,0402,0500,0B05
outClusters: 0003
model: SZ-PIR02_SF
manufacturer: Sercomm Corp.

Logs

dev:112020-08-13 08:30:42.155 pm infoMotion Securifi 1 Livingroom - Test notice

dev:112020-08-13 08:30:41.174 pm infoMotion Securifi 1 Livingroom - Battery defect notice

dev:112020-08-13 08:30:01.535 pm infoMotion Securifi 1 Livingroom - Test notice

dev:112020-08-13 08:30:00.498 pm infoMotion Securifi 1 Livingroom - Battery defect notice

dev:112020-08-13 08:29:31.707 pm debugMotion Securifi 1 Livingroom - Sending request to set ZigBee reporting

dev:112020-08-13 08:29:31.693 pm infoMotion Securifi 1 Livingroom - Configuring device...

snell · August 14, 2020, 11:33am

I will try to take a look, although if it was working before with the driver it really should still work now. I actually already have the SZ-PIR02_SF fingerprint in the driver and the way it determines device it should not function any different than the SZ-PIR02 (without _SF).

Looking at the driver I do see it will not detect the battery defect AND sensor activity at the same time (I only coded that for the SZ-DWS04N_SF, so it looks like I need to do the same thing for this one).

Can you tell me which seems to report when? Does the Battery defect notice report when it detects motion, or is it the Test notice? I see where I have them in the code but I do not know which one to rework as which.

Ranchitat · August 14, 2020, 8:02pm

Battery defect notice = motion is active
Test notice = motion is inactive

This is the strange part of the _SF series, I have the one contact sensor still using the driver from the first time I tried to install it back in Feb. Then all the rest, phht, round and round we go.

W.T.F. So, just tried to reset/re-pair the sensor, pulled the battery, held down the button, inserted battery, ran discovery (nothing found?) and it started working properly including tamper. Pulled the back off again to test tamper and everything quit... Red light flashes but nothing in logs or Current States. And now it won't freakin re-pair or reset or whatever. Even tried a new battery. Like you said, time for a break.

Briefly working again.

dev:112020-08-14 01:35:44.260 pm infoMotion Securifi 1 Livingroom - Reset tamper notification

dev:112020-08-14 01:35:41.431 pm infoMotion Securifi 1 Livingroom - Motion inactive

dev:112020-08-14 01:35:40.356 pm infoMotion Securifi 1 Livingroom - Tampered and closed

dev:112020-08-14 01:35:39.384 pm infoMotion Securifi 1 Livingroom - Motion inactive

dev:112020-08-14 01:35:38.364 pm infoMotion Securifi 1 Livingroom - Tampered and opened

dev:112020-08-14 01:35:29.296 pm infoMotion Securifi 1 Livingroom - Tampered and closed

dev:112020-08-14 01:35:26.921 pm infoMotion Securifi 1 Livingroom - Reset tamper notification

dev:112020-08-14 01:35:25.622 pm infoMotion Securifi 1 Livingroom - Motion inactive

dev:112020-08-14 01:35:09.617 pm infoMotion Securifi 1 Livingroom - Tampered and closed

dev:112020-08-14 01:35:08.601 pm infoMotion Securifi 1 Livingroom - Tampered and opened

dev:112020-08-14 01:34:48.520 pm infoMotion Securifi 1 Livingroom - Tampered and closed

dev:112020-08-14 01:34:43.489 pm infoMotion Securifi 1 Livingroom - IASZone descMap = [raw:4D0A0105000A0200192C00, dni:4D0A, endpoint:01, cluster:0500, size:0A, attrId:0002, encoding:19, command:0A, value:002C, clusterInt:1280, attrInt:2]

dev:112020-08-14 01:34:42.550 pm infoMotion Securifi 1 Livingroom - Unknown IASZone notice

dev:112020-08-14 01:34:12.798 pm infoMotion Securifi 1 Livingroom - IASZone descMap = [raw:4D0A0105000A0200192C00, dni:4D0A, endpoint:01, cluster:0500, size:0A, attrId:0002, encoding:19, command:0A, value:002C, clusterInt:1280, attrInt:2]

dev:112020-08-14 01:34:10.531 pm infoMotion Securifi 1 Livingroom - Test notice

dev:112020-08-14 01:34:09.549 pm infoMotion Securifi 1 Livingroom - Battery defect notice

snell · August 14, 2020, 9:05pm

OK. I got most of the rest of it ready. I can update those areas. Plus I noticed it is triggering "tampered and closed" or opened responses, which should be tied to motion not a contact sensor. So a couple things I should have updated tonight.

Version 0.98.0 is now posted:

General changes and improvements throughout.
More consistent logging method (you will need to Save Preferences to set the logging).
Some changes to try to accommodate another _SF sensor.

Ranchitat · August 15, 2020, 6:21am

Tried the latest driver 0.98.0 not sure what's what.

Debug Logs

dev:112020-08-15 12:01:49.877 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:01:41.894 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:01:33.954 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:01:25.437 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:00:37.839 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:00:29.863 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:00:21.887 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:00:13.926 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:00:05.931 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-14 11:58:58.123 pm debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-14 11:58:50.126 pm debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-14 11:58:42.166 pm debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-14 11:58:34.190 pm debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-14 11:58:26.204 pm debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-14 11:58:24.307 pm debugMotion Securifi 1 Livingroom - Unhandled cluster. 0006 is On/Off, descMap = [raw:catchall: 0000 0006 00 00 0040 00 B1CC 00 00 0000 00 00 08FDFF040100010005, profileId:0000, clusterId:0006, clusterInt:6, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[08, FD, FF, 04, 01, 00, 01, 00, 05]]

dev:112020-08-14 11:58:03.399 pm infoMotion Securifi 1 Livingroom - Configuring device...

dev:112020-08-14 11:57:58.725 pm debugMotion Securifi 1 Livingroom - Driver version up to date

dev:112020-08-14 11:57:57.370 pm infoMotion Securifi 1 Livingroom - Configuring device...

dev:112020-08-14 11:57:57.289 pm infoMotion Securifi 1 Livingroom - Saved preferences

Events

Name	Value	Source	Date
motion	inactive	DEVICE	2020-08-15 12:02:38.805 AM MDT
motion	active	DEVICE	2020-08-15 12:02:37.811 AM MDT
motion	inactive	DEVICE	2020-08-15 12:02:00.889 AM MDT
motion	active	DEVICE	2020-08-15 12:01:59.881 AM MDT
motion	inactive	DEVICE	2020-08-15 12:01:26.457 AM MDT
motion	active	DEVICE	2020-08-15 12:01:25.435 AM MDT
motion	inactive	DEVICE	2020-08-14 11:58:24.231 PM MDT
motion	active	DEVICE	2020-08-14 11:58:23.673 PM MDT
motion	active	DEVICE	2020-08-14 11:58:23.661 PM MDT

The motion detection is being reported and shows on the device page, dashboard and triggers rules. Just the strange readout on the Logs.

The tamper is reported on the Device page and clears by command.
Nothing showing in the regular or Debug Logs.

Trace Logs

dev:112020-08-15 12:16:56.516 am traceMotion Securifi 1 Livingroom - Motion inactive

dev:112020-08-15 12:16:55.510 am traceMotion Securifi 1 Livingroom - Motion active

dev:112020-08-15 12:16:49.175 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:16:41.189 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:16:33.225 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:16:25.212 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:16:20.519 am traceMotion Securifi 1 Livingroom - Reset tamper notification

dev:112020-08-15 12:16:17.236 am traceMotion Securifi 1 Livingroom - Motion inactive

dev:112020-08-15 12:16:16.244 am traceMotion Securifi 1 Livingroom - Motion inactive and tampered

dev:112020-08-15 12:16:16.243 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:15:35.346 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:15:27.361 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:15:19.341 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:15:11.386 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:15:06.542 am traceMotion Securifi 1 Livingroom - Reset tamper notification

dev:112020-08-15 12:15:03.409 am traceMotion Securifi 1 Livingroom - Motion inactive

dev:112020-08-15 12:15:01.326 am traceMotion Securifi 1 Livingroom - Motion inactive and tampered

dev:112020-08-15 12:15:01.322 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:14:27.003 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4A00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4A, 00]]

dev:112020-08-15 12:14:25.232 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4A00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4A, 00]]

dev:112020-08-15 12:14:25.127 am traceMotion Securifi 1 Livingroom - Battery at 86%

dev:112020-08-15 12:14:25.076 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4A00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4A, 00]]

dev:112020-08-15 12:14:25.042 am traceMotion Securifi 1 Livingroom - Battery at 86%

dev:112020-08-15 12:14:24.998 am traceMotion Securifi 1 Livingroom - Battery at 86%

dev:112020-08-15 12:14:24.478 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:14:17.993 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4800, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[48, 00]]

dev:112020-08-15 12:14:17.143 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4600, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[46, 00]]

dev:112020-08-15 12:14:17.103 am traceMotion Securifi 1 Livingroom - Battery at 0%

dev:112020-08-15 12:14:17.049 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4600, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[46, 00]]

dev:112020-08-15 12:14:17.016 am debugMotion Securifi 1 Livingroom - Unhandled cluster. 8021 is Bind_rsp, descMap = [raw:catchall: 0000 8021 00 00 0040 00 B1CC 00 00 0000 00 00 4600, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:B1CC, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[46, 00]]

dev:112020-08-15 12:14:16.489 am debugMotion Securifi 1 Livingroom - Unknown cluster. descMap = [:]

dev:112020-08-15 12:14:14.308 am debugMotion Securifi 1 Livingroom - Driver version up to date

dev:112020-08-15 12:14:13.573 am traceMotion Securifi 1 Livingroom - Sending request to set ZigBee reporting

dev:112020-08-15 12:14:13.571 am traceMotion Securifi 1 Livingroom - Sending request to read device attributes

dev:112020-08-15 12:14:13.545 am infoMotion Securifi 1 Livingroom - Configuring device...

dev:112020-08-15 12:14:13.483 am traceMotion Securifi 1 Livingroom - Reset tamper notification

dev:112020-08-15 12:14:13.480 am traceMotion Securifi 1 Livingroom - model SZ-PIR02_SF = motion sensor

dev:112020-08-15 12:14:13.469 am infoMotion Securifi 1 Livingroom - Saved preferences

So it seems to be working, just some strange messages.