Had the exact same problem. Battery went flat, I replaced it, then no events were received in Hubitat from that point on (note I was using Hubitat's inbuilt driver). I spent 2 days trying to get it paired, tried all of these things:
- pairing again: it would come up as 'found existing device' in Hubitat, sometimes logging a battery level, sometimes not, but still wouldn't receive any button pushes
- pairing again several times, as @SmartHomePrimer suggests
- switching to @cybrmage's driver, & re-pairing several times
- several different batteries (maybe the cheap eBay ones were no good?)
- deleting the device from Hubitat entirely, and pairing again
None of it worked, and I was considering returning it, despite how well it had worked previously... however then I found this discussion on pairing the remote:
It joins deCONZ's ZigBee network without issues. However, it's only responsive for a very brief period after joining the network, and then goes incommunicado. It won't wake on click, turn, or briefly pressing the reset button.
After several attempts, bombarding it with Read Attributes commands to keep it awake after joining the network, I managed to bind the client OnOff cluster to a group. And then the client Level Control cluster. After that, it now behaves normally, waking up to send commands on click and turn.
So I opened two Hubitat tabs, one on the device pairing screen, and one on the existing remote device page (set to the Hubitat driver, but it would probably work with @cybrmage's driver too). I started pairing in Hubitat, clicked the pair button on the remote 4 times quickly to enter pairing mode, kept rotating the remote to help keep it awake, and then once Hubitat found the existing device again, hit Configure on the device tab.
Worked first try - I'm now receiving events from the remote again!
Edit: ok so now I'm apparently receiving 2 button push events for one press (on both drivers)... still better than none I guess?! need to play with it more...
