HomeSpan

I think you've identified a bug in the new release (likely a result of all the refactoring). I can see by the QR code it generates that something is incorrect....

I have identified the problem and will fix in the next release (was an inadvertent error introduced in 1.9.0). However, there is an easy workaround: * If you are using...

This has now been fixed -- `homeSpan.setPairingCode()` works as before with two slight changes to behavior: 1. the method now operates silently if a valid pairing code is provided (i.e....

These changes have now been released into production as version 1.9.1.

Sorry, HomeSpan only directly supports double-clicking. However, you could create some custom logic/code that tracked the double-clicks and then waited for a short period to act until it sees if...

Let's start with a direct test of the Pixel code using the following script (change the PIN number accordingly): ```C++ #include "HomeSpan.h" #define PIXEL_PIN 33 // set this to whatever...

If it's blinking correctly but the colors do not match this may be a result of how the driver chip is connected to specific LEDs within the strip. I suppose...

The fact that it works with 140 pixels is very good news - suggests that everything is working fine, with the exception of the color mapping. I pulled the specs...

I added a new method to Pixel called `setColorMap(uint8_t *map)`. It allows you to set the order in which the color bytes are transmitted. Six color maps are pre-defined in...

In the Pixel example you would enter it below the following line: ```C++ pixel=new Pixel(pin); // creates Pixel LED on specified pin