Integration fails to setup if AVR is off when integration starts #48
Comments
|
Does this mean your AVR can be turned off (ie. standby) by the integration when it is on, but never turned on if it is standby? A debug log of a successful setup and an unsuccessful setup would probably help me better understand what is going on here, and whether the issue can be worked around. |
|
No, it turns off and on just fine, however if it is in off (standby) and I restart home assistant, it the integration will fail to locate my AVR and failed to initialize the integration. If ai turn the AVar on manually and restart hone assistant with the AVR on, then it initialize normally. |
|
Ok, so it sounds like your AVR doesn't respond to one or more query commands that the integration sends on integration setup, when the AVR is in standby. Can you enable debug logging from the integration page on your HA instance, then reload the integration instance (via the dots menu)? Then disable debugging, save the downloaded log, and post the relevant excerpts from the log. Hopefully I can work out which command(s) your AVR is not responding to. |
|
home-assistant_pioneer_async_2024-11-12T15-13-04.626Z.log Here is the debug log. I've tried to remove as much of the other integrations as possible. |
|
For your device |
|
Hia, it seems I'm having the same issue as the OP, but mine also disconnects when it's on standby after a long time. The time of how long it will be controllable until it disconnects is unknown to me. When it does disconnect it spits out... ... every few minutes. I can get it working again if I turn on my receiver and reload the integration. |
|
PR crowbarz/aiopioneer#39 might help with reconnects, but it can't be merged at the moment because it breaks zone detection on other AVRs. It would help if you could enable debug logging to ascertain what is happening in the integration when the disconnects occur. To enable debug logging, add the following logging config to |
|
This is what I got: HA History: HA Core Log: I just realized that it never detects when I turn off the receiver. I turned it off at around 10 am. |
|
Maybe this integration shouldn't try to re-detect after initial setup has been completed. If a user needs to make a change they can always remove the device and re-add it again. |
The polling interval could be increased to rely more on events raised by the AVR itself. Problem is, these older AVRs have some really flaky firmware, even my top of the range amp has some problems in it's IP stack and sometimes doesn't raise events at all, so without the polling, things that I actually use (detecting the number of channels a audio source has for example) actually sometimes never updates. And that's just because the AVR never raises an event to say something has happened. I think I've said this before somewhere, but if you have a serial port on the back of the device, you could use a bridge like ser2net instead. |
This reconnect issue looks to me like a different issue to the OP's issue. In the OP's case, the AVR does respond on the network, but the integration disconnects from the AVR because it does not respond to the initial commands that are sent by the integration. In your case, the AVR completely stops responding and becomes unreachable on the network. I logged #51 to track this issue separately. |
|
@PhAzE-Variance have you tried enabling the |
|
I tried it with the volume option disabled, The integration will complete, then it becomes unavailable after 60 seconds or so. I did some tinkering with my unit through telnet. First, this VSX-1325K is a rebranded VSX-33. ?P (Zone 1 power query) - Responses: PWR1 (off) - PWR1 (on) Volume query, source query, listening mode query, tone query, bass query, treble query, etc, all fail to respond (not errors given). Power commands do work from standby: I'm not sure if these are the commands this integration is using, but the power state for sure doesn't detect correct as is when the unit is off. After removing the receiver from the integration, I can't seem to add it back in at all when its on or off and with settings enabled or disabled for source and volume scanning. |
|
They are indeed the power commands and queries that are used by the integration. The 0.9.2 release should help with this issue. In this release, if a zone is discovered to be off on integration startup, then the integration does not send any further queries for that zone. Additionally, it sends 4 system query commands to collect AVR system information, but a response is expected only from |
|
Just updated to 0.9.2, and enabled skip audio in the config. I turned off the ARV and restarted home assistant, and it appears that it was able to startup properly now, maintaining the originally discovered items. It also doesn't seem to go into an unavailable state anymore, so the power commands work while off. Thank you! |
Love this integration for my older Pioneer VSX-1325K. The only issue I'm coming across is that the integration will fail to setup if the receiver is off (but has network standby enabled). My server updates every night or two so this integration spends most of the time in a failed state.
Receiver: VSX-1325k
Standby: Enabled
IP: Static
Are there any settings in the integration that can be changed to detect the receiver in standby mode upon initialization?
The text was updated successfully, but these errors were encountered: