Skip to content

fix: give the Dot its own busy program - #7

Merged
benkelly merged 1 commit into
mainfrom
dot-busy-program
Nov 19, 2026
Merged

benkelly merged 1 commit into
mainfrom
dot-busy-program

Conversation

@benkelly

Copy link
Copy Markdown
Owner

Summary

In direct mode, the busy program rolls a four-LED comet along the strip. The SidePulse Pro has eight LEDs, so the comet moves smoothly. The SidePulse Dot has two LEDs. It shows only a slice of the comet, and each LED is dark for most of the cycle, so the LEDs look like they flicker.

This change adds a two-LED busy program for the Dot. Both LEDs pulse cyan, and the second LED starts 260 ms after the first. Upstream SidePulse uses the same pattern in cyan-roll-2.LED.

off
0:#00ccff 760ms pulse 0ms; 1:#00ccff 760ms pulse 260ms
repeat

The plugin selects the program from the volume name. A volume whose name starts with PulseDot gets the Dot program. Every other device gets the comet. The idle, waiting, error, and done programs do not use LED positions, so they do not change.

The brightness option applies to the Dot program too. The self-check in plugin.mjs makes sure that the Dot program stays within the controller limits. The version changes to 0.4.1, so the merge publishes the release.

Test

Run these commands from the repository root, on the dot-busy-program branch:

npm test
node test/run.mjs Dot

The first command shows 69 of 69 passed. The second command shows 2 of 2 passed.

To see the program on a real Dot, connect the Dot, stop the SidePulse service, and run:

node plugin.mjs --demo

The busy state shows two cyan pulses, one after the other, with no flicker.

The busy program rolls a four-LED comet along the strip. The Dot has
two LEDs, so it showed only a slice of the comet, and the LEDs looked
like they flickered.

On a PulseDot volume, the plugin now writes a two-LED program. Both
LEDs pulse cyan, the second one 260 ms after the first, like upstream
cyan-roll-2.LED. The other programs do not use LED positions, so they
stay the same on both devices.
Copilot AI balanced review requested due to automatic review settings November 19, 2026 04:18

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

@benkelly
benkelly merged commit 52b4d78 into main Nov 19, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants