:house: My Home Assistant configuration. This repo will be archived 🗄️ in the future

License: MIT License

Shell 0.05% Python 27.62% Ruby 0.01% JavaScript 72.33%

home-assistant home-assistant-config automation zwave internet-of-things iot mqtt-smarthome yaml-configuration dsmr fibaro klikaanklikuit google-home telegram assistant-configurations p1-cable html5 intel-nuc

smarthome-homeassistant-config's Introduction

Smart Home = Home Assistant

⚠️ This repository has been archived and will no longer be maintained. Thanks for all the stars, help and brainstorms!
In the meantime, you can always take a look at my other HA config repository and give it a ⭐ if you like.

You will probably think, what is Home Assistant!? Well Home Assistant is a open source home automation platform that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server.

To inspire others I have set up this github and update it regularly with new code. Be free to use code from this repo for your own Home Assistant environment, keep in mind that you can not always copy everything line by line. If you can not get out, you can always contact me.

This is by the way not my first Home Assistant configuration that you can find on Github. Since this year I have a second Home Assistant installation, you can read all about it on the website www.student-techlife.com and you can find the configuration/repository here on Github.

Status Information


This shows whether the configuration in this repo is valid	This shows how up to date this repo is

I now use the issues as a TODO list	This is the version that I am currently running with Home Assistant

I use Uptime Robot to monitor my instance from outside in case of crashes	Shows how active I am with this repo annually

Please ⭐ this repo if you find it useful, like these people have	If this config was very helpfull, you could buy a fanta 🍹 for me 😄

Current Configuration

Recently I switched from a raspberry pi 3B+ to an Intel NUC. I noticed that the Pi for my house was no longer powerful enough to run all processes. That is why I invested in an Intel NUC at Christmas 2018, which is now smoothly running after a long transition in the 2018-2019 Christmas holiday. I also switched from hassbian to Home Assistant - Supervised in docker.

My HA Server

Below my server setup on which I run Home Assistant:

Intel Baby Canyon NUC7i5BNH - Inside it 16GB Ram, 500GB SSD and running Ubuntu Server LTS.
Using the Hass.io installation.
Aeotec USB Z-Stick - Z-Wave Plus
Deconz - Conbee 2
RFXCOM RFXtrx433E
P1 cable

In House

Curious about what kind of hardware I have in my Home Assistant system? I have a list: Check it out (Last update: 30 April 2020).

Grafana gas/energy consumption dashboard

I have built my own dashboard in grafana for my gas and energy consumption, which I can call through an iframe panel in Home Assistant. If you want to know more about this, take a look here.

Back-ups

Every Sunday at 3:00 am an automation makes a snapshot of my installation. In the past it happened that the sd card of my Pi became corrupt and I lost everything. That's why this backup is also made locally on my Synology NAS automatically and this is fully automated. (Inspired by: @adonno)

Apps to control

Nothing is better than being able to control your own smart home from your phone or tablet.

Needing Help?

License

MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

smarthome-homeassistant-config's People

Contributors

Stargazers

Watchers

smarthome-homeassistant-config's Issues

Operate the garden lighting

Setup and wallmount Android Tablet with Dashboard

Interactive Telegram bot communication

request and operate

Entities no longer loading well after update to 0.85.0

After the update I found out that not all of my entities were loaded nicely in my dashboard. As far as I know, this has to do with the warning in the release notes.

So check your config well after the update!

Build Grafana dashboard

Wait until this PR has been implemented in Grafana V5.4

Install door/window sensors

Migration to hass.io

I have decided to drastically change my current home assistant installation.

I move to the use of Hassio. After a bad first start I am convinced that this OS has a greater added value.
I will replace my raspberry pi for an Intel NUC. For most, everything works fine on a Pi, but with a view to the future and the use of even more integrations, I am going to change this.

Aftership component transition

At the moment I use the custom component of Aftership, since HA 0.85.0 this component is included in to HA itself. So... get rid off the old custom version and start using the new component 😄

Do more with TTS Feedback (Google Home)

I want my Home Assistant to speak more of itself, as if the system is really alive.

It is possible that I can find some nice examples here.

Adding Gitlab Ci sensor

Adding Aftership sensor

Adding a guest mode

Work with Traccar

Start using the Traccar add-on.

Possibly I will replace nmap or gpslogger if I like it, soooo much testing in the coming period 😄

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.