Welcome to Animus Talk

This is where users of Animus Heart can share ideas,
solve problems and inspire fellow enthusiasts.

Animus Heart?

Aeotec Key Fob Gen5

Just bought Aeotec Key Fob Gen5 to the wife thet hought was that she would have it to unlock and lock the door among other things.

But after adding it I only get these choices? have tried to add and remove it several times, but the same.

What am I missing or not understanding?

Bump

Bring up my post

Hi there,

what’s missing is an option named “Key Pad” or something like that.
I am using the Fibaro KeyFob which looks like that:

fob

When klicking it you will find all available options for each key.

Perhaps the Aeotec Fob is simply not working with the Heart at least it is not listed here:

https://www.animushome.com/en/partners

Did you try to ex- and include the device via the console, to see if there is a helpful log output?

Greets
Olsen

Hi,

no it’s not in that list. but its in the list were u add devices. there fore i thougt it was compatible.

otherwise i don’t understand why it’s listed there. Just as u show in ur picture im missing the part where u will see the key commands. i have tried exclude and include many times without any diffrence

Did you try to re-include via the console (web terminal) and kept the device close to the Heart?
Maybe it makes a difference between including via your computer’s web-browser or mobile phone?
Otherwise, and if you are sure that the Fob is not defective, it seems to be a question for the developers or a more skilled person than I am.

Yeah i tried it with my Brothers homey, and there it worked. soe nothing wrong with the device.

Have tried to include it by a computer and with the browser, and by the phone. Keept it Close.

maybe the new update will fix it, will buy a fibaro key instead. and put this on the shelf

Not tried this key-fob previously, does it support Z-Wave+?
Just like Olsen said, trying to re-add it but closer to the Animus Heart could maybe fix it since it enters the system but all packages are not being added. Try the automatic adding alternative also.

"The Aeotec Gen5 KeyFob is a Z-Wave+ Remote Control, which features all the functionality of larger Z-Wave remote controls into a smaller, more modern design. Because of its small size it can be fit on a keyring and taken anywhere with you.

This Key Fob Remote Control can be set up as the primary controller of a Z-Wave network or as an additional Z-Wave controller. This is perfect for including it as a remote control in an existing Z-Wave network. This device operates in two distinct modes: setup and use. Each of the four buttons on the Key Fob can control multiple Z-Wave devices with a simple push and can control up to 8 different scenes. "

it does support z-wave+

i have tried the automatic adding, but same thing.

kind of sad, becuase i like the feeling of it. and “m.nu” hade them cheap as hell right now

Thanks for the hint with the cheap price!
As I am looking for a more solid Fob than the Fibaro to carry around on my keyring, I ordered one , too, couldn’t resist. :roll_eyes:
So you will hear from me again maybe at the end of this week.

2 Likes

I just received my FOB, unfortunately my results are the same as yours.
Here is what I tried:

  1. inclusion via webconsole resulted in a timeout for 2 times
  2. inclusion with the GUI, chosing the appropiate device worked
  3. inclusion using auto-add worked, too.
    This is the log output from the inclusion:

info 2019-09-21 12:13:45 #bid114 - Node46: Connected socket
info 2019-09-21 12:13:45 #bid114 - Node46: Started Connection
info 2019-09-21 12:13:45 #bid114 - Device null: Interview process started
info 2019-09-21 12:13:46 #bid114 - Node46: was interrupted. Closing the receiver completly
info 2019-09-21 12:13:46 #bid114 - Node46: Closed connection
info 2019-09-21 12:13:46 #bid114 - Node46: Connected socket
info 2019-09-21 12:13:46 #bid114 - Node46: Started Connection
info 2019-09-21 12:13:46 #bid95 - New device detected: com.animushome.heart.packages.zwave.devices.0086-46
info 2019-09-21 12:13:46 #bid114 - ServiceEvent REGISTERED
info 2019-09-21 12:13:46 #bid13 - device found, DAL, sid=244, bid=114
info 2019-09-21 12:13:46 #bid13 - no driver for DAL, sid=244, bid=114
info 2019-09-21 12:13:46 #bid114 - ServiceEvent REGISTERED
info 2019-09-21 12:13:46 #bid114 - ServiceEvent REGISTERED
info 2019-09-21 12:13:46 #bid114 - ServiceEvent REGISTERED
info 2019-09-21 12:13:46 #bid26 - Created JsonStorageNode: /config/abe61822-57cb-42e4-8b49-d3cbc536a016 [ com.google.gson.JsonOb
ject ]
info 2019-09-21 12:13:46 #bid26 - Returning writer for node: /config/abe61822-57cb-42e4-8b49-d3cbc536a016
info 2019-09-21 12:13:46 #bid26 - Returning writer for: /var/ah/framework/datastorage/com.animushome.heart.packages.zwave/confi
g/abe61822-57cb-42e4-8b49-d3cbc536a016.data.json
info 2019-09-21 12:13:54 #bid26 - Returning writer for node: /config/abe61822-57cb-42e4-8b49-d3cbc536a016
info 2019-09-21 12:13:54 #bid26 - Returning writer for: /var/ah/framework/datastorage/com.animushome.heart.packages.zwave/confi
g/abe61822-57cb-42e4-8b49-d3cbc536a016.data.json
info 2019-09-21 12:13:54 #bid114 - Device 46: Interview process done
Connecting to server …
CONNECTED

There is a message in the log, saying “no drivers found”, maybe that’s the problem?
I also found that the Fibaro FOB has 2 associations for each button, while the Aeotoc has only one.
ID 50 = Aeotec
ID 25 = FIbaro

aeofob

Also unsuccesfully tried changing parameter 250.
Seems like the Heart doesn’t like Aeotec devices…

But why is the product in the gui? When its not working

I have no idea, maybe the device list comes from a global Z-Wave database?
Anyway, I started a support case for this, so let’s wait for an answer.

2 Likes

@kristoffer.hanquist
Looks like other platforms have similar problems integrating this device:

Except for resetting the Heart there seem to be practicable workarounds.
Did you already try any of them?
I will return home this weekend and keep fiddling about with it. :sunglasses:

naw i have given up, gave it to my brother who has a homey. there it worked like a charm.

im also thinking about going over to the dark side, so much more u can do with homey. Yes it has some bugs and flaws.

it’s been over a month since Animus dropped the news about the coming update. but nothing since then

1 Like

Thinking the same, with all the time and frustration you get working with the Animus there are much better option out there.

My first thougt was the homey pro, but it lacks a ethernet port. And seems very unstable judging by my brothers, and The range of both z-wave and 433 is a joke. Samething with zigbee. Im to old to use hassio, just want plugg and play. Thats why i choosed animus from the begining. It lacks a lot of features, but stable like stone. Running 86 devices on mine, and it just works.

2 Likes

A Raspberry Pi 4, a Aeotec Z-Stick Gen5 and a Domoticz installation and you have a lot more option. https://www.domoticz.com/wiki/Raspberry_Pi
Add USB adapters for what every you need, and it still cheaper then the Animus.

Wrote to support but they completely stopped responding, so really don’t see the point of using the Animus anymore. Every other product have more users and more documentation and options.

Sad to hear that the support stopped responding, not a very good customer service and good for the reputation.

My thoughts exactly.

To come back to topic, I tested all the workarounds, but the result stays the same.
Still no answer from the support. :disappointed: