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.