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

homeassistant

12102 readers
16 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
GreatAlbatross@feddit.uk
10
'Touch points' in HA (lemmy.world)
submitted 11 hours ago by Bluesheep@lemmy.world to c/homeassistant@lemmy.world
8 comments fedilink hide all child comments
 

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
[–] huskypenguin@sh.itjust.works 2 points 9 hours ago (1 children)

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

[–] schizo@forum.uncomfortable.business 1 points 7 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.