feat: sds firmware update #3142
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Julusian
force-pushed
the
feat/sds-firmware-update
branch
from
57b9427 to
153a536
Compare
peternewman
reviewed
Nov 17, 2024
peternewman
reviewed
Nov 17, 2024
Co-authored-by: Peter Newman <peternewman@users.noreply.github.com>
… check for more streamdeck models
# Conflicts: # package.json # yarn.lock
|
For now this has no data being fed into the update checks so will never find anything. But once the api starts reporting some real values it will begin prompting for updates. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Inform users about available firmware updates for their connected stream deck studios
The notification number in the tabs bar is not something we do currently, but is important as some of the firmware updates are important so should be pushed hard on them.
In this first iteration, we are relying on an external proprietry tool by Bitfocus to perform the updates. In a later iteration, we can look into this being a command line tool that is invoked automatically.
This isn't differentiating between important and optional updates, that would add quite a lot of complexity and without public release notes for the firmware won't make much sense