@merck Hm, it seems like the watchdog isn’t getting disabled automatically on my bridge. I had manually turned off the watchdog via API and just re-enabled it. 10 minutes later, my uptime_s from sys/version dropped back to 0. This also seems to have triggered the Bond Config AP to start broadcasting again.
Rebooting the bridge gets it back into the expected state, but soon after startup, the watchdog does its thing and Bond Config is back! Disabling watchdog and rebooting again keeps Bond Config turned off.
Let me know if you need any more information to help troubleshoot this.
Thanks, fixed on our API docs.
It was previously mentioned that the docs also have the endpoint for the watchdog endpoint incorrect, as it’s actually /v2/sys/wifi/watchdog, not sys/watchdog. Could this be fixed as well?