This probably belongs in a new thread, as the issue you're experiencing is not related to the ABC Application. Rather, it appears that the Pico remotes have not been added to Hubitat correctly, as the hub does not seem to be 'seeing' any events from the Pico remote. Did you use the Lutron Integration App to add these Pico remotes?
1 Like
Thanks @ogiewon . I will do some additional troubleshooting and if I have additional questions will spin up a separate thread! Thanks for the quick response!
2 Likes
Does anyone have any pointers on how the buttons map for a Zooz ZEN71 switch?
I want to double-click "off" to turn off all the lights downstairs. Would that be Button 5?
Simply open the Hubitat Device details page for your Zen17. While pressing, double tapping, holding, etc… the buttons, you will see the attributes update on the page in real-time.
5 Likes
Hi,
Still quite new to Hubitat.
Is ABC still supported? If I try to install the driver the usual way of cutting raw content and pasting into Hubitat Drvers section I get the error below.
No signature of method: Script1.definition() is applicable for argument types: (java.util.LinkedHashMap) values: [[name:Advanced Button Controller, namespace:stephack, singleInstance:true, ...]] on line 19
The driver URL is https://raw.githubusercontent.com/stephack/Hubitat/master/apps/Advanced%20Button%20Controller%20(ABC)/Advanced_Button_Controller.groovy
What am I doing wrong? Is that the right driver?
I'm trying to configure a Symfonisk rotary should controller as a volume knob for a Sonos speaker without the Ikea hub.
Thanks in advance.
Paul
try installing it in the App Code section instead of as a Device driver
4 Likes
Is it possible to add the ability to turn on a scene? I was thinking for the Wiz bulbs.
Most "scenes" are represented within Hubitat as a simple switch device. This allows scenes to be 'activated' by simply turning on their corresponding scene activation "switch" device.
So, assuming your scenes are implemented in this manner, the answer to your question is "Yes, scene activator devices can be turned on within ABC, just like any other switch device." Hope that helps!!
1 Like
I can do this action in Hubitat Button Controller 5.1. I just didn't see where this is possible in ABC. Was trying to keep it under the same app. Thank you for responding.
Button Controller 5.1:
Here is one of my Wiz bulb current states:
Summary
@thebearmay Thank you so much for your Button Controller and the effort!
We have the APP Code installed.
The ABC Controller shows in the APP.
Our objective: Create a Legacy Shade (controlled 100% via HTTP post).
1- We created a Virtual Button (Button A), with 3 push.
2- We created a Virtual Shade (Virtual Shade A)
3-
a)We created a child in ABC, "Somfy Showroom"
Inside the Child we have the Virtual Button (Button A), and it refreshes with the 3 buttons automatically. Great.
b) Setup of each button inside ABC, to work with the Virtual Shade A. One button for open, one for stop, and one for close. All Associated with the Virtual Shade A.
4- We have 3 rules in RM:
a) When Virtual Button A, Button 1 pushed - send HTTP POST request for open
b) When Virtual Button A, Button 2 pushed - send HTTP POST request for stop
c) When Virtual Button A, Button 3 pushed - send HTTP POST request for close
(The rules if triggered manually, they work OK, and shade opens/closes/stops via http post in the rules)
Now comes the doubt.
How do we add to the dashboard, and which template to use to have the window shade show with 3 buttons (up/stop/close).
We tried adding the virtual button A, as a template Button, but only shows 1 button and each in different tiles.
We tried the Shades, but the scroller doesnt work either. The same with Garage, or Garage control.
If someone could point me in the right direction I would really appreciate.
Thanks!
We tried the
2 posts were split to a new topic: Remotec ZRC-90 Scene Master driver?
Have been using this for years but just saw last update was in 2022. Is ABC still the go to app app for button devices on Hubitat?
Is it possible to use Hubitat's virtual buttons in ABC?
Here is my use case:
I have a few BlueAir Wifi Air Purifiers. I can connect them to Alexa/Echo to control them. I have configured Echo speaks to execute a routine on my echo device. I then have created a virtual button to trigger the echo speaks execution.
Virtual Button 1 triggers the routing on the echo to set all fans to high
Virtual button 2 triggers the routing on the echo to set all fans to off
Now, I am trying to configure a Lutron pico with those virtual buttons.
Press button 1 on the Lutron pico, trigger Virtual button 1 push which launches route 1 on echo speaks, fans on high.
Press button 2 on the Lutron pico, trigger Virtual button 2 push which launches route 2 on echo speaks, fans to off.
I'd prefer a virtual button in ABC for this as it would be a single device vs multiple virtual switches.
Am I thinking this too complicated?
Is there a way to toggle on and off a Hue Scene?
I was told that moving this query here may get me the help I need
–
Hub: C-8 Pro
App: ABC Button
There are four buttons on my Moes scene controller. So far, I have buttons 1 and three set up to toggle lights (1) and a little floor fan (3). All work fine.
What I want to do: I want to set up buttons 2 and 4 as follows: a) press and hold button 2 to raise light levels, and b) press button 4 to lower the light levels.
What I did: I selected ramp up with auto stop and ramp down with auto stop.
What happened: Button 2 does not ramp up the lights if they are off. If I turn the lights on with button 1, then press button 4 to dim them down, just pushing it dims the lights to zero.
The problem: All I see for a choice is “Pushed”. There is no “Hold” or “Hold and Release”.
What am I doing wrong?
Thanks, gang.
What specific model number is this Moes scene controller?
For now, let's ignore the ABC app, and focus our attention on the Moes Scene controller device in Hubitat. Please open that device's page in the Hubitat web user interface. Once you have that page open, please press each button on the Moes scene controller and observe the Current States section of the device's page as shown below.
Note: The above is for a Lutron Pico remote, so your screen will look a little different.
Each time you PUSH a different button, the number next to the "pushed" attribute should change. Please verify that all 4 button numbers appear as expected.
Each time you HOLD a different button, the number next to the "held" attribute should change. Please verify that all 4 button numbers appear as expected.
When a button is RELEASED, its numeric value should appear next to the "released" attribute.
PLEASE NOTE: Not all devices support pushed, held, and released for all (or any) buttons. Much depends on the specific device and the driver that that is being used.
By determining how your Moes Scene Controller behaves, it will greatly help in understanding whether or not each button can be used as you intend.
I think it would make more sense to keep this discussion here:
For the exact reason @ogiewon stated; the issue is likely related to the button device, rather than the app being used to control it (until proven otherwise).
All are behaving as intended.
-
Please share a screenshot for the Moes device like the one I shared above.
-
Please share the model number of the Moes device as reported in the Hubitat device page.
-
Please share the name of the driver being used by the Moes device.
It appears that particular device/driver combination does not support “held” events per the Hubitat standard definition.
Your screenshot is also odd that the pushed button number and the released button number are not the same. Typically one presses and release a button, causing the pushed and released values to change to the same button number. Pressing a different button will cause the number to change for the pushed and released attributes.