Guys, thanks for all the comments here. We’re bumping priority on this to investigate for next maintenance release. @borski can you confirm that you meant to write v2.14.5-beta, rather than “v2.4.15”? (v2.4.15 was indeed released, but back in Feb 2019.)
1 Like
Yup, I meant 2.14.5-beta.
I am still seeing this in my house. I think its the fan retro kits that are doing it.
I too have this problem with one of my fan kits. The only option is for me to pull the breaker as you can restart the device from the app. I’m on firmware v2.15
-Dan
I’m still seeing this in my house also
1 Like
I see it also with 2.15
1 Like
@merck, until this gets fixed can we add in the app to restart a fan controller? Pulling the breaker isn’t a good option to stop the hotspot.
Hmm that could work, and potentially be useful in some circumstances.
But actually, we’re in Q/A right now on v2.17.x firmware, which fixes this issue. Trying to get it out to y’all asap.
2 Likes
Would it also be possible to change the channel that the Bond Bridge AP defaults to? That way, even if the WiFi network does pop up, it will cause less interference.
Currently, the Bond Bridge defaults to WiFi channel 1+6 (40MHz mode), which causes an incredible amount of interference across more than 2/3rds 2.4 GHz spectrum. This also has a tendency to knock out nearby Zigbee devices, because Zigbee channel 11 (which is the default for most Zigbee devices) overlaps with WiFi channel 1.
I would highly recommend using WiFi channel 6 (20Mhz mode) or 11 (20MHz mode) instead. There’s no need to broadcast across 40MHz just for configuration purposes, and no need to default to a channel that has a high likelihood of interfering with Zigbee devices.
Edit: The Bond Bridge may actually be in violation of the IEEE 802.11-2012 specification by defaulting to 40MHz operation.
Thanks for the note. We’re using vendor defaults for the access point configuration. Strange that the setting is so suboptimal. I’ve added a backlog item for us to tweak the channel configuration as you’ve suggested. Currently targeting v2.18 beta release for early April.
Only if you connect to the AP and then transfer data. The Bond’s once-per-second beacon announcing the SSID shouldn’t cause much interference at all.
Actually, @Leapo , please let us know the first digit of the serial number of your unit. If you’ve got a “snowbird” (A/B) there’s very little we can do since it has an undocumented binary wifi driver (
). But for “zermatt” and “smart by bond” fans (Z/K) we have nearly full-control because we build most of the Wi-Fi stack from source.
Only if you connect to the AP and then transfer data. The Bond’s once-per-second beacon announcing the SSID shouldn’t cause much interference at all.
Unfortunately, that does not appear to be the case. I have a Hue Hub (Zigbee) on the same shelf as the Bond Bridge, and as soon as the Bond enables its AP, all of the Hue bulbs start flapping between “Online” and “Unreachable” in the Hue app. While this is occurring, bulbs often fail to respond to commands.
As soon as the Bond Bridge stops broadcasting its AP, all Zigbee devices begin behaving normally again.
I will note that many WiFi chipsets will generate broad-spectrum noise, increasing the overall noise floor of the surrounding area, even when not actively transmitting data (Think of it like the hiss you hear when you turn up amplified speakers). This is especially true if the WiFi chipset’s transmit power is turned up too high (and a lack of cooling can exacerbate the issue).
So, in addition to switching to Channel 6 or 11, and switching to 20MHz mode, it might also be a good idea to dial down the transmit power to the minimum required for setup from a reasonable distance.
please let us know the first digit of the serial number of your unit. If you’ve got a “snowbird” (A/B) there’s very little we can do since it has an undocumented binary wifi driver (
). But for “zermatt” and “smart by bond” fans (Z/K) we have nearly full-control because we build most of the Wi-Fi stack from source.
The first digit of my Bond’s serial number is a “Z”, so it looks like I’m good there! 
I’m seeing KNKSADE42149 and KNKSADE41945 both broadcasting the WIFI config after an extended internet outage yesterday. They didn’t reconnect automatically. These are the only two with older firmware that don’t have an update available yet so I assume the reconnect logic has already been fixed but isn’t available yet for these models.
cc @merck
You’re right, it’s not released yet to production.
However, you could use the beta firmware. Right now that requires installing the beta app. However, in next app update (v2.32.0), we will have a Firmware Channel feature where you can select BETA firmware even from the production app.
2 Likes
Thanks. I updated to the beta firmware 2.18.8 from 2.15 successfully. The first attempt failed, but the second one went though. I think that was due to another bug that was fixed in the upgrade process that I just got unlikely and hit during the upgrade.
1 Like
Great. Do let me know if you see that AP pop up again. It should ONLY appear if you lose internet for more than 1 min. (And, it will require a PIN to be entered before allowing setup, to secure it.) EDIT: And it disappears 30 sec after internet comes back.
1 Like
Will do if it happens again 
1 Like
UPDATE: We have a beta firmware v2.29.0-beta for ZZ, ZP, KNKSA, and KSM units (almost everything). This fixes a problem that many users where experiencing where the connection would be unstable and the AP SSID would broadcast continuously. We never did reproduce it at our desks, but we managed to work remotely with a few customers with the issue and confirmed the fix in alpha that way. So I’m fairly confident this will fix this issue.
1 Like
In case it helps, this just happened again after an internet outage.
I had quite a few devices from various vendors end up with a link local address 169.254.0.0/16 and needed a physical reboot to get them back on the network.
I’ll upgrade to 2.29.0 for the next time this happens
I’ve updated to of the “Home Depot” generic ones to v2.29.0. Both of them are online and controllable in the app and via Home Assistant on the LAN. Unfortunately they are also broadcasting the WiFi AP
I’ve also updated 4 of my progress lighting fans to v2.22.4 since v2.29.0 wasn’t available for these models. Two of them are now showing offline and not broadcasting WiFi either even after a power cycle.