FAQ (Frequently Asked Questions)
Where does Reactor run?
Reactor can be run on any Linux or Windows system that supports nodejs. Reactor is distributed in a generic platform package for most Linux systems and Windows, and a Docker image for Synology NAS systems that support Docker. Support for QNAP is also planned (a lot of HA users have NAS systems that run full-time, so a NAS is really a good platform for this tool). Reactor runs great on a Raspberry Pi 4B with 2GB RAM (the base model), although the use of an SSD is recommended as Micro-SD cards aren't up to long-term use as storage for a Linux/Raspian system.
Can I install Reactor on my Hubitat hub?
No. Although Hubitat is a Linux system, it does not permit the installation of external packages (and with good reason -- if users could install anything, they would install everything, and that would create a huge support tangle for them).
Can I install Reactor on my Vera or eZLO hub?
No, for the same reasons you can't install it on a Hubitat system. These are embedded systems that don't permit the installation of external packages, and that's probably a good thing.
What hubs/controllers are currently supported?
Reactor currently supports Vera (UI7), Home Assistant, and Hubitat hubs, with planned support for OpenHAB. If the hub you are using is not yet on our support list and it offers a local API, please let us know/make a support request.
Why not just use Node-RED?
Node-RED is awesome, but like many tools, it's not for every user. Reactor and Node-RED perform similar functions but operate very differently and present very different views of their workflow. Some people just don't "get" Node-RED, finding the learning curve too steep, while some take to it immediately. Use the system that works best for you. Having more choice is never a bad thing.
What if my device is not supported through any hub?
Anything that has an API can be integrated with Reactor. That's not to say it will be automatic, quick, or easy. Writing an interface to a new API to fully expose the capabilities of that API takes some skill. Put in a support request if you have a product with a local API that you'd like to see supported directly.
How do I get Support
See the Support & Suggestions section of this document.
What is the purpose of the state packages produced by
The state package contains a snapshot of your running Reactor system and its significant configuration elements. It can be helpful in troubleshooting problems you may be having. It encapsulates the data into a single file; the contents are encrypted, but can only be decrypted by authorized staff. This makes the data secure enough to post to the bug tracking system.
Is the state package produced by
make_state_package.sh really secure?
It's as secure as we can trust OpenSSL's encryption to be. The state package is encrypted with a one-time-use random passtext, and that passtext itself is encrypted using public key cryptography. The state package can only be decrypted by first decrypting the passtext, decrypting the passtext requires a private key, and the private key is held only by Kedron Holdings, LLC and is not distributed as part of any release package, nor is it stored on any server outside of our offices. The AES encryption used is a high standard and believed to be impractical to crack.
Although your private information is contained in the state package, it's unlikely that its disclosure, if possible, would be little more than a temporary nuisance (someone may get your OpenWeatherMap API key... the horror!!!). The encryption done here is really to prevent that from being a common, trivial nuisance (which it could be if the data were not encrypted at all), and to address the requirements of GDPR and similar laws.
Is there API documentation?
Yes, it's here: https://reactor.toggledbits.com/apidocs/