Aeon Gen5 Key Fob ZW088-A not communicating with Vera.

[Bena]

Hi Guys,

I got 2 Aeon Lab Gen 5 Key fob (ZW088-A) which I successfully added into my Vera (1.5.622) system.

But it seems that Veralite are unable to extract any information from it and also unable to configure it.  I am trying to put these key fob into Use (Scene) mode in order to control the scene that I set up. 

According to the Key fob user manual, "If you wish to change your remote?s mode to Scene Mode, you will need to send it an instruction via your gateway (Vera, I assumed), If you?re unsure of how to do this, please refer to the gateway?s  user manual".

I can't find any information on vera user manual.  I am stuck! I have been digging around and nothing is available.  Please help me guys.

Appreciate all your help.

[AChilton]

Similar problem here, but with Vera 3.

I believe the Vera device setup, using the current firmware, is not communicating with the new key fob correctly, as I am assuming that it is setting it up as if it is the older key fob. This would prevent it from being able to set the device in the correct use mode, even if you set a parameter of 250 to a 1 byte value of 1, as the key fob directions instruct.

I was told by Vera support to try it again with the December 2014 firmware release, however after installing it (1.7.481), it still does not add to the system correctly, and the release notes of the new firmware do not state any addition/change to the Aeon Key Fob setup.

I have emailed Aeotec asking for information on how to set it up correctly on a Vera 3, however, more than a week later, no response.

Appreciate hearing from anyone who has set this up successfully.

[Bena]

Does anyone have any idea / update on this issue?

Thanks,

[funluvn]

I have a VERA edge and have been searching for days without any luck.
 

[ng191]

I have the same issue on a Vera3.

[dzmiller]

Any resolution? Any other brands that work well?

[Kullematz]

My two AEO Minimotes working very well under UI5 as scene controllers.

[dzmiller]

My two AEO Minimotes working very well under UI5 as scene controllers.

Are your minimotes the new "Gen 5"? These new models seem to be a problem with Vera.

[Kullematz]

They are not GEN5 products and as far as I know, there are no Minimote GEN5 versions in production/available.

[JS007]

My two AEO Minimotes working very well under UI5 as scene controllers.

the Minimotes (non-gen5) worked well for me also under ui5 and ui7

so far none if the gen 5 stuff I have purchased has worked fully on ui7 on the veraedge

[maddingo50]

I can't even get mine to add the remote. Don't even know what mode it is in anymore. Any ideas?

[dzmiller]

Hopefully Vera can get the gen 5 Aeon key fob to work. This seems to be the only remote small enough to be routinely carried in the pocket.

[Kullematz]

There are even non-gen5 key fobs from Aeon in the market (same size).

[cpmilez]

After many hours, i've finally managed to get my key fob (Gen5) to work.  I was able to pair it easily using the same instructions as found online, however after switching to scene mode the buttons failed to send any commands to Vera.  The light was indicating red as well which didn't seem right and the instructions indicated it should be green. 

I then set the parameter 250 =1 in for the device in Vera and then whilst holding down a button on the fob and clicking "configure node right now" under the device settings it updated the key fob with the new parameter and after that the key fob gave me a green light when pressing buttons, some progress!  From checking the logs I could see Vera was then getting a command when a button was pressed so I setup a scene to trigger when scene 1 was activated.  This worked hooray!!!  However... I then found the same scene triggered regardless of which button i pressed, booo!!!

At this point I contacted Vesternet who gave me some pointers.  Apparently Aeon changed the way that they send Scene commands in the Gen5 version of the keyfob, so they no longer get mapped correctly to the "sl_SceneActivated" variable - this is what the built in Scene Controller support in Vera uses to Trigger Scenes from.

The Scene IDs are now as follows:

Button 1 short press = 1
Button 1 long press = 2
Button 2 short press = 3
Button 2 long press = 4
Button 3 short press = 5
Button 3 long press = 6
Button 4 short press = 7
Button 4 long press = 8

However this part didn't really help as if I set the scene to trigger on scene activated = 1 it would trigger for all 4 buttons.  From my logs I found the "sl_SceneActivated" variable was always 1, however "LastSceneID" variable was correct and matched to the mapping table above.  Using this and another example from Vesternet support for the Z-wave.me Wall Controller I was able to easily add some Luup code to the scene to act differently for each button.  Here's the code I used.

Firstly set the trigger for the keyfob device - "scene activated" and put the scene number to *

Then in the Luup code use something like this below.

- Replace: "232" for the deviceid of your key fob.

- pushbullet_push is just a function I used for testing, you can put anything you want here to control a device or run another scene for example.

Code: [Select]

luup.call_delay('scene_controller', 1)

function scene_controller()
    local lastSceneID= luup.variable_get("urn:micasaverde-com:serviceId:SceneController1", "LastSceneID", 232)

      if (lastSceneID== "1") then
        pushbullet_push('Debug', 'Button1 Pressed')
      elseif (lastSceneID== "2") then
        pushbullet_push('Debug', 'Button1 Press/Hold')   
      elseif (lastSceneID== "3") then
        pushbullet_push('Debug', 'Button2 Pressed')     
      elseif (lastSceneID== "4") then
        pushbullet_push('Debug', 'Button2 Press/Hold')       
      elseif (lastSceneID== "5") then
        pushbullet_push('Debug', 'Button3 Pressed')       
      elseif (lastSceneID== "6") then
        pushbullet_push('Debug', 'Button3 Press/Hold')       
      elseif (lastSceneID== "7")  then
        pushbullet_push('Debug', 'Button4 Pressed')       
      elseif (lastSceneID== "8") then
        pushbullet_push('Debug', 'Button4 Press/Hold')       
    end
end

References:
Add keyfob to Vera: http://www.vesternet.com/resources/application-notes/apnt-22 (switching modes is different for the Gen5 it seems, see manual for this)
Additional Luup Code: http://www.vesternet.com/resources/application-notes/apnt-69  (toward bottom of page)

Please note this was done on a Vera Lite with Firmware: 1.5.672

Hopefully this will help someone else and save you some frustration!

[AChilton]

Thank you cpmilez1! Fantastic work figuring it out!

Here is some additional and expanded information to get your Aeon Gen5 Key Fob working WITHOUT luup code (until Vera fixes the device setup in a firmware update).

Tested on a Vera 3 running UI7 with Firmware 1.7.481

- Include your key fob as a device in Vera (help on this is not discussed here)
- Set your key fob in USE mode. Do this by depressing and holding the pin in the rear of the fob's Mode and Learn holes simultaneously for 3 seconds. To make sure you are now in USE mode, press all four buttons, one at a time. They all should light up in red when pressed. If not, repeat this step.
- Go to Devices, click on the > next to the controller name (default name is: _Scene Controller)
- Scroll down and select "Device Options"
- On the Device Options screen, click on "Add configuration settings"
- In the "Variable" field, input: 250
- In the "Data Size" field, select: 1 byte dec
- In the "Desired Value" field, input: 1
- Click on the "Back" button at the top of the screen
- Scroll down and click on "Advanced"
- On Advanced screen, scroll down to the bottom where the "Configure node right now" button is
- Bring the key fob withing 3 feet of the Vera box and press and hold the top left button on the key fob (button 1), and then click on "Configure node right now" button. Keep the key fob button pressed for at least 10 seconds.
- Click "Ok" on the popup
- Check to see if your key fob is in Scene mode by pressing each of the buttons. If each of the buttons light up green, you are in Scene mode. If not, repeat the "Configure node right now" step
- Your key fob is ready to activate scenes
- Go to "Scenes" to create a scene for your key fob
- Click on "+ Add Scene"
- Click on "Select a device"
- Choose your key fob controller
- Select "A scene is activated"
- Enter the scene number (button number) you want to use to activate this scene

- Here's where it gets odd:

IF Vera had the setup right, the scene numbers should associate like this:

Button 1 short press = 1
Button 1 long press = 2
Button 2 short press = 3
Button 2 long press = 4
Button 3 short press = 5
Button 3 long press = 6
Button 4 short press = 7
Button 4 long press = 8

HOWEVER, the associated numbers are actually:

Button 1 short press = 5
Button 1 long press = 6
Button 2 short press = 7
Button 2 long press = 8
Button 3 short press = 1
Button 3 long press = 1
Button 4 short press = 8
Button 4 long press = 1

As you can see, you will only have 5 out of 8 unique button variations to choose from. Pressing Button 3 short, Button 3 long, and Button 4 long will activate the same scene. Pressing Button 2 long and Button 4 short will activate the same scene.

- Click on "Validate"
- Continue setting up the scene as you normally would
- Your key fob should now work!

If you want/have to use all the buttons on your key fob for unique scenes, set up one scene with multiple triggers to be activated by button numbers 1,5,6,7, and 8.  Leave Step 2 - Device Actions empty. Then use cpmilez1's luup code to configure each button's action. This should work in theory, however, I have not tried it.

Many thanks again to cpmilez1. Any help my post is for someone is due to your research on the problem.