# Watchdog api endpoint and running locally

**URL:** <https://forum.bondhome.io/t/watchdog-api-endpoint-and-running-locally/2867>\
**Category:** BOND Setup and Hardware\
**Created:** [November 29, 2021, 5:43pm UTC](https://forum.bondhome.io/t/watchdog-api-endpoint-and-running-locally/2867 "2021-11-29T17:43:44Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![spercure](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.bondhome.io/spercure/32/817_2.png) [@spercure](https://forum.bondhome.io/u/spercure)\
**Post date:** [July 5, 2022, 1:24pm UTC](https://forum.bondhome.io/t/watchdog-api-endpoint-and-running-locally/2867/18 "2022-07-05T13:24:58Z")

</div>

@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](https://forum.bondhome.io/t/watchdog-api-endpoint-and-running-locally/2867/2) 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?

---

_[View the full topic](https://forum.bondhome.io/t/watchdog-api-endpoint-and-running-locally/2867)._