[RELEASE] Wall controller port (Popp, Devolo, Z-Wave.me and more)

AdamV · 2018-12-05 23:34:19 UTC

This is a port of my ST handler for Wall controllers and Key Fobs from Z-wave.me, Popp, & Devolo. It's a bit rough around the edges but it works! - will update if necessary:

github.com

adampv/Hubitat/blob/master/SecureWallController

/**
 *  Copyright 2018 AdamV
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *
 *  Version 1.0
 *  Author: AdamV
 *  Date: 2018-12-05
 *
 */
 
metadata {

This file has been truncated. show original

Here is the original ST thread: [Release] Z-Wave.me, Popp, & Devolo Wireless wall Controller & Key Fob (EU), with button controller dimming apps and CoRE integration - Community Created Device Types - SmartThings Community

AdamV · 2018-12-06 08:47:33 UTC

@bravenel Sorry if you are not the right person to ask this:

I am currently going around my home and adding devices to Hubitat and also implementing a 2 way sync to ST to minimise disruption the house and also so that we have a working app. This Driver is the first one that I have ported. I have implemented one thing a bit strangely - and I wanted to find out what the "correct way" to do it is:

When a button event is fired the state of the button device seems to keep the last event. This caused problems because it wasn't always easy to determine if a new event had fired if the same button was operated in the same way.
To get around this I added a button push / hold / double click with value 0 which fires 1 second after the actual event - to reset the state to a default / neutral state.
This is working well for what I need right now - but would be good to understand the correct thing to do

Cheers

Royski · 2018-12-06 11:18:02 UTC

Hi @AdamV,

Brilliant work on this! My key fob is the last thing to get connected
Got it paired with no issues (thankfully had the document to reset).

All buttons working, Push, Double click and Hold!!

Thanks very much
Roy

AdamV · 2018-12-06 11:31:08 UTC

No problem @Royski. I made a slight improvement to it this morning - will update the github when I get home

bravenel · 2018-12-06 13:43:31 UTC

Buttons don't really have state, or at least you shouldn't be thinking in those terms nor your code. All they have are events. What you see in the state display on the device page is only the shadow of the last event, not state. Your driver should be driven entirely from events.