I used an iPhone QR code reader to get the value of the QR code on each bulb and used the Brother P-Touch label printer to print the QR code using the code I had read and stuck the new QR code near each bulb so that I can scan the QR code without having to remove the bulb. The good thing is that I do not need to remove the previous instance from the app before re-adding the bulb. It seems to know it is the same so I do t wind up with two copies.
2 Likes
I reset the bulb thru the Aqara app, then re-added it. The bulb had been using the Zigbee firmware. When I re-added the bulb, I switched to Matter firmware, then switched back to Zigbee, keeping my phone close to the bulb to make sure I got a clean Zigbee firmware download over my phoneās Bluetooth. Then I reset my automations and the bulb behaved as expected for about 2 days, then the āAnti-deleteā notifications came back, and I am once again being flooded with them. I am using an M2 Hub btw.
1 Like
Hello.
You can take the lamp and plug it into another light fixture, for an experiment. Just a bedside lamp, for example.
1 Like
I did that. Same problem. Itās not the socket, itās the bulb.
2 Likes
Could you have spikes in your electricity supply, the reason I ask is that if power drops below a certain level perhaps the bulb is detecting this as a reset request.
I would ask a friend if you have one to test the bulb in their environment to eliminate electricity spikes.
Spikes can be caused by Fridgeās & Freezers or heat pumps etc or just come though the mains electricity.
I have a UPS on my house setup and I get notified of spikes and youād be surprised how many can occur daily.
Iām not saying it is this but itās worth a check.
I donāt think so. We do have spikes and brownouts but the bulb seems to do just fine. The M2 hub is on a UPS. The bulb is part of an automation that turns the light on or off based on motion sensor activity. When the no-motion timeout occurs and the bulb turns off, thatās when the āanti-deleteā notification occurs. I can manually turn the light on or off with no issue.
Wow, Iād remove the automation with regards to thew motion sensor for now as this could be causing the issue.
Please test this by disabling the automation.
Also you could attach a notification to the motion automation to see if it multi-triggers.
Can you share your automation?
Itās a simple automation. When motion is detected, turn the light on. When motion has stopped for 20 minutes, turn the light off. I can see in the logs that the anti-delete notification coincides with the light turning off. If this simple automation (which Iāve used before with Aqara plugs) is a problem for the Aqara bulbs then Iāll be switching to Hue bulbs.
Indeed but did the purpose of testing disable the automation helps pinpoint the issue somewhat
Not necessarily. There have been random anti-delete notifications as well. In fact, Iāve often been flooded with them. But every time the automation turns off the bulb, it reliably generates one. If we take a step back, I am not the OP on this issue. OP and others in this thread are reporting the same issue with the bulb losing pairing or triggering anti-delete notifications.
I would almost suspect Zigbee noise or interference but OP had the issue with Matter.