-
Notifications
You must be signed in to change notification settings - Fork 3
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
Show update notifications on the display #4
Comments
This could make use of #5 but it might also make more sense to implement it in some other way. |
I realized that devices might be running in the field for years before the user updates them, if they ever update at all. Especially because updating with the webinstaller requires filling the configuration (lnbits API key) again, which might be a challenge. So the update indication should be small and subtle, rather than big and annoying. |
This is done. From the commit message:
|
This is ready and deployed in v2.0.0 in the webinstaller. |
Currently, the device checks for the availability of updates and outputs the result on the serial port. But it doesn't show any update notification on the display, so most users won't be made aware of them.
This can be improved by showing a notification (like: "UPDATE ") somewhere on the display to indicate to the user that there's an update.
Some considerations:
Optionally, we could create a whole new "Update screen" that shows "Update is available at ." and also displays a QR code of that URL, if that makes sense. To make this work, we need a good and long-term static URL as a landing page for the updates, ideally a webpage that describes how to do the update using the web installer. This could be the web installer itself (currently https://lightningpiggy.github.io) but that URL is not under our control (github might break it in the long term) so perhaps something like https://update.lightningpiggy.com/ would be better, even if that one redirects to https://lightningpiggy.github.io for now.
The text was updated successfully, but these errors were encountered: