Hmmm, after re-including, did you click the Configure button and wait the few minutes for it to finish? (You can watch its progress on the logs screen)
Joel,
I did that and everything is working with a few exceptions.
- HE responds perfectly to a button press setting the associated indicator to 1 or back to 0 but the LED's on the keypad continue to light in sequential order.
- The All Off button doesn't do anything
- Cycling power to the keypad appears to put it back into setup mode where a single push of the All Off button puts it into Inclusion/Exclusion mode.
The LED's should stop cycling when HE finds the keypad during the inclusion but that's not happening. It's as if it's not getting fully included. So the issue doesn't appear to have anything to do with your drivers.
I tried a second keypad, new out of the box, and received the same result where the LED's continue to cycle even after the keypad has paired with the hub.
I also tried pairing with the old ST hub and it appeared to work. Immediately after pairing with ST the LED's stopped cycling.
Here is some info and images of the keypad for comparison.
Model #: RFWDC
FCC ID: UH2-RFWDC
IC: 4706C-RFWDC
I really appreciate your help but want to be sure I'm not abusing your time.
Thank You.
New update...
I was able to pair the keypad and have the LED's stop cycling by pairing it once (LED's continue to cycle) then pairing it again (LED's stop cycling).
Everything is working except for the All Off button but I think I know why.
This appears to be a slightly different version of the keypad. The All Off button is actually an On/Off button addressable by the hub unlike the other keypad's All Off button that turns off all the buttons locally within the keypad.
In addition, buttons 1-5 can be used to dim lights up and down. Click and hold they dim the associated z-wave device up, click and hold again and they'll dim the associated z-wave device down. Obviously would need a driver to support these.
I'm not concerned with dimming but I may try and figure out what you did and see if I can get the On/Off button usable.
Ah yes, you have the curvy version. Sounds like it has slightly different firmware than the boxy version I have.
On mine, the all off button has to be held for 2 seconds to work.
Regarding dimming: I’ve looked into it, but unfortunately the zwave commands that are being sent back to the hub don’t include the info of which button is being held. So I think the dimming would only work with devices that are zwave associated directly to the scene controller.
I'm not concerned with the dimming but would like the On/Off button to work. I'll give the 2 second push a try.
For anyone using this driver, the new HE v2.1.8 introduced a bug. I've included a fix here:
1 Like
At some point, I am not sure when, my keypad has started SOMETIMES registering a single press as multiple presses. here is the log output after I pressed a button a single time:
dev:702020-03-30 04:46:13.159 pm infoDave's Lamp was turned off [digital]
dev:752020-03-30 04:46:12.795 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:702020-03-30 04:46:12.278 pm infoDave's Lamp was turned on [digital]
dev:752020-03-30 04:46:11.926 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:702020-03-30 04:46:11.559 pm infoDave's Lamp was turned off [digital]
dev:752020-03-30 04:46:11.228 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:702020-03-30 04:46:10.882 pm infoDave's Lamp was turned on [digital]
dev:752020-03-30 04:46:10.558 pm infoDave's Switch (Virtual Button) button 1 was pushed
I have two of these keypads, and they each control multiple different devices and it occurs on all of them. I am using the button configuration.
Any ideas?
I am still having my lights sometimes go on/off after pressing the buttons.
Not sure if relavent, but when I run configure, I get the following debug output:
dev:742020-07-15 05:26:38.826 am debugUNPARSED CMD: SceneControllerConfReport(dimmingDuration:0, groupId:5, sceneId:255)
dev:742020-07-15 05:26:35.347 am debugUNPARSED CMD: AssociationReport(groupingIdentifier: 5, maxNodesSupported: 232, reportsToFollow: 0, nodeId: [1])
dev:742020-07-15 05:26:14.265 am debugUNPARSED CMD: SceneControllerConfReport(dimmingDuration:0, groupId:4, sceneId:254)
dev:742020-07-15 05:26:10.708 am debugUNPARSED CMD: AssociationReport(groupingIdentifier: 4, maxNodesSupported: 232, reportsToFollow: 0, nodeId: [1])
dev:742020-07-15 05:25:49.572 am debugUNPARSED CMD: SceneControllerConfReport(dimmingDuration:0, groupId:3, sceneId:253)
dev:742020-07-15 05:25:46.044 am debugUNPARSED CMD: AssociationReport(groupingIdentifier: 3, maxNodesSupported: 232, reportsToFollow: 0, nodeId: [1])
dev:742020-07-15 05:25:24.947 am debugUNPARSED CMD: SceneControllerConfReport(dimmingDuration:0, groupId:2, sceneId:252)
dev:742020-07-15 05:25:21.394 am debugUNPARSED CMD: AssociationReport(groupingIdentifier: 2, maxNodesSupported: 232, reportsToFollow: 0, nodeId: [1])
dev:742020-07-15 05:25:00.316 am debugUNPARSED CMD: SceneControllerConfReport(dimmingDuration:0, groupId:1, sceneId:251)
dev:742020-07-15 05:24:56.811 am debugUNPARSED CMD: AssociationReport(groupingIdentifier: 1, maxNodesSupported: 232, reportsToFollow: 0, nodeId: [1])
Those messages are fine.
Let me recap, and make sure I'm understanding your setup:
- You're using my driver, set up with buttons as the child devices
- You're using Rule Machine to respond to those button presses?
- When a rule fires, it toggles a smart switch?
thanks!
Correct, well currently it is set up as virtual switches because I wanted to give that a try to see if it did that then as well and it continues to toggle multiple times for a single press. Buttons are the desired behavior though.
not sure if this helps, but I put debug messages in both
def zwaveEvent(hubitat.zwave.commands.basicv1.BasicSet cmd) {
// Fired twice when a button is physically pushed off
and:
def zwaveEvent(hubitat.zwave.commands.sceneactivationv1.SceneActivationSet cmd) {
// Fired twice when a button is physically pushed on
the off event fires multiple times as demonstrated below:
dev:742020-07-14 08:39:04.360 pm debugoff
dev:742020-07-14 08:39:04.289 pm debugoff
dev:742020-07-14 08:39:03.919 pm debugoff
dev:742020-07-14 08:39:03.839 pm debugoff
dev:742020-07-14 08:39:03.780 pm debugoff
dev:742020-07-14 08:39:03.411 pm debugoff
dev:742020-07-14 08:39:03.376 pm debugoff
That's very odd, and unfortunately difficult to debug remotely. It really looks like the device is sending multiple reports back. Unfortunately, I've gotten other reports from other folks about devices with slightly different firmware and sending different combinations of reports back.
You may have to debug this yourself, but if you're comfortable doing it, look at line 88, the "Simplification figured out by tchandle". If you put more log statements throughout the parse() method, you might be able to figure out what path it's taking in there for each of the messages.
I got a little more information, looks like it is actually sensing multiple pushes... If this was not happening on two different keypads, I would think it may be a hardware issue. Also, the intermittent nature makes debugging it hard to do. All of this was from a single key press.
dev:692020-07-19 07:49:46.298 pm infoDave's Lamp was turned on
dev:692020-07-19 07:49:46.290 pm infoDave's Lamp was turned on
dev:3612020-07-19 07:49:45.944 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:672020-07-19 07:49:45.930 pm debugpush
dev:672020-07-19 07:49:45.917 pm debugCMD: SceneActivationSet(dimmingDuration:0, sceneId:251)
dev:672020-07-19 07:49:45.913 pm debugDESCRIPTION: zw device: 03, command: 2B01, payload: FB 00 , isMulticast: false
dev:692020-07-19 07:49:43.744 pm infoDave's Lamp was turned off
dev:3612020-07-19 07:49:43.339 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:672020-07-19 07:49:43.307 pm debugpush
dev:672020-07-19 07:49:43.271 pm debugCMD: SceneActivationSet(dimmingDuration:0, sceneId:251)
dev:672020-07-19 07:49:43.267 pm debugDESCRIPTION: zw device: 03, command: 2B01, payload: FB 00 , isMulticast: false
dev:692020-07-19 07:49:42.212 pm infoDave's Lamp was turned on
dev:692020-07-19 07:49:42.196 pm infoDave's Lamp was turned on
dev:3612020-07-19 07:49:41.799 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:672020-07-19 07:49:41.777 pm debugpush
dev:672020-07-19 07:49:41.757 pm debugCMD: SceneActivationSet(dimmingDuration:0, sceneId:251)
dev:672020-07-19 07:49:41.752 pm debugDESCRIPTION: zw device: 03, command: 2B01, payload: FB 00 , isMulticast: false
IMPORTANT UPDATE: These RFWC5 drivers can now be installed from Hubitat Package Manager. This is the best way to make sure you keep up-to-date with bug fixes and new features.
Can you try something for me?
Disable all the automation that is firing off of the events. (So disable whatever is turning "Dave's Lamp" on and off.) This is so we can test the keypad in isolation.
Then retry your test and send me the new logs.
Looking forward to trying this device handler. I've got one of these devices on order.
dev:3612020-07-26 04:24:19.214 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:672020-07-26 04:24:19.181 pm debugpush
dev:672020-07-26 04:24:19.147 pm debugCMD: SceneActivationSet(dimmingDuration:0, sceneId:251)
dev:672020-07-26 04:24:19.144 pm debugDESCRIPTION: zw device: 03, command: 2B01, payload: FB 00 , isMulticast: false
dev:3612020-07-26 04:24:18.191 pm infoDave's Switch (Virtual Button) button 1 was pushed
dev:672020-07-26 04:24:18.139 pm debugpush
dev:672020-07-26 04:24:18.106 pm debugCMD: SceneActivationSet(dimmingDuration:0, sceneId:251)
dev:672020-07-26 04:24:18.103 pm debugDESCRIPTION: zw device: 03, command: 2B01, payload: FB 00 , isMulticast: false
Sorry for the delay, it does look like even with the rule paused, it still registers multiple pusches from a single physical press. I notice when I do it, too, it seems like the indicator light takes longer to go off.
Has anyone updated to 2.2.3.132+ on a C-7 hub and still have the keypads working? I'm using two separate keypads with @jwetzel1492's driver configured as virtual switches. I can turn the virtual switches ON by pressing the keypad but pressing them again to turn OFF does nothing to the virtual switches. I downgraded to 2.2.3.119 and it works great. Upgrading breaks it.
Here's the logs after physically pressing a button to turn it off on 2.2.3.119
Here's the same on 2.2.3.135
The IndicatorReport is not showing up in .135. I sent a message to hubitat support but they asked I check with the developer and ask them to confirm and have them let support know directly if it's suspected to be a platform, so here I am 
@jwetzel1492 does it work for you on .135?
1 Like
It does work for me on .135 and .142, but I'm on a C4. I don't have a C7 hub. Have you tried .142 yet?
I have been having some problems, also. I'll post some additional details, but off the top of my head, if I try and configure child devices as virtual buttons, only on child device appears in the devices list and an error occurs in the log. There has also been inconsistent behaviour when configuring as virtual switches. As I say, I'll post more later, but any immediate thoughts? I'm running a C-5 with v2.2.3.118. The driver was installed using the Hubitat Package Manager and the device is a RFWC5D.
Thanks in advance for any assistance you can offer!
Oh, didn't see .142 yesterday. Just tried it and it works now! Thank you and thank you for making this driver! I made a smart app that uses the keypad with virtual switches to act as a Bathroom Fan timer (so button 1 is 5 min, next is 15, etc) and it works well!
1 Like
