Aeon Labs Key Fob Issues

  • 50 Views
  • Last Post 11 April 2017
joey10e posted this 30 March 2017

I am having some issues getting my new Aeon Labs Key Fob working. I have tried to follow both of these articles.(http://www.axialcontrol.com/recipes/recipe/26, http://www.incontrolha.com/DeviceLibrary/viewDevice/41) I am able to get the key fob added to Axial Control and I am able to get the device to auto configure twice with a success message. The issue I have is when I go to a scene and click the "Assign Activation Button" and then click a button on the key fob nothing happens. It seems like at that point the key fob is not being recognized. Am I missing a step? Has anyone else had this issue? Thanks in advance for any help.

Order By: Standard | Newest | Votes
rscott posted this 31 March 2017

Assuming you used the pin to switch it to group mode and then did an auto configure, you should be good to go. What message did you get after your autoconfigure? 

joey10e posted this 01 April 2017

So I decided to try and start over so I removed the device from incontrol using zwave commands/remove device. I then reset the fob by holding down the mode pin hole for 20 seconds until the green light came on. I then added the fob using zwave command/include device. the device added with no issues. I then followed the guide to change the device to group mode. I then tried to auto configure. I then kept getting this message.

autoconfiguration failed with the following message:

the server did not respond.

So I tried a few times with the same results. I then removed and re-added the fob using the same process as before excluding the reset of the fob. After a few tries I finally was able to auto configure twice. with this message.

Auto-configuration node 54

Associating device with main controller...

...Sucess!

Manufacturer id is 134. Product id is 88.

I then try to assign a button to a scune and nothing happens.

rscott posted this 01 April 2017

It seems the product id has changed, maybe as a result of a firmware update Aeon Labs did. As a result. Axial Server isn't setting the proper configuration on yours.

You can try to manually set the configuration. You'll want to use the "Config" button to set param 250 to a value of 1. Be sure to wake it up first.

Let me know how it goes - if its a success, I'll make sure product 88 is added to the auto configure list.

 

joey10e posted this 02 April 2017

Okay, I did not find a "Config" button but I did use a "Params" button to set param 250 to a value of 1, but still now success. Let me know if that was what I was supposed to try.

rscott posted this 09 April 2017

Joey10e, is everything working after you manually changed that param?

joey10e posted this 10 April 2017

No, it still just won't add a button. It seems to be working otherwise. Axial shows the device being woken up and the battery level.

rscott posted this 10 April 2017

Ok, so setting param 250 to a value of 1 is indeed what you needed to do.Could you retrieve that value and verify that it's set to 1? 

Also, please try the following for further troubleshooting:

  • Double click the remote
  • Check the "audit" option
  • Go offline, wait 30 seconds, go back online
  • Go to a scene and click "Assign activation button"
  • Press a button on your remote
  • Wait 2 minutes, then attach your logfile.txt to this message (or email it into support)

 

joey10e posted this 11 April 2017

Okay, I was able to retrieve the param 250 and it came back set to 1. So I did not find an "audio" option but I checked "audit node (requires restart)" I then followed the rest of the steps. here is the last 10 minutes of my log file from while I ran the test.

 

4/10/2017 9:00:27 PM: SEC: Sending LockOperation command to node 25

4/10/2017 9:00:30 PM: Alarm_level 1 received from node 26

4/10/2017 9:00:30 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:00:30 PM: Unrecognized alarmType 0 with event 0

4/10/2017 9:00:30 PM: Alarm_level 1 received from node 26

4/10/2017 9:00:30 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:00:30 PM: Unrecognized alarmType 0 with event 0

4/10/2017 9:00:30 PM: SEC: Sending LockOperation command to node 27

 

4/10/2017 9:00:43 PM: Unknown alarm_type of 23 found for node 25.

4/10/2017 9:00:43 PM: Alarm_level 1 received from node 25

4/10/2017 9:00:43 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:00:43 PM: Unrecognized alarmType 0 with event 0

4/10/2017 9:00:43 PM: Unknown alarm_type of 23 found for node 25.

4/10/2017 9:00:43 PM: Alarm_level 1 received from node 25

4/10/2017 9:00:43 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:00:43 PM: Unrecognized alarmType 0 with event 0

4/10/2017 9:00:45 PM: Unknown alarm_type of 23 found for node 25.

4/10/2017 9:00:45 PM: Alarm_level 1 received from node 25

4/10/2017 9:00:45 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:00:45 PM: Unrecognized alarmType 0 with event 0

4/10/2017 9:00:45 PM: Unknown alarm_type of 23 found for node 25.

4/10/2017 9:00:45 PM: Alarm_level 1 received from node 25

4/10/2017 9:00:45 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:00:45 PM: Unrecognized alarmType 0 with event 0

 

4/10/2017 9:00:51 PM: Command COMMAND_CLASS_DOOR_LOCK.DOOR_LOCK_OPERATION_SET, data: FF failed to node 27

 

4/10/2017 9:02:09 PM: Unknown alarm_type of 167 found for node 26.

4/10/2017 9:02:09 PM: Alarm_level 1 received from node 26

4/10/2017 9:02:09 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:02:09 PM: Unrecognized alarmType 0 with event 0

4/10/2017 9:02:09 PM: Unknown alarm_type of 167 found for node 26.

4/10/2017 9:02:09 PM: Alarm_level 1 received from node 26

4/10/2017 9:02:09 PM: Found zwaveAlarmType of `0` with event of `0`

4/10/2017 9:02:09 PM: Unrecognized alarmType 0 with event 0

 

4/10/2017 9:02:48 PM: [BOR] Node.level = 0

 

4/10/2017 9:04:40 PM: [BOR] Node.level = 0

 

4/10/2017 9:05:51 PM: SEC: Sending LockOperation command to node 27

 

4/10/2017 9:06:13 PM: Command COMMAND_CLASS_DOOR_LOCK.DOOR_LOCK_OPERATION_SET, data: FF failed to node 27

 

4/10/2017 9:06:27 PM: Properties requested for device 8cb9857b-8fef-465e-8526-efe9b8c19be9

4/10/2017 9:06:27 PM: Found device: yes

4/10/2017 9:06:27 PM: getDeviceDetails: 1

4/10/2017 9:06:27 PM: getDeviceDetails: 2

4/10/2017 9:06:27 PM: getDeviceDetails: 3

4/10/2017 9:06:27 PM: getDeviceDetails json: {"lastCommunication":"0001-01-01T00:00:00","queuedCommandCount":0,"pollTimeSeconds":30,"isSleeping":false,"pollDevice":false,"smartRoutePolling":false,"enableReporting":false,"mobileHidden":false,"shortId":108,"auditNode":true,"pushUpdates":false,"allowRoomManagerUse":true,"queueCommandsUntilWake":false,"neverUseSecureComms":false,"markOfflineNoComms":false}

 

4/10/2017 9:07:20 PM: Original FolderC:\WINDOWS\system32

4/10/2017 9:07:20 PM: Changed to:C:\Program Files (x86)\AxialControl.com\Axial Server

4/10/2017 9:07:20 PM: Starting Service

4/10/2017 9:07:20 PM: Preparing service base

4/10/2017 9:07:20 PM: Original FolderC:\Program Files (x86)\AxialControl.com\Axial Server

4/10/2017 9:07:20 PM: Changed to:C:\Program Files (x86)\AxialControl.com\Axial Server

4/10/2017 9:07:20 PM: Config file location: C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\Moonlit_Software,_LLC\MLS.ZWave.Service.exe_Url_2oj1mabccafkjznq1c34xhwze50a55sc\4.1.6123.12854\user.config

4/10/2017 9:07:20 PM: Running service base

4/10/2017 9:07:22 PM: Starting version 4.1.6123.12854

ZenLib: True

StickType:OpenZWave

ComPort:3

Service:True

4/10/2017 9:07:22 PM: Cloud: Attempting to connect to cloud server over chanId: 6174d...

4/10/2017 9:07:23 PM: socket: Opened!

4/10/2017 9:07:23 PM: Cloud: Cloud connected!

4/10/2017 9:07:23 PM: Plugin: Processing C:\Program Files (x86)\AxialControl.com\Axial Server\plugins\EnhancedSecurity.dll

4/10/2017 9:07:23 PM: Plugin: Processing C:\Program Files (x86)\AxialControl.com\Axial Server\plugins\FoscamController.dll

4/10/2017 9:07:23 PM: Loaded Controller Plugin HaFoscamController

4/10/2017 9:07:23 PM: Plugin: Processing C:\Program Files (x86)\AxialControl.com\Axial Server\plugins\OpenWeatherMapDevice.dll

4/10/2017 9:07:23 PM: Loaded Controller Plugin OWMDevicePlugin

4/10/2017 9:07:23 PM: Plugin: Processing C:\Program Files (x86)\AxialControl.com\Axial Server\plugins\VirtualHaController.dll

4/10/2017 9:07:23 PM: Loaded Controller Plugin VirtualHaController

4/10/2017 9:07:27 PM: Weather plugin using coordiates 39.094602, -121.613545

4/10/2017 9:07:27 PM: Checking version

4/10/2017 9:07:27 PM: checkVersion failed - System.Net.WebException

The remote server returned an error: (503) Server Unavailable.

 

   at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)

   at System.Net.WebClient.UploadString(Uri address, String method, String data)

   at System.Net.WebClient.UploadString(String address, String data)

   at MLS.Common.InControlHaService.doPost(String url, String json) in Z:\work\mls\MLS.ZWave.Controller\MLS.Common\InControlHaService.cs:line 66

   at MLS.Common.InControlHaService.<>c__DisplayClass5_0.<checkVersion>b__0() in Z:\work\mls\MLS.ZWave.Controller\MLS.Common\InControlHaService.cs:line 43

4/10/2017 9:07:29 PM: DirectConnect: New client connected from 127.0.0.1

 

4/10/2017 9:08:50 PM: [BOR] Node.level = 0

 

4/10/2017 9:09:11 PM: Command COMMAND_CLASS_SECURITY.SECURITY_COMMANDS_SUPPORTED_GET failed to node 29

 

rscott posted this 11 April 2017

What's the node id of your key fob?

joey10e posted this 11 April 2017

The node ID for my key fob is 54.

rscott posted this 11 April 2017

Hmm, there's nothing in your logs from your Keyfob - meaning it's not sending anything to your USB stick/Axial Server when you press the button. Can you verify that your USB stick is setup in association group 1 for the remote? Also, is your USB stick setup as your primary or is it a secondary controller?

Did you also restart (go offline/online) your server after enabling the audit?

Close