Welcome to Smart Home Forum by FIBARO
Dear Guest,
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
As a member you can:
- Start new topics and reply to others
- Follow topics and users to get email updates
- Get your own profile page and make new friends
- Send personal messages
- ... and learn a lot about our system!
Regards,
Smart Home Forum by FIBARO Team
Question
garywiz 7
We have a client who loves the button. In fact we do too. It's very cool! Except that out of 10 that we have purchased, only 2 actually work reliably. About 5 of them work after a few clicks. One doesn't work until you click it about 10 times. 7 of them are brand new. One is still in the shrink wrap because so far, taking them directly out of the packaging consistently produces the flawed interchange on our ZWave network. This is a VERY popular problem I see here in the forum, and although Fibaro comments here says "the button works fine", I am very skeptical (with all due respect). I'm a firmware designer and have a lot of experience with this, so maybe I can lend a hand to debug these. I have three ZWave networks, all configured differently. The thing they have in common is "Indigo" as well as the AEOTEC USB Z-Stick. The buttons exhibit the EXACT SAME behavior if I disassociate them with one network, move to another location, repair, and debug. All networks are working flawlessly with the exception of the button. Even the Fibaro keyfob (the cool one with + - and triangles etc) works flawlessly and each network contains many Fibaro devices that are also working perfectly. So, I believe the problem purely has to do with the button.
Because it is a very useful device (and an expensive one), I have been spending some time with the people at Indigo (the hub software we use), and have been doing some RAW packet debugging. It's possible that there are flaws in the Indigo implementation of the protocol, and I'm spending some time learning what the RAW packets should be, and perhaps going to write my own driver specifically to debug what is happening.
I'm well aware of the internal microswitch and there is always a possibility that the button hasn't been fully pressed. So, in my testing, I press the button down slowly until there is microswitch contact, then carefully assure that I hear the small "click" when the microswitch makes contact so I'm sure I'm making a closure.
I can break down the problems into two classes:
Category 2 buttons have a very interesting behavior:
All of the buttons are labelled as FGPB-101-X (where X is the colour code) v3.2 AH.
However, some of them indicate, upon a status report, that security is supported, others (the original ones we purchased) indicate that security is not supported. So, even though the version numbers appear to be all the same, it almost is hard to believe that there are not slightly different versions of firmware.
As we are under contract to deliver this home automation system, we want to please our client by assuring that we figure this out. It is hard to believe that so many of them are "defective"! Our local supplier is willing to swap them out, but the two we have returned were replaced with buttons which have the same, identical flaws!
I am willing to do quite a bit of technical work to solve this. I have had nothing but wonderful experiences with Fibaro products, and they are the most reliable and incredible products we've used. However, this particular item, despite it's promise, seems to have something haywire going on.
Can you please suggest any starting points?
Link to comment
Share on other sites
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.