Konnected Alarm Panel PRO Outputs

[b.griffiths1207]

I have purchased 4 @ Alarm Panel PRO units for conversion of my hard-wired existing system. I am using this with Hubitat C7 running platform 2.4.0.151. I am presently bench-testing the first Alarm Panel PRO to familiarize myself with how things work, and have run into an issue using the Konnected auxillary outputs that seems easy enough, but I cannot figure it out.

1. I have successfully completed the firmware for all the inputs and outputs using the Konnected mobile app and am using an Auxillary Output to use for a Door Chime:

2. I can test the Door Chime Piezo buzzer by pressing the PUSH button within Hubitat on the Commands tab, so I know it is working correctly:

3. I want the Door Chime to work when the Utility Door Input is seen as “open”. The problem lies when I try to create a rule within Hubitat where I cannot find the “Door Chime output” listed within Hubitat. I have tried creating this rule as both a “Basic rule” as well as with “Rule Machine” with the same results, i.e. neither shows me the Door Chime Output as an option, even though it is clearly there in the list of devices:

In making changes to the device type in the Konnected firmware, I have discovered that the only device that shows up as an available device in Hubitat as an ACTION item tha can be used in a rule is a Switch On/Off:

Any outputs on the Konnected board that are set up with any other type of output, e.g. momentary, that use a Konnected Button Trigger type do not show up in the list of ACTION devices where they are be used in a rule:

This has me stumped. Any assistance would be appreciated.

@nate

[SmartHomePrimer]

I don't have Konnected, but can guess how this can probably be achieved. Use Rule Machine and look under "Custom Attribute". You'll likely find a device state you can use for the trigger.

[b.griffiths1207]

Appreciate the response.
However, it is not the "trigger" that is the issue (I can see all the Konnected INPUT devices (in the screenshots above I am using the Utility Door contact sensor as the trigger device. The issue is the Output device (ACTION), i.e. the only output devices listed in Hubitat are those that are On/Off Switches - it is not showing any of the momentary output devices - even though they are listed in the device list:

[nate]

Thanks for posting the detail @b.griffiths1207
To get to the heart of the question/problem we're trying to solve -- Konnected implements the Momentary capability for some output types (chimes, momentary switches) that respond to the push() command using this DH: konnected-hubitat/drivers/konnected-button-trigger.groovy at master · konnected-io/konnected-hubitat · GitHub

@b.griffiths1207 is reporting that these devices don't show up as selectable when Push is selected as an Action for a basic rule.

I'm looking for help about what needs to be added to the DH above to make this device selectable in a rule.

Thanks!

[Johnnyvaneddie]

I have already been thru all that and luckily @user2574 was kind enough to modify a generic component switch with auto off for me so now I have a momentary switch. It is still here.
https://raw.githubusercontent.com/cburges2/Hubitat/refs/heads/main/Drivers%20Code/Generic%20Component%20Switch.groovy
He also gave me some tips so I could modify the times. You can check this post.

Generic Component Switch Mod

Is it possible to make this switch with an enable auto off option. I really need a momentary switch that will work with this child device. I was told the device that is labeled button trigger will work but it does not. [Screenshot 2025-01-12 134335]

[user2574]

@Johnnyvaneddie

now I have a momentary switch

It looks like this is a different issue than you were trying to solve before. This is about how a device implements the push() capability, to show up in a filtered device list, when going to select it as a device.

I see where you were thinking that a switch driver with auto-off would help in this case though.

Edit: Now that I see in the screenshot that it says "Switches to turn on" I totally see where you were going with that suggestion.

[user2574]

@nate

I'm looking for help about what needs to be added to the DH above to make this device selectable in a rule.

When I create a new action for Control Switches, Push Buttons -> Push Button, I get a dialogue box with "Push a Button", not "Switches to turn on. "

Something is funky with why it is asking for a switch when "Push button" was selected. So maybe an issue with Rule Machine?

Of course, I'm assuming "Push button" was in fact selected since it is not in the screenshot.

[nate]

@user2574

When I create a new action for Control Switches, Push Buttons -> Push Button, I get a dialogue box with "Push a Button", not "Switches to turn on. "

Correct. I'm trying to get our Momentary button device to show up in the list of Push a Button.

[Johnnyvaneddie]

Not wanting to get off track but since we have your attention here @nate could you tell me what these konnected log warnings mean and do they require attention.

[user2574]

@nate

Correct. I'm trying to get our Momentary button device to show up in the list of Push a Button.

My question was why Rule Machine is asking for a switch and not a button in the screenshot, IF you chose Push button. I'm not seeing that. It just looks like switch is chosen in the right side menu that we cannot see.

This shows I can select a button when choosing Push Button.

This shows when I selected "Turn switches on/off"

When what is posted in this thread is this, not asking for a button, because it looks like switch is chosen in the menu I can't see, unless it is an RM issue that I am not having.

@b.griffiths1207

[b.griffiths1207]

Thank you all for your responses.

In the interest of further clarity to the question:

1. When you set up your devices in the Konnected App you get to choose what device "type" of device you are wanting to use for the output, i.e. a Momentary Device, Switch On/Off, etc.
2. I set up several of each "type" in the Konnected App firmware when I discovered the problem with the screenshots I posted at the beginning of this thread.
3. When you go to RM to create a rule (in my case I want the Door Chime output to work when the Utility Door is opened) you only get to see the option to select ACTION devices that are set up in the Konnected firmware as Switches On/Off - the devies set up as momentary devices are not populated in the list even though they are there in the list of devices. In this case the Door Chime Output in Image #1 was set up as a "Konnected Button Trigger" momentary device. Image #2 shows the device is there in the list of devices and I can turn the Door Chime on manually by sending a PUSH command to the device. However, as shown in Image #3 - this device does not show up as a ACTION button device when I am trying to create a rule.
4. If I set up the device as a Generic Component Switch in the Konnected firmware as shown in Image#4 (Door Chime #2) - then the device is available as a switch to turn on as shown in Image#4 which reflects Door Chime #2 is an available switch to turn on.
5. Image #5 shows Door Buzzer #3 that was set up in the Konnected firmware as a momentary button - which yields the same results as Image #3 where the device is not available in the list of devices in RM.

Hence the question @nate reiterated in his response that he is trying to figure out:
Why are outputs on the Konnected board that are set up with any type of output aside from a Switch On/Off type (that use a momentary contact that use a Konnected Button Trigger type) not showing up in the list of ACTION devices where they are available to be used in a rule.

I hope this provides further clarity to the issue.

[user2574]

@b.griffiths1207

not showing up in the list of ACTION devices

I understand all that, but can you explain the screenshot I was referring to in my post? It looks like you selected switches instead of a button, and then you are saying none of my buttons are showing up in this list of switches I selected for the action.

I just don't get why you show a of screenshot the switch list when you are looking for a button.

[b.griffiths1207]

I thought I had explained that:

@b.griffiths1207

I set up several of each "type" in the Konnected App firmware when I discovered the problem with the screenshots I posted at the beginning of this thread.

Door Buzzer #2 and Door Chime #2 (in the image you reposted) are both set up in the Konnected firmware as "Switches to turn on" - not buttons. They are shown in that screenshot as examples of Konnected output device that do show up in the list of ACTION devices, whereas button devices are not showing up in the list of devices.

@user2574

I just don't get why you show a of screenshot the switch list when you are looking for a button.

I did not just show a screenshot of a switch list when I am looking for a button.

The verbiage associated with the screenshots clearly denotes why a screen shot of each TYPE was posted. If you go back to the very beginning of these threads and look at Image #3 it clearly reflects an example of a Konnected devices that is set up as a button, and also clearly reflects that the Konnected output device Door Chime Output is not populated in the list of button devices you can select from:

Hence the question @nate reiterated in his response that he is trying to figure out:
Why are outputs on the Konnected board that are set up with any type of output aside from a Switch On/Off type (that use a momentary contact (button) using a Konnected Button Trigger type) not showing up in the list of ACTION devices where they are available to be used in a rule.

[user2574]

Ok, that clears up that screenshot confusion.

@nate links to the Button Trigger driver.

    name: 'Konnected Button Trigger',
    namespace: 'konnected',
    author: 'Konnected Inc.',
    singleThreaded: true,
    importUrl: 'https://github.com/konnected-io/konnected-hubitat/blob/master/drivers/konnected-button-trigger.groovy'
){
    capability "Momentary"
}

In addition to what @nate posted, there is this momentary driver

If you go into the button devices, what driver is it using under Type? Is it the "Konnected momentary switch" or the "Konnected Button Trigger"?

[Johnnyvaneddie]

@user2574

In addition to what @nate posted, there is this momentary driver

99 percent sure that is the old legacy switch and wont work with ESPHome. Any how I thank you again @user2574. You fixed my problems by the auto off mod you did for the switch

[user2574]

Ok, I'm looking at the Capabilities of that driver:

capability "Switch"
capability "Actuator"
capability "Momentary"

That driver will display as both a switch and a button.

However, it implements push() differently:

def push() {
def val = invertTrigger ? 0 : 1
parent.deviceUpdateDeviceState(device.deviceNetworkId, val, [
momentary : momentaryDelay ?: 500
])
}

The button driver just calls the parent for Push
:
public void push(_) {
parent?.componentPush(this.device)
}

It is not clear which implementation is needed here. However, Konnected Switch driver does the "parent.deviceUpdateDeviceState" like the Konnected Momentary Switch Driver, which is unlike that button driver that just calls the parent Push.

def on() {
def val = invertTrigger ? 0 : 1
logDebug "Turning on $device.label (state = $val)"
parent.deviceUpdateDeviceState(device.deviceNetworkId, val)
}

So I'm wondering what driver is being used by the buttons, the button driver or the momentary switch driver

@b.griffiths1207 could either change to the Momentary Switch Driver for those button devices manually, if currently using the Konnected Button driver, or edit the driver code for the Konnected Button driver and add Capability Switch to it, so it will show up in the switch list if that is what is needed. It doesn't have to implement capability switch, but it will affect what list is shows up in.

[ogiewon]

@user2574

    name: 'Konnected Button Trigger',
    namespace: 'konnected',
    author: 'Konnected Inc.',
    singleThreaded: true,
    importUrl: 'https://github.com/konnected-io/konnected-hubitat/blob/master/drivers/konnected-button-trigger.groovy'
){
    capability "Momentary"
}

@b.griffiths1207 - If you want this device to show up as a Hubitat Button Device in Rule Machine and other Hubitat Apps, the driver will need to be updated to include the "PushableButton" capability.

[user2574]

Pushable Button is a different capability than Momentary though.

It uses the push(buttonNumber) method, instead of push().

[ogiewon]

Yep, I understand... However, that is the simplest way of getting this device to show up in standard Hubitat Apps, as it appears they do not really utilize the Momentary capability.

The driver can support both PushableButton and Momentary, and just have the command that handles push(buttonNumber) simply call push().

[user2574]

@ogiewon

as it appears they do not really utilize the Momentary capability

I don't know why you think that, so I tested it.

I created a driver with a capability Momentary, then created a device called "Test Momentary" with the driver. Than I created an app that uses a device with the momentary capability. It show up fine.

    section("<b>Virtual Momentary Button Device</b>") {
        input (
          name: "button", 
          type: "capability.momentary", 
          title: "Select Momentary Device", 
          required: true, 
          multiple: false,
          submitOnChange: true