Aqara vibration sensor does not work properly after update to 1.40.2-1 version

[bytdoma]

Hello,
after an upgrade to new version 1.40.2-1 in Homeassistant Aqara vibration sensor only shows values for vibration and strength, others: angle_x, angle_y, angle_z, x_axis, y_axis, z_axis became Unknown. I did not check other entities unfortunately. I reconfigured the device, prompted, restarted Homeassistant and let it run for about na hour, but no change. I downgraded back to 1.40.1-1 via my backup and it is working again.

[MarcoZ76]

I have the same issue (i have 2 devices, on both this issue)

[Maggie70]

Same problem here, i downgraded and it working again

[MurilloRacing]

Same problem here.

[MurilloRacing]

I downgraded to 1.40.1-1, still has same issue. Aqara vibration sensor: angle_x, angle_y, angle_z, x_axis, y_axis, z_axis Unknown

[Maggie70]

try shaking the sensor to trigger it

[MurilloRacing]

That worked, thank you

[Koenkk]

Could you provide the debug log when triggering it in 1.40.1?

See this on how to enable debug logging.

[Claude2666]

I rolled back to 1.40.1-dev commit: [0540e4f]

Attached a debug log of my tilt sensor, I hope it contains the needed info.

tilt.txt

[MarcoZ76]

Can you tell me how to downgrade to the previous version? I have HA OS and the Z2M is installed as addon component. Thanks

[Maggie70]

when updating created a backup of the old one, read it back when it didn't work with the new one.

[raforo]

I have the same issue in two Aqara DJT11LM, downgrading to previous version works as usual.
Shaking the device, shows vibration and action changes, but angles remain unknown.

[rojoricardo]

I'm having the same issue with latest version, I'm downgrading right now, and I'll check and update.

UPDATE I can confirm that performing the downgrade / Restoring backup of version 1.40.1-1 fixed the issue.

[Koenkk]

fixed!

Changes will be available in the dev branch in a few hours from now.

[MarcoZ76]

Thanks! When will be available on stable release?

[Koenkk]

1 November

[Nevynnyi]

Thx!!! ☺️

[jeremysherriff]

Confirmed fixed using docker tag latest-dev with zigbee-herdsman-converters release 20.25.0, many thanks

Note to others: the values seem to stay 0/null until I made the device sends through a vibration event, at which time the values all updated.

[paulbrause]

Updated to latest Dev-Version, but still not working correctly. Values updating one time after first vibration event, but after that no further update of the axes and accelerometer values.

[jeremysherriff]

Updated to latest Dev-Version, but still not working correctly. Values updating one time after first vibration event, but after that no further update of the axes and accelerometer values.

Agreed, I'm seeing the same behaviour. Things are not working right, @Koenkk. I think this needs to be reopened.

@paulbrause I've had more time to experiment today and I cannot reproduce an issue on 1.40.2-dev commit: db00759 with zigbee-herdsman-converters release 20.25.0. To me this looks to be resolved, I'm not sure what was causing the data to not update last night but today I cannot fault it.

Edit: If it helps (?) I rolled back to 1.40.1, and then forward to latest-dev. Having checked the edit in the commit I cannot see why this would make a difference, but it is what I did.

[paulbrause]

Updated to latest Dev-Version, but still not working correctly. Values updating one time after first vibration event, but after that no further update of the axes and accelerometer values.

Agreed, I'm seeing the same behaviour. Things are not working right, @Koenkk. I think this needs to be reopened.

@paulbrause I've had more time to experiment today and I cannot reproduce an issue on 1.40.2-dev commit: db00759 with zigbee-herdsman-converters release 20.25.0. To me this looks to be resolved, I'm not sure what was causing the data to not update last night but today I cannot fault it.

Edit: If it helps (?) I rolled back to 1.40.1, and then forward to latest-dev. Having checked the edit in the commit I cannot see why this would make a difference, but it is what I did.

@jeremysherriff You are right. After rolling back to 1.40.1. and then updating to latest-dev everything works fine. Thank you!