Hi @GodmanchesterGoblin ,
Update files can be applied manually by using the /recovery.html tool on a Pixelblaze, or if that is missing it can be uploaded via the /update built-in page.
That is, if your pixelblaze was usually accessible at http://192.168.1.123, then you would add one of the above paths, e.g. http://192.168.1.123/recovery.html
The recovery tool is nicer because you can see your update progress even for manual files. For the /update page you just have to wait a few minutes without knowing whats going on.
Risks
There may be bugs in this version, probably relatively minor ones, but they might cause some patterns or features to not work.
You can revert to the released version by using the built-in firmware update tool on the settings tab, or by using the ‘/recovery.html’ tool.
It is unlikely to completely brick your PB.
The most common issue happens if there is a problem updating the main web app file, usually when the system is low on storage. 500-600K seems like a safe bet. Less than 300k seems to frequently cause issues. If this happens, the recovery tool can still be used to attempt to repair or revert to the release version.
There is a different update file for each kind of PB v3. One for Standard with the pb32 in it’s name, and one for the Pico with pico32 in the name. Uploading the wrong file won’t cause anything bad to happen, it just won’t update.