Hi there!
As a long-time home-automation fan and embedded systems engineer, I’ve always found it unfortunate that all home-automation devices are closed-source and we’re dependent on the manufacturer’s efforts regarding compatibility and functionality. This has resulted in a user-base effort of implementing quirks and workarounds and a large stack of similarly functioning devices.
This, in my opinion, requires an unnecessary amount of time, effort and resources. A few months ago, I took matters into my own hands and came up with a product idea; a multisensor/actuator with a breakout for extendable functionality. Soon, I started prototyping hardware and software. Since then, a lot of software has been tweaked, hardware designed and soldered (and fried) and multisensors tested. This brings us to this post; we’re ready to take things to the next level, by enabling other people to provide feedback to further improve the product.
While aiming not to make this a complete advert, we do encourage you to check out our website with a complete list of features, blog and manual.
In short, we’ve made a multisensor based on the nRF Connect SDK in combination with a temperature, humidity and pressure sensor, illuminance sensor, motion sensor, piezzo buzzer, RGB-led and over-the air update support. These work as expected; sensors are represented as sensors, the buzzer is controllable as alarm and the led can be controlled as a color-bulb.
Ironically, we’ve chosen for closed-source software for now. This will become open-source when we have a larger production capacity and have incorporated more feedback from user experiences. Keeping the code closed-source allows us to precisely control the speed of development. While we’re aware this is quite controversial, we do believe this is the right choice for the upcoming 3-4 months. Early 2023 we’re going open-source nonetheless; we either accomplished our goals, or we’re halting our efforts.
After having open-sourced our code, we hope to see a community forming and collaborations happening in the open GitLab environment. We also hope people to come up with new ideas, concepts and implementations for expansion boards; the ultimate goal.
I’d love to hear your opinion and get some feedback!