this post was submitted on 01 Oct 2023
20 points (95.5% liked)

homeassistant

15045 readers
10 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.

Home Assistant can be self-installed on ProxMox, Raspberry Pi, or even purchased pre-installed: Home Assistant: Installation

Discussion of Home-Assistant adjacent topics is absolutely fine, within reason.
If you're not sure, DM @GreatAlbatross@feddit.uk

founded 2 years ago
MODERATORS
GreatAlbatross@feddit.uk
greatalbatross@lemmy.world
20
Lowest latency input (lemmy.nz)
submitted 2 years ago by Sim@lemmy.nz to c/homeassistant@lemmy.world
14 comments fedilink hide all child comments
 

I'm using a ZigBee button to call an automation which notifies via Pushover and Alexa. Works fine.

I'd like to reduce latency and use a physical button. I can use a Pi, ESP32 or similar to respond to a closure and tell HA.

What's the lowest latency input to HA? My MQTT server is separate so I'm thinking an HTTP post direct into HA might be best.

Is there anything faster? HTTP is fast enough in my testing, it's an experiment as much as anything else.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] peregus@lemmy.world 2 points 2 years ago (1 children)

I don't think that MQTT could add any perceptible latency. Maybe is the button itself that adds it. Isn't the button able to recognize multiple pushes? If yes, there lies the delay: the button waits for a second push and if it doesn't arrives, it sends out the command to the coordinator. What kind of ZigBee button are you using?

[โ€“] Sim@lemmy.nz 1 points 2 years ago

That's a good point; the button does support double push, I might be able to disable that. It's some old unit I picked up for next to nothing, I have some Aqura buttons about to try.