I have 3 Yamaha AVRs, all configured in Home Assistant and 2 of them work exactly as they should, the third (an RX-A810) has a behavioural problem.
I have the A810 set for 'Network Standby' in order for it to be accessed over the network while 'asleep' and in particular, be turned on and report its state etc. However, after a short period of time being in Standby, it stops responding to any such commands.
By which I mean it can no longer be accessed by HA, nor its own web interface and not even by Yamaha's own mobile apps. It is as if its network interface has shut down - except it still responds to 'ping'. So the interface is still 'up' and functioning but simply not responding to any control attempts. Trying to access its web interface, Safari reports immediately that the device 'dropped the connection' which confirms to me that the device is still on the network, but refusing to respond to control commands.
I have read elsewhere that these problems can arise when there are multiple Yamaha AVRs on the same network, but cannot confirm that.
What I do know is that waking the AVR instantly resolves the problem, but it will re-occur some time after putting it into Standby again, sometimes within a few hours, usually within a day, but infrequently it can be a little longer.
I am firmly of the opinion that this is entirely a Yamaha problem and nothing to do with HA, nor the Yamaha Integration I'm using. However, it occurs to me that there must be many people here using Yamaha AVRs and wondered if anyone has come across this problem and of particular interest would be if anyone has actually found the real reason and can offer a fix.
I also have an RX-A810 and ran into (probably) the same issue. The receiver would just stop responding on the network interface after a while when using the built-in Yamaha integration. I always fixed it with a powercycle which was cumbersome. I don't recall if it still responded to ping.
This was when I started using Home Assistant, before that I had some DIY automation scripts to control the receiver which were very stable, so I made a custom integration that uses the same protocol (YNCA) that my scripts were using. It is a different protocol from what the built-in integration is using. It has been working great ever since.
In case you are interested, the custom integration is called "Yamaha (YNCA)".
It is available in HACS or you can get it from the Git repo
btw I think there was a firmware update at some point which mentioned network fixes or something like that, but I never went back to the built-in Yamaha integration to try.
Hi Michel, we've discussed this before, but it's still happening which is annoying, even though I'm using your Integration.
I don't believe it's anything to do with Home Assistant or the Integration. When it goes deaf like this it stops responding to web connection attempts and even Yamaha's own control apps.
The network is definitely still up and it responds to pings - always. Try to connect to the web interface and it 'drops the connection', so I think the network layer is up and running, but the application layer(s) above that are not running. So nothing apart from basic networking like ping will work.
IMO this is a Yamaha bug and it's not unknown. Often seems to be reported when several Yamaha amps are on the same network.
If you turn it On (from Standby and when it's gone deaf), the full networking is instantly reawakened. Alternatively, as you say, power it off and then back on (starts in Standby), full networking is available and working as it should.
My solution is to power it from a smart switch and use HA to turn it off when the integration reports it as 'unavailable' and back on again after a few seconds. That'll only be about once a day.
Currently just waiting for the smart plug I want to use to be delivered. The automation is ready and waiting for that.
Was wondering though if there was any known actual fix, rather than having to work around the problem as I just mentioned.
AFAIK I am on the latest firmware, but I'll check again just in case.
BTW, I am also using your Integration with an RX-V777 and an RX-A3050, both of which work faultlessly. It's only this A810 that gives any trouble.
I now use an Automation to monitor the A810 and power it off then on again when it goes deaf and also send a notification.
Over the last 2 days it has gone network deaf 5 times and although today there were 3 instances but only 2 yesterday, there is something of a pattern there.
