Synchronization Speed

Slow down the sync check firing interval so the plugin puts less strain on older routers and devices.

Overview

By default, the plugin fires every second to assess whether sync check signals or keep-alive signals should be dispatched. This keeps device states in the Home app as fresh as possible.

That pace is not always ideal. On some consumer routers the constant polling can cause a network slowdown, and on older devices that are incompatible with newer OpenSSL versions (v3.1), it can result in sustained 100% CPU usage.

The speed value adjusts the firing interval to address both issues. Lowering it trades faster updates for lighter load.

Speed Values

The speed field is a number that maps to one of four preset intervals. The default is 1.

Value	Label	Description
`1`	Normal	Fires every second. The default and fastest option.
`0.75`	Moderate	Slows the firing interval slightly to reduce load.
`0.5`	Slower	Slows the firing interval further for more constrained setups.
`0.25`	Slowest	The slowest option, for the most resource-limited routers or devices.

Lower values reduce network and CPU pressure but may result in slower device updates in the Home app.

Configuration

Set the speed field inside the platform block of your config.json. This example uses the slowest interval:

config.json

json

{
  "platforms": [
    {
      "platform": "ADTPulse",
      "name": "ADT Pulse",
      "speed": 0.25
    }
  ]
}

Startup Warning

If the plugin does not run at 1 (Normal) speed, a warning is issued on every startup. This warning cannot be disabled.

warning

Any speed value other than 1 triggers a startup warning that cannot be turned off. Only lower the speed if you are experiencing router slowdowns or high CPU usage.

When to Lower the Speed

The default speed is recommended for most setups. Consider a lower value only when you observe one of these symptoms:

Network slowdown — The router struggles under the plugin's constant polling.
Sustained 100% CPU — An older device incompatible with OpenSSL v3.1 stays pinned at full CPU usage.

The speed field sits alongside the other platform settings. See Operational Mode for pausing or resetting the plugin, and Advanced Options for disabling specific behaviors.