HomeSpan

HomeSpan version 1.6.0 (just released) now includes the ability to seamlessly add pushbuttons attached to a pin expander. Complete details can be found in the the latest version of [SpanButton()](https://github.com/HomeSpan/HomeSpan/blob/master/docs/Reference.md#spanbuttonint-pin-uint16_t-longtime-uint16_t-singletime-uint16_t-doubletime-boolean-triggertypeint)...

See #131 for a discussion of this issue and a few different solutions.

Yes, it will automatically reconnect if disconnected. It also reports this automatically to the weblog if used.

No plans to add Matter to HomeSpan at present. I assume the use case would be for HomeSpan to work with Google and other non-HomeKit ecosystems?

To certify requires an MFi license from Apple, and they need to test the device before certifying. I believe that means that those using the library would also need to...

Note that HomeSpan version 1.7.0 (released a few weeks ago) now includes an embedded ESP-NOW library with examples of how to create remote, battery-operated sensors.

By coincidence, @frankonski just posted a similar problem. See #781 for discussion and expected solution. Which specific Neopixel are you using?

Thanks for the link --- it seems the protocol for this chip is indeed reversed from the protocol I used in the Pixel library. Should be able to address shortly.

@honear, please see update in #781. Also, I think the device you have is RGBW, so make sure to set the second parameter of the Pixel constructor to "true" so...

Since everything seems to be working with the update in the dev branch I'll close this issue - please feel free to re-open if needed.