I am seeing multiple instances of the button controller child apps failing. I was able to capture the details from the latest failure after the boss came up to angrily tell me that she could not turn off the lights in her craft room.
I checked the event logs and found the button press event. However, the app shows the subscription to the button events but has logged nothing. The app has existed for at least 2 weeks.
@bravenel any thoughts on this one?
Show the app page itself.
I ran into something possibly similar a few days ago -- after setting up an ST button (first one, so new to me), I couldn't get the accompanying simple lighting action to fire -- I noticed that a physical push would not work, however a software push (clicking the device in web app) did -- then noticed that I had not entered a button number for the device when I set it up -- it was being logged as 'null' -- so I updated that field to 1 and the simple lighting action worked as expected.
Same thing for me too. After populating the physical button to 1 instead of null, it worked. I use ABC Button Controller for my button.
Button Controller doesn't put out any App Events, so we don't have that to go on to shed any light on this. The one other thing you could look at are the device events for the button device (from Events button on device page). What driver is being used for this button device?
The very first screenshot I posted in this thread was from the event log for the button. The button is a virtual button using the stock driver. It shows the button as sending both a push and held event.
The device being controlled was a Hue light connected to a Hue bridge, so I cannot even point to my recent Zigbee mesh issues as a potential culprit.
Actually, that screenshot is from the Logs, not from the device events. I don't need you to post it. But just go look at it. Events are different than Log entries. The latter happens due to code in the driver that is "log.info". The former is from the system actually seeing an event thrown by a driver. Apps respond to events, not to logs.
I'm going to introduce either app events or logging to Button Controller. There is no other obvious explanation. Hopefully, that will make it to the next release...
For grins, why don't you try turning on some other device with that BC instance.
@bravenel I appeciate your help, but with all due respect I've provided more than enough feedback on this particular issue. My Hubitat system is the home automation equivilent of a dumptser fire right now with all of the bugs, glitches, and unexplanable issues. I cannot devote any futher time on this issue.
But thank you for the help anyhow.
For whatever it's worth, you are the only person to report a problem of this sort with Button Controller. It's a relatively simple app, as you can imagine. And, your instance is itself quite simple. So, from a position of a good bit of experience with it I'd be very surprised if your problem is actually a Button Controller problem.
Your situation is unique. I'm sorry you are having so many issues. We just do our best to plow through them, isolating issues, diagnosing specifics, etc. I think you know the drill. Problems with complexity are not easy to solve.
I agree. But it would be nice to get some action or at least a response on a ticket that has been open and idle for 2 weeks now. At this point we're not solving anything and the issues continue to pile up.
That's interesting. I'm under the impression there has been fairly constant contact with you. I guess I can pull the records and see. You make it sound as though we've been sitting on our hands, and that's not true.
I respectfully disagree with that statement. I'll let the facts speak for themselves.
Ticket #11505 - SmartPlugs going unresponsive. Opened 12/29, last response from support 12/29. Status: No action/unresolved.
This ticket was opened because SmartPlugs were going unresponsive after sitting idle for a short period of time.
Ticket #11543 - Zigbee Network - Poor Performance. Opened 1/2. Last response from support 1/2. Status: No action/unresolved.
This ticket was opened because the entire Zigbee network was failing. I recevied no response to the prior ticket so I started a new one since this was a more critical and widespread problem.
Lacking a response from support, I nuked the Zigbee network and rebuilt it over the course of 3 days. (All 172 devices!) It did not help.
Seriously? That's all you can say?
Download the Hubitat app
