Hello, I’ve been sailing pretty smoothly with Hubitat for about 5 years. Suddenly in the last day or two my button controllers have gone haywire. I have some pico remotes, some Zooz Scene controllers, Inovelli switches, etc.
Basically when I push the buttons on some devices, the logs show a button pushed, but the Button Controller App isn’t responding. This isn’t across the board - it’s on one particular pico remote and several of my Zooz scene controllers but not all of them. I’m really hoping to not have to rebuild all of the button apps. Any suggestions?
At a random guess it sounds like a network issue, rather than an issue with your automations. Would I be right in thinking most of those devices are Zigbee?
(FYI - My ability to help will quickly run out here I expect...)
I appreciate the suggestion - I had wondered if network was the issue, too. They are not all zigbee - though I just did some trials.
My pico controls a mix of lights upstairs (all zigbee) and a zwave fan in our bedroom. The remote works on the fan but not on the lights.
I have an inovelli switch in our bedroom, and it WILL control the lights with the appropriate “button push.” (Ie It’s not directly wired into the lights)
Strangely enough when I activated logs, the buttons start working ONLY on the ones for which the logs have been activated. Also, these all appear to be Button Controller-5.1.
One other note - after I've turned logging on, run the command, and then turned logging off, the buttons appears to continue working. I have A LOT of buttons for which I would need to do this. Is there a quick workaround? Can these be upgraded to the newer version of button controller?
Button Controller 5.1 makes "Button Rule" (grand)child apps, so I used both names depending on where you look.
I suspect what happened is that you clicked "Done" after enabling logging. This would re-add the event subscriptions, which it's possible were lost for some reason before. The App Status page ("i" icon) would show you this information, though that would mostly be a matter of curiosity as the only fix is something like this anyway.
Logging per se has no effect; that's just for your troubleshooting.
I also have several Aeon Minimote and Aeon Wallmote (all controlling Zwave devices), stop working a few days ago. I know I did an update, (to Platform version 2.4.2.129 (hardware C-7), a few days ago.
I have gone to the device pages and can watch the buttons being triggered when pressed and recorded in the logs. I turned on debug logging and again saw the device button being pressed. The logs indicate the button press is triggering a CentralSceneNotification, but the action / scenes are not actually being triggered.
Almost all of my scenes replicate turning on a device or sets of devices. Activating the scene through the hubitat app, web interface, or through alexa (or through Home Assistant) all work as expected.
But I can't seem to do anything to get the button to trigger the actual scenes.
Does anyone have any suggestions on further troubleshooting?
Not sure what you mean by this: you don't need debug logging (just descriptionText logging) to see things like "button 1 pushed" for the device in Logs, at least with stock drivers or other that follow that convention. Debug logging (again with this convention) will show you more "raw" data, which for a Z-Wave device with this kind of functionality is probably going to be a CentralSceneNotification. But it's the CentralSceneNotification that should result in a button event on the hub, not the other way around (the real-world action should result in both).
I'd suggest just hitting "Done" in any affected app and enable logging, as suggested above, if that doesn't help. (You could check "Event Subscriptions" before and after doing this to see if anything changes -- the button device should be there -- but there's no way to change this, other than that "Done" should [re]set them, and my thinking is that maybe this got lost for you for some reason.)
Doing what is mentioned here worked for me. Took some time to click “done” on every butt, but that did fix the issue. I think an update broke mine, as well. I guess it’s time to rewrite my buttons for the newer controller. Good luck!
Good luck!
