https://github.com/boneskull/particle-neopixel
Color cycle a NeoPixel (WS2812B) strip w/ Particle Argon/Xenon/Boron
https://github.com/boneskull/particle-neopixel
argon boron led mesh neopixel particle rgb ws2812b xenon
Last synced: 6 months ago
JSON representation
Color cycle a NeoPixel (WS2812B) strip w/ Particle Argon/Xenon/Boron
- Host: GitHub
- URL: https://github.com/boneskull/particle-neopixel
- Owner: boneskull
- License: other
- Created: 2019-06-09T04:52:10.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2019-06-14T16:47:07.000Z (over 6 years ago)
- Last Synced: 2024-10-29T22:37:19.229Z (over 1 year ago)
- Topics: argon, boron, led, mesh, neopixel, particle, rgb, ws2812b, xenon
- Language: C++
- Homepage:
- Size: 5.86 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# particle-neopixel
> Color cycle a NeoPixel (WS2812B) strip w/ Particle Argon/Xenon/Boron
There are many like it, but this one is mine.
## Particle Cloud Functions
- `enable()` - Turns the NeoPixel strip "on"
- `disable()` - Turns the NeoPixel strip "off"
- `setBrightness(short)` - Set brightness from 1-100, inclusive
- `setDelay(short)` - Set update delay in ms
> Note: Particle Cloud Functions only accept a single `String` value; any args are converted/coerced into the proper data type.
## Particle Cloud Variables
- `settings` - `{String}`: All settings in a JSON object. Properties:
- `enabled` - `{bool}` (default `true`): Whether or not the strip is currently enabled
- `delay` - `{short}` (default `20`): Current delay setting
- `brightness` - `{short}` (default `50`): Current brightness setting
## Notes
- Settings are persisted in EEPROM. Should I be doing this? I have no idea.
- `setBrightness(0)` just invokes `disable()`. It does not save `0` as the `brightness` setting.
- Very obviously adapted from Adafruit's "rainbow" example.
## License
Copyright © 2019 Christopher Hiller. Licensed Apache-2.0