Closed jaroschek closed 4 months ago
Since I just tried your alpha release, let me put this here. It seems that I am notified that an update is available, but for my heat pump, there is actually no new firmware available.
For CTC (which are also using myUplink) the firmware releases are here: https://software.ctc.se/ Not sure where you are getting the input from, but it would obviously be great to get notified also for CTC firmware updates =)
Thanks for feedback to this feature. As I can see from your screenshot, there is no latest version
available from the API.
I'm using the api endpoint /v2/devices/{deviceId}/firmware-info
to check for available firmware updates. So there is no manufacturer specific solution.
This endpoint should at least provide information about the current installed firmware and the latest available firmware. But it seems, these value can also be empty as in your case. So I will fix the comparison of firmware strings to exclude empty values.
The version 1.2.0 is currently planned to provide the following new features:
There is one thing to mention, that I'm still not quite sure, if these features would be worth.
In issue https://github.com/jaroschek/home-assistant-myuplink/issues/15 we observed, that the API would timeout from time to time. The solution to this problem was to reduce the number of requests to the API.
The new features for version 1.2.0 do now require additional requests:
connection_state
for each device will require one additional request for each configured integration entry.As the update coordinator is currently configured to poll every 60s this could cause problems with the request limitations of the API (see https://dev.myuplink.com/intro
Rate Limiting and Client Abuse
):(The API implementation already contains throttling, to only allow 1 request every 5s. This leads to a limit of 12 requests every 60s.)
But there could be a simple solution: As observed with my integration, the values/states of the parameters points are only updated every 5 minutes. But the integration is polling the API every minute (60s). As this seems unnecessary frequent, the polling interval could be increased to 300s (5 minutes).