Northern Man

When investigating and resolving some homebridge backup and restore issues, we found that some users plugins were creating unusually large files, and we changed the backup process to ignore any...

I think your issue is documented here - https://www.rflink.nl/wires.php That receiver is effectively garbage. One option, is the openMQTTGateway implementation of RF, and a decent receiver

This is feasible using a CC1101 transceiver module, and is part of the openMqttGateway firmware package. OpenMqttGateway leverages rc-switch

With a CC1101 device, you can only listen/receive to one frequency at a time, but can transmit to a different one. And can listen with one protocol and transmit with...

This was likely a CC1101 connected to an ESP32 

Personally I find the range of those transceivers is pretty limited, typically a few feet or so. If you can work thru the range issue, they do work.

@trickert76 With homebridge-apt-pkg, we are sandboxing our own implementation of NodeJS outside of the OS. So that any changes with other packages do not interfere or break people's existing homebridge...

The ability to use the library with any hap-nodejs implementation is a feature and not an issue. I use it with my HomeKit-bridged devices, to expose them to Alexa. For...

@lilyball I was recently working thru removing the dependency on the request package ( long since deprecated ) and replacing it with Axios and making a couple of other improvements,...

What I found during testing was that **this** was undefined 100% of the time when homebridge-alexa invoked the functions. I did go thru various versions of the bind position, but...