What is the update interval? (seems pretty slow) #41
|
I've managed to integrate the integration and it is grabbing infos... but it seems bretty slow that the infos are updated. |
Replies: 1 comment 3 replies
|
The update interval is set here, which is pretty much HA standard which is used in most other integrations, too. For some specific items (CPU, RAM, LAN Usage, Temperatures, Fan speeds) we might do some extra programming in the future, but this will require an extra update coordinator, and we will need to take some extra care to not 'overload' the system with this - see my notes on 'polling frequency' here. /tom |
|
Ah perfect, thnak you. I searched the repo with some keywords but not "polling". Sorry for the duplicating now. |
|
no worries, all good :) |
|
Update: As of 2025.08.1, there is a second update coordinator, polling quickly changing status entities more frequently (every 5 s). To reduce CPU/RAM load, and to not let the NAS reach out to UGreen so often (1), slowly changing entities (like name, serial etc) are still polled every 60s. /tom (1) p.s. / comment on the above: It seems some of the API calls are triggering the NAS to update UGreen servers on its status, see here. If contacting the wrong endpoints too often, this can lead to flooding both your DNS/Internet connection as well as UGreen's servers. |
The update interval is set here, which is pretty much HA standard which is used in most other integrations, too.
For some specific items (CPU, RAM, LAN Usage, Temperatures, Fan speeds) we might do some extra programming in the future, but this will require an extra update coordinator, and we will need to take some extra care to not 'overload' the system with this - see my notes on 'polling frequency' here.
/tom