Since sometime last night, I’ve suddenly encountered problems with both of my Aeon Minimotes (both with the latest firmware and full batteries; they are from different batches from different suppliers) being used as secondary controllers with my SmartThings (v2) hub. Nothing in my setup has changed recently, and both remotes were working flawlessly less than 24 hours ago. The remotes are used to control simple switches and Philips Hue lights via SmartThings. The switches are various brands.
Tonight, suddenly button presses on both remotes don’t trigger anything as they did for the past several months. Instead, when a button is pressed, both red and blue lights flash briefly, followed by a pause of about a second and then a single flash of the red light. I discovered through trial and error that if I press and hold any button for a couple seconds and THEN press the desired button, it works as expected – but only that once. I have to repeat this each time I want to press a button.
For troubleshooting, I have tried the following:
- Replacing the remotes via SmartThings
- Completely removing and re-adding the remotes via ST
- Cycling power on the ST hub
- Repairing the Z-wave network via ST
- Live logging via the ST API – nothing is logged unless I press/hold and then press again as described above
Aside from the remotes, everything is working as expected. I can control devices directly through SmartThings, and the Alexa integration works as usual. It’s only the Minimotes. If it was just one of them, I’d think it had gone bad; however, both developed this same issue within the past 24 hours, so it would have to be one helluva coincidence if somehow they both went bad.
I’ve tried Googling this light sequence but am coming up with nothing concrete. (The closest I came was this thread from April, but these guys seemed to be having problems from the get-go, whereas mine had been working fine for ages.) Anyone know what this light sequence means or have any suggestions for things I haven’t tried, aside from the device handler mentioned in that thread?
- ST knows about the issue and is working on a fix: http://status.smartthings.com/incidents/6gt95l317l9s
- I solved the problem, at least temporarily, by changing to the device handler from @Kyse: