Remote key fob as scene trigger

Community Playground General Discussions
1

Hi,
I’ve four aeotec key fob as scene trigger. Usually in the scene editor I can add a trigger specifying the number of the button.

After the upgrade of the firmware I can no more insert the button number, when I try to specify the button I have this message: “A scene is activated Which scene numberNo buttons available on controller”

Anyone has the same problem? are there any other ways to set the triggers?

thankyou

Vpiff

2

Unpair and start over…

To enroll your aeotec key fob correctly… first make sure you are really close to your vera.

When adding the device use the “Handheld->Aeon Lab Key Fob”
When it tells you to press the button on the Key Fob, press the Learn button on the Key Fob
Just let the wizard count down to zero (the minimote might start flashing blue again while your waiting… just don’t touch anything… just wait).
Press Exit on the wizard once the count down gets to zero… do not press retry!

This should take you back to the device Screen with a Generic key fob listed under “No Room”
Go into the device and check the “select scenes for device buttons” menu
If 4 on buttons and 4 off buttons are listed… you are in luck… the enrollment worked.
If instead it says “how many buttons does your controller haver” well… unfortunately you are out of luck. UnPair and try again.
Going slow and letting the enrollment wizard time out is the trick. If you go in and try to edit the key fob too early Vera doesn’t sync all the right capabilities.

3

I’m having the exact same issue with my LightwaveRF Mood switch and doorbell via RFXtrx433e, just says no buttons available. I haven’t been able to get a round it yet even by re-adding the devices multiple times. I’d assumed it was because they were lightwaveRF but maybe this is a wider Vera bug?

4

[quote=“shallowearth, post:2, topic:187143”]Unpair and start over…

To enroll your aeotec key fob correctly… first make sure you are really close to your vera.

When adding the device use the “Handheld->Aeon Lab Key Fob”
When it tells you to press the button on the Key Fob, press the Learn button on the Key Fob
Just let the wizard count down to zero (the minimote might start flashing blue again while your waiting… just don’t touch anything… just wait).
Press Exit on the wizard once the count down gets to zero… do not press retry!

This should take you back to the device Screen with a Generic key fob listed under “No Room”
Go into the device and check the “select scenes for device buttons” menu
If 4 on buttons and 4 off buttons are listed… you are in luck… the enrollment worked.
If instead it says “how many buttons does your controller haver” well… unfortunately you are out of luck. UnPair and try again.
Going slow and letting the enrollment wizard time out is the trick. If you go in and try to edit the key fob too early Vera doesn’t sync all the right capabilities.[/quote]

I’ve tried many times but when I enter the confiugration page I’ve always the message “How many buttons does your Scene Controller have ?”…
Isn’t there a way to edit some file (via ssh) and force the configuration without using the UI?

5

Thanks for your tips shallowearth…

I’m having fun with these aeoec fobs too (using vera3 @ 1.7v599). Its amazing how finicky and variable (I have two of them) these units can be!

Interesting what you say about "letting the countdown timer complete… makes sense to let the pairing fully finish. I thought that would do i for me (had the “how many buttons” prompt) , but alas, still no go. Wierd that the manual and instructions like yours said that the final step of inclusion was “2 second green light”… for some reason, mine would stay green for most of that 60 second timer (vera UI would say “setting up node” or similar) and then just go off (no failure indicating red light). I’d hit EXIT and then still get the “h/m buttons” prompt.

So with no real progress, and after countless attempts, I switch to the other of my two fobs - the same type of fob that I bought around 6 months earlier. It did the green light at end of inclusion in more like 10 seconds, and then thankfully knew about all the buttons (even showing scene triggers for held vs pressed buttons) and came with a device name of “Keyfob” instead of “scene controller” as the previous (newer) unit had always been assigned. It even came bundled with the parameter “250” with value “1” already set (to be in scene instead of group mode). All looking good for this unit.

Don’t know where that leaves me with the first unit I mentioned (the newer of the two).

As for other anomalies… I find it amazing to see such different descriptions of how to achieve certain functions with these units… comparing the online manual with the manual that came with the unit… and then comments in these forums and other howto’s…

  • switching from setup to use mode: some say hit the mode button with pin, others say hit mode and link buttons together for 3 seconds with combo pin supplied with unit.
  • To include this fob on existing network: put vera3 in include mode via zwave button on front of unit? or add-device => handheld => aeotec keyfob? or add-device => advanced => [something about fobs] ? The manual for my newer unit says “gen5” - is this a zwave+ variant? The new-device => handheld list offers “keyfob.gen5” (that oughtta do it!) but then the description of that says its a zwave.me unit. Obviously there are differing versions of fob and vera3 firmware in the mix here… :expressionless:

I find it astounding that the add device wizard could be so ambiguous as to not be clear that it is still setting up the new device and so one shouldn’t hit the EXIT button yet, and that if one DOES prematurely hit the EXIT button, the setup just gets chopped leaving one with a half configured device in the list that works enough to seem to be ready to go (to the novice user) but clearly missing a bunch of config params (like num buttons) required for it to work properly. I guess the forum regulars here just know these things by now… but its a bit of a crappy initiation for the newbies. Anyway I guess that vent is already old news here…

Stu.

6

For the one key fob that you can’t get I working. Try the key fob zwave+ device. If you still get the how many button question, enter 8.

Then map the buttons this way:
Upper left -1
Upper left long -2
Upper right -3
Upper right long -4
Lower left -5
Lower left long -6
Lower right -7
Lowe right long -8

7

thanks… I’ll try the zwave+ option when I get another battery for that unit. :expressionless:

Also, re the scene number mappings for buttons tapped/held… I’m already trialling your suggested mapping, except directly in pleg rather than the vera scene mgmt… (call me a glutton for punishment…).

Stu.

8

Nup, that didn’t work any better. Will tinker more with it some other time…