Is there a Hubitat compatible vibration sensor with sensitivity adjustment?
I have an Aeotec Multipurpose Sensor, but I’m not aware of any way to reduce the vibration sensitivity.
Is there a Hubitat compatible vibration sensor with sensitivity adjustment?
I have an Aeotec Multipurpose Sensor, but I’m not aware of any way to reduce the vibration sensitivity.
The SmartThings (now Aeotec) Multi-sensors have a setting for the 3 axis sensitivity from what I can tell. But probably depends on what you are trying to do, and I don't know if that setting affects the "acceleration" attribute or not.
I have the tuya vib sensor and it's been behaving good.
here';s the info
@kkossev might know if there are multiple versions of the Tuya Vib Sensor
Yes, the sensitivity for Tuya Vibration sensors can be adjusted.
There are 3 different Tuya models that are supported by the custom driver. I am planning to create a new dedicated thread with pictures and links to the different models, as the information now is scattered in several threads. Tuya Vibration Sensor driver can be installed from Hubitat Package Manager (HPM), the GitHub code is here: https://raw.githubusercontent.com/kkossev/Hubitat/main/Drivers/Tuya%20ZigBee%20Vibration%20Sensor/Tuya%20ZigBee%20Vibration%20Sensor.groovy
BTW, the SmartThings/Aeotec multi sensor is a great gadget, I have it for several years now (came with my ST hub), it provides also 3-axis acceleration values that are not available in Tuya sensors.
I don't remember whether the "Three Axis reporting options" preference, 'normal' and 'maximum' option afects the acceleration active/inactive triggering.
Hi Karissimir, Is the following any clue why I'm gettings hundreds of messages from my Tuya Vib sensors?
Mine is the _TZ3000_bmfw9ykl
dev:20512023-03-02 12:53:52.918 PMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-02 12:53:52.870 PMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:20512023-03-02 12:53:52.866 PMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:20512023-03-02 12:53:52.745 PMinfoMailbox_Vibe_Tuya: Sending IAS enroll response...
dev:20512023-03-02 12:53:52.741 PMdebugMailbox_Vibe_Tuya: Parsing: enroll request endpoint 0x01 : data 0x0015
I have experienced something similar with a PIR motion sensor whose battery was nearly dead...
Can you try changing the battery to a new one?
Checked the code quickly - nothing non-standard there ... this is what all IAS device drivers do:
//------IAS Zone Enroll request------//
else if (description?.startsWith('enroll request')) {
logInfo "Sending IAS enroll response..."
return zigbee.enrollResponse()
}
Hi Krassimr, I did change the battery and it is the same behavior. Could these excessive Zone Enroll requests be due to the Tuya device changing it's address? I have 4 repeaters(2 of which are the Tuya USB repeaters) near the mailbox, under my porch, so I assume the signal is good.
After I changed the battery I hit configure while waking the sensor, but i seems stuck on most sensitive, while the device page shows a setting of "4"
I think i had something similar over in the other thread.
For me it was only solved after i had the batteries out for an extensive time.
Well, definitely something is not OK here ..
Can you change the driver to the inbuilt Generic Motion Sensor, enable the debug logs, and check whether this messages loop will stop?
I can implement a workaround to stop responding to the enroll requests and switch into 'offline' healthStatus if these messages come too frequently, but this is not the right approach.
At first reading, this Tuya sensor returns a Zone Status message that I can not find in the IAS official specs.. : (
Do you have only one of these sensors? You first mentioned the same device 4 months ago, is the problematic a new one or the same?
@Rxich I forgot to inform you that I have made some changes in the Tuya Vibration Sensor driver (similar to how the IAS cluster messages are handled in the Tuya 4-in-1 driver) - can you run some tests again? (update to the latest dev. branch version from within the HE driver code editor - Import button)
Thank You Krassimir, I greatly appreciate all your incredible work.
So I changed the driver last night, saved device, set prefs and saved. I think it's a little less messages but still a good number of unparsed data, and not sure if it's relevant.
dev:20512023-03-13 01:40:06.211 PMinfoMailbox_Vibe_Tuya: battery is 100.0 %
dev:20512023-03-13 01:40:06.206 PMdebugMailbox_Vibe_Tuya: Parsing: read attr - raw: 72D001000110210020C82000201E, dni: 72D0, endpoint: 01, cluster: 0001, size: 10, attrId: 0021, encoding: 20, command: 0A, value: C82000201E
dev:20512023-03-13 01:27:48.984 PMinfoMailbox_Vibe_Tuya: Vibration reset to inactive after 11s
dev:20512023-03-13 01:27:38.996 PMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 01:27:38.947 PMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0801 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 01:27:38.944 PMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0801 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 01:27:37.622 PMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 01:27:37.525 PMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 01:27:37.522 PMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 11:47:18.028 AMinfoMailbox_Vibe_Tuya: battery voltage is 3.0 volts
dev:20512023-03-13 11:47:18.024 AMdebugMailbox_Vibe_Tuya: Parsing: read attr - raw: 72D0010001082000201E, dni: 72D0, endpoint: 01, cluster: 0001, size: 08, attrId: 0020, encoding: 20, command: 0A, value: 1E
dev:20512023-03-13 09:40:06.519 AMinfoMailbox_Vibe_Tuya: battery is 100.0 %
dev:20512023-03-13 09:40:06.513 AMdebugMailbox_Vibe_Tuya: Parsing: read attr - raw: 72D001000110210020C82000201E, dni: 72D0, endpoint: 01, cluster: 0001, size: 10, attrId: 0021, encoding: 20, command: 0A, value: C82000201E
dev:20512023-03-13 08:29:30.928 AMinfoMailbox_Vibe_Tuya: Vibration reset to inactive after 10s
dev:20512023-03-13 08:29:20.952 AMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 08:29:20.887 AMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 08:29:20.885 AMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 08:00:14.115 AMinfoMailbox_Vibe_Tuya: Vibration reset to inactive after 10s
dev:20512023-03-13 08:00:04.136 AMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 08:00:04.066 AMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 08:00:04.063 AMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 05:39:40.877 AMinfoMailbox_Vibe_Tuya: battery is 100.0 %
dev:20512023-03-13 05:39:40.872 AMdebugMailbox_Vibe_Tuya: Parsing: read attr - raw: 72D001000110210020C82000201E, dni: 72D0, endpoint: 01, cluster: 0001, size: 10, attrId: 0021, encoding: 20, command: 0A, value: C82000201E
dev:20512023-03-13 05:29:22.524 AMinfoMailbox_Vibe_Tuya: Vibration reset to inactive after 10s
dev:20512023-03-13 05:29:12.527 AMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 05:29:12.475 AMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 05:29:12.472 AMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 02:15:07.635 AMinfoMailbox_Vibe_Tuya: Vibration reset to inactive after 10s
dev:20512023-03-13 02:14:57.637 AMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 02:14:57.580 AMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 02:14:57.578 AMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 01:39:14.566 AMinfoMailbox_Vibe_Tuya: battery is 100.0 %
dev:20512023-03-13 01:39:14.560 AMdebugMailbox_Vibe_Tuya: Parsing: read attr - raw: 72D001000110210020C82000201E, dni: 72D0, endpoint: 01, cluster: 0001, size: 10, attrId: 0021, encoding: 20, command: 0A, value: C82000201E
dev:20512023-03-13 12:47:02.608 AMinfoMailbox_Vibe_Tuya: Vibration reset to inactive after 10s
dev:20512023-03-13 12:46:52.660 AMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-13 12:46:52.565 AMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-13 12:46:52.563 AMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-12 11:47:24.652 PMinfoMailbox_Vibe_Tuya: battery voltage is 3.0 volts
dev:20512023-03-12 11:47:24.647 PMdebugMailbox_Vibe_Tuya: Parsing: read attr - raw: 72D0010001082000201E, dni: 72D0, endpoint: 01, cluster: 0001, size: 08, attrId: 0020, encoding: 20, command: 0A, value: 1E
dev:20512023-03-12 11:32:55.775 PMtraceMailbox_Vibe_Tuya sendZigbeeCommands received : [he raw 0x72D0 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, zdo bind 0x72D0 0x01 0x01 0x0001 {A4C13897C8D72299} {}, delay 2000, he cr 0x72D0 0x01 1 32 32 43199 43200 {} {}, delay 2000, he raw 0x72D0 1 0x01 0x0001 {10 00 00 20 00}, delay 2000, he wattr 0x72D0 0x01 0x0500 0x0010 0xF0 {DF042016006F0D00}, delay 2000, he raw 0x72D0 1 0x01 0x0500 {01 23 00 00 00}, delay 2000, he raw 0x72D0 1 0x01 0x0500 {10 00 00 00 00}, delay 2000, null]
dev:20512023-03-12 11:32:55.771 PMtraceMailbox_Vibe_Tuya sendZigbeeCommands received : [he wattr 0x72D0 0x01 0x0500 0x0013 0x20 {04} {}, delay 2000]
dev:20512023-03-12 11:32:55.768 PMdebugMailbox_Vibe_Tuya: Configuring vibration sensitivity to : 4
dev:20512023-03-12 11:32:55.760 PMinfoMailbox_Vibe_Tuya: Battery reporting frequency: 12h
dev:20512023-03-12 11:32:55.758 PMinfoMailbox_Vibe_Tuya: Updating preference settings
dev:20512023-03-12 11:32:50.281 PMtraceMailbox_Vibe_Tuya sendZigbeeCommands received : [he raw 0x72D0 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, zdo bind 0x72D0 0x01 0x01 0x0001 {A4C13897C8D72299} {}, delay 2000, he cr 0x72D0 0x01 1 32 32 43199 43200 {} {}, delay 2000, he raw 0x72D0 1 0x01 0x0001 {10 00 00 20 00}, delay 2000, he wattr 0x72D0 0x01 0x0500 0x0010 0xF0 {DF042016006F0D00}, delay 2000, he raw 0x72D0 1 0x01 0x0500 {01 23 00 00 00}, delay 2000, he raw 0x72D0 1 0x01 0x0500 {10 00 00 00 00}, delay 2000, null]
dev:20512023-03-12 11:32:50.274 PMtraceMailbox_Vibe_Tuya sendZigbeeCommands received : [he wattr 0x72D0 0x01 0x0500 0x0013 0x20 {04} {}, delay 2000]
dev:20512023-03-12 11:32:50.259 PMdebugMailbox_Vibe_Tuya: Configuring vibration sensitivity to : 4
dev:20512023-03-12 11:32:50.211 PMinfoMailbox_Vibe_Tuya: Battery reporting frequency: 12h
dev:20512023-03-12 11:32:50.209 PMinfoMailbox_Vibe_Tuya: Configuring
@Rxich the logs look OK! Where is this vibration sensor mounted?
... and are you ready to compare this device performance when paired to Z2M? : )
It's back inside the mailbox. It doesn't have the excessive messages, but whenever a vibration occurs, i get unparsed messages.
Each single vibration produces this"
dev:20512023-03-15 06:09:15.527 PMinfoMailbox_Vibe_Tuya: Detected vibration
dev:20512023-03-15 06:09:15.483 PMdebugMailbox_Vibe_Tuya: Zone status: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
dev:20512023-03-15 06:09:15.479 PMdebugMailbox_Vibe_Tuya: Parsing: zone status 0x0401 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000
I have to still move it to Z2M to see what happens
Tuya Zigbee Vibration Sensor driver version 1.1.0 is now available for update from HPM.
Update May 2024: now there is a dedicated thread for the Tuya driver :
Hi Krassimir, I finally !! got around to pairing my Tuya Vib sensor to Z2M. I triggered a vibration on the mailbox and captured debug logs from Z2m. Not sure if any valuable info is found, not sure if it produces less messages than when paired to HE?
PS my sensor is version #2176( _TZ3000_bmfw9ykl), since Tuya has at least 3000 versions
Button","networkAddress":39844,"powerSource":"Battery","softwareBuildID":"2.3.015","type":"EndDevice","vendor":"IKEA"},{"dateCode":"20190723","description":"TRADFRI ON/OFF switch","friendly_name":"Button Tradfri","hardwareVersion":1,"ieeeAddr":"0x5c0272fffeb56b61","lastSeen":1680533490369,"manufacturerID":4476,"manufacturerName":"IKEA of Sweden","model":"E1743","modelID":"TRADFRI on/off switch","networkAddress":25813,"powerSource":"Battery","softwareBuildID":"2.2.010","type":"EndDevice","vendor":"IKEA"},{"dateCode":"","description":"Vibration sensor","friendly_name":"Vib Tuya From HE","hardwareVersion":1,"ieeeAddr":"0xa4c13897c8d72299","lastSeen":1680543434724,"manufacturerID":4417,"manufacturerName":"_TZ3000_bmfw9ykl","model":"TS0210","modelID":"TS0210","networkAddress":46502,"powerSource":"Battery","type":"EndDevice","vendor":"TuYa"}],"type":"devices"}'
Debug 2023-04-03 13:52:24Received Zigbee message from 'Vib Tuya From HE', type 'commandStatusChangeNotification', cluster 'ssIasZone', data '{"extendedstatus":0,"zonestatus":1025}' from endpoint 1 with groupID 0
Info 2023-04-03 13:52:24MQTT publish: topic 'zigbee2mqtt/Vib Tuya From HE', payload '{"battery":100,"battery_low":false,"last_seen":1680544333576,"linkquality":54,"sensitivity":"medium","tamper":false,"vibration":true}'
Debug 2023-04-03 13:52:27Received Zigbee message from 'Vib Tuya From HE', type 'commandStatusChangeNotification', cluster 'ssIasZone', data '{"extendedstatus":0,"zonestatus":1025}' from endpoint 1 with groupID 0
Info 2023-04-03 13:52:27MQTT publish: topic 'zigbee2mqtt/Vib Tuya From HE', payload '{"battery":100,"battery_low":false,"last_seen":1680544337009,"linkquality":36,"sensitivity":"medium","tamper":false,"vibration":true}'
Info 2023-04-03 13:53:57MQTT publish: topic 'zigbee2mqtt/Vib Tuya From HE', payload '{"battery":100,"battery_low":false,"last_seen":1680544337009,"linkquality":36,"sensitivity":"medium","tamper":false,"vibration":false}'
I bought one of these Moes from Aliexpress which came with AAA batteries, it worked fine. Then I bought another one from a different vendor, it didn't come with AAA batteries. The driver reports the Zigbee IDs to be identical.
With this newer one which didn't come with batteries, I got some similar behavior as @Rxich with not being able to adjust sensitivity with the Tuya Vibration driver and it would just go off all the time. So I pulled the battery as suggested by @Rxich and waited for the thing to die completely without the battery. Any capacitive charge remaining. Switched the driver to simply Generic Zigbee motion controller... danced on one foot by patting myself on the head and rubbing my stomach at the same time. Prayed to the electronic gods and then finally put the battery back in. Bingo fixed. Noticed that the sensor LED stopped blinking all the time. So I switch driver back to the Tuya Vibration Driver and this time, I was able to change both sensitive and timeout from 3 sec to 10 sec. Seems that if these are not set up right to begin with they stay in some kind of state where they wont take any configuration request until you pull the batteries out and let it completely discharge. Holding down the repairing button without pulling the battery doesn't fix it. Pulling the battery out and letting it discharge completely, seems to be key. So strange.
Has anyone found someone selling these Tuya Zigbee vibration sensors that reliably work with Hubitat, and don't activate continuously?
I bought 13 from "Moes Official Store" on Aliexpress (_TZ3000_bmfw9ykl
) and 10 of them worked, so I bought another 4; thinking at least a few would work but none did! I then bought 2 on Ebay without the "Moes" brand (_TZ3000_xsjsnzhz
) and 1 of those worked at least!
I'd really like a few more working ones!
I tried what @alex1 said but it didn't help.
With the "Tuya Zigbee Vibration Sensor" driver already assigned, try pairing the device again very close to the hub. Will this bring it to life?