When pairing it, it showed 2 devices, and neither one worked with the natively selected driver. I was able to change the driver to the Philips Dimmer Button Controller, but I can't actually use any of the buttons in Button Controller. It doesn't show any buttons at all to select from. When I got into the Device and select events, I can see it registered recent button pressed.
Further, in Devices, under current states, all I see is Current States
battery : 77
pushed : 1
I don't see any button numbers. What am I doing wrong here? I've tried googling quite a bit and am sure there's some additional button mapping or something simple that needs to be done when updating drivers? Thank you!!
See if hitting the "Configure" button on the device page helps (you won't see anything happen, except maybe in the logs, but this is something you should run if the device has such a command available and the hub didn't select the right driver upon pairing).
I'm not sure what you mean with "options," but you should see pressed and held events (whose last value will be represented under "Current States" with attributes having those names) if you do indeed perform those real-world actions on the device. If that isn't working, it's likely the "Configure" didn't work (or this device is radically different from whatever Hubitat tested with this driver, though I'm not aware of Philips having made changes since v2 was introduced). I would make sure you're using the "Philips Dimmer Button Controller V2" driver--I just re-read your original post and it looks like you might be using the "original" driver.
If that doesn't help, maybe try resetting and re-pairing the device. Don't remove it from Hubitat first, and keep the driver at the correct "Philips Dimmer Button Controller V2" driver. Hubitat will recognize it as the same device, and the "Configure" command will automatically run on pairing, which should help if the device happens to not listen for these normally (but most do; just a guess for this one).
Well, part of the issue is that the hub was running version 2.2.6. I am updating my hub to 2.2.8 right now, and it sounds like that is what I need to get the native driver for V2. I updated the Hub and selected the Driver for V2 now that I see it. I clicked the configure button listed under the device. I still don't see any number for buttons held, pressed, or released.
When attempting to make a rule in Button Controller, it asks how many buttons I want to add. I say 4, and then select "Push" and then click the Define buttons,
Unexpected Error
An unexpected error has occurred trying to load the app. Check Logs for more information.
Error: Child app not found for namespace: hubitat and name: Button Rule-5.0a
Now, when I try to create a rule with the device, I do not see the option to select any buttons.
Thanks again for all of your help, it is greatly appreciated!!
A reboot should solve this particular error (not sure why it's happening, but it seems to have affected some people the last couple updates when app "versions"/names get updated, as they were in 2.2.8 and a recent hotfix). That would be a different problem from "numberOfButtons" not showing for the device, but a "Configure" (sounds like you just tried that) or "Save Preferences" might help if you haven't tried them since switching to the correct driver.
(What you should see is one line for "numberOfButtons" under "Current States," by the way; "pushed," "held," and "released" should just show the last button number that experienced one of those events. There are ways to force this to appear, like switching to the Virtual Button drive or one that lets you manually set the number of buttons, then switching back, but if won't help you if the device didn't get its configuration correctly sent to it, which it might not have if it isn't reporting button events back correctly. The suggestion above to re-pair without deleting the device might help if you haven't done that, either.)
This is great, thank you! I rebooted, and am not seeing the error, but am still unable to use this device in button controller. When I try to set it up, now it asks how many buttons there are. None of my other buttons ask that question, so I suspect you're 100% correct that it wasn't setup correctly.
I tried to get the Hue Switch into pairing mode by holding the top button for 3 seconds, and I can't get it to repair. I have tried about a dozen times now. I've removed the back battery. Is there another trick to getting these to pair again? Would it help if I deleted the existing device in the Hubitat portal?
I only have the v1 remote (and had bad luck with it falling off Hubitat, so I moved it back to Hue, where it still does everything I need), so I'm not sure about the v2. I'm assuming you've consulted the Hue docs for the reset/re-pair, but Hubitat has instructions too that might be useful if you haven't seen them already: Join and Reset Instructions - Hubitat Documentation (scroll down to the ones for this device).
Deleting the device on Hubitat shouldn't matter, but I have seen reports that sometimes the device doesn't pop up again on the pairing screen like it used to (and like it does the first time), so you may just never know that it happened. That being said, if you don't have any apps/automations using this device yet (or just delete the failed attempts), removing it should also work--I'm just assuming that it will choose the wrong driver again and you'll be back where you are. But then I suppose you can just choose the v2 remote driver again, hit "Configure," and see if your luck changes.
Maybe someone else who has one of these can chime in.
I feel like I'm getting somewhere! I deleted the device, then I was able to reset the device by hitting the small button on the back that is inside the battery compartment. Following that I was able to repair the remote right away. However, I am still having the same issue when trying to add buttons in button controller. The moment I select "add buttons for these actions" it blanks out and won't let me add any buttons or advance in anyway.
Yeah, Button Controller reads the "numberOfButtons" attribute from the device (visible under "Current States" on the device page--or should be). If that's empty or missing, apps like Button Controller won't know what to display in their UI.
If the device is otherwise working, you could try my suggestion above: change to a driver like Virtual Button that allows you to set this number, then switch back. But if the device didn't get configured correctly (again, the driver should do this automatically on pairing, or with a manual "Configure" if you switched drivers), the button events themselves will probably not get generated, which is still a problem. I'm not sure what more you could try for that given that I think you've exhausted all reasonable troubleshooting at this point.
