How to configure Aqara T1 Vibration sensor

figured to try a device I didn’t have yet, so bought this VB- S01D

at first it wouldnt be configured at all right out if the box, but after I had checked the battery was ok, pushed the button on the side a few times, and tried a bit, discovered that I had to hold to until it flashed… nothing in the accompanying ‘manual’ of course..

could successfully add it to the Zigbee network on my HA ZBT-2 but the device does exactly nothing…

I re-configured a few times, and always get the green succes, but empty table

the entities are even less useful, so I am wondering if there is anything else that I can do, other than return it?

Not sure if it’s the same sensor or not. Looks the same . I connect my Model DJT11LM ,using Z2M and this is what I have for this sensor:

Thx.
Apparently not the same as mine is recognized as a Lumi device, not Aqara…

It’s useless hardware like this. Can’t imagine being anywhere near reliable stuff.

Does comply with my earlier Aqara experience with different sensors, but given several reviews I figured to give it a try.

IDK. I have few Aqara sensors, no problem at all

So this page shows model I have

While Amaz. Shows your product number. Also double the price almost…


US Amazon page

Right…
Anyways I stopped buying from Am.

Back to the issue at a hand, maybe someone else got the same hardware model and can show their config for it

I do not own the Sensor.
But in generally you can configure ZHA devices over 3 dots —> Manage Zigbee Device.

Sure, but then what . I have no idea which to set to what ..

Also the green Tick seems to indicate a successful config..

Do you have Z2M? If yes, try to delete this sensor(unpair) from ZHA and connect to Z2M. Maybe it will start work properly with MQTT

ZHA is not supported for T1..

Yeah it’s not natively supported on ZHA. That vibration sensor is what put me over the edge to finally move from ZHA to Z2M. You can create sensors manually though: ZHA & Aqara Vibration Sensor DJT11LM missing values/sensors - #11 by mekaneck

After I got it working on Z2M I found out the sensor was worthless for what I needed it for… it’s sitting in the drawer of shame.

slightly off topic then: how can a zigbee compliant device be not supported in the ZHA integration? Does that need to configure drivers of sorts for each and every individual device?

I mean, even with your trigger templates, (thanks for pointing me to the event trigger) half of the functionality we need for full device support isnt there..

and I have to see the first event being picked up..

And for what I know, the next device would again be unsupported on the ZtM

Seems to flakey a device to rely on in any important alarm triggering event, I’ll add it to the other Aqara devices experience list: unreliable (for which ever reason), dont use and return.

Thanks for your final word.
I need a reliable home, not an experimental playground for buggy devices.

fwiw, Ive added to tht open issue in core Aquara T1 door and window sensor connects, no updates · Issue #158489 · home-assistant/core · GitHub

will return it, and look for another vibration sensor device…

apparently the other DJT11LM is

seems the older model.

I had the older model Aqara ones, and they were not 100% reliable. The one I placed on my dryer never registered vibration (too little to register perhaps). I changed to these, and so far they have been very reliable and also register vibration on the dryer. I don’t use ZHA so not sure of the support there, but you can look that up yourself.

Spoiler alert. Most zigbee devices aren’t really “zigbee compliant” in the strictest sense. They mostly rely on quirks to get full functionality. To borrow a phrase from Pirates of the Caribbean, for zigbee spec “the code is more like guidelines”.

Yep, pretty much. ZHA has a massive zha_quirks folder which handles these. Unfortunately for you, no one has ever written a quirk for your device. Z2M’s custom_converters is vastly bigger & is the reason why I switched to it.

Only if you buy a device without first checking if it’s in the supported devices list

This I will remember now
Of course I knew of it, I just figured I could buy blindly now having the Zbt-2

Thx!

I’ve marked that as solution….

Coordinator model has no effect on supported devices. It’s the underlying integration (ZHA, Z2M or Deconz) which controls that.

yes I understand tht now,
hope me adding that diagnostics file of the device might help including it in the zha_quirks file at some point then :wink:

btw no zha_quirks file here? core/homeassistant/components/zha at dev · home-assistant/core · GitHub

found it zha-quirks · PyPI and zha-device-handlers/zhaquirks at dev · zigpy/zha-device-handlers · GitHub

not a single Aqara quirk around.

well what do you know…

I noticed this

and did as such.

it included with a true finished success message

so it got my hopes up.

unfortunately, the device panel remained without real sensors

I decided to give it another -reconfigire, and while it was doing so, I opened the details, and kept pressing the little button, so it emitted the led doing so.

after which I saw the resulting panel I got before with he green Tick.

it shows a few more entireties now, but more importantly, there is action logged

no matter what I do, there’s always value: 1

and a bit later I got the lqi and rssi entities too

now Ive already called it in for return, so wonder if this is enough to keep it after all, or Id better wait for better inclusion…