mirror of
https://github.com/esphome/esphome.git
synced 2024-12-22 05:24:53 +01:00
3fcdaaefe0
* fix: FastLED SPI_DATA_RATE being truncated to 8 bits
FastLED expects SPI_DATA_RATE as an uint32_t, but we had it as uint8_t.
Fix that to avoid the data rate being truncated.
* fastled: allow specifying data rate
Previously, we've just taken the default data rate from FastLED.
However, that does not always work properly. In my case, I had a
slow level shifter that couldn't keep up with the 1 MHz data
rate default for WS2801. Long cabling might also be a reason why
one might want to reduce the data rate.
This will add a new optional "data_rate" config option where one
may specify the desired data rate as a frequency:
light:
- platform: fastled_spi
chipset: WS2801
data_pin: GPIO23
clock_pin: GPIO22
data_rate: 500kHz
num_leds: 178
|
||
|---|---|---|
| .. | ||
| component_tests | ||
| test_packages | ||
| unit_tests | ||
| .gitignore | ||
| custom.h | ||
| livingroom32.cpp | ||
| livingroom8266.cpp | ||
| README.md | ||
| test1.yaml | ||
| test2.yaml | ||
| test3.yaml | ||
| test4.yaml | ||
Tests for ESPHome
This directory contains some tests for ESPHome.
At the moment, all the tests only work by simply executing
esphome over some YAML files that are made to test
whether the yaml gets converted to the proper C++ code.
Of course this is all just very high-level and things like unit tests would be much better. So if you have time and know how to set up a unit testing framework for python, please do give it a try.
When adding entries in test_.yaml files we usually need only
one file updated, unless conflicting code is generated for
different configurations, e.g. wifi and ethernet cannot
be tested on the same device.
Current test_.yaml file contents.
| Test name | Platform | Network |
|---|---|---|
| test1.yaml | ESP32 | wifi |
| test2.yaml | ESP32 | ethernet |
| test3.yaml | ESP8266 | wifi |
| test4.yaml | ESP32 | ethernet |