My alarm clock setup is based on a Sonos One that plays music and Home Assistant in combination with DeCONZ and Node-RED to automate my bedroom lights as a wake up light. I could also control the music to the Sonos One from Home Assistant, but I don’t want to rely on my home automation setup for me to wake up. Currently, the Home Assistant integration does not get the alarm data itself, but luckily the Sonos API is easily accessible!Continue reading “Use the Sonos API to gather alarm data”
My smart home journey started years ago with a simple Philips Hue configuration. After integrating Home Assistant, I wanted to have some door/window sensors and temperature sensors. I bought the Xiaomi Aqara bridge and implemented all the sensors into Home Assistant. I quickly realized I now have two Zigbee bridges due to the fact that both Philips and Xiaomi want a ‘customized’ standard. ¯\_(ツ)_/¯
I needed to do something…
Microsoft recently announced the Public Preview of the ability to run PowerShell code in an Azure Function. This means that the PowerShell code will run in a Platform-as-a-Service solution, completely serverless! You pay only for the time that you use the solution and you don’t have to manage the underlying infrastructure! In this blog post, I will show a practical example of how to use an Azure Function in combination with an Azure Logic App.
People who follow me on Twitter might have noticed that I’m working more and more with Microsoft Flow. Microsoft Flow allows me to create simple automations (like IFTTT) and to create a bridge between services like Office 365 and my home automation with Home Assistant. Recent changes to the pricing model made me decide to move away from Microsoft Flow, back to Azure Logic Apps. In this blog post, I’ll explain how easy it is to move your flows to Azure Logic Apps.
The Dutch Government is aiming on providing smart meters to every household before Q4 2020. All the smart meters need to comply to DSMR (Dutch Smart Meter Requirements). DSMR allows us to read data from the smart meter by using a cable. In this guide, I will explain how I got this to work with Home Assistant.
My last blog post was all about getting Hass.io (or HassIO) installed on the new Raspberry Pi 3 Model B+. This guide starts right where we left off: configuring Home Assistant to work with the configuration files we already have from Home Assistant running on Raspbian. Below are the steps I took in a nutshell.
- Install and open the Configurator Add-on on Hass.io to make sure you can always open the web UI to change your configurations.
- Create a snapshot so you can always go back to this point in time.
- Cut/paste the BaseURL and SSL settings from the configuration.yaml on your old Pi to the new configuration.yaml on your new Pi by using the Configurator add-on. Make sure that you have an SSH session open to the old Pi on the IP address of the old Pi, so you can still copy/paste the contents of various configurations. Also stop the Home Assistant service on your old Raspberry Pi and change any port forwarding rules in your firewall or DNS settings. (Depending on your old setup)
- Got your Home Assistant ready under the original URL? Create a new snapshot, just to be sure.
- Start copying the contents of your configuration.yaml and other relevant YAML configurations by grabbing it from SSH and pasting it in the Configurator Add-on. I was surprised to see that all the modules I’ve used before on Raspbian are working fine on Hass.io! So don’t worry too much about that.
- Go to your Hass.io URL and confirm the dashboard is back to where it was before.
Let me know if this guide helped you out!
Home Assistant recently announced a brand new image of Hass.IO running on HassOS. I instantly ordered a new Raspberry Pi 3 Model B+ to replace my older Raspberry Pi Model B, which was running Raspbian and Home Assistant. The guide below helps you with installing your new Hass.IO instance!