Releases: phodgers/roosterwake
Release list
Rooster Wake firmware 2.6.1
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.6.1-pico2_w.uf2 |
roosterwake-2.6.1-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.6.1-pico_w.uf2 |
roosterwake-2.6.1-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.6.1.sha256.
Flash used: 522368 bytes on the Pico 2 W of
720,896 available per slot; 538716 on the Pico W.
Changes
- net: power save off - inbound delivery must not depend on the AP's buffering (fw 2.6.1)
- PROTOCOL + README: the ready capability, and honesty about the beacon
- PROTOCOL: the session capability - workspaces, session_start/stop
- PROTOCOL: the awake capability - hold_awake/release_awake/awake_result
Rooster Wake firmware 2.6.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.6.0-pico2_w.uf2 |
roosterwake-2.6.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.6.0-pico_w.uf2 |
roosterwake-2.6.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.6.0.sha256.
Flash used: 522368 bytes on the Pico 2 W of
720,896 available per slot; 538716 on the Pico W.
Changes
- plug: presence sigint on unreachable + the status read's rssi (fw 2.6.0)
- docs: firmware stays current on its own - the hosted relay's auto-update, stated where setup ends
Rooster Wake firmware 2.5.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.5.0-pico2_w.uf2 |
roosterwake-2.5.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.5.0-pico_w.uf2 |
roosterwake-2.5.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.5.0.sha256.
Flash used: 521584 bytes on the Pico 2 W of
720,896 available per slot; 537812 on the Pico W.
Changes
- plug: the plugfw verbs - firmware standing and vendor updates (fw 2.5.0)
- PROTOCOL: the plugfw capability - firmware standing and vendor updates for power switches
Rooster Wake firmware 2.4.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.4.0-pico2_w.uf2 |
roosterwake-2.4.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.4.0-pico_w.uf2 |
roosterwake-2.4.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.4.0.sha256.
Flash used: 518792 bytes on the Pico 2 W of
720,896 available per slot; 534868 on the Pico W.
Changes
- @ Firmware 2.4.0
- net: an association is not a network - rejoin when the address goes
- plug: Shelly power-switch driver + PROTOCOL plug frames
- PROTOCOL: the bye frame - deliberate silence, announced
Rooster Wake firmware 2.3.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.3.0-pico2_w.uf2 |
roosterwake-2.3.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.3.0-pico_w.uf2 |
roosterwake-2.3.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.3.0.sha256.
Flash used: 509128 bytes on the Pico 2 W of
720,896 available per slot; 524812 on the Pico W.
Changes
- Firmware 2.3.0
- A device that cannot reach the relay now recovers, and says why
- PROTOCOL: the rdp capability and the frame pair it gates
- docs: /v1/me and the entitled flag
- docs: DOWNLOADS.md -- the direct-download reference
- PROTOCOL: the adopt frame's token extension, documented
- docs: the audit export -- row schema, CSV columns, paging, retention
- docs: the hosted REST API, now that clients beyond ours speak it
- README: voice is free, and the agent exists
- PROTOCOL.md: the other half of the power button
Rooster Wake firmware 2.2.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.2.0-pico2_w.uf2 |
roosterwake-2.2.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.2.0-pico_w.uf2 |
roosterwake-2.2.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.2.0.sha256.
Flash used: 507656 bytes on the Pico 2 W of
720,896 available per slot; 523356 on the Pico W.
Changes
- mDNS names are UTF-8: reject deception, not scripts
- Name Macs, Linux boxes and phones in the LAN scan via mDNS
Rooster Wake firmware 2.1.1
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.1.1-pico2_w.uf2 |
roosterwake-2.1.1-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.1.1-pico_w.uf2 |
roosterwake-2.1.1-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.1.1.sha256.
Flash used: 506256 bytes on the Pico 2 W of
720,896 available per slot; 521892 on the Pico W.
Changes
- v2.1.1: first release signed by the production key
Rooster Wake firmware 2.1.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.1.0-pico2_w.uf2 |
roosterwake-2.1.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.1.0-pico_w.uf2 |
roosterwake-2.1.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.1.0.sha256.
Flash used: 506256 bytes on the Pico 2 W of
720,896 available per slot; 521892 on the Pico W.
Changes
- Rotate to the production firmware signing key
- The open path stops calling itself Remote Wake
Rooster Wake firmware 2.0.0
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-2.0.0-pico2_w.uf2 |
roosterwake-2.0.0-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-2.0.0-pico_w.uf2 |
roosterwake-2.0.0-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-2.0.0.sha256.
Flash used: 506256 bytes on the Pico 2 W of
720,896 available per slot; 521892 on the Pico W.
Changes
- Protocol v2: the device stops holding a list of machines
- The case is test-printed and fits
Rooster Wake firmware 1.11.1
Install
You do not need a toolchain. Pick whichever suits you:
- Browser — open https://setup.roosterwake.com, plug the dongle in, and
follow the steps. It writes both files for you. Chromium-based browsers only
(Web Serial and WebUSB). - Drag and drop — hold BOOTSEL while plugging the board in, then copy
loaderonto the drive that appears. The board restarts, finds no
firmware and comes back as a drive by itself; copy-installonto it. - Already flashed — kits ship ready to go; just plug it in.
Copy them one at a time. A single file spanning both regions loses whichever
region's blocks arrive last, in either order, and leaves one of them erased.
| Board | Loader | Firmware |
|---|---|---|
| Pico 2 W (RP2350) — the product | loader-1.11.1-pico2_w.uf2 |
roosterwake-1.11.1-pico2_w-install.uf2 |
| Pico W (RP2040) | loader-1.11.1-pico_w.uf2 |
roosterwake-1.11.1-pico_w-install.uf2 |
The two boards are not interchangeable. RP2040 firmware on an RP2350 does not boot.
Configuration in flash survives a firmware update, so a device reflashed this
way comes back already provisioned.
Updating over the air
The .rwfw files are signed firmware images. They are not flashed by hand —
the relay streams one to a device over its existing connection, and the device
checks the signature against a key compiled into the image already running. Each
release carries one per slot because firmware executes in place and is linked at
the address of the slot it occupies; a device is offered the one built for the
slot it is not running from.
A device that updates gets three boots to reach the relay. If it cannot, the
loader returns to the previous image on its own.
Verify downloads against roosterwake-1.11.1.sha256.
Flash used: 510408 bytes on the Pico 2 W of
720,896 available per slot; 526212 on the Pico W.
Changes
- chore(release): 1.11.1
- Watch for the factory-reset button across a window, not at one instant