this post was submitted on 06 Dec 2023
176 points (98.9% 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I’d suggest reporting to the second issue to the team in a github issue, it sounds like it may be unintentional.
The first is less likely to be altered, but you’re right that you can likely work around it. May be a good idea to look into the config options in case there’s a way to change button options, and worse case you can do a full UI mod like card-mod. Wouldn’t hurt to mention it in a different issue either, though it being an intentional change may not result in an alteration.
Going from your suggestions I was able to find a workaround to change the device's state with just one click, so thank you for that.
For the second problem, it seems that while HA sends a command instantly, it only actually changes states on the dashboard once the device sensors update, which seems to be hard coded to happen about every 30 seconds. I am using an integration from HACS (Custom VeSync) though, so I feel like the problem is more likely to do with my own setup. Then again HA would previously just send the requested command no matter what the state was before...
Either way I'm not really familiar with Github beyond reading release notes and readmes.
Edit: Reading further into the integration I'm using, I realized that it relies on cloud polling. I wonder if there's a way to make Home Assistant assume that a command went through, change states immediately, and then confirm the change with the next polling cycle, rather than just waiting. Unfortunately I don't know how to implement something like this.