FIBAROKeyFob, Remote, Z-Wave Scene Controller, White, FGKF-601, Doesn't Work with HomeKit

I love this device. As far as I can tell, it's the only available pocket-sized controller with more than a few actions. In the morning I click a button and the house wakes up. (I'm using Hubitat.) At bedtime I hold (as opposed to press) the same button and the house goes to sleep. Another button activates "TV mode" such that the lights in the TV room will stay dark, not responding to motion. There are six buttons providing for 12 programmable actions. (Hubitat can't detect double-click, only Press, Hold, and Release.)There is just one con: The buttons are too easily activated by accident when carried in a pocket.

Not much to say beyond, it works real well. The worst part about it was mine had the little rubber o-ring on the battery door stuck between the threads of the core and body of the thing and getting it to stay in the groove when it was split in two was a hassle.

I tried both of the Aeotec remotes, but wasn't happy with them at all. The older, sliding one (shown here) was too finicky with button pushes, and didn't work half the time. The newer four button version didn't have any feedback, and felt cheap and just generally wasn't good. I avoided the Fibaro model because of mediocre reviews on here, but finally caved and decided to give it a try.I LOVE it. I am so glad I finally did. SmartThings recognized it immediately, and automatically added options for single press, double-press, triple-press, and hold for all six buttons. The remote itself gives light feedback so you know when it registers and when you're too far away from your Z-Wave network (pretty critical if you're using it for home entry), and will let you know when the battery is running low as well. It has fantastic range, though, and it just works!If I could come up with minor complaints, it's that sometimes the buttons are a little too easy to press, and can sometimes go off in my pocket (you can mitigate that by locking them, or setting your routines to double-tap or hold, but I haven't bothered, so that's really on me). The battery life isn't AMAZING, but it's at least as good as the non-rechargeable Aeotec, if not better, and it's good enough for me. It is a Z-Wave device, after all.The size is just fine -- it's smaller than most car key fobs today. Here you can see it pictured next to the old Aeotec remote (closed), a remote access gate fob, and a car keyfob. It's really not bigger than any other kind of fob you carry around these days, and the teardrop shape actually makes it more manageable and pocket friendly, oddly enough.EDIT: The remote is great, but the case and Fibaro support, not so much. The first one of these I had I dropped on pavement and it shattered, and I wasn't able to put it back together. No big deal, I actually ordered a second one.The keychain on my second one got a little caught on something and the case gave out, and now there's no way to reconnect the keychain part because of a bad design (pictured). The tip of the fob where the keychain connects is incredibly thin and a badly engineered point of failure.I reached out to Fibaro support about this, and got a pretty terse response about the case being out of warranty (also pictured). They could have just sent me a plastic case replacement, how much would that have cost them? So, two stars deducted.

I bought this to make it easier for my son to control his lights and fan in his bedroom. I’m only controlling three devices with one button for on and one for off for each. The commands execute instantly and the build quality feels great. Battery life has been great so far (it has only been a month or so). I’ve tried a few other button options and this one has been the best by far.

I bought four of them. The more I use them, the more I hate them. Not because they don't function. To the contrary, digitally, they are probably the best Z-wave fobs made, to date. However they are VERY flawed and terribly impractical.Pros:- Buttons send signal immediately.- Range is fantastic for something transmitting from such a small device. I can hit the button about 2 houses away and it works.- There are 6 buttons. This turns out to be a "con" unless they fix the driver problem. Then it will be a HUGE pro.- Another pro and a con is that pressing a button attempts to make contact with the hub and tries several times before timing out. This ensures your commands make it to the hub, but when you are away from the hub it is murder on the battery. Remember the physical design of this clicker lends itself to being mis-clicked constantly.Cons:- 6 buttons has turned out to be the downfall. See, if it only had four buttons there would have been more motivation from coders to make the double click and triple click (and multiclick) drivers work.- The Fob continues trying to get its command to the hub until it times out. This eats batteries if you intend to carry the fob away from the hub. Unintended clicks are a problem.- The physical design of this fob is it's single biggest flaw. Everything else could be forgiven and compromises could be made for functionality if it was just shaped differently.- No custom driver in Hubitat. You get single click and button held of each of 6 buttons. That's it.- Single click (and held for that matter) is worthless on a device that is designed to sit in a pocket, purse, or backpack. Double clicks are far less likely to be mis-clicked.- Battery life is terrible. This is probably a function of the buttons being mis-clicked ALL the time. I've had a fob last about 2 weeks in my pocket. My kids can kill a battery in a day in the front pouch of their backpack. True story.In case you haven't put it together yet, I hate the physical design of this fob. So, a word on how bad the physical design is:Most key fobs, have keys that are recessed into the body, or are under a piece of rubber that has to be pressed a few mm before actuating a mechanical button. This fob has 6 raised buttons that stand out from the body. If that's not bad enough, the body is then convex (picture pushing your thumbs into a deflated balloon), which really sets those raised buttons out there for everything to lean up against them. Finally, the tear drop shape causes everything else in your pocket or backpack to slide right onto the raised buttons. I'm not joking when I say, there is no way anyone tested this in the real world. It took about 5 minutes to realize how bad this design flaw was. In your pocket, when you sit down, the fabric from you shorts can pull tight enough to hit the buttons. Turned around, your pants can pull the fob into your leg and press the button. These buttons are always getting pressed by something. It's ridiculous. I get form vs function, but you can't dismiss all function for the sake of form. If someone with some CAD talent and a 3D printer wants to endeavor designing a better enclosure I am willing to sacrifice one of these to build a better housing, because at the end of the day, they are great digitally, and unfortunately, they are the only option right now.Final thought, I don't understand why Z-wave manufacturers make devices and then don't write drivers for their devices for at least the top four platforms. You built a cool device. If I can't use it to it's full potential, what's the point? This key fob has some neat features that I haven't even had a chance to try because they only work on one platform. There is some kind of lock mechanism that I couldn't make work in Smartthings, Home Assistant, or Hubitat. To be fair, I only halfheartedly tried in ST and HA. My main hub is Hubitat and I am just so bitter about all the other functions/problems that I barely gave it a chance on the other platforms. Pretty sure it's not accessible in them either, but the lock function wasn't the deal breaker for me. The reality is, no one is going to go through all the trouble of pressing an unlock sequence on the fob just to hit the button to open the door lock. It would be much faster to just punch your code into the door lock. It obfuscates the convenience of the key fob.