Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] provide FW update available of add-on via MQTT #242

Open
thyzzv opened this issue Mar 17, 2024 · 2 comments
Open

[Feature] provide FW update available of add-on via MQTT #242

thyzzv opened this issue Mar 17, 2024 · 2 comments
Labels
feature request Request for change or new feature pinned Pinned

Comments

@thyzzv
Copy link

thyzzv commented Mar 17, 2024

Describe the feature
Would it be possible to provide the 'Firmware update available' of the add-on itself via MQTT?
That way we wouldn't have to login to the add-on itself to check for newer versions (or follow the GoT toic very precisely)

Expected behaviour
Provide an 'fw_update_available' boolean on the mqtt status topic for the add-on.
or a 'available firmware version' field

@thyzzv thyzzv changed the title [Feature] provide FW update available of addon via MQTT [Feature] provide FW update available of add-on via MQTT Mar 17, 2024
@arjenhiemstra
Copy link
Owner

certainly possible. The json file could be parsed from github lets say once a day. Only downside is that connecting to github requires https client support in the firmware which is quite costly firmware size (adds about 180kb).
Maybe some other solution is possible...

@arjenhiemstra arjenhiemstra added pinned Pinned feature request Request for change or new feature labels Mar 18, 2024
@thyzzv
Copy link
Author

thyzzv commented Mar 19, 2024

Ah I had not noticed that the firmware check is done locally in the browser. Not on the device
180kb is indeed a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for change or new feature pinned Pinned
Projects
None yet
Development

No branches or pull requests

2 participants