Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Konke motion sensor #1607

Closed
sweebee opened this issue Jun 19, 2019 · 27 comments

Comments

@sweebee
Copy link

@sweebee sweebee commented Jun 19, 2019

I bought this zigbee sensor off aliexpress. It looks nice but it doesnt work yet with deconz.

https://nl.aliexpress.com/item/33014773963.html?spm=a2g0s.9042311.0.0.5dff4c4d8Csnuz

What to do to get this sensor supported? I tried to pair it as a sensor but nothing happens.

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Jun 19, 2019

We need to add it to the REST-API first. Can you please provide the information as described here:
https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support

@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Jun 19, 2019

I have raspbee but no interface on my rasbian. does the debug info give enough info?

deCONZ --dbg-info=1 --dbg-aps=1 --dbg-zcl=1 --dbg-zdp=1 --http-port=80

edit: I tried this command but i get:

QXcbConnection: Could not connect to display 
@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Jun 20, 2019

@manup I think its this device:

Schermafbeelding 2019-06-20 om 08 16 40

@manup

This comment has been minimized.

Copy link
Member

@manup manup commented Jun 20, 2019

This gives us the manufacturer code. We'd also need the attributes from the basic cluster like model identifier and the endpoint clusters as shown in the above screenshots.

@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Jun 20, 2019

Schermafbeelding 2019-06-20 om 17 37 04

Schermafbeelding 2019-06-20 om 17 40 15

@BigWumpus

This comment has been minimized.

Copy link

@BigWumpus BigWumpus commented Jun 30, 2019

here are some other data
0
1
3-1
3-2
500_1
500_2

@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Jul 8, 2019

@manup Do you need any more information?

@goermezer

This comment has been minimized.

Copy link

@goermezer goermezer commented Jul 16, 2019

Any progress with this sensor? I bought one too in hope to get a motion stop status. Want to replace Xiaomi motion sensors.

@online002

This comment has been minimized.

Copy link

@online002 online002 commented Jul 18, 2019

Hi add ?

@vandalon

This comment has been minimized.

Copy link

@vandalon vandalon commented Jul 18, 2019

I just bought the same little sensor. I'm happy to test where wanted :)

@phdelodder

This comment has been minimized.

Copy link

@phdelodder phdelodder commented Jul 27, 2019

Any timeline on the integration of this device? Just bought one.

@Smanar

This comment has been minimized.

Copy link
Contributor

@Smanar Smanar commented Jul 27, 2019

Lol, I have just discovered theses devices, there is same device than Xiaomi, but cheaper.

@jurriaan

This comment has been minimized.

Copy link
Contributor

@jurriaan jurriaan commented Jul 31, 2019

@manup I've got the same device, also got their temperature and humidity sensor and contact sensor.

Both the contact sensor and motion sensor work with IAS.

Got this log of the motion sensor when it detects motion:

18:43:06:268 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -43
18:43:06:269 APS-DATA.request id: 218, addrmode: 0x02, addr: 0xfaf4, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04
18:43:31:031 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -48
18:43:31:031 APS-DATA.request id: 151, addrmode: 0x02, addr: 0xfaf4, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04

And contact sensor (while opening and closing the contact):

18:45:32:616 APS-DATA.indication srcAddr: 0x201e, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -44
18:45:35:808 APS-DATA.indication srcAddr: 0x201e, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -49
18:45:37:637 APS-DATA.indication srcAddr: 0x201e, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -43
18:45:37:641 APS-DATA.indication srcAddr: 0x201e, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -44

For temperature/humidity I got these logs:

18:12:33:298 APS-DATA.indication srcAddr: 0xc3ca, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0405, lqi: 255, rssi: -52
18:12:33:298 APS-DATA.request id: 171, addrmode: 0x02, addr: 0xc3ca, profile: 0x0104, cluster: 0x0405, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
18:17:15:472 APS-DATA.indication srcAddr: 0xc3ca, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0402, lqi: 255, rssi: -51
18:17:15:473 APS-DATA.request id: 11, addrmode: 0x02, addr: 0xc3ca, profile: 0x0104, cluster: 0x0402, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
18:36:58:098 APS-DATA.indication srcAddr: 0xc3ca, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0402, lqi: 255, rssi: -52
18:36:58:098 APS-DATA.request id: 63, addrmode: 0x02, addr: 0xc3ca, profile: 0x0104, cluster: 0x0402, ep: 0x01 -> 0x01 queue: 0 len: 5 tx.options 0x00
18:42:47:434 APS-DATA.indication srcAddr: 0xc3ca, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0405, lqi: 255, rssi: -51
18:42:47:435 APS-DATA.request id: 36, addrmode: 0x02, addr: 0xc3ca, profile: 0x0104, cluster: 0x0405, ep: 0x01 -> 0x01 queue: 1 len: 5 tx.options 0x00
@jurriaan

This comment has been minimized.

Copy link
Contributor

@jurriaan jurriaan commented Jul 31, 2019

After rejoining the contact sensor and setting the IAS_CIE_Address to the gateway IEEE address I do get more log messages:

19:00:58:759 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -52
19:00:59:767 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -52
19:01:00:775 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -52
19:01:00:822 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 239, rssi: -64
19:01:00:827 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 239, rssi: -64
19:01:01:884 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 239, rssi: -64
19:01:01:975 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -52
19:01:01:984 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -52
19:01:02:792 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -51
19:01:02:840 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -61
19:01:02:845 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -61
19:01:03:807 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -61
19:01:04:269 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -53
19:01:04:276 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -52
19:01:04:813 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -53
19:01:05:822 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -57
19:01:06:864 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -49
19:01:07:855 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -55
19:01:08:852 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -52
19:01:09:864 APS-DATA.indication srcAddr: 0xc62f, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -57

Same for the motion sensor:

18:59:28:831 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -45
18:59:28:832 APS-DATA.request id: 142, addrmode: 0x02, addr: 0xfaf4, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 2 len: 12 tx.options 0x04
18:59:49:430 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -47
18:59:49:432 APS-DATA.request id: 32, addrmode: 0x02, addr: 0xfaf4, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04
18:59:50:492 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -46
19:00:18:763 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x00 dstAddrMode: 2, profile: 0x0000, cluster: 0x0000, lqi: 255, rssi: -47
19:00:18:764 APS-DATA.request id: 16, addrmode: 0x02, addr: 0xfaf4, profile: 0x0000, cluster: 0x8000, ep: 0x00 -> 0x00 queue: 1 len: 12 tx.options 0x04
19:00:19:867 APS-DATA.indication srcAddr: 0xfaf4, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -47
jurriaan added a commit to jurriaan/deconz-rest-plugin that referenced this issue Jul 31, 2019
It does work partially on my system, somehow the IAS_CIE_ADDRESS doesn't
get set automatically, but after that, at least my door/window sensor
and temperature sensor works.
jurriaan added a commit to jurriaan/deconz-rest-plugin that referenced this issue Jul 31, 2019
It does work partially on my system, somehow the IAS_CIE_ADDRESS doesn't
get set automatically, but after that, at least my door/window sensor
and temperature sensor works.
jurriaan added a commit to jurriaan/deconz-rest-plugin that referenced this issue Jul 31, 2019
It does work partially on my system, somehow the IAS_CIE_ADDRESS doesn't
get set automatically, but after that, at least my door/window sensor
and temperature sensor works.
jurriaan added a commit to jurriaan/deconz-rest-plugin that referenced this issue Jul 31, 2019
It does work partially on my system, somehow the `IAS_CIE_ADDRESS` doesn't
get set automatically. After manually setting that, at least my door/window sensor works.
@jurriaan

This comment has been minimized.

Copy link
Contributor

@jurriaan jurriaan commented Aug 1, 2019

I got the motion sensor and the window/door sensor to work, but it requires some manual actions still to get it set up. Hopefully someone more familiar with the matter can help me out. See #1722.

@Hypfer

This comment has been minimized.

Copy link

@Hypfer Hypfer commented Aug 18, 2019

Koenkk/zigbee2mqtt#1689 (comment)

According to this issue, the sensors only work on channel 15, 20 and 25.
Is this correct? That might be the reason why mine won't show up in the deconz gui.

@phdelodder

This comment has been minimized.

Copy link

@phdelodder phdelodder commented Aug 27, 2019

Can't see my konke motion sensor in phoscon but visible in home assistant.

@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Aug 27, 2019

@phdelodder the sensor is only supported by the api, not by the frontend (phoscon).

@Hypfer

This comment has been minimized.

Copy link

@Hypfer Hypfer commented Aug 28, 2019

@phdelodder @sweebee

Which zigbee channel are you using?

@phdelodder

This comment has been minimized.

Copy link

@phdelodder phdelodder commented Aug 28, 2019

@Hypfer I'm using channel 15.

@sweebee thanks for the info.

@vandalon

This comment has been minimized.

Copy link

@vandalon vandalon commented Aug 30, 2019

Am I the only one or is this sensor slow in reaction to motion? It takes up to 3 seconds for me for the sensor to report motion.

@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Aug 31, 2019

Yea, to be honest the sensor is quite bad. Slow reaction. And no “no motion” trigger.

Also a small fov. I hoped it would be like 160 degrees or so.

@Hypfer

This comment has been minimized.

Copy link

@Hypfer Hypfer commented Aug 31, 2019

It does however push state updates every few seconds instead of the 1 minute weirdness of the xiaomi motion sensor.

Maybe a combination of those two would make sense? Use the Xiaomi for brightness & fast initial response + the Konke to detect end of motion?

Semi-OT: Is there a proper Motion sensor which does everything well?

@sweebee

This comment has been minimized.

Copy link
Author

@sweebee sweebee commented Aug 31, 2019

I have one hue motion sensor and it works great. But also quite expensive.

The xiaomi pirs work better if you mod them.

@ivan-leschinsky

This comment has been minimized.

Copy link

@ivan-leschinsky ivan-leschinsky commented Aug 31, 2019

I had two Xiaomi motion sensors( latest version for now, with light sensor). I modified them accurately but they stopped sending any motion at all, pinky illumination data. Even when I returned all the changes I made to the sensors hardware

@sweebee sweebee closed this Aug 31, 2019
@subzero79

This comment has been minimized.

Copy link

@subzero79 subzero79 commented Sep 19, 2019

I managed to set the IAS_CIE address

image

channel is set to 25 in deconz, device pairs so it shows in deconz

Also in the logs i can see the response everytime i pass my hand over it

docker logs -f --tail 50 deconz | grep -i 'b267'
13:07:13:090     * neighbor: 0x086BD7FFFE91562A (0xB267), LQI: 42, relation: 0x01 rxOnWHenIdle: 0
13:07:29:205 APS-DATA.indication srcAddr: 0xb267, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -53
13:07:52:349 APS-DATA.indication srcAddr: 0xb267, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -53
13:08:00:127     * neighbor: 0x086BD7FFFE91562A (0xB267), LQI: 42, relation: 0x01 rxOnWHenIdle: 0
13:08:07:682 APS-DATA.indication srcAddr: 0xb267, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0500, lqi: 255, rssi: -53

But no matter what it doesn't appear in ha, if i query all sensors to the API endpoint also no traces.
Anything else to try?

@nicedevil007

This comment has been minimized.

Copy link

@nicedevil007 nicedevil007 commented Dec 5, 2019

is there anything new to this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.