-
-
Notifications
You must be signed in to change notification settings - Fork 28.4k
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
onkyo component not working after upgrade to 0.82 #18353
Comments
+1 on that one! The entity_id "media_player.onkyo_amp" is no more. I am running docker under Debian. |
+1. Same issue here. However, this does not seem to apply to the (newer) TX-NR575E amp I have; this one continues to work in Hass as before. The older 656 no longer works with Hass. |
It seems that It seems that a check is missing in case this is false. |
Hi, could you try adding
before and see if that solves it? |
Currently running through the tests, will send in a PR to fix it when done. And sorry for the inconvenience caused. |
Hi! Just installed beta 0.83.0 to see if it includes this fix. My error message no longer appears in the use case I reported: "Error messages appear when HA is started while Onkyo receiver is already turned on." I did not see this error occur. Also, a collateral issue I had with the volume control becoming unresponsive no longer occurs. So I can report that this fix (or some other change in this release) fixes my Onkyo issues. Thanks to all developers involved! |
Yes. Same here. With 0.83.0 beta it is working finde |
Home Assistant release with the issue:
0.82.0 (running on Raspbian)
Last working Home Assistant release (if known):
0.81.6
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian
Component/platform:
onkyo
https://www.home-assistant.io/components/media_player.onkyo/
Description of problem:
After the upgrade to 0.82.0 i got this message in the log an the system is not starting:
if the configuration is removed, the system works fine.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):The text was updated successfully, but these errors were encountered: