[Solved] Remove a Konnected Blaq from the list of "locks" tracked by Home?

🛎️ Get Help Devices
1

I installed a Konnected Blaq GDOv2-Q for my garage door. It has a "lock/unlock" function that ONLY disables or enables remote controls. I have no foreseeable need to lock our remotes.

The Hubitat Home page lists this device under "Security" and of course it's always red-flagged as unlocked.

Is there anyway to remove this device from the list of "locks" tracked by Home?

2

If you do not intend to ever use the "lock()" and "unlock()" commands for the Konnected Blaq GDO device, one possible solution is to simply modify the Konnected driver code to remove suport for Hubitat's lock capability.

You can just comment out the Lock capability as shown below, to see if that successfully removes the device from Hubitat's "Security" list of devices.

Open up your hub's list of custom drivers, and then open the 'Konnected Garage Door GDOv2-Q' driver. Then, simply add the "//" comment symbol as shown below in front of the " capability 'Lock' " line of code as shown below. Be sure to SAVE the modified driver code.

    definition(
        name: 'Konnected Garage Door GDOv2-Q',
        namespace: 'konnected',
        author: 'Konnected Inc.',
        singleThreaded: true,
        importUrl: 'https://github.com/konnected-io/konnected-hubitat/blob/master/drivers/konnected-gdov2-q.groovy'
    ) 
    {

        capability 'Actuator'
        capability 'Sensor'
        capability 'Refresh'
        capability 'Initialize'
        capability 'SignalStrength'
        capability 'DoorControl'
        capability 'GarageDoorControl'
        capability 'ContactSensor'
        capability 'Switch'
//        capability 'Lock'
        capability 'MotionSensor'

I do not have this device, so I cannot test this change. Give it a try. You're not going to permanently hurt anything. If any problems arise, simply remove the "//" comment symbol.

3 Likes
3

Ninjaed - but that’s a good thing because my response wouldn’t have had the detail in yours anyway!

1 Like
4

Thanks! That worked perfectly! [Except for the possibly totally coincidental but exactly coincident loss of connection to my Hub, requiring a power-plug reboot!]

2 Likes
5

Glad to hear that helped!

1 Like