even after connecting my Bond device to my home wi-fi network I continue to see the Bond device Wi-Fi access point being being advertised, why is this?
If the device is connected to a wi-fi network this should turn off. All it’s doing is providing unnecessary noise on the already crowded 2.4GHz airwaves.
Apparently you can’t even change the channel it uses either?
It’s probably not connected to our backend. (MQTT broker, specifically) Presumably it doesn’t work when you’re not on your home network? Or maybe you’re using another device locally that in turn controls the bridge?
If you intend for it not to be connected to our backend, you’re not alone, and we have an “offline” mode in the backlog. This’d just be a flag that suppresses two bad behaviors when not connected to our backend: rebroadcast of the config AP, and reboot after a timeout.
If it is connected to our backend, then that’s a bug. Could be that the Bond doesn’t realize it’s connected. Basically if it’s connected, the AP should be hidden.
It’s configurable but we haven’t documented it, assuming lack of user interest. The intent is to only broadcast on setup.
I have a couple SBB Minka fans that are doing this and I’m trying to determine how to tell through the app whether the fans are talking to the MQTT broker(s) or not. I also would like to see if there is a way without resetting a breaker to initiate a test. I can control them both through my app while on my LAN, but not if I am on cellular. When I look at my DNS logs, I only see NTP requests from the two fan IPs and nothing else.
I was trying to see if there a tool built-in on the device, but I cannot figure out how to find the PIN for these devices. The page says press the “learn” button for 5 seconds to unlock it too, but I can’t find any documentation that specifies which button may be the learn button.