Time constants
Less than 1 minute
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 sensorsUnits: seconds |
| Consider home | integer | 45 | Time to consider device connected after the last home state.Units: secondsRefer to the section Consider home |
| Firmware data | integer | 21600 | Interval to update the update entityUnits: secondsDefault value is equal 6 hours |
| Entities update | integer | 30 | Interval to update all the other entities Units: secondsAvailable 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: secondsAvailable if Operation mode / Enable per-sensor update intervals is set to TrueRefer to the section Entities update |
Consider home
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 getnot homestate as soon as device state is checked and it is not connected.consider home > device tracker update,not homestate will be assigned only after device is offline for longer thanconsider home.
Entities update
Currently AsusRouter supports the following data types, which are polled separately:
- CPU
- Firmware
- Guest WLAN
- Light
- Misc
- Network stat
- Parental control
- Ports
- RAM
- Sysinfo
- Temperature
- VPN
- WAN
- WLAN
Each of these types support setting polling interval.