You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compared to many other systems I know (e.g. HomeAssistant, OpenDTU, ESPHome, QNAP, Nextcloud) it's currently very difficult and tedious to find out about new firmware versions for the Charger and EM. Sure, there is a forum thread that one can frequently poll and the product pages also show the latest version. But this requires frequent and active initiative of the users.
I thus suggest, e.g. similar to OpenDTU, for the web interfaces of the Charger and the EM to offer a firmware check / update notification that informs users about new firmware versions. Ideally by also offering a button to directly download and install the latest version.
In parallel it would also be good to have the latest firmwares as "Releases" on GitHub - again, to make it easier to find them (where people would also expect them to be). The update notification / firmware check could directly get its information from there.
The text was updated successfully, but these errors were encountered:
andreas-bulling
changed the title
[FeatureRequest] Update notifications
[FeatureRequest] Firmware update notifications
Feb 15, 2024
Compared to many other systems I know (e.g. HomeAssistant, OpenDTU, ESPHome, QNAP, Nextcloud) it's currently very difficult and tedious to find out about new firmware versions for the Charger and EM. Sure, there is a forum thread that one can frequently poll and the product pages also show the latest version. But this requires frequent and active initiative of the users.
I thus suggest, e.g. similar to OpenDTU, for the web interfaces of the Charger and the EM to offer a firmware check / update notification that informs users about new firmware versions. Ideally by also offering a button to directly download and install the latest version.
In parallel it would also be good to have the latest firmwares as "Releases" on GitHub - again, to make it easier to find them (where people would also expect them to be). The update notification / firmware check could directly get its information from there.
The text was updated successfully, but these errors were encountered: