-
MagicMirror
MagicMirror² is an open source modular smart mirror platform. With a growing list of installable modules, the MagicMirror² allows you to convert your hallway or bathroom mirror into your personal assistant.
-
Home Assistant
:house_with_garden: Open source home automation that puts local control and privacy first.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
An upcoming project of mine is to setup magic mirror: https://magicmirror.builders/
Then start moving my other stuff onto the rpi as well like pihole for example.
I wonder if RPI has a zigbee module or similar for automation. It doesn't seem like it? Anyone ever find anything like that?
Home Assistant[1] is the best approach I've found for this. It's pretty amazing but has a pretty steep learning curve (although they're getting better and better at this). The real power of HA is the rich integration ecosystem[2], the Community Store[3], and that it runs locally (more reliable and much faster for things like motion sensors, etc).
It expresses everything from every integration as an entity in various device classes so as long as some random tech is supported by an integration you can group them seamlessly. For example - I have Z-wave based motion detectors but I can control Hue lights and Wemo switches for motion detection - but only if I'm home as reported by the zone feature in their iOS companion application.
Their supervisor/docker based install for Raspberry Pi is pretty slick[4]. Write an image to disk as you usually would and you get a bare-bones OS with Home Assistant running in docker. Then there are additional docker-based add-ons you can install for stuff like MQTT, Z-Wave, Let's Encrypt, SSH access, nginx, and more. All managed in the web ui. Pretty cool.
[1] https://www.home-assistant.io/
It is possible, and a few years ago seemed quite a trend (just going by /r/homeassistant spectating) - https://github.com/hassio-addons/addon-node-red - but I gather HA's own automation scripting has at least visualisation if not GUI programming now.
They've also been pretty hostile to OS packagers trying to let you run it without dedicating an entire device to it, most publicly NixOS but they indicated they planned to insist the same against Fedora and Gentoo too: https://github.com/NixOS/nixpkgs/pull/126326
That behaviour kind of makes it hard to trust that it won't lead to the next Marak situation.
This kind of pushed me away from HA. I've ended up using integrations built using hc [0] to bridge devices to HomeKit, either existing or ones I've built, and then using Promtheus to collect metrics. It's not something that 'just works', but I feel much happier with how it works than HA.
[0] - https://github.com/brutella/hc
https://linuxgizmos.com/catalog-of-136-open-spec-community-b...
Take a look also at the devices supported by Armbian and DietPi.
https://www.armbian.com/download/?device_support=Supported
https://dietpi.com/#download
Also worth visiting is the Linux-sunxi site, where you can find a huge load of open documentation about hardware and software for Allwinner CPUs used in some of these boards.
https://linux-sunxi.org/Main_Page
Also available are Amlogic CPUs docs at the Hardkernel site.
https://dn.odroid.com/
Example: here's the over 1000 pages long S905x3 full data sheet.
https://dn.odroid.com/S905X3/ODROID-C4/Docs/S905X3_Public_Da...
The public Raspberry Pi CPU data sheet is 166 pages long.
I have had success integrate Ring and Wyze cameras through Home Assistant. If you'd rather not go that route, there is a project that publishes Ring cameras over MQTT and RTSP links: https://github.com/tsightler/ring-mqtt
Did you try changing the CPU governor settings? I've found that light workloads don't always push the governor enough to push the CPU into higher frequencies. I have mine set to 100% CPU, for lowest latency. See: https://github.com/home-assistant/operating-system/issues/19...
On my Venstar you can adjust the spread. I guess you probably wouldn't really want to.
Looks like that integration is implemented on top of an external library (so you have 3 layers of implementation):
https://github.com/hpeyerl/venstar_colortouch/blob/master/sr...
The HA integration doesn't use it, but the library exposes the spread value.