core: Kodi integration not updating state when becoming available
The problem
Environment
- Home Assistant Core release with the issue: 0.115.1
- Last working Home Assistant Core release (if known): -
- Operating environment (OS/Container/Supervised/Core): container
- Integration causing this issue: Kodi
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/kodi/
Problem-relevant configuration.yaml
No configuration because it is an integration
Traceback/Error logs
No trace as it is an behavior issue
Additional information
Given that the Integration uses discovery (zeroconf) as far as I know, I would expect the component to become available as soon as kodi starts up. This however is not the case and instead kodi only becomes available after sending a random command to it or after a very long delay.
Pinging @OnFreund as you have been the one working on the integration 😃
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 56 (55 by maintainers)
Yeah, I totally understand how you feel and it’s a sad day for Home Assistant (and open source in general) quite frankly when real issues are punted on in this fashion and with this tone 😦
I’ve got plenty of experience with running custom components (though never due to the code owners not willing to admit major functionality regressions and help resolve them in a productive fashion) so I will take your changes tomorrow and test them out on my setup. Is the latest iteration what you posted above?
I’ve been running with just setting the watchdog timeout to 10 seconds and it works well enough for my purposes that I might consider just doing that in order to make integrating future fixes easier.