I ran mine down quickly but I messed around with it a lot, besides the battery arrived at 60%. I’ll stick in a fresh one and see how long it’ll last. Should be a fair while with normal use.
You can get rechargeable coin cells though.
Hi battery life time heavily depends on usage and configuration. The device CAN be turned into wakeup mode with regular wakeup. Reason here is that it makes sense to report battery life once a week or so. On the other hand every wakeup costs energy.
So max battery life is achieved when wakeup is disabled and led turned off (configuration parameter 24 = 0).
When no operated the devices take less than 2 mycro Ampere, so battery last to self de charging. heavy use will certainly decrease battery, so its very hard to give precise number. The device goes back into sleep 2 seconds after last action. This means that every button press takes you min 40 mAs (plus LED9. Hitting a button 1000 times takes then about 12 mAh. Configuration and management mode takes much more but this should be done once and then hopefully never again.
Do I use button 1 or 3 to add the fey fob as a device in VeraLite?
I am holding the four buttons on the fob to enter management mode, then hitting the + button on VeraLite and then pressing the button on the key fob but I don’t get a new device in VeraLite showing and the lights on VeraLite don’t flicker like they normally do when adding a new device.
Also there are 3 small screws on the back of the key fob and one is missing on mine is that normal ?
Thanks
Below is the response from the distributor:
With regard to the Fob do I use button 1 or 3 to add the fey fob as a device in VeraLite? I think it should be button 3 from reading the forums posts about it, but I tried button 1 as well.
No button 3 is th LEARN mode and this should be in the manual as well We accidently sent out a few douzen devices with wrong manual.
I am holding the four buttons on the fob to enter management mode, then hitting the + button on VeraLite and then pressing the button on the key fob but I don’t get a new device in VeraLite showing and the lights on VeraLite don’t flicker like they normally do when adding a new device.
If the device is not included every button press is 3 times red LED. Pushinh all four buttons results again in 3 times red and then silence for about 4 sec. After
5 sec the devices turns into management mode. Nod the LED is flashign slowly. Hittign button 3 includes the device, later one button 2 wake it up.
Still can’t figure out how to add the device to Vera, I am quite possibly doing it incorrectly or maybe this key fob is faulty?
Try excluding it first: set Vera to exclude a device, then hold the 4 buttons on the keyfob and hit button #3. After that, try including again.
intveltr that’s twice today you have saved me with that suggestion! Its now added a new device called _Scene Controller that correct?
Cheers
I’ve renamed the device to Key Fob and assigned it to a room. It looks like the attached screen shot.
It says waiting for wakeup to configure device now.
Looks good. Try waking it up now (hold 4 buttons, then hit #3) and see if Vera configures it. You may have to try a few times. If you want to make it trigger scenes, try applying Paetz’ workaround a few posts up in this thread.
Maybe 3 times is the charm? 
[quote=“intveltr, post:29, topic:172543”]Looks good. Try waking it up now (hold 4 buttons, then hit #3) and see if Vera configures it. You may have to try a few times. If you want to make it trigger scenes, try applying Paetz’ workaround a few posts up in this thread.
Maybe 3 times is the charm? :)[/quote]
OK I pressed the 4 buttons again for 5 secs, then I pressed button 3. Now in Vera it no longer says waiting for wakeup to configure!
I am on VeraLite firmware V1.5.408 do I still need the work around ?
Cheers
Ideally what I want to be able to do with the key fob is be able to arm / disarm an Everspring HSM02 Door contact sensor, so I can get in and out of my garage.
And also to be able to run a scene or two, I had the idea of having a “Leaving House” scene I can just push a button on the key fob when leaving and all the lights are turned off etc.
I’ve not tried the work around yet, but tried proximity, if I press button 1 near a device nothing happens it doesn’t turn it on.
The battery level is now showing in Vera at 44%, battery gets hammered whilst trying to set it up! Also all the capabilities are now showing: 83,156,0,4,18,2,R,B,RS,|45,112,114,117,119,128,132:2,133,134,142, and its set to poll every 60 secs, this poll field was blank initially as were the capabilities.
This is how the Scenes tab currently looks like:
OK so trying to follow the work around to get the scenes working.
I have set Variable 11 to 1 byte Dec with a value of 4
I have created an association group 1
I added the ZWAVE device
I edited the Leaving House scene and added a new trigger - “A scene is activated” - Scene Number 11
I am now stuck on this part:
- Wake up the FOB
I woke the fob, by pressing the four buttons and then button 3.
It then says: Failed at: Setting special association
Is that the correct way to wake the fob? For Vera to send the configuration to it.
EDIT: Just tried deleting the Association Group 1 in the hope of it adding back in correctly, but when saving / waking the fob after removing the Group 1 it still says: Failed at: Setting special association
Reply from the Distributor:
“Dont bother the status comments on VERA. VERA tries t osend the commands but the device is sleeping. it says then “failed” but in fact its waiting for the wakeup of the device (button 2 in management mode)”
If I go in to management mode by holding the four buttons and then press button 2 nothing happened in Vera and it still says waiting for wakeup to configure device.
I then pressed the four buttons and number 2 several times and it did then start to update in Vera however at the end it still says:
Failed at: Setting special association
The device currently selected in the Association Group is called _SceneController see screen shot, this should be set to ZWAVE.
I am not sure what _SceneController actually is? As I have renamed the Key Fob and the Mini Mote so I now shouldn’t have any devices called _SceneController.
In fact you can see my only two scene controllers at the top of the screen shot, MiniMote Remote Control and Key Fob.
I deleted the key fob from vera and re-added the device again and then setup the configuration and association group etc. I now see two _SceneController devices under unassigned devices, see screen shot:
I am still getting the Failed at: Setting special association message.
When I press button 1 its meant to run the scene to turn the lights off, but nothing happens.
Proximity is also not working. Think I will have to send this fob back as its just not working and I think I am doing it correctly?
Thanks
It’s probably working correctly. You need to associate the keyfob on group 1 with device #2 called _scene controller. For now, remove the trigger on your scene. Then try and configure the keyfob, it should go through. When it does, go back to your scene and add a trigger for scene activation #11.
By the way, this stuff is why z-wave isn’t ready for prime time yet
[quote=“intveltr, post:37, topic:172543”]It’s probably working correctly. You need to associate the keyfob on group 1 with device #2 called _scene controller. For now, remove the trigger on your scene. Then try and configure the keyfob, it should go through. When it does, go back to your scene and add a trigger for scene activation #11.
By the way, this stuff is why z-wave isn’t ready for prime time yet :)[/quote]
This works and does not error when I wake up the fob. If you look at the screen shot I have two _SceneController entries now since deleting and re-adding the fob to Vera. I selected the top one. I also removed the trigger from the scene. I then held the four buttons and pressed number 2. The Fob in Vera seemed to send the config and it did not error.
So now do I add the trigger back in?
And you need to select _SceneController and not ZWAVE in the Association group ? As per the instructions.
Thanks
EDIT: More from the distributor:
“if you can include the device into very its is very unlikely that there is something wrong with the device. The problem is certainly the setup of VERA. The “Failed at: Setting special association” is an annoying error message because this is actually no error but a designed function. For battery powered devices communication will always fail until the device wakes up. You can see if the fob is sending something. It you receive a triple blink, there is no association group valid, if its a single blink, the packet went out.”
When I just pressed the four buttons and then button 2 I got a single red light on the fob not three.
When adding the trigger back on the scene I can now see two _SceneControllers as options to select. #2 and #28 I will pick #2.
EDIT: Having just said the above, if I look at the _SceneController in the device tab in Vera it has a Device # of 28, maybe I need to use #28 in the trigger, getting more confusing now as I have two entries.
Your scene needs to trigger on the keyfob (#28 I suppose), “a scene is activated”, scene nr 11. I recommend renaming it in the GUI