I'm not recommending that as a solution at this time, I don't know what's up with this guy, but this should not be required for proper operation.
Yes, there was an centraLite outlet, Iris V3 keypad, Hue motion (maybe two), two AduroSmart Eria button controllers and an Xiaomi motion.
Good to know on both accounts. I appreciate your reply.
I have the 4 button on a hub without any lamps and it is slow, to respond and slow to accept a press. It hasn't dropped off, but seems to wake up slowly.
Same here. It's the only device on my 3rd hub at all and it's still wonky.
I removed the switch, and suddenly my intermittently failing lightify sensors, started working reliably again.
Something interesting I saw on the Amazon reviews
This one Amazon item appears to be for two different devices, one for Europe and the other for the US. They are different hardware and firmware. The case is the same.
The US version is useless. Worse, actually. Linking it to smartthings creates a device that causes an Off signal to be sent to all devices on the hub. The 'good' drivers appear to apply only to the Europe version. Loading device handlers for the US version is a waste of time.
This product should never have been shipped.
I don't know the truth to it but might be worth exploring.
I ended up not buying this device after all.
Even though they have less functionality and are more expensive I bought some samsung buttons. I am very happy with them. They don't drop, are responsive and have not been messing with my zigbee network. The few extra dollars were worth it for less headaches.
@mike.maxwell mine (3 of them) worked fine until I added two SmartThings moisture sensors, an orbit water hose timer, and a 3326-L motion sensor. They were never an issue before then with 10 or so Sengled bulbs only. They basically take a button press to wake up, then another to execute the command. Sort of a bummer as these were priced right and (used to) work well. I wish we could run a daily refresh on them to keep them “active”. I did this with my SmartThings buttons. I'm not entirely sure it's a button issue, as I can watch the logs on my system and see button presses but the actions never happen. For instance:
I pressed the button twice; first time the light went out (it was already on), the second time it didn't do anything (light should have come back on).
If the button presses are showing in the logs, it's not a button issue as the pushed event is making it to the hub.
Well that was a test after it was already “woken up”. I’ll try to check logs when trying as device that has been “asleep”.
I'm more concerned about why the second press didn't turn the light off as you expected it to do.
I assumed you all might be limiting duplicate presses within x ms from each other. Feel free to poke around on my hub; I’d be glad to help debug these switches now that I gave my zwave minimotes away.
No dup filtering, whatever the device sends we process.
Came home tonight, pressed button (not held) and nothing. Logs showed the battery level only. Then I held the button to turn the light on and it worked (both press and hold work for turning on).
Not sure if it matters, but in my non-scientific tests, if the command issued is a “push and hold”, then the device seems to wake and execute without issue. Just a push, not so much.
I uninstalled all of mine a few weeks ago. I then decided to install one switch and see if it would work. It has worked flawlessly for 4 days now. I have no idea why. I’m afraid to install the rest.
Just to update: the switch is still working reliably at this time. I added a second in a different location that worked well for a couple weeks, but now often requires 2 presses initially to turn on or off the lights. Still better than the 3 presses they were requiring. I did notice that I had to press buttons 2&3 (at the same time) while pairing, or the buttons wouldn’t configure properly. I know that during pairing with the Lightify gateway they were flashing the entire time they were being set up, but not when being configured on HE.
Any ideas @mike.maxwell? Still getting inconsistent issues with these buttons - it does appear Hubitat sees them, or at least Zigbee knows the device has been woken up. Looks like the Profile ID, cluster ID, src and dst are different between the two presses. I'm guessing src is the button # pressed, and since it's 0, Hubitat just throws this away? I wonder if there is a firmware update and how we'd go about doing that.
Lightify button hasn't been touched all day. Here it is with me touching it to turn off a light.
It registers this in Zigbee logs, so it appears to be talking to Hubitat, but nothing in Hubitat logs:
Lightify Button - Brian 2019-09-05 19:48:55.363 profileId:0x0, clusterId:0x13, sourceEndpoint:0, destinationEndpoint:0 , groupId:0, lastHopLqi:255, lastHopRssi:-53
But the light doesn't go off.
So I press it again, light goes off (these are in reverse - bottom actions happened first):
Brian's Desk 2019-09-05 19:49:08.150 profileId:0x104, clusterId:0x300, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-53
Brian's Desk 2019-09-05 19:49:08.048 profileId:0x104, clusterId:0x300, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-53
Brian's Desk 2019-09-05 19:49:07.544 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-53
Brian's Desk 2019-09-05 19:49:06.636 profileId:0x104, clusterId:0x300, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-53
Brian's Desk 2019-09-05 19:49:06.634 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-53
Lightify Button - Brian 2019-09-05 19:49:06.330 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-53
And Hubitat logs:
dev:11832019-09-05 07:49:06.288 pm infoLightify Button - Brian button 1 was pushed
I see the exact same behavior, except i usually have no response or zigbee logging on the second press and the action occurs finally on the third. This is with 2 of the 4 Lightify switches I currently have joined. The other 2 work perfectly every time, but they are both within 5 feet of a peanut plug. The ones that need multiple presses are near Samsung and Sylvania outlets. Thats the only difference I can see. Might be coincidence though.
The ones I have trouble with are close to Samsung and Iris plugs.
I just pressed all the buttons on mine, it's been on my dev hub for months now, and I haven't pushed any of the buttons on it for a month at least.
all the buttons registered first press.
I did notice while I had zigbee logging running it registered the following:
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:57.771 profileId:0x104, clusterId:0x8, sourceEndpoint:3, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:56.962 profileId:0x104, clusterId:0x8, sourceEndpoint:3, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:54.846 profileId:0x104, clusterId:0x6, sourceEndpoint:4, destinationEndpoint:1 , groupId:0, lastHopLqi:254, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:53.733 profileId:0x104, clusterId:0x8, sourceEndpoint:4, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:51.414 profileId:0x104, clusterId:0x8, sourceEndpoint:4, destinationEndpoint:1 , groupId:0, lastHopLqi:254, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:46.362 profileId:0x104, clusterId:0x6, sourceEndpoint:4, destinationEndpoint:1 , groupId:0, lastHopLqi:254, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:45.151 profileId:0x104, clusterId:0x6, sourceEndpoint:3, destinationEndpoint:1 , groupId:0, lastHopLqi:254, lastHopRssi:-50
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:37.171 profileId:0x104, clusterId:0x6, sourceEndpoint:2, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-51
[Lightify Smart Switch](http://192.168.1.172/hub/zigbeeLogs#zigbeeRx57490)2019-09-06 08:32:34.080 profileId:0x104, clusterId:0x6, sourceEndpoint:1, destinationEndpoint:1 , groupId:0, lastHopLqi:255, lastHopRssi:-49
note the endpoints and clusters involved, endpoints 1 through 4 and clusters 6 (switch) and 8 (level)
These are the correct clusters and endpoints that the device produces if configured correctly.
Yours is producing some some data on cluster 0300 (color), this tells me that the device configuration is not correct.
There is a ton of configuration commands that need to be sent and received by the device in order for it to work correctly, it looks like your device didn't get all of them.
Try waking up the device by holding down buttons 2 and 4 until it flashes green, then immediately click the configure command in the driver.
Download the Hubitat app
