We already allow reloading the most important pieces of configuration: groups, scripts and automation.
2,085 karma · joined August 27, 2012
We already allow reloading the most important pieces of configuration: groups, scripts and automation.
Backend is Python 3 with asyncio. Source: https://github.com/home-assistant/home-assistant - License: Apache 2
Frontend is a PWA powered by Polymer 2 Source: https://github.com/home-assistant/home-assistant-polymer - License: Apache 2 - Demo: https://home-assistant.io/demo/
We still offer the old API on top of asyncio, so we have been able to incrementally transition. By now the core and important components are all fully asyncio. Most integrations are not.
The published version of Home Assistant is 100% what is on GitHub. Home automation is able to gather very private details of your house. It knows when you're home, what TV shows you watch, when you go to sleep. We keep all this data locally in your house, without the cloud. We want to make sure that anyone can check and influence the code that is distributed. No data should leave your house without your permission.
(Automations have been able to be reloaded without restarting for a while now by calling the automation/reload service)
[edit: added word "service" at the end]
Besides being able to install it as a Python package on Python 3, you can also install it using our Hass.io OS. Based on ResinOS and powered by Docker, it offers over the air updates and management of your device via the user interface: https://home-assistant.io/hassio/
The answer for this is already in your browser: CSS custom properties http://caniuse.com/#feat=css-variables
On top of that the CSS working group is working on ::part and ::theme pseudoselectors to help theming across components. Brief intro in this Polymer Summit 2017 talk: https://youtu.be/rvpJ5O0W_6A?list=PLNYkxOF6rcIDP0PqVaJxqNWwI... (skip back to 16:17 to hear why the CSS mixins proposal didn't work out)
Use our Hass.io OS build to setup Google Assistant easily on your Pi. Need a USB microphone and speakers connected to the Pi and you'll get the full Google Assistant experience.
(disclaimer: I'm the founder)
YouTube video showing a user installing Homebridge in 30 seconds on Hass.io https://youtu.be/A_LmQ5OlofY?t=61
https://github.com/home-assistant/home-assistant/blob/dev/ho...
Asyncio has a steep initial learning curve (especially in our hybrid setup) but it's well worth it. We target low resource computers like Raspberry Pi and using async over threads has speed up things a lot.
The biggest catch is that while writing code you have to think about every function that you use. Is it doing I/O, is it a coroutine or is it callback/async friendly.
All videos will be recorded so you should be able to watch it online. I'm planning to give a similar talk soon at a Python SD user group meeting to practice for my PyCon 2016 talk.
You can find my sliders for tomorrow here: https://docs.google.com/presentation/d/1P2WsmwGSSni4gAriY5IA...
As AcidBurnNSA said, Home Assistant is free, fully open-source and fully community driven - no company involved. We have over 240 components and platforms to include a wide range of products and services: https://home-assistant.io/components/
If you're attending OpenIoT Summit in San Diego, I'll be speaking tomorrow about Home Assistant 1:35pm - 2:25pm in Harbor Ballroom F: http://openiotelc2016.sched.org/event/6DBd/automating-your-h...
I used it myself to have the ESP8266 report temperature and humidity to my home automation: https://home-assistant.io/blog/2015/10/11/measure-temperatur...
Use your side project as your playground to learn new things by doing mini projects within your side project:
- Want to learn about testing? Add test coverage. - Want to learn about webcomponents? Find a way to integrate it.
You don't have to finish all the mini projects. Dropping something is fine, you still have the experience and knowledge!
What really helped for me in keeping steam is publishing the source of my side projects on GitHub. The idea that someone else uses your code is very satisfying. Once some traction comes, the pull requests and issues start coming in and it gets even more fun.
And when you get bored? No problem, just switch to a different side project or think of a new mini project.
Components use internally a shadow DOM for representation so that they are untouched by / do not affect the CSS on the main page.
Tool that allows users to create their own tours using Android Photospheres and embed them on their website/view online.
See https://www.youtube.com/watch?v=M0zk_VuX2b0 for a demo of the interface
Our current commitments prevent us from finishing it.