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
MrNoTip 2
tl;dr I just moved my two Aeotec Gen5 garage door controllers from my HC2 to HC3. One of them got a third binary switch slave and one didn't. Why?
As the garage is such a critical device for us, I fully migrated one device before touching the second door. I took the first device down and brought it to the controller (mainly for my own convenience as that's where the computer is anyway), had a smooth setup experience, finishing up with a generic master device and a slave barrier controller.
I reinstalled the first controller, tested it, and then started on the second using the exact same process. This time I got another slave device - a generic binary switch. From testing it without a door connected, it seems to be a 'dumb' way to open and close the door without reporting the open/opening/closing/closed status - it makes the same flashes and relay noises anyway.
I don't think I had this third device for either of them on the HC2, but I can't check now. I've already set up the other one, and don't really need the binary switch, so I am not going to spend time removing and re-adding, but I expect there is some chance the third device would turn up if I did that.
I have had this sort of thing happen at times before, but its usually that there's a slave that I actually need missing, and I can only remember that happening when I was having difficulties getting the thing to remove/add in the first place - like the connection was weak in the first place. This time around the devices were about a metre from the HC3, following the exact same process for both, and the pairing started immediately on the first try.
I'd be shocked if I'm the only one who's had this issue intermittently when adding devices, but does anyone know what causes it? Or even better, any tricks to avoid it?
0 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.