This is my personal home assistant configuration. I'm sharing it to provide the community ideas on how to organize one's files and on which kind of automations are feasible and how.

Disclamer: While I don't think it changes anything regarding how I manage my home automations and what I'm sharing here, I prefer to be transparent and reveal that I've recently starting to work for Google Nest and might be biaised towards the Nest products. Taht said I was already using my Nest Doorbell and my nest speakers/screens before joining so it's not like it changes anything.

After staring like everybody with everything in my configuration file, I started to split it to better keep track of the changes using GitHub. I followed the example of @jonathanadams and split (or actually tried to since it's a work in progress) all the configuration this way:

• basic configuration will stay in configuration.yaml

• every integration has its own yaml file in the integrations folder

• when an integration corresponds to multiple entities (lights for ex.), then they each have their own YAML file in the corresponding folder located in the entities folder.

• scripts, automations and scenes are grouped by "theme" (everything related to a room or a device for ex.) in their corresponding folder. Each folder has or will have its own documentation to explain what each automation/script/scene does.

With things moving to the UI more and more it's becoming more and more complicated to keep things organized but I'm trying my best.

After some time using Ariela I then switched to HassKit. While it has a bit too much an iOS-feel for me, I find it more convenient to be able to create specific views for the mobile. Ariela was also not liking all the custom components and the more I was customizing Lovelace, the more Ariela was becoming unusable. That said, in the future, I might reuse Ariela to refurbish an old Android phone into a new connected device.

Recently I've moved back to using the offical app since it also gives you the opportunity to expose a lot of data from the phone to Home Assistant. My only worry is that the battery consumption semms quite high, especially on my watch. But maybe that's just an impression, I haven't really investigated.

I'm using CircleCI to check the configuration of every pull request or every time something is pushed to the master branch. This is configured in the .cicleci/config.yml file but it's still far from perfect checking lint raises way too many errors at the moment (likely due to all the custom integrations, but I'm worried it won't work otherwise). It was based on @mhaak work.

I used to use Travis because it was free for open source. But since it's not the case I've move top to CircleCI. That said you can still have a look at my Travis configuration in the .travis.yml file.

I'm a former video game producer so I love Jira :D To keep my habits, I'm using Jira to keep track of what I plan to do. It's integrated with github (my commits and PR are linked to the Jira issues), slack (for notifications) and circleCI for continuous integration.

• hacf.fr - French Home Asssitant community

• zigbee.blakadder.com - Zigbee devices compatibility database