Author Topic: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.  (Read 19458 times)

Offline cpmilez

  • Newbie
  • *
  • Posts: 19
  • Karma: +1/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #15 on: February 09, 2015, 03:32:39 pm »
Thanks ACHilton it seems like UI7 is probably interpreting the scene activated number better than it is in UI5 as its always coming through as 1 for me, hence the need for the Luup code as it has to get the actual scene from the LastSceneID variable.  Glad it was of some help at least and I can use my fob now!

Offline Bena

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #16 on: February 10, 2015, 08:08:16 am »
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!

Hi cpmilez,

I still having issue trying to configure the Aeon Key Fob.  Here are list of action that I take once I successfully added the key fob into my Vera lite V1.5.672.

1. I hold the Mode and Learn button behind the Key Fob to change it to USE mode.

2. I go the device setting pop-up under 'Device Options' tab  --> Add Configuration Settings --> Variable:250, Data Size:1 byte dec, Desired Value:1 (see attachment: "Setting Parameter")

3. Close the device setting pop-up and SAVE.

4. I then hold down the top left button on my key fob until green led flashing.  then on the device setting pop-up under "Settings" tab, I clicked "Configuration node right now".

5. Vera telling me that trying to communicate with the key fob.

6. I got an error from Vera telling me "Unable to get any information on node".  (See attachment: "Configuration Error")

I kept trying step 4 for a couple of time but no good outcome.  Please do let me know if I got any set up wrong or missing any steps.

Appreciate your help!

Thanks in advance.

Offline cpmilez

  • Newbie
  • *
  • Posts: 19
  • Karma: +1/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #17 on: February 10, 2015, 08:30:47 am »
All I would try is to make sure you are near the Vera box when you do it and ensure you start holding down the button BEFORE you press "Configuration node right now".

Offline BoneyCheng

  • Newbie
  • *
  • Posts: 7
  • Karma: +1/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #18 on: February 11, 2015, 12:04:46 am »
You want to wake up the Key Fob Gen5 before you click on "configure now", i haven't tried holding down any other buttons, but I know for a fact that the "Learn" Button can be used to wake up the Key Fob and allow configurations to it.

Take the pin, and put it into the "Learn Pin"

Method 1
1) Pressing and holding the Learn button will allow the Key Fob to send a wake up notification to your controller, will go back to sleep pretty fast, so i suggest using the method below.

Method 2
2) Pressing and holding the Learn Button will keep the Key Fob awake as long as you hold it down. The Green LED will stay on while you hold it



-------------------------------------------
Heres a cool method to determine what your Key Fob is set to using Button 3.

Single Tap to Button 3

- No LED Flash = Setup Mode
- LED Flashes
         - Red      = Group Mode
         - Green   = Scene Activation Mode
« Last Edit: February 11, 2015, 12:09:39 am by BoneyCheng »

Offline Bena

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #19 on: February 11, 2015, 08:39:03 am »
Hi Guys,

Thanks for all the replies and help.

Unfortunately I still can't get my gen 5 key fob configured. Not sure what went wrong.  Can you guys let me know which model of Gen 5 key fob you guys have? Mine is ZW088-A.

Thanks,

By the way did anyone successfully configured their key fob following method above? Definitely not doubting what they say and really appreciate they hardwork. Just want to know am I the only unlucky one.

Thanks,

Offline AChilton

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #20 on: February 11, 2015, 06:41:06 pm »
If you can't get your key fob into Scene mode, try starting from scratch. Put the key fob back into Setup mode, unpair and include it again into your Vera. Then immediately go through the steps outlined in this thread. It worked for me.

It took me three times holding down the button on the key fob and clicking "Configure node right now" before it magically lighted up green on all button presses.

Good luck.

Offline MNB

  • Hero Member
  • *****
  • Posts: 689
  • Karma: +4/-9
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #21 on: March 27, 2015, 01:25:58 pm »
I recently purchased two Gen 5 minimotes are these different from the key fobs? The reason I'm asking is that I do not have a green led but rather a blue (over button 1) and a red (over button 2) when I do a short depress I get both blue and red led light up and with a long depress of a button I get a flashing blue. The Mode pin is next to the Learn button under the slide compartment. I'm wondering if this procedure will work for the minimote (gen5)?
Edge-1.7.2607, VRI06-1LX Dimr (6), VS05-1LX Sw (4), GE ZW3002 Dimr (1), HA01C Outlet (12), HA02C Sw (6), HA04C Sw (4), GE Sw (2), HA05 Sw (3), MiniMote Contr (5), HSM200/100 Sensor (2), ZW100A Sensor (8), Nest thermostat (1) & Protect Fire/CO (6) Kwikset Locks (3), F18918W (1) & IP3M-9 (6) Cam's

Offline marcjw

  • Jr. Member
  • **
  • Posts: 74
  • Karma: +9/-3
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #22 on: May 13, 2015, 11:00:03 pm »
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 Save
- 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 within 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 "Devices" to create a scene for your key fob
- Scroll Down to "Select scenes for device buttons"
- If you are asked how many buttons you have, choose 8
- Activate the buttons you want by selecting the mode or scene you want
- When finished click "Activate scenes to buttons"


The button mapping finally works and looks 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


Woohoo!!!  When I got home today I found my Vera Edge had a firmware update waiting for me.  After applying it, I found my Aeon Gen5 key fob finally works!!  I modified the above quote from AChilton with the steps that worked for me.  The modifications are highlighted.  I did go through an unpair-delete of my previous install and started from scratch before it would work.  And I chose the new Hand Held -> ZWave+ keyfob as the device to install.

To repeat, the above worked for my Aeon Gen5 key fob for my Vera Edge running 1.7.1142 firmware.

Offline JacekRing

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #23 on: July 05, 2015, 06:28:12 pm »
Aeon Gen5 KeyFob doesnt work with VeraEdge UI7 firmware 1.7.1248 (or the one immediately before hand didnt work either updated today). I got it paired, switched to scene mode, and sent the 250=1 command but button presses register as:

1 = 1
2 = 0
3 = 1
4 = 2
5 = 1
6 = 3
7 = 1
8 = 3

weird thing is, according to the logs vera gets the proper inputs from the keyfob but interprets then wrong.  checked by quickly pressing the same button 4 times to simulate a dup call error. here are log excerpts:

button 1 multipress:
02   07/05/15 17:48:31.673   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 1 duration 255 is a dup <0x77662520>
02   07/05/15 17:48:32.203   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 1 duration 255 is a dup <0x77662520>
02   07/05/15 17:48:32.823   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 1 duration 255 is a dup <0x77662520>

button 3 multipress:
02   07/05/15 17:48:51.763   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 3 duration 255 is a dup <0x77662520>
02   07/05/15 17:48:52.323   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 3 duration 255 is a dup <0x77662520>
02   07/05/15 17:48:52.903   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 3 duration 255 is a dup <0x77662520>
06   07/05/15 17:49:08.463   Device_Variable::m_szValue_set device: 75 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 1 now: 1 #hooks: 3 upnp: 0 skip: 0 v:0x95c610/NONE duplicate:0 <0x77662520>

(as you can see scene 3 button pressed but sl_sceneactivated set to 1)

button 5 multipress:
02   07/05/15 17:49:20.343   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 5 duration 255 is a dup <0x77662520>
02   07/05/15 17:49:20.883   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 5 duration 255 is a dup <0x77662520>
02   07/05/15 17:49:21.453   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 5 duration 255 is a dup <0x77662520>
06   07/05/15 17:49:29.053   Device_Variable::m_szValue_set device: 75 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 1 now: 1 #hooks: 3 upnp: 0 skip: 0 v:0x95c610/NONE duplicate:0 <0x77662520>

button 7 multipresss:
02   07/05/15 17:49:37.843   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 7 duration 255 is a dup <0x77662520>
02   07/05/15 17:49:38.193   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 7 duration 255 is a dup <0x77662520>
02   07/05/15 17:49:38.603   ZWaveController::HandlePollUpdate_SceneActivation scene_act node 42 device 75 scene 7 duration 255 is a dup <0x77662520>
06   07/05/15 17:49:41.533   Device_Variable::m_szValue_set device: 75 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 1 now: 1 #hooks: 3 upnp: 0 skip: 0 v:0x95c610/NONE duplicate:0 <0x77662520>



I ofcourse can not duplicate this for the even number buttons as they are a 3 second press to generate so wont read as dup events.

but as you can see from the dup messages it does detect as the correct scene but doesnt set sl_SceneActivated correctly.

anyone have any idea on what can be done to resolve this?

Offline jsondag

  • Newbie
  • *
  • Posts: 12
  • Karma: +1/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #24 on: July 17, 2015, 10:30:58 pm »
I have a similar issue, and see a similar thing in my logs.
My mapping is
1=1
1l=1
2=2
2l=3
3=4
3l=5
4=6
4l=1

just like you I see it register the number right.
For 3l, which should be button six. I get this.

06      07/17/15 21:26:55.885   Device_Variable::m_szValue_set device: 35 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_SceneActivated was: 1 now: 5 #hooks: 2 upnp: 0 skip: 0 v:0xaee048/NONE duplicate:0 <0x7722a520>
06      07/17/15 21:26:55.887   Device_Variable::m_szValue_set device: 35 service: urn:micasaverde-com:serviceId:SceneController1 variable: LastSceneID was: 8 now: 6 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7722a520>

Offline jsondag

  • Newbie
  • *
  • Posts: 12
  • Karma: +1/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #25 on: July 18, 2015, 01:44:18 am »
I figured out how to fix it. The keyfob is setting the value "sl_SceneActivated" which is what Vera is looking at for the scene number incorrectly. It's setting "LastSceneID" to the right button.

So I created a new .json file for it called D_SceneControllerAeon5.json which is a copy of D_SceneController1.json but in the file I edited the line which contained "sl_SceneActivated", and replaced it with "LastSceneID", and then edited the advanced tab in the device to contain "D_SceneControllerAeon5.json in the device_json param.

Step by step:
1. Goto APPS
2. Click Develop apps
3.Click Luup Files
4a.Download "D_SceneController1.json" from there and edit the line as described, and save as "D_SceneControllerAeon5.json" OR...
4b. Download the pre-edited file attache to this post.
5. Upload the file into Luup files.
6. Goto the device page and choose advanced options
7. Set 'device_json' to "D_SceneControllerAeon5.json"
8. Reload luup engine/reboot vera.

This will make the buttons map correctly.

Offline adamroff

  • Sr. Newbie
  • *
  • Posts: 21
  • Karma: +0/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #26 on: August 16, 2015, 03:46:18 am »
I figured out how to fix it. The keyfob is setting the value "sl_SceneActivated" which is what Vera is looking at for the scene number incorrectly. It's setting "LastSceneID" to the right button.

So I created a new .json file for it called D_SceneControllerAeon5.json which is a copy of D_SceneController1.json but in the file I edited the line which contained "sl_SceneActivated", and replaced it with "LastSceneID", and then edited the advanced tab in the device to contain "D_SceneControllerAeon5.json in the device_json param.

Step by step:
1. Goto APPS
2. Click Develop apps
3.Click Luup Files
4a.Download "D_SceneController1.json" from there and edit the line as described, and save as "D_SceneControllerAeon5.json" OR...
4b. Download the pre-edited file attache to this post.
5. Upload the file into Luup files.
6. Goto the device page and choose advanced options
7. Set 'device_json' to "D_SceneControllerAeon5.json"
8. Reload luup engine/reboot vera.

This will make the buttons map correctly.


You sir, are a bloody legend!
after hours of trial and error manually mapping out which button was doing what i followed your post and BAM! all is logical again!

Offline kenray536

  • Full Member
  • ***
  • Posts: 119
  • Karma: +1/-2
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #27 on: August 26, 2015, 04:19:32 pm »
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!

I just got this working on my Vera 3 with Firmware 1.5.672 as well. I had to upgrade firmware as I was on 1.5.622. I was nervous but the upgrade only took about 20 minutes. I have about 80 devices and about 50 scenes, but all went well! I used this thread to do the upgrade. http://forum.micasaverde.com/index.php?topic=27870.0

Before the firmware upgrade the Vera was not able to set the 250 dec 1 bit when trying to do "Configure Node Right Now" in Settings. After doing the upgrade it did it instantly.

Also, I could not get the 1 long press and 4 long press buttons to work via Lua. I coded the other buttons though. Here is some code you can run if you want each button to set a scene.

Thanks to everyone else that put in hours before me. That helped me a lot as I was working on setting my KeyFOB up.

My KeyFOB device ID is 160. So you would change that one line to whatever device ID your KeyFOB is.
Code: [Select]
luup.call_delay('scene_controller', 1)

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

-- Button 1 Press OK --- Looking at KeyFOB with buttons on the top and slide down cover on the bottom - changed from 76
     if (lastSceneID== "1") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "4"}, 0)
-- Button 1 Press Press and Hold - BAD ?? - Not Working
      elseif (lastSceneID== "2") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "3"}, 0)   
-- Button 2 Press OK
      elseif (lastSceneID== "3") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "4"}, 0)     
-- Button 2  Press and Hold OK
      elseif (lastSceneID== "4") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "3"}, 0)   
-- Button 3 Press OK changed rom 76
      elseif (lastSceneID== "5") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "4"}, 0)     
-- Button 3  Press and Hold OK
      elseif (lastSceneID== "6") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "3"}, 0)     
-- Button 4 Press OK
      elseif (lastSceneID== "7")  then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "4"}, 0)     
-- Button 4 Press and Hold - BAD ?? - Not Working
      elseif (lastSceneID== "8") then
         luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "RunScene", {SceneNum = "3"}, 0)
    end





end
Vera 3 1.5.677 - DSC Envisalink 3 - Wemo - Philips Hue - Harmony - Wink Hub - Sonos - Echo Vera Bridge - HomeKit Bridge - GE - AEON Labs - Evolve - Leviton - Schlage - Honeywell - Ring Doorbell - Eagle Rainforest Bidgely

Offline DarkParty

  • Newbie
  • *
  • Posts: 10
  • Karma: +1/-0
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #28 on: November 29, 2015, 04:55:07 pm »
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.

This worked for me with a Vera Edge FW 1.7.1598

Offline Ironbar

  • Sr. Newbie
  • *
  • Posts: 29
  • Karma: +8/-6
Re: Aeon Gen5 Key Fob ZW088-A not communicating with Vera.
« Reply #29 on: January 26, 2016, 11:10:13 pm »
I figured out how to fix it. The keyfob is setting the value "sl_SceneActivated" which is what Vera is looking at for the scene number incorrectly. It's setting "LastSceneID" to the right button.

So I created a new .json file for it called D_SceneControllerAeon5.json which is a copy of D_SceneController1.json but in the file I edited the line which contained "sl_SceneActivated", and replaced it with "LastSceneID", and then edited the advanced tab in the device to contain "D_SceneControllerAeon5.json in the device_json param.

Step by step:
1. Goto APPS
2. Click Develop apps
3.Click Luup Files
4a.Download "D_SceneController1.json" from there and edit the line as described, and save as "D_SceneControllerAeon5.json" OR...
4b. Download the pre-edited file attache to this post.
5. Upload the file into Luup files.
6. Goto the device page and choose advanced options
7. Set 'device_json' to "D_SceneControllerAeon5.json"
8. Reload luup engine/reboot vera.

This will make the buttons map correctly.

Thank you sir!  This fixed my problem and worked perfectly.