This repo contains my home automations which are executed on Node Red. Many integrations interact with Home Assistant which is used to interface with various devices.
These are public in case they are interesting or even useful to someone else, so that I can ask help from other home automation enthusiasts, and show off a bit.
All Node Red Modules used are incidentally listed here as part of the Node Red project.
flowchart LR
A[Node Red] --> |Websockets| B[Home Assistant]
A --> C[Sonos]
A --> D[Elasticsearch]
A --> G[HomeKit]
B --> E[Phillips Hue]
B --> F[Dyson]
B --> H[Apple TV]
B --> I[Bravia TV]
B --> K[Google Calendar]
B --> J[Roborock Vacuum]
If you would like to see what these nodes look like in a local instance of Node Red, clone this repository and run:
make
That should create an instance of Node Red with all of these flows at http:https://127.0.0.1:8080.
The dependencies for doing this are:
- GNU Make
- Docker
When you're done you can run a cleanup with:
make cleanup
This should cleanup any remaining containers or networks; it does not attempt to cleanup the container images which were created.
The Node Red flows in this repository are updated and published using Node Red's Projects feature. Although there's a bunch of extra stuff in the repository, it should still be possible to use their instructions to clone this repository into an instance of Node Red.
Sonos speakers play audio ambiently at basically all times. Different playback behavior is defined in music_config.yaml and activated by this flow.
Music config remains quite complex, and is actually flattened out in the longest function node in the whole setup. This file remains the point of modification for music configuration. Playlist can be tried out directly through the Sonos app or Spotify, but then get added in a small PR to this repository.
Phillips Hue lights are used to provide accent and ambient lighting in the home. Task lighting is entirely separate and uses manually switched lights. Some conditional behavior is driven by hue_config.yaml but a scene in the Hue system must exist for activation based on the "day phase" of the home.
Hue config got significantly less complex when I adopted Home Assistant, as it has wonderful Hue integration which allowed me to key off the string names of the scenes for each Hue "room" in the home. At this point, modifying the lighting of a scene is done directly through the Hue App and you just save the Scene with the name matching which "Home Day Phase" it is for, e.g. Morning.
A Roborock vacuum is controlled so that it only runs at night if there are no guests, or when we are not at home. The device is denied an Internet connection by the router, but can be interacted with via WLAN from the same network.
I wanted to be able to git track the fairly complex configuration objects that I needed to describe my intents for music playback and lighting. These were the first files in this repository to be source controlled. Those configuration objects take the form of YAML files:
The config files are validated for YAML correctness using yamllint in a GitHub Action. Because the majority of music playback leverages public Spotify playlists, the music_config.yaml gets some additional validation by a script which confirms every indicated Spotify Playback URI is a valid, reachable, and public Spotify Playlist.
The Node Red Flow which manages Configuration is:
Responding to the occupants of the home requires tracking state, largely facilitated with Homekit presence tracking and a pair of door sensors. The behavior of the home varies depending on whether or not a guest is present, so that manifests as a manually-switched configuration controlled via Homekit.
We're working on sleep hygiene right now and have enslisted the home automation to help.
We display art on the TV, so like for it to come on in the mornings and evenings.
When we watch something on the TV we want the nearby speakers to mute. So, we monitor what's going on with the TV itself and the associated Apple TV to drive some automations.
Verbal alerts are played for us based on calendar events. Home Assistant is actually integrated with our calendars, and this automation checks those calendars and notifies us if we should really be going to be bed instead of watching that next YouTube video or whatever.
Changes to state variables which drive behavior are written to an Elasticsearch instance in the home, originally setup to track energy consumption.
Configuring the speed of the fans in the home and activating the humidifier in the bedroom when appropriate, plus recording the interior temperature and humidity. These flows have significant issues with being hardcoded to this home.
The data collection bits let me do this in Elasticsearch dashboards:
