forum

Hello
I repost here the. Ticket opened to aeon.
Any help is welcome.

Hello
I am following the instructions to manage a fibaro fbs 221 dual load switch with the aeon key fob remote but it does not work.
I am able to include the first switch on any of the key fob buttons but there's no way to manage switch2.
If I try the inclusion procedure always the first gets reincluded.

1) I click and hold down the desired key fob button
2) I triple click contact 1 on the fibaro (procedure to start inclusion on the fibaro)
3) Then turn on switch 1

The key fob acknowledges and I can manage the switch1

If I repeat the same and switch on switch2 atbstep 3 above... Always switch1 gets managed.

The network is composed by a zstick II on a synology nas managed through zwave.me software.

In zwave.me the key fob is recognized as a remote controller (interview of the device is correctly completed according to zwave.me).

I am posting this also on the zwave.me forum and I am available to give help in troubleshooting if needed.

I am waiting to be authorized on fibaro forum to post here too.

Thank you
Best regards

The usual way to manage Associations using button hold in Aeon Fob does not allow to handle second relay. You need to use AssoiationCommandConfiguration or MultiChannelAssociation Command Classes to solve your issue. Both are accessible from Expert Commands tab in Z-Way (if supported by the Fob)

I can't find in expert tab of the key fob any AssoiationCommandConfiguration or MultiChannelAssociation Command Classes.

I have got just
configuration, ManufacturerSpecific,Battery, wakeup,association,version as avaialble CommandClass.

Can I use the Set/Get commands under configuration to "program" the keyfob with the help of the advanced paragraph of the keyfob?

I have an advanced manual that specifies what to send through :

Using the Configuration Command Class:
When using the Configuration Command Class to set up scenes, all values saved will be sent via
the Basic Command Class such that most Z-Wave devices can respond. If other (or custom)
command classes are required to be sent, please see “Using the Association Command
Configuration Command Class” instructions below

For aeon labs 4 keys Key fob (looks veeerysimlar to the zway keyfob btw).
Have been trying now for weeks to use it without success.

It is supported in openzwave so, perhaps, it is not so difficult to add support.
Ty in advance

I don't really understand what should we support in this device. Afaik, it has almost same firmware (and hence behavior) as the minimote. We have tested the minimote and it is very buggy - goes to sleep to fast, never replies to some commands. Does not passes our interview. Hope Aeon has fixed it since.

So, what does not work for you? Are you able to finish the interview and get the list of Association groups?

Didn't check for a long time the post.
Thanks for replying quickly.
I agree on the opinion about the keyfob.
Not really a good product.
Have almost given up on configuring it.
The Interview does not even finish so little to do.
I will try to define it a minimote as per your suggestion.

And... yes indeed you are right focusing on other devices until AEON takes care of the device itself

Is the zwave.me remote supported in a better way?
The zwave.me is agood candidate?
TY

It is not fair to reply, since Z-Wave.Me Key Fob was done by us

But it is supported 100%

Ok i will be the not fair
The aeon is really weak product.
Not supported not only by your platform but by several others.
Support from the company is not so good either....
Usually I am the first one praising when some product is good. This one is not.
I will buy a zwave.me