This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Comments
Still waiting for my one though so I can test it.
There is a new feature in there that needs thorough testing before sending it to the public.
Cool!
Could you please let us know when the keyfob will work?
I need some ‘hardware’ buttons to switch of the alarm (variable) and turn off the sirene in case of a false alarm.
but that is a mistake on fibaro's side they made a few BAD mistakes in their manuals.
1st mistake:
Wake up according manual: Hold circle and plus at the same time. this does not wake up the keyfob enough to accept parameters though.
real wake up: Open menu by pressing circle and minus at the same time, press triangle once so the LED is green, press plus to wake up the keyfob long enough to accept parameters.
2nd mistake:
to reset/delete you need to be able to enter the menu and perform the manual way of removing (see the wakeup steps in the first mistake), even though this works, if something is up, and you want to force reset the keyfob manually the manual states:
hold circle and plus while inserting the battery.
but this does not force reset the keyfob, you need to hold the square and plus while inserting the battery
still a little bit more testing, but i will finish the driver today and send it towards athom to be accepted in the app itself.
EDIT:
Just a side note.. definitely have the keyfob with lock sequence if you have it in your pocket/bag, or the battery will be dead within a week
But i just wanted to say, also receiving a fibo keyfob Monday. Nice to compare them to the Aeotec's for durability
Would it be possible to use the keyfob also as a presence detector by Homey sensing the keyfob is back in the network? If so it would make an even better addon.
OK, that's a shame. I was hoping that entering the Z-wave network would set of a trigger. It's not handy to carry it with you leaving the house then.
Just have to install next to the door and everyone entering presses 1 and leaving 0, that way it would be a very accurate people count. Although there are probably easier/cheaper solutions to that.
So it's going to take a little longer before the driver is completely done.
But indeed the keyfob, or for that matter any zwave battery device, won't "come back" into the zwave range unless it wakes up or gets activated by pressing a button.
The keyfob won't wake up at all unless you do it manually.
It is working, just not with the lock mode.
for now that is, am in the talks with fibaro about it, but... they are not the fastest with responding.
I have put the code on github for people that want to use it, and it works perfectly (except for that lock mode of course).
but, it will not go into the appstore until that is working.
since the lockmode is the biggest thing that needs to work besides the normal button uses/sequences of course.
Hi @caseda ;
Do the series also work? I'm testing but cannot trigger a flow when pushing two buttons in sequence. Below my config:
Pushing whitin 1 sec:
Reeks 5: (- +)
Reeks 6: (+ -)
when I tested it, it was working perfectly.
did you wake up the keyfob? (not by holding Circle and plus, homey doesn't know it's awake then, only use the menu way I described in a post before)
It does not wake up on its own
It's best to wake it up just before you press the save button.
Do note that settings only get send when the value was changed from previous value.
So it's best to change the value, save, then change the sequence back to the value you want, wake up the keyfob, and press save
@caseda: Did you have any luck with the lock mode? Problem is to set the local protection I assume
but almost seems like they don't want to answer (now almost 6 weeks later)
The setting of the local security is not a problem (signals was send properly etc) , but seems it takes more to activate the lock mode
Some issues:
but this would most likely not fix your battery drain issue as the lock mode only locks the buttons, i don't have this issue myself and have not been able to reproduce it as of yet. (you are the 2nd issue post about this anyway, but have seen multiple on other forums, so it is most likely not an homey issue)
2. This should not be the case, as the keyfob works in "broadcast mode" when disconnected from the network for a few seconds, this means it just sends it's signal into the world (the node that then is the most nearby will pickup that signal and relays it to homey), so no need to be connected to the network beforehand, the only thing it could be is that there is no powered device near the vicinity where you arrive with your car that can relay the signal.
3. as stated in point 2, it broadcasts the signal, this signal is a bit stronger then the normal signals but still a car works like a "cage of Faraday", your mobile phone and gps have the same issue, and inside the car, the range just suffers by this, you can try by holding the keyfob closer to the window of your car door as that is the most easy to come trough for RF signals, but nothing more can be done.
4. i have no experiences with other keyfobs, but point 2 and 3 will be the same for every keyfob there is, even normal RF ones, usually if normal RF ones work better it is because the receiver is near the garage door where you enter, so always nearby.
Probably a noob question, but how do I add this to the driver? I checked the box and I've got v3.2 (15/2/2017 although I bought them last week (thx Coolblue ;-)))
well if you know how to develop in javascript then it is not that hard and send it in as a PR.
but my guts say that you are not a developer, so i think the best idea is to add it as an feature request on the fibaro github repo, even though i might find some time soon as i want it too, somewhere in the near future, (just the lack of time and especially energie is bouldering through my life) if you add it there and robin (athom employee) has time before i do, he will add it
I cannot get this to work, in fact, I'm able to completely crash Homey Fibaro module while trying to..
I've created a ticket on this one: https://github.com/athombv/com.fibaro/issues/179
Though don't use it now as i like the responsiveness more when only single press is activated.
What do you mean with crash the module, that is impossible without a stack trace, and probably a totally different reason for the non responding devices
Can you give a zwave log just after changing the parameter(s)?
There's a send log code in there directly after I "crashed" it.
What I mean by crashing is that I can "hang" the Fibaro stack (reproducable) in a way non of my Fibaro devices work anymore from Homey when trying to configure the KeyFob.
Restarting the "Fibaro" module isn't sufficient to correct the problem then, only completely rebooting Homey solves the problem.
So assuming the keyfob is node(25) it looks like it is getting the new settings pushed but no reason why the whole homey needs a reboot in order to be able to communicate again with other Fibaro modules