-
-
Notifications
You must be signed in to change notification settings - Fork 32k
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
HA log flooded with connection errors after turning off Yamaha receiver #14241
Comments
Please check #14748 which should suppress the traceback. |
Thanks for the patch, I had partial success with it, i.e. the patch suppresses the continuously tracebacks after the receiver goes offline. But: The status of the entity doesn't update (it is still shown as 'on'). And HA still throws errors if I try to change states of the receiver, f.e. the volume:
|
Update: The component is still shown as 'on' after more than 1 hour. Changing attributes still throws three Tracebacks for every change. |
Home Assistant release with the issue: 0.68.1
Last working Home Assistant release (if known): I encountered the issue at first with version 0.66.1, but I'm not sure, which version I was updating from to 0.66.1
Operating environment (Hass.io/Docker/Windows/etc.): Docker @ Synology
Component/platform: https://www.home-assistant.io/components/media_player.yamaha/
Description of problem:
After switching off a Yamaha (RX-V475) receiver that has been already auto-discovered by HA (i.e. the widget is shown in the frontend), the HA log get’s flooded with connection errors several times a minute, until I restart HA. This issue also seems to severely affect the HA server performance. Commands are only executed with a lag of several seconds and triggering automations seems to get unreliable:
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant): n/ATraceback (if applicable):
Additional information:
These devices have two different standby modes. An “active” standby, that basically turns off the display, but leaves almost everything else running. Especially the network device, which keeps the API up and running 24/7, even if the device seems to be switched off.
The second mode is a deep (i.e. real) standby, that turns off everything except the IR receiver unit. In this mode, the network device is also shut down and the receiver is no longer available via it’s IP address.
The expected behavior would be HA dealing better with a yamaha device switched off to deep standby or becoming otherwise unavailable over the network. It should give up connecting the device after a certain timeout, stop writing errors for this in the log and removing the the widget from the frontend.
The text was updated successfully, but these errors were encountered: