Open noofny opened 2 years ago
From looking at https://github.com/Makuna/NeoPixelBus/wiki/NeoPixelBus-object-API it appears that clock_pin is only valid for DotStar . But I may have missed something since I don't understand the API completely
Thank you @martgras - yes that's right, I was using clock_pin
& data_pin
to try get a DotStar working. I have a NeoPixel and a DotStar device, both are mini-LED-matrix Feather boards (Adafruit). The NeoPixel works flawlessly so I got excited and was trying to get the DotStar going. Maybe I'm trying to do something that isn't possible? Apologies for my ignorance.
This is the NeoPixel board that works fine... https://www.adafruit.com/product/2945
This is the DotStar board that I was trying to get working... https://www.adafruit.com/product/3449
I hope that is helpful.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The problem
I can successfully use this component when using a single-pin configuration, by defining value for
pin
. When I try using a 2-pin configuration by defining values fordata_pin
andclock_pin
the core compilation fails with the following error...I have tried different different permutations of values for
type
andmethod
but the same compilation error occurs.Which version of ESPHome has the issue?
2021.9.1
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
core-2021.9.6
What platform are you using?
ESP32
Board
Adafruit Feather 32
Component causing the issue
NeoPixelBus Light
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response