-
-
Notifications
You must be signed in to change notification settings - Fork 29k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WoContact has incredible delay in reporting events and is missing an entity for the built in button. #82795
Comments
Hey there @bdraco, @Danielhiversen, @RenierM26, @murtas, @Eloston, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) switchbot documentation |
So it looks like the only time it updates is from the scan response. If we could get them to change the service data to come in as an advertisement whenever it changes on the device this would fix the slowness but it would require change in the switchbot firmware. This would also be a great change because it would make it work with passive scans |
I opened an issue here OpenWonderLabs/SwitchBotAPI-BLE#15 |
Would be nice if they actually did make the change. Guess now we wait. |
It looks like that PR was abandoned #79632 |
Some of the data is in the |
The problem
WoContact reports events with a delay of anywhere from 0 to 30 seconds.
WoContact is also missing an entity for the device's built in button.
What version of Home Assistant Core has the issue?
2022.11.2
What was the last working version of Home Assistant Core?
none
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Switchbot
Link to integration documentation on our website
https://www.home-assistant.io/integrations/switchbot/
Diagnostics information
No option to download diagnostic file is available.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
The logs just list the events, as they are received, with no discernable reason for the issue.
Additional information
No response
The text was updated successfully, but these errors were encountered: