Fantem MultiSensor ZB003-X

[kirovilya]

new strange device for Tuya.

https://aliexpress.ru/item/1005001878974427.html

sniffer log
multisensor.zip

issue for work with the device

[dsantos21]

Hi! I've bought this device too, thanks for your PR! Just to let you know, there's a small mistake in this code. Tamper is not been shown, but it's reported as occupancy. And occupancy is not been reported.

Effect: zigbee2mqtt cannot report this sensor motion, but if you shake it, is does report as occupancy :) believe me, I tried it with 2 different devices (I bought 4 of them!).

As I could see in debug, zone status first bit is occupancy, and bit 3 is tamper, so:

Motion detect: zonestatus=1

Tamper and motion detect (impossible to cause just one, I think): zonestatus=5

No motion, nor tamper: zonestatus=0

I've no experience with git, but let me know with o can help somehow!

Ive attached the debug pictures, but obviously they lack context :/

[dsantos21]

I think the bitwise shift was the problem (found it in from Zigbee2mqtt):

Original:
occupancy: (zoneStatus & 1<<2) > 0,

Solution (I think!):
occupancy: (zoneStatus & 1) > 0,

Course, I didn't try it. I have no idea how to test it... :( I just simulated the results using a site that allows you to run python expressions online.

[dsantos21]

Just to let you know: I've just edited my "fromZigbee" file with that proposed solution and it's working now :DDD
All I have to do is not reboot my instance :D. On the weekend I'll look how to propose a PR.

[drzony]

@dsantos21 @kirovilya
I'm adding a new type for Tuya cluster. Could you comment with the output of your debug log?
I need something like this, but from this sensor:

Zigbee2MQTT:debug 2021-03-23 13:23:32: Received Zigbee message from '0xbc33acfffe462752', type 'raw', cluster 'manuSpecificTuya', data '{"data":[9,127,6,0,56,102,4,0,1,2],"type":"Buffer"}' from endpoint 1 with groupID 0