Time constants

Available during initial setup of the integration as well as via Configure option

Options

Option	Type	Default	Description
Caching time	`integer`	`5`	Time to cache data from the API endpoints Units:`seconds`
Devices / AiMesh update	`integer`	`30`	Time interval for devices and nodes monitoring. This value is used for both `device_tracker` entities, as well as `connected devices` sensor and `aimesh` sensors Units:`seconds`
Consider home	`integer`	`45`	Time to consider device connected after the last `home` state. Units: `seconds` Refer to the section Consider home
Firmware data	`integer`	`21600`	Interval to update the `update` entity Units: `seconds` Default value is equal `6 hours`
Entities update	`integer`	`30`	Interval to update all the other entities Units: `seconds` Available if `Operation mode / Enable per-sensor update intervals` is set to `False`
{Type} data	`integer`	`30`	Interval to update data fom a single {type} Units: `seconds` Available if `Operation mode / Enable per-sensor update intervals` is set to `True` Refer to the section Entities update

This value controls how fast does device tracker change state to not home after the last home state was recorder.

consider home <= device tracker update, device tracker will get not home state as soon as device state is checked and it is not connected.
consider home > device tracker update, not home state will be assigned only after device is offline for longer than consider home.

Currently AsusRouter supports the following data types, which are polled separately:

Each of these types support setting polling interval.