Advanced Button Controller (ABC)

stephack · January 20, 2020, 7:41pm

It would be difficult for me to troubleshoot without the logs and a few more details.
Just to confirm a few things:

When you look in the Apps Code section, you should only have once instance of the ABC app and one instance of the ABC Child Creator.
Are you manually setting the number of buttons in ABC or did it find the correct number of buttons automatically?
What is the exact option you are choosing to "turn everything off"?
For good measure, what version of the HE firmware, ABC parent app and ABC child app are you running?

beddini · January 20, 2020, 9:18pm

Thanks for getting back @stephack.. I'm on site and can verify:

Have the latest:
ABC button mapping (child creator) v0.2.191105
Advanced Button Controller v0.2.190114

those are the only 2 instances of imported app code I have.

I let abc find the correct number of buttons (no override).. Of course when I import the 4button pico in, I have to ensure I set it from 5 to 4 buttons under Devices

When I say "turn everything off" I use: Switches->Turn Off->When Pushed. FWIW I can add 3 scenes and when I add the 4th button for all off.. it chokes.. or I can add 2 scenes for buttons 1-2 skip button 3 and add the Turn Off command to the 4th button. But if I try to add the 3rd scene to button 3 after that.. it chokes.

Hubitat Elevation® Platform Version: 2.1.7.127
Hardware Version: Rev C-5

And lo and behold.. I run the mapping add sequence in debug and it worked just fine (sorry):

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:16:18.134 pm [debug](http://192.168.1.24/installedapp/configure/86)Kitchen Scene Mapping

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:16:18.130 pm [debug](http://192.168.1.24/installedapp/configure/86)INITIALIZED with settings: [collapseAll:true, buttonDevice:Kitchen Scene, logEnable:true, lightOn_1_pushed:[Kitchen Scene 1], lightOn_2_pushed:[Kitchen Scene 2], lightOn_3_pushed:[Kitchen Scene 3], lightOff_4_pushed:[Kitchen UnderCab Stove, Kitchen UnderCab Sink, Kitchen Entry Ceiling, Bar UnderCab, Bar Ceiling, Kitchen Ceiling]]

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:16:12.668 pm [debug](http://192.168.1.24/installedapp/configure/86)Device Type is now set to: Lutron Pico

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:15:01.931 pm [debug](http://192.168.1.24/installedapp/configure/86)Device Type is now set to: Lutron Pico

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:14:44.417 pm [debug](http://192.168.1.24/installedapp/configure/86)Device Type is now set to: Lutron Pico

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:14:27.138 pm [debug](http://192.168.1.24/installedapp/configure/86)Device Type is now set to: Lutron Pico

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:14:23.318 pm [debug](http://192.168.1.24/installedapp/configure/86)Device Type is now set to: Lutron Pico

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:13:58.479 pm [debug](http://192.168.1.24/installedapp/configure/86)Device Type is now set to: Lutron Pico

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:13:48.805 pm [debug](http://192.168.1.24/installedapp/configure/86)

[app:86](http://192.168.1.24/logs#app86)2020-01-20 04:13:48.797 pm [debug](http://192.168.1.24/installedapp/configure/86)INITIALIZED with settings: [collapseAll:true, buttonDevice:Kitchen Scene, logEnable:true]

stephack · January 20, 2020, 11:12pm

Sorry, I dont follow. Did you get it working? I'm not sure what u mean by "mapping add sequence in debug"

beddini · January 21, 2020, 4:33am

Sorry for the confusion @stephack, I went to generate a debug log with the error in it by generating a new Pico device mapping from scratch. When I did, it worked fine.. but the day before no matter how many times I tried it would error on the 4th button. I will send the log when/if it happens again. Thanks for your help!
Best,
Andrew

wayne2 · January 21, 2020, 6:52am

Fantastic app @stephack. Do you take pull requests? I have changes to 4 lines of code and added 1 line. This adds support for cycle of CoCoHue Scenes.

stephack · January 21, 2020, 11:38am

Glad to hear that. If it does happen again, please try to remember the exact steps it took to recreate and when precisely the error occurs in the sequence of steps.

stephack · January 21, 2020, 11:43am

You can submit the PR but it may take a while for me to accept. I dont have a hub in production at the moment to properly test any changes and I also have a couple of feature requests to get added. I will do my best to get your changes incorporated as time permits.

wayne2 · January 21, 2020, 4:33pm

Excellent, will do.

wayne2 · January 21, 2020, 9:12pm

Done.

yototogblo · February 25, 2020, 6:49am

I use ABC to turn off my Hue bulbs from my Inovelli ZWave light switches. Also, I reboot my hub every other day to cut back on the slowdowns.

I've noticed that ABC takes a while to respond to button presses after a restart. Typically, my hue bulbs turn on or off in about 800ms after the switch is pushed. However, right after a restart, it typically takes about 7s. It almost feels like the app doesn't actually get initialized until the first button press.

Please help look into this. I created the same automation using Hubitat Simple Lighting and it doesn't have the same issue.

Thanks

stephack · February 25, 2020, 4:37pm

I still haven't had the time to put one of my Hubitat hubs back into production, so I cant test your theory on my end yet. However, I'm pretty sure wasn't seeing your issue when I was using HE a few months ago.

A few questions:

Is this a recent problem?
What firmware version are you on?
How long after the reboot are you testing? It takes a while after a reboot for the meshes to truly settle in.
Can you replicate the problem consistently?
If you look at the logs, it should provide clues as to where the delay is occurring. Share a screenshot of the logs when this occurs if you can.

Please bare with me as I'll be trying to assist blindly until I can get my hub back in production.

yototogblo · February 25, 2020, 5:50pm

Thanks for your response! Answers below:

Nope. Had this issue from day 1 which was back in December

Latest i.e. 2.1.9.114

I've tried 2 minutes and a few hours after. Doesn't make a difference

Yup, every time! The amount of time it takes to respond varies each time after a reboot but is always slower than the typical timing.

This time is actually one of the fastest I've seen of it responding after a restart. It typically takes about 7s. I just did the latest update also though so maybe that helped.

Also, the delay is always between the switch sending the central scene (or the button press) and the ABC debug app picking it up.

stephack · February 25, 2020, 6:05pm

I may be misreading the logs above, but it looks fine.
Assuming that dev23 is your inovelli switch and app28 is the ABC instance associated with it, then it's taking 500ms to respond to the CentralSceneNotification. It then takes another 600ms or so for Ben and P lights to actually turn on (which is not in the control of ABC...it can only send the command it is configured to).

Please let me know if I'm not seeing the obvious.

yototogblo · February 25, 2020, 7:13pm

No, you're right in this case. That's why I mentioned that it was much faster than typical and was wondering if that had more to do with the latest update that I just installed. However, even in this case, you can see that the next 2 times I toggled the switch, it only took 300ms (vs 530ms) for ABC to respond.

I just tried rebooting the hub again and here are the new results. As you can see, it took about 2.6s for ABC to register the button press right after the restart and then only 200ms after that.

stephack · February 25, 2020, 8:30pm

Thanks for the update @yototogblo.
@bravenel @chuck.schwer any thoughts on what was described above? I don't know what is considered normal for the first time an app is initialized so I can't say if my app is outside of what is to be expected. I would appreciate any feedback you could provide.

Tldr for issue

after a hub restart the ABC app takes anywhere between 500ms and 7s to process a button event. Thereafter it operates at an expected speed.
I am currently unable to do a comparison on my hub as it is offline.

kuzenkohome · February 26, 2020, 12:19am

First, thanks for this great app.

Feature request: Under "Only Execute When:" "Only during a certain time" can it updated to support sunset/sunrise rather then only specific times?

Mike

stephack · February 26, 2020, 12:21am

...I have no clue how to subscribe to sunset or sunrise events in HE. I will have to ask the community and/or the hubitat team.

kuzenkohome · February 26, 2020, 12:23am

Ok understandable, will wait and see then.

stephack · February 26, 2020, 12:26am

Keep an eye on this thread

stephack · February 26, 2020, 12:32am

I got an answer from Bruce but before I really thought out your request. I assume you are asking to only have the button work between a certain time and sunset/sunrise. This might be trickier than I thought initially. Will have to think it through.