On the YAML front: we've added support for configuring integrations via the UI, no YAML involved[1]. However each integration will need to be adopted individually for this. YAML will still be around for power users and people who like to use version control.

For Z-Wave: the current integration is based on openzwave, a reverse engineered implementation of the Z-Wave protocol with an irregular release interval. As we depend on their releases, it's out of our control.

However, there is hope :) Sillicon Labs (owner Z-Wave) has recently published an official SDK for Z-Wave[2]. Once Home Assistant Cloud is generating money, the plan is to pay a developer to integrate it into Home Assistant. Once we're on an official stack, I expect our Z-Wave story to improve significantly.

[1]: https://www.youtube.com/watch?v=_qpKe-FW9Yk [2]: http://zwavepublic.com/developer

Glad to hear there are plans to improve it. I'd be willing to do a patreon or monthly donation just for better zwave!

Keep up the great work!

My experience has been a bit different to yours but has included a fair bit of headbanging 8)

Zwave support seems to be really good to me. This: https://www.amazon.co.uk/gp/product/B00YETCNOE/ref=oh_aui_de... works passed through to a VM after a vMotion to another host! All Zwave devices I've tried seem to simply work but to be fair I have not done anything like an exhaustive set of tests.

The support on the forums is awesome - one of the best communities about. I'm not quite there yet to really give decent advice but I'm close.

Home Assistant is being developed at a breakneck pace. That means that you must be careful and treat your project with respect. Backups and backout plans and testing must be taken seriously. You have to read everything you can get your eyes on - the forums and docs are very, very, very good. If you do all that then you will be richly rewarded.

I would be happy to contribute $ towards an improved Z-Wave implementation in HA if its based on an official SDK. I'm pretty sure I know a few others who would do the same if you set up a funding campaign somewhere.

Have you looked at AppDaemon [0] [1] or Node-Red [2] [3] as alternatives to using YAML to write automations? AppDaemon allows you to write automations in Python, and Node-Red allows you to do it in a visual workflow editor. I haven't made the switch from SmartThings to Home Assistant yet because I haven't been limited by SmartThings yet and it was simple to set up, but when I do switch, I will probably start with those tools since the paradigm is more familiar to me. You can't get away from YAML completely since you would still need to build your sensor and device definitions in YAML, but I think the YAML structure works better for that use case anyway.

[0] https://appdaemon.readthedocs.io/en/latest/ [1] https://github.com/home-assistant/appdaemon [2] https://diyfuturism.com/index.php/2017/11/26/the-open-source... [3] https://nodered.org/

I only tried Node-Red, it was good enough that I felt no need for AppDaemon, even though as a programmer it probably is even easier than Node Red.

One huge problem with YAML compared with Node Red is the turnaround, node-red restarts blazingly fast. HA, not so much....

I've struggled with this as well. I actually find the YAML harder to write than a full programming language would be. For example, conditional logic such as "Turn on this light when the sun goes down only if this person is home" get complicated quickly. The breadth of options and plugins available is impressive but the documentation presents a lot of small snippets and not many explanations of how to design a coherent system.

I have a feeling that my next step will be reading the source code to get a better sense of how the YAML is translated into the internal state machine, but an official "beginners guide" would go a long way to making this not necessary.

See my reply to the parent

Thanks, I hadn't heard of AppDaemon. It looks a lot like what I found lacking the last time I tried to set up Home Assistant.

... and find the alert module.

Home Assistant should offer basic support (on/off/dim) for your switches out of the box - I've also got a house full of them. The work around should only be required if you want to use multi-tap gestures that the switches support. What's not working for you?

The multi-tap workaround is not terribly involved. If I recall correctly, it consisted of pasting a couple of lines of XML in the "zwcfg" file for each switch.

I can't get specific because my house was struck by lightning a month ago and fried my pi and a half dozen switches (among lots else), and I don't remember the details. Replacements are on the way. Important tip for home automators: don't get struck by lightning. The affected switches didn't just turn off, they started to strobe the lights in the connected fixtures. I had to turn off the circuit and pull them out of the wall to stop the disco dance party.

I did get a few other zwave devices connected, and these do pair with the zwave hub, but otherwise Home Assistant can't see them at all. I messed with zwcfg with no difference.

I had a similar experience with home assistant. The yaml configuration was so obtuse.

I basically just ended up writing my own python scripts and/or batch files and then I would have Home Assistant simply execute them.

That's how I managed to do some of my more complex, un-supported integrations with Home Assistant, anyways.