@DanHi I pulled up your account here… at exactly 1AM Phoenix time, we received 18 requests from Alexa to turn lights off. And, because of the toggle nature of the light control signals, they will turn on if they were already off.
Here’s what has worked for others:
Disable “Hunches” in the Alexa app. If it’s already disabled, try enabling and then disabling.
Search for and remove any Routine in Alexa for turning off the lights at 1AM. I know… you would remember if you created it, but it would appear that these Routines can create themselves automatically.
OK, I turned hunches on (it said it was off) and then off, so we’ll see if that makes a difference. On the 18 alexa requests, was one of them for couch? In the past I removed this light from Alexa and it didn’t make a difference.
We’ll see what tomorrow will bring (hope springs eternal).
This doesn’t appear to be from my Bond. I have two Bond (a regular and a pro) but neither of them have that Bond ID, and none of my devices have that device id or name.
Sorry the example above was from my account. I was just showing the screen.
Anyways, this is really something you want to take up with Amazon, because they are creating these hidden routines and sending commands at 1AM in the morning. Nothing we can do to stop it other than de-authorize the account linking entirely.
I really don’t think this is the case, as I’ve looked at all my routines and none of them fire at 1:00 am. Also, in the past I’ve deleted the light from Amazon (which I did today) and still had the problem.
How did you get to the screen shot you sent me so I can check on my account and see if I can figure anything out.?
ResidualImages, I want to start off by saying thanks. Thanks for responding. Thanks for having such a depth of information.
I also want to apologize. Although I am not convinced the Bond Bridge isn’t sending errant commands (unless the Bond Bridge support was inaccurate or I misinterrupted), I unplugged the Bond Bridge early morning Sunday. Since then I have had more incidents of the lights coming on. For example, yesterday around 5pm, with my wife at home with me in the living room, the light came on suddenly. We were both perplex and immediately located the remote. I was confident we were not in a situation where we pressed a button, but couldn’t be 100% sure.
However, last night at 2 AM, while me and my wife slept, the light came on. The remote was 10 feet away from me so I know no one touched it. Annoyed, I got up and turned it off. IT HAPPENED AGAIN AROUND 4AM. The irony is that when it happened at 5pm that night, I mentioned how terrible that would be if it happened while we were sleeping. I lost multiple hours of sleep as a result.
I can say with confidence that the events I just described are free and clear of Bond Bridge because it’s been disconnected.
This has been a terrible experience and I am super disappointed with my experience thus far but I cannot place the blame squarely on Bond, obviously. I really expected this area to be much more robust. This isn’t high level automation. This is rather basic.
Please forgive me for not taking the initial comments regarding looking outside the Bond Bridge that seriously.
Thanks for continuing to post updates, @InoSiX - this is quite the adventure, but i understand not exactly fun for you / your family.
Well that’s super aggravating! I hope you can find whatever is causing the issues… A neighbor’s remote? I’m somewhat mystified whenever the Bridge has been powered off (assuming that’s what you meant by disconnected, and not solely just unlinked from Google) and you’re still having phantom light presses.
If your existing fan receivers + remotes have dip switches, might be worth changing the combination of those?
I know how to do this, I want to be able to see activity for the device. You said you could see Alexa sending 18 light off commands at 1:00 am. Where did you find this information?
This issue happens when the bond loses connectivity to the wifi router and resets itself. I have faced this issue of lights turning on/off and it happens when the wifi has an issue.
Next time it happens, check your phone and you will find that the BondXXX network will be visible (which would mean that Bond lost the Wifi connection and started it’s internal AP).
It’s OK. I know, once a remote-controlled appliance is connected to Bond, it is natural to attribute behaviors of that device to Bond.
Most likely cause, in my view, is (1) poor implementation of RF receive algorithm in the light causing random noise to be occasionally interpreted as a command.*, or (2) a neighbor with the same product or a product with a similar protocol, in which case you could possibly use the DIP switch trick @residualimages speaks of.
(*) Many of these protocols use 24-bit packets (16 address bits, 8 command bits) without any checksum. Some receivers have automatic gain correction turned up so high that in the absence of any signal, random noise at ~4 kbps is constantly impinging on the decoder. Although any single random packet has only a 1 in 16 million chance of decoding as “turn light X on” (exact match for 24 bits), at 4 kbps its possible that 4 thousand random packets are decoded every second, so we expect a successful (spurious) decode every few hours.
I think what happened is, our customer service agent (and I) looked for approximately the time you said there was an unexpected action and we indeed found an action from Google Home, but that’s because you used Google Home to attempt to shut off the light after it spontaneously turned on.
This was information I took from our customer service portal. Unfortunately the actions history information is not available directly to end users. We did experiment with such a feature, but the monthly database costs skyrocketed and was not sustainable for a pay-once-use-forever product like Bond Bridge, so we had to pull it. — Perhaps a more efficient or more limited implementation could work, but it is not currently on roadmap.
Can you send me the information from the portal for my device from two nights ago? I disconnected the device from Alexa, and it wasn’t on this morning. So, if indeed it’s not on tomorrow I’ll start digging into Alexa more. I’ve reviewed all my routines, but maybe there’s something hidden there.
I’d really like to get this info, as I do think it’s Alexa. I disconnected the device from Alexa and it hasn’t come on since. But I’ve looked at all my visible routines and nothing fires at 1:00 AM. Having this info would help me troubleshoot it.
