- versionBranch was renamed to watchedVersionBranch (including all variables and strings. even config)
- Enhancements for JSON Editor. Detection of advanced was not so good. Now you can see advaced if advanced or expert is selected. expert is the highest and should also make advanced visible.
- The levels default, advanced, expert are now also respected in the information tabs. Same logic as for the forms itself. Expert is highest and will also show all advanced settings.
- Build problems:
- Qt 5.13 obsoleted some calls that were used in our Qt library.
- The PhilipsHueLight and PhilipsHueBridge classes did not use the private logger class
- Undo changes:
- In Commit e6c2e7e, I made changes that were not covered. An apology goes to @b1rdhous3
Signed-off-by: Paulchen-Panther <Paulchen-Panter@protonmail.com>
- added native RPi docker image instruction to CompileHowto.md
- version channel is received from JsonAPI instead of reading from the configuration file
Signed-off-by: Paulchen-Panther <Paulchen-Panter@protonmail.com>
Now the last stable will be used when the latest stable version have a higher version number than the last beta version. This only triggers when Beta Branch is used. If the user chooses Stable only stable versions will be considered.
Update Check:
- New Property which allows you to select stable or beta branch checks.
- This would rely on current versions.json. It selects the first version in list with you branch (stable, beta). If it is newer hyperion tells you that a update is available
- For this we should keep our deployment pipeline in mind to format the json this way.
Cleanup:
- I cleaned up the WebUI from dead links and the support page with the affiliate links and donation adresses as we don't have them under our control. Currently only disabled, not deleated
Switcher:
- If the address which is published via bonjour serve is IPv6 the Switcher was bugged. Fixed that.
OSX packaging is currently broken. CPack is now called individually so that the make process is no longer displayed incorrectly in Travis / Azure.
The variable PACKAGES in the build script is no longer overwritten, so in travis / Azure you can globally assign the variable and start a package build process manually.
Signed-off-by: Paulchen-Panther <Paulchen-Panter@protonmail.com>