this post was submitted on 22 Nov 2024
10 points (100.0% liked)

homeassistant

12102 readers
15 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago
MODERATORS
 

I was reading the HA roadmap and thinking about the points where everyone (else) interacts with my HA environment. I’ve wanted displays/dashboards for a long time but mostly have either battery powered buttons or smart wall switches. These are good in that I can automate them but with two teenage children we have a lot of variability.

Tell me how everyone else uses HA in your house. Do they love it? Do they see only that buttons ‘do things’? Do they read dashboards and crave data?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 10 hours ago (3 children)

I've gone way too far down the automation path.

All manner of temperature, humidity, occupancy, motion, and air quality sensors make all sorts of things do appropriate responses.

For example, I've got a mmwave motion/occupancy sensor in the bathroom, and if there's no motion/occupancy and the humidity is more than 5% higher than the hallway sensor, then turn on the exhaust fan until it's not.

Or, if the air particulate count in the kitchen is too high, turn on the exhaust fan until it's not.

Or, if the living room is occupied, and the tv is on and playing media, turn the overhead lights off and turn the RGB accent light on very dimly. And if the media is paused or stopped, increase the brightness of the RGB lighting so you can see where you're walking, and if it stays paused or stopped for more than 10 minutes, turn the main lights back to whatever state they were in before media playback started.

No dashboards though, since the goal is essentially that you don't have to think about what is going on, because it should Just Work(TM) and never be something you have to deal with.

...though, really, I'd say we're at like 80% successful with that.

For manual interactions I've got a bunch of NFC tags in various places that will trigger the appropriate automation in the case that you either want to do it by hand or it fails to do the needful, plus the app is configured to allow manual control of any device and to trigger specific automations.

[–] [email protected] 2 points 8 hours ago (1 children)

Are you using node red or keeping all of this native?

[–] [email protected] 1 points 6 hours ago

Both!

The native automation is perfectly cromulent for what I want, usually, but there's a couple of cases where the integrations either don't exist or don't return meaningful data.

FOR EXAMPLE, the video playback in the living room thing. Sure, the roku integration says "something is playing" but it's shockingly wrong and unreliable. What happens is it falls into 'idle' status between videos, or if you're fast forwarding sometimes and thus the automation was not doing exactly what I wanted.

The Jellyfin API, though, can look at the living room tv user and is spot on as to what is going on with play/pause/stopped statuses, so I have node red yank that data direct from the API and it works great.

load more comments (1 replies)