Syncthing reports itself as seen "488384 hours ago"

cloonix · September 18, 2025, 8:36am

I’m writing a python script to monitor my sync status of my main syncthing (version 2.0.9) host via the API. I got warnings for the host itself:

”Device ‘bart’ has issues: Last seen 488384 hours ago”.

I checked the data on the API endpoint:

Device: bart
   Raw stats: {
      "lastSeen": "1970-01-01T00:00:00Z",
      "lastConnectionDurationS": 0
}

I tried the API call on a different device with the same output:

Device: nas
   Raw stats: {
      "lastSeen": "1970-01-01T00:00:00Z",
      "lastConnectionDurationS": 0
}

On the WebUI i can’t see any problems.

Also my API endpoints has a folder which was never synced but shows perfectly fine on the WebUI. I don’t know whether this is related to the device issue above?

   Raw stats: {
      "lastFile": {
            "at": "0001-01-01T00:00:00Z",
            "filename": "",
            "deleted": false
      },
      "lastScan": "2025-09-18T08:15:34Z"
}

This folder is also reported on every device on my syncthing network.

Has anyone an idea where i can’t start to troubleshoot that issue?

tomasz86 · September 18, 2025, 8:55am

Somewhat related:

github.com/syncthing/syncthing

Remove the "self" device as it's confusing and serves very little purpose

opened 04:18PM - 12 Feb 21 UTC

tomasz1986

enhancement

1. Use the "Pause All" button to pause all devices. 2. All devices in `config.x…ml`, including the own one, which normally has no option to be paused, have been changed to `<paused>true</paused>`. 3. Resume devices one by one by unpausing each of them separately. 4. The own device stays `<paused>true</paused>`. 5. The only way to get it back to `<paused>false</paused>` is to use the "Resume All" button (or modify the config file). I would say that the "Pause All" button should not affect the own device at all, simply because as far as I understand, it does not even have the capability to be paused. This issue does not seem to affect Syncthing itself, as synchronisation still works, but it does affect 3rd party wrappers like Syncthing Tray (see https://forum.syncthing.net/t/yet-another-syncthing-tray/8502/102). I am not sure if this is possible, but is there any reason to have the `<paused>` element under the own device at all? If not, maybe it could be possible to simply remove it, as it is only relevant for remote devices anyway. Tested with Syncthing v1.13.1.

cloonix · September 21, 2025, 2:21pm

“NAS” is the device itself.

Since I have encountered several warnings related to the API, I’m curious about its current status. The WebUI indicates that everything is functioning properly, but the API is generating numerous warnings about devices that were “last seen” thousand years ago and about perfectly synced folders that are currently unsynced (according to the API status).

calmh · September 21, 2025, 6:08pm

The gui exclusively presents the data returned by the api. You will get empty date fields etc for devices never seen, folders currently paused, etc.

system · October 21, 2025, 6:08pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.