Hass has probably been the biggest help to this quadriplegic in the past decade. The way it's made it easy to stitch together a massive variety of Internet connected devices is absolutely awesome. I've got lightbulbs from one company, plugs from another, sensors from another and then there are all the web-based sensors which I can easily control with my Amazon echoes. It truly is a remarkable piece of technology.

Were I to ask a specialist disability company to replicate the setup I have at home it would probably cost me 10 times what it already has, and unfortunately that's not hyperbole is it really would cost me that much.

Not only that, but the Discord[1] channel is not full of terrible old greybeards having a go at n00bs for not knowing things. The amount of patient and helpful advice I've had was learning over these past six months how to set it up has been amazing. That seems to be getting rarer and rarer these days among technical online communities, or maybe it's just confirmation bias. Either way they are very nice people. I've even had the developers help me with problems that are specific to me and my disability and probably not to very many other people just because they could.

They deserve serious props for this work, they really do.

@robotsandcake over on Discord

I've been using Home Assistant for about 1.5 years on an RPi3, controlling some outdoor and indoor lights using a Zwave hub. It has been rock solid and never given me any issues.

Thank you for this awesome software and community!

I apologize if this is silly question but how is the smartphone in the pic on the home page displaying that interface? The control section notes:

>"Control all your devices from a single, mobile-friendly, interface."

I had a cursory look through the github repo and everything just looked like python, nothing UI wise jumped out at me.

There is an extra repo for the web frontend: https://github.com/home-assistant/home-assistant-polymer

I typed: 192.168.0.5:8123 into my phone browser. Adjust your IP accordingly.

Are there any plans to improve the integration with openzwave?

Currently, there is not much feedback available to the API when adding/removing nodes except for viewing the openzwave log files and comparing state lists before and after.

Also, are there any plans to provide hot reloading of config files, instead of having to reset hass? Large zwave networks can take 10mins+ stabilise after a reset.

Contributions to improve Open Z-Wave integration are always welcome :)

We already allow reloading the most important pieces of configuration: groups, scripts and automation.

You allow reloading, but that is not the same as hot reloading. Love your work btw.

We reload right after you make a change in the UI. Seems pretty hot ;-)

If you want automatic reloading when a file changes, feel free to contribute a watchdog component to Home Assistant so people can hook it up themselves.

I've been hammering away on lifx discovery for a month or so, I'm absolutely stuck but in https://github.com/home-assistant/netdisco/issues/128 you've said you don't want to pull in any additional components.

Would you be open to pulling in an extra lifx library that's tested and working until such time as lifx discovery can be rewritten?

I use LIFX bulbs all throughout the house, I think we have about nine of them and they are always discovered every single time I restart Hass and have been doing for as long as I've been using it.

Are yours just not showing up at all, or are they coming on and off-line?

Hass.io? In case you don't know, hass means hatred in German.

Coincidentally, it is also a short name for the home assistant software in English.

In turkish it might sound like "hassiktir," which means "fk off", "WTF", but pronouncing only the first half is very common.

David Hasselhoff will not be pleased to hear that - his surname loosely translates as "Court of Hatred"

If I had to guess, I'd say "Hassel" is related to "Hasel" in this case (as is the case with quite a few similar place names), which would make it more like "David from the farm with the hazel trees" or something.

"Hassel" is German slang and translates to "hassle".

.. but that is new slang, and originates in "hassle" afaik. And I would rather say, it is just used (and written) as the original english word.

It could very well be exactly the other way around. Even my grandparents knew this word and taught it to my parents. It's absolutely not new.

Interesting, I never heard of it and will ask mine. Which area are you from? (maybe it is dialect?)

Anyway, I suppose most teens who use today, got the word from gangsta rap and their "street hassle" ..

When you ask geeks to name a product the result might resemble marketeers engineering it.

Interesting. It is also a not uncommon last name.

It is also a cultivar of avocado, named after its breeder [1]

[1] https://en.wikipedia.org/wiki/Hass_avocado

Isn't that usually Haas? I know 3 or 4 independent people with the last name Haas, as well as the Haas business school at berkely, but only know Hass as the avocado brand.

Haas is also the name of one of the biggest CNC machine companies. They also have race teams.

Haas is rabbit

Yep, unfortunate naming...

Huge fan of Home Assistant — I'm currently using it with a Broadlink RM3 Mini to control the media setup at a hackerspace.

Thanks everyone for your hard work!

Did you guys consider distributing reference 3D printing designs to accommodate the Raspberry Pi at home. For example replacing a wall light switch? The wall niche for the Pi+ switch is a perfect place because it supplies electricity and is already reserved for a human interface.

I've developed a open hardware 3d printable LCD touchscreen which uses WiFi+MQTT to interact with Home Assistant which fits into a standard wall panel which you can find here: https://github.com/aderusha/HASwitchPlate

This still requires Home Assistant to be running somewhere else on the network and uses an ESP8266 instead of a Pi for several reasons, but it might help you out on your use case.

Wow that is awesome. Good work!

It's weird that you guys with a open source project don't have a IRC chanel, at least I couldn't find one on https://home-assistant.io/help/

We are on Discord which has a better experience for our users https://discord.gg/c5DvZ4e

Have you heard of / considered Matrix/Riot?

Consider Keybase as well.

How is this project funded?

I don't have a external screen and http://hassio.local:8123/ says 'Server not found', because my network is a bit special. Therefor I connected via serial to the rp and now it asks me for a username and password which I can't find. Would you care sharing this?

I'm not a Hass user, but recommend you try user pi with password raspberry. (That's an RPi standard of sorts.)

I tried that but it's not it, this is default for raspbian I guess, the hassio people use Yocto to create a custom linux distribution, I guess I'll need to check out the yocto layers if I can find which password is used.

Hey Baloob. Will you be implementing access control levels anytime soon?

interesting naming, Hass in German meats hate but I guess that was not the intetion.

Founder? Is this for-profit? If so, how you gonna make money?

Edit: glad to see the project on Github is APACHE licensed. Any drawbacks from using the software compiled str8 from Github as opposed to downloading the binary blob from the website?

It is not for-profit. We will soon start a program for people to support the project.

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.

Hey Baloob. I watched you talk at PyCon. How have your experiences been since you switched to asyncio?

asyncio is amazing. It has been way faster and more predictable. Home Assistant has a lot of small tasks running all the time with the occasional task taking a long time (ie. trying to reach a device which has been turned off). The number of tasks running simultaneously used to be limited by the size of the thread worker pool, which is no longer the case. A request taking a long time is now just a coroutine pending result in our event loop.

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.

Dude. A blog post on writing application on top of asyncio which may interchangeably use threads or async/await, and incrementally making the switch to asyncio would be awesome.

I work with a large-fintech platform which is partially powered by Python. Our old server was based around threads, queues, and socket multiplexing but we are gradually starting new applications in asyncio.

I recently completed a project in aiohttp which has been fantastic. What are your thoughts on aiohttp vs tornado?

I have not used tornado but I love aiohttp. it's super fast (part in cython) and does HTTP + websocket client and server. Their team is are part of the asyncio contributors, they know their stuff.

this would be another great talk.. consider! :)

I submitted a talk proposal for PyCon 2016 about this but was not selected.

No, and it is encouraged for those who are capable of it. Send pull requests if you think anything can be improved please!