I am running Home Assistant at home. It kind of works, in a kind of haphazard way as if you had an old-school Lego set with no instructions and you just puttered around building things until you were bored or done.
Is there any organized, methodical, "here is how you do it well" guide to HA? Principles of operation, design guidelines, some reasonably well worked out non-trivial examples, suggestions for what not to do, etc?
I will summarize replies.
=> More informations about this toot | More toots from w8emv@hachyderm.io
@w8emv If there is I haven't found it!
Other than the #1 point in almost all the videos seeking to address this topic, which seems to be "come up with a naming convention" for all your things.
I currently have a dashboard for each functional area (heating, lighting, solar generation), each of which has two tabs, Performance and Control, plus a System Monitoring dashboard with a tab for radios (RSSI) and a tab for batteries.
I'll run with this for a while and see if I like it any better than my previous haphazard mess.
Of course if #HomeAssistant had role based access control that'd be different, you'd maybe want to organise things round that.
=> More informations about this toot | More toots from TimWardCam@c.im
@w8emv boosting because apparently I'm doing this too now I guess
=> More informations about this toot | More toots from ifixcoinops@retro.social
@w8emv My biggest tip is to find/create/adapt a blueprint for your common scenarios like motion sensors, buttons etc then use the blueprint everywhere.
That way you’re not writing and maintaining multiple automations, just filling in a few fields. If you change the blueprint all areas using that blueprint will change.
=> More informations about this toot | More toots from codechimp@mastodon.online
@w8emv What an accurate description of Home Assistant! 😆 There really isn't a solid set of "how to do this well" documentation out there - yet. Believe me when I say I know this pain. You can search online for some examples but you often run into them being out of date.
I typically suggest hopping on our forums or into our Discord server to ask for help, but I also boosted your post - maybe others will chime in. 😊
=> More informations about this toot | More toots from homeassistant@fosstodon.org
@homeassistant @w8emv I guess that's what I like the most about HA. No idiotic PM who knows better, No marketers optimizing one workflow to please a random coporate partner. Basically no Dunning Kruger syndrome here. HA is giving blocks. Up to me to assemble them the way I like and works for me. There is no right way. Anything that works for you is the right way.
=> More informations about this toot | More toots from primalmotion@antisocial.ly
@primalmotion @homeassistant @w8emv this. I love how well it conforms to what I need vs having to confirm to it.
=> More informations about this toot | More toots from bhhaskin@bitsofsimplicity.com
@w8emv
Hey Ed. I have been running the HA Yellow appliance for about a year now. AMA.
Take a look at the NODE RED add-on for HA. I thought it was too much until I made my first automation with it. It is also fun, and that makes things just a bit easier.
https://community.home-assistant.io/t/node-red-flow-examples/83644
=> More informations about this toot | More toots from jeff@soapbox.hackdefendr.com
@jeff @w8emv I wouldn't recommend step one be "use a third party automation tool." Stay in the native ecosystem first. NodeRed used to be a good first step when the automation tool was weak. Not now.
=> More informations about this toot | More toots from gmartin@hometech.social
@gmartin @w8emv
This is one of those things where I started using Node Red and never went back to the native automation tool because I didn't see the need. I only recommended it from my own experience, I didn't say it was the only way.
=> More informations about this toot | More toots from jeff@soapbox.hackdefendr.com
@w8emv I have never met an HA user who did anything else but "you just puttered around building things until you were bored or done" with it so such a guide would be very welcome
=> More informations about this toot | More toots from msh@coales.co
@w8emv I find it challenging to have some "How To" as it feels like it changes with every new device we integrate.
The one thing I know: If you need to watch metrics, i.e. on energy consumption or plant/room climate to find out peaks over the year and filter by device, the HomeAssistant's internal historical view won't help.
InfluxDB and Grafana did it for us.
For just switching around some lights one dashboard seems enough.
We tried by room, by floor, by type - nothing fitted all use cases.
=> More informations about this toot | More toots from mafe@layer8.space This content has been proxied by September (3851b).Proxy Information
text/gemini