I’ve been using the Aeotec door/window sensor Gen 6 for a while now, and I must say, it’s a fantastic device. However, I recently encountered an issue where the sensor was giving me double events. Initially, I thought it might be a software glitch, so I checked for updates and found that it had already been updated to version 2.1.5. Unfortunately, the update didn’t resolve the issue.
I decided to experiment with different positioning and magnet placements, but every time I tested it, I still got two quick events. This was a bit frustrating because it affected the reliability of my automation rules. For instance, if the sensor was supposed to turn off a light when closed, it would sometimes flip the light off and then back on again.
After some research and reaching out to the community, I found that others had similar experiences. Some suggested trying a factory reset, which I did, but it didn’t help. I then looked into adjusting the sensor’s sensitivity settings within the mobile app. Lowering the sensitivity seemed to help, as it reduced the chances of the sensor detecting multiple events in quick succession.
Another tip I came across was ensuring that the magnet is aligned properly with the sensor. Sometimes, even a slight misalignment can cause the sensor to trigger multiple events. I also found that placing the sensor slightly further away from the magnet helped in reducing the double events.
If anyone else is experiencing this issue, I recommend trying these troubleshooting steps:
- Check for firmware updates.
- Reset the sensor to factory settings.
- Adjust the sensor’s sensitivity settings.
- Ensure proper alignment and distance between the sensor and magnet.
It’s also worth noting that if the problem persists, reaching out to Aeotec support might be the next step. They’ve been responsive in the past, and they might have additional solutions or firmware updates that aren’t publicly available yet.
Overall, while the double event issue was a bit of a nuisance, it’s reassuring to know that there are steps we can take to mitigate it. I’m glad I didn’t have to replace the sensor, and with a bit of tweaking, it’s working smoothly again!