Replies: 9 comments 11 replies
-
I have the same issue (i have 2 devices, on both this issue) |
Beta Was this translation helpful? Give feedback.
-
Same problem here, i downgraded and it working again |
Beta Was this translation helpful? Give feedback.
-
Same problem here. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue in two Aqara DJT11LM, downgrading to previous version works as usual. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
fixed! Changes will be available in the dev branch in a few hours from now. |
Beta Was this translation helpful? Give feedback.
-
Confirmed fixed using docker tag 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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions