Hi
Is anyone using successfully one of these Z-Wave.Me 4 Button Key Fobs with Vera ?
Thanks
EDIT: Click this link here which is a WIKI page explaining the setup so you don’t have to read this long thread.
Awesome little thingy, just what I need. I’ll go and order one, no idea if it works with Vera but other ZME equipment does work.
Hi
thanks for the reply, please let us know about your progress with this key fob and Vera! I am going to be buying an Everspring door contact sensor for my garage and I would like to use a key fob like this to be able to arm and disarm the sensor for when I wish to open the garage door.
Regards
Stuart
I ordered mine but it’ll be about 2 weeks before it arrives.
Nice! Please let us know if it works!
This key fob sounds really good, I am going to order one.
I just got this email from the distributor as I signed up as a dealer.
The ZME_KFOB is now available
It has taken way too long but now the Z-Wave.Me ZME-KFOB is finally available. The 4 button controller is optimized for use with IP gateways. It does therefore not offer the capability to include devices itself because in such an environment this creates more problems than it solves. It can directly control devices but also activate scenes. The cool feature is the proximity control. In this mode the fob will switch the device that is in proximity (50…100cm). This means you walk in you home and whenever you enter a room, you hit the same button, you walk to the window, hit the same button to open the blinds, … If course this functions can never be 100 % accurate but it works surprisingly well.
The Z-Wave Alliance made a press release for this amazing product. I can be found on the Z-Wave Alliance website. The product will be officially launched at bElektro in Berlin from October 17th to October 19th. It made it into the list of technology highlights featured at the show.
A few words on Aeon labs KFOB. We will soon launch the Aeon labs Key Fob as well and there are good reasons to support both devices.
Advantage Aeonlabs: It’s a full controller with SUC/SIS support and inclusion/exclusion and scene control
Advantage Z-Wave.Me: It’s based on SDK 4.5 for plug’n play network management, Explorer Frame support, offers the cool proximity control, scene control, single/dual button mode
I asked the distributor if this new key fob had been tested with VeraLite for running scenes etc and the reply I got was simply “Of course”
I have ordered a key fob for testing from the European distributor: http://store.zwaveeurope.com/
I can now supply any products from this store to end users, PM me if interested. 
Yes this does work with Vera. We have checked it with UI4 (1.1.1338) and UI5 (1.5.408) sucessfully. Use Learn mode and preconfigured scenes for inclusion and scene control respectively. Note buttons 2 & 3 are transposed in this mode.
Got mine in the mail today.
First, a word to pretty much all manufacturers of Z-wave devices out there: please keep your battery-powered devices awake a little longer (30-60 secs) when in learn or config mode. Messing around to keep these devices awake long enough for Vera to configure them has to be the most annoying, stupidest time waster in Z-wave land.
Anyway…
The device itself is cute, the form factor small enough to go on a key chain, with a nice sliding cover for the buttons. The device looks and feels of good quality. Inclusion and configuration is straightforward (other than the sometimes too-short wakeup period during configuration).
The “proximity” mode is interesting, allowing you to control nearby devices. Could be useful for quickly turning on lights etc when in a room, but I have to be careful there: when switching on the lights in my office, it also turned on all the garden lights and the sprinklers (the control box for those is nearby).
Associating buttons to other devices is straightforward, and can be done from the keyfob itself, or via settings in the Vera UI.
I did not get the thing to activate scenes, though. When I try adding a trigger to a scene for this device, Vera wants to reconfigure the device and always fails at “setting special association” or some such. I am on firmware 1.5.401 though, perhaps it does work on the latest beta. (I haven’t upgraded yet as 1.5.408 breaks my ZME wall controller)
Interesting. Do you feel the device just goes back to sleep after a preset amount of time after having been woken up, or Vera is too slow to keep it awake?
I thought that with the wake-up mechanism (i.e. where the device periodically wakes up autonomously), the time-out is typically after the last transmission (if any) from the controller (or actually, the controller is supposed to put the device back to sleep). They could do something similar for manual wake-up/learn/config mode, I imagine.
Sounds like that is how it is supposed to work, but my experience with battery powered devices is that it often fails due to timeouts or the thing going back to sleep.
By the way, scenes are sometimes coming through. Hot tip: in the device, set up a notification for “A scene is activated”, with scene number *. That catches all scenes, and reports which number was sent. I had buttons 1 and 2 associated to devices, and buttons 3 and for set up for Scenes. In this case I got notifications for button 4 (not 3).
Now I have set all buttons for scenes. And no notifications are coming through at all.
Setting a trigger on scene 41 activation still results in a failure to “set special association”, however a trigger on scene 11 activation (button 1) is accepted (though doesn’t work).
I suppose I’ll try on the new firmware at some point. And get a new battery; I pretty much ran down the battery that came with the keyfob while messing with it.
My VeraLite is on v 1.5.408 will try to get a button running a scene. Waiting for my order from Germany so could be a few days yet. I ordered some other Z-wave goodies as well, an Everspring door contact sensor and siren plus a Everspring motion sensor looking forward to getting these new devices up and running!
It works ok on 1.1.1338 so probably should be ok your UI5 version. I set the key configurations (parameters 11-14) to ‘5’ (Direct activation of preconfigured scenes). Right enough the device is a little intermittent whether it seems to complete the configuration before it appears to go back to sleep.
Then within the Scene for the trigger set the scene number so it corresponds to buttons 1-4 as required - note one bug - buttons two and three are transposed so selecting scene number=3 is activated when button ‘2’ is pressed. :
Hm, I had the buttons set to mode 4. Setting them all to 5 didn’t help though. Now buttons 2 and 3 don;t seem to do anything (the LED doesn’t go on when I push these buttons). I did get a notification for scene #129 being activated, which is not a number mentioned in the manual. The one time I got button 4 working as a scene controller, it was consistent with the manual, i.e. 41 for click, 42 for double click etc.
I set the buttons back to mode 4, and at least I got button #4 to generate scene events again (scene 41, same as the manual mentions). But I still get a failure on device configuration “failed to set special association” when I try to trigger a scene based on code 41.
So far I haven’t been able to get it to work or even discern a consistent pattern in scene activation. At least it is consistent with my ZME wall controller, in that the scene numbers generated are completely different from both the manual and the what the ZME support guy mentioned. Maybe my Vera is buggered… others have reported better success with that ZME wall controller. Upgrading to the last private version of firmware 1.5.408 actually did fix the ZME wall controller, but they pulled that patch from the public 1.5.408 release for some reason.
So far it’s not been a good experience… Scene controllers and Europe just do not seem to mix well 
Weird. It works reliably for me even on UI4.
Did you use buttons 3 or 1 to include? I used 3.
I set parameters 1 & 2 to zero also.
BTW button 3 seems to wakeup rather than 2 in the manual.
I also have parameters 1&2 on zero. I think I used button 3 to include the device into the Z-wave network, but that doesn’t seem to be the issue; the device works prefectly well in all respects… except triggering scenes in Vera.
Hello,
I’ve added the Key Fob to my Vera. The problem is that it is not possible to activate the preconfigured scenes.
How to change between the five modes?
How do I activate the mode 3 (Scene Activation …) in Key Fob?
I do not understand parameter settings and how I should do ???
Please, help…
Hi Folks,
a couple of clarifications.
-
The very first KFOBS sent out had as error in the manual. Button and 3 are mixed. Button 3 is the LEARN mode button
and must be used for inclusion and exclusion. -
There is a problem with scene acivation with VERA, at least for FW version 1.5.401. Some explanation:
FOB is using the noral Scene activation commands and in order to enable them the config parameter need to be set and a target
for the command need to be defined. The last is what VERA refers to a “special associations” and this is what goes wrong
for the firmware mentioned above. This is confirmed as a bug in VERA by MIOS support.
Here is the work around, this is for button 1 as scene activation
- Include the FOB
- Set the config paramezer 11 to value 4
- activate the association group dialog for group 1 and assign ZWAVE device (thats VERA itself) into this group [THIS
IS THE WORKAROUND STEP] - Set your scene with the FOB as trigger and scene acivated as event as scene number 11 as number
- Wake up the FOB
- Hitting Key 1 sends scene activate scene no 11 and trigger the scene if set correctly.
In FW 1.5.408 our buddies introduced another interesting bug. Not changing the setup above and using scene number 11 as trigger -
now button 3 need to be pushed to create the same result, means scene activation number 0x0C (in my option this would be 12d)
will trigger the scene.
Regards
Chr.
Nice, manually setting the association with Vera did work, it can now trigger scenes!
And yes, they did something wonky between 1.5.401 and 1.5.408; that is why I stayed on the older firmware as it messes up scene numbers in the ZME wall controller as well. Hopefully the fix for this (which was removed from 1.5.408 because it broke Minimote scenes) will be corrected and put into the next firmware.
Buttons 2 and 3 also swap scene numbers: 21 is button 3, and 31 is button 2.
Should hopefully get mine tomorrow. Glad to see it works. I gave up waiting for the MyKey remote.
The downside is this isn’t rechargeable. I wonder how long the battery with last.