-
Notifications
You must be signed in to change notification settings - Fork 5
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
AVR not reachable any more #79
Comments
I'd guess this is probably similar to this: v3 relies on the YXC API, which appears to not be available on some receivers... I'll likely end up rolling this back as it seems the number of receivers that doesn't support this is higher than I had anticipated. In the meantime, if |
Same issue for me. Rolled back to 2.1.1 (I have a RX-V677) |
Just adding this here, also had to roll back to 2.1.1 with the same error as reported above. Working in 2.1.1 |
also needing to roll back to 2.1.1 for RX-V673 |
Also had to roll back for RX-A1020. |
hi, |
Hello!
We have been working together on the issue with the error messages in the log. Since we fixed the error message, I was not able any more to access the AV receiver in the home app on my phone. I just gave a try today to switch back to older versions to see if it is working fine there (except the error messages in the log file) - and yes, it works fine again, so it somehow has something to do with the version.
With version 2.0.6, the connection works fine again, as it had been.
When updating to 2.1.1, I saw a message that I have to add the device as an extra one in my home app - with setup code. I did that, and it worked fine too.
Updating back to 3.0.1, when starting the server (AV device is running), I get this error message:
Failed to get system config from AV Receiver. Please verify the AVR is connected and accessible at 192.168.1.103
What can I do here? The IP address is correct, this is how the config looks like:
The text was updated successfully, but these errors were encountered: