I'm now having some crazy zigbee binding issues with several of my Blues -- totally unsolicited, two of them have bound to each other and at least one more is binding itself to other zigbee devices on my network. The two bound to each other are also binding themselves to other zigbee stuff too.
This is too bad, but I should've known better than to be so tip-of-the-spear with getting these - excitement got the best of me... Hopefully, Inovelli fixes the problems they have with these, but I can't have random stuff getting turned on unawares on my network, so I'm now ripping all of mine out.
I wish Inovelli well, but it's back to Caseta and Zooz for me.
I posted over there too, but no traction - it doesn't seem like anyone else is experiencing this (yet?), but since none of the binding stuff is exposed as UI options, I know it's not a setup error on my part.
Sadly, given that I have no confidence in what other stuff these things will turn on/off, I'll start taking them all out tonight and replacing them with whatever mix of old dumb & smart stuff I happen to have handy in the house here. I'm unfortunately not in a position to wait indefinitely on a fix for this.
"epow" (user over there) had a good suggestion -- see if the bindings stick if my HE is offline. My wife has a work thing tonight, so I'll try that when she leaves here soon.
Incredibly flexible. However if the XBee LQI values are accurate, I am surprised. My Iris plugs are incredible repeaters, time will tell with these new switches.Seem to operate fine so far.
This is the switch
No joy - the bindings stayed as-is with HE powered down.
And it got worse as the evening progressed... Now 5 of my remaining 8 switches have bound themselves together (along with a smattering of other zigbee stuff) -- it's so completely bizarre. It's like some kind of growing virus.
I wonder of they'll all be bound together by morning!
Anyway, I decided to go with a mix of HomeSeer and Zooz as replacements for all 9 Blues (I somehow totally bricked one Blue this afternoon attempting a reset) -- I need scene control options for most of these switches, or I would've gone with more Caseta.
Replacements will arrive by Weds, so I'll take time off Thurs to re-do everything. Wish me luck!
Right on! I'll keep the Blues, and keep an eye on the Inovelli forums -- hopefully some future firmware and/or driver update will squash whatever bug this is. If so, I'll likely dust them off again for another try in a couple/few spots.
I'd normally try to ride something this out for longer, but yikes -- it's just too crazy to have so much random stuff come on all over the house and garage when you're just trying to turn on a small hallway light lol... Gratefully, my wife is patient with this sort of stuff, but not infinitely so
You replied very quickly, sorry I took so long. I created a rule in RM, run custom action, actuator (Like the reds), choose device, but I don't have the additional parameter options you appear to have.
I don't know if my problem is exactly like your issue, but it's at least in the same realm. My issue with my blues is when I create a group for my four kitchen switches and turn on zigbee messaging, they are acting like they are bound to each other even though each individual switch shows they have no associated bindings. It's not my first go with zigbee groups and group messaging, so it is definitely unexpected behavior. For the time being I've had to kill the groups I created with the blues because it drastically alters my after dark motion lighting flows in NodeRed.
I posted my issue over on the Inovelli forums as well. We'll see if we get some sort of resolution.
Sounds like Eric has a possible fix -- they are testing furiously as we speak and hope to release it in a day or two here (not totally certain if it's a driver or f/w update - maybe both?)
In my confused haze last night, I stupidly forgot that the Blues work just fine as a basic switch (w/ load of course) when factory reset, so that at least buys me some time before the wife goes nuclear.
I have a bunch of (other brand) replacements enroute, and that gives me some peace-of-mind, but hopefully I'll be able to just return them instead.
I had no issues with any initial pairings, and overall performance was perfectly fine for all my switches (in terms of responsiveness once installed etc).
But the binding craziness derailed me before I could take a good look at LQI stuff -- I did take a couple quick glances at my ZB routing table and the numbers were not good, but I decided that as long as performance was OK, I'd just roll with it.
My ZB mesh was in really good shape before I added these, so I was not depending on them to do any heavy-lifting in terms of being "must-have" repeaters in my mesh or anything like that.
I just hope that they don't drag other stuff down if they do try to route, but time will tell -- Eric & team is keenly aware of those issues too, so hopefully they can make progress in that realm also.
Yeah I have to give mad props to the crew over there - they seem to be very open and honest about what is going on... that definitely gives me some hope/confidence.
Interesting that your issue is likely a hidden "feature" that wasn't fully worked out before release but not removed. Looks like it actually does kinda work but maybe too well...
Let us know how the new firmware works out for you.
