MusicCast Yamaha R-N1000A discovered immediately on 2.8.1 but delayed or missing on 2.9.0 after power cycle

[isanto1306]

What server version of Music Assistant has the issue?

2.9.0

How is the MA server installed?

Docker Container

Mandatory: Carefully read the Troubleshooting FAQ and confirm that

• I have examined the logs and tried to resolve this issue
• I have fixed any errors or warnings in the logs that relate to tags
• I am not running MA across a VPN, VLAN, subnet, behind a firewall, or using local SSL or have any other complex network setup
• I am not using or have disabled tools such as AdGuard, Pi-hole or pfSense and retested
• I have checked my network setup to ensure mDNS/multicast is not being blocked
• I have reviewed the Open and Closed Issues and Discussions
• I have reviewed the applicable player or music provider documentation
• I have reviewed the MA Status Page
• I have tried restarting MA and rebooting the host

As Applicable: Carefully read the Troubleshooting FAQ and confirm that

• If using HA, I have confirmed the internal URL is set correctly
• I have tried a wired connection for issues related to interrupted or poor playback quality
• If the problem relates to a device then I have checked the device settings
• If it is a frontend issue, I have tried a different widely used browser
• For voice problems, I have sought help elsewhere before returning here
• For playback problems, I have recycled power to the physical device

The problem

After upgrading from Music Assistant 2.8.1 to 2.9.0, my Yamaha R-N1000A (MusicCast) is no longer discovered reliably after a power cycle.

My setup uses a Yamaha R-N1000A connected via wired LAN with a static DHCP reservation.

The Yamaha is completely powered off every night using a smart plug. When power is restored, Music Assistant is automatically restarted.

With Music Assistant 2.8.1, the Yamaha is discovered almost immediately after startup and Plex Connect attaches correctly.

With Music Assistant 2.9.0, the Yamaha is sometimes discovered much later or not immediately. The logs show:

Player DCF51B5F11F4___main not found yet, waiting for PLAYER_ADDED event

Other devices such as AirPlay devices, HomePods and LG TV players are discovered while MusicCast discovery appears delayed.

Downgrading back to 2.8.1 immediately restores the previous behavior.

The hardware, network, DHCP reservation, firmware and Docker configuration are identical. Only the Music Assistant version changes.

Important:
This issue only appears on Music Assistant 2.9.0.

Downgrading to 2.8.1 immediately restores normal MusicCast discovery with the Yamaha R-N1000A.

How to reproduce

1. Install Music Assistant 2.9.0 in Docker.
2. Yamaha R-N1000A connected via LAN with static DHCP reservation.
3. Power off the Yamaha completely.
4. Power on the Yamaha again.
5. Restart Music Assistant.
6. Observe that MusicCast discovery is delayed or the Yamaha is not immediately available.

Expected behavior:
The Yamaha should be discovered immediately as it is with Music Assistant 2.8.1.

Observed behavior:
Music Assistant waits for PLAYER_ADDED and the Yamaha appears later than expected or is temporarily unavailable.

Music Providers

Plex Media Server Library

The issue is not related to the music provider itself.

The problem occurs with MusicCast player discovery (Yamaha R-N1000A).

Player Providers

MusicCast

Additional player providers installed:

• AirPlay
• Chromecast
• DLNA
• Plex Connect

The issue appears specific to MusicCast discovery.

Full log output

I no longer have the full 2.9.0 log export because I downgraded back to 2.8.1 after testing.

Relevant startup log excerpts are included in the report and show a difference between 2.8.1 and 2.9.0 MusicCast discovery behavior.

If needed, I can reproduce the issue again on 2.9.0 and provide a full log export.

Additional information

2.8.1

11:48:00.393 Loaded player provider MusicCast
11:48:00.608 Player registered: DCF51B5F11F4___main/Wohnzimmer Hi-Fi

The Yamaha is discovered almost instantly.

2.9.0

Player DCF51B5F11F4___main not found yet, waiting for PLAYER_ADDED event

Downgrading from 2.9.0 back to 2.8.1 immediately restores normal behavior.

Environment:

• Docker Container
• ZimaOS
• Host network mode
• No VLANs
• No VPN
• No AdGuard or Pi-hole affecting local discovery

What version of Home Assistant Core (if used) are your running

No response

What type of installation are you running?

Other - Please do not select this as support is only available for the above two options

On what type of hardware are you running?

Generic x86-64 (e.g. Intel NUC)

Have you included ALL of the information specified in the Troubleshooting FAQ or explained why you cannot

• Yes

[github-actions]

⚠️ Issue Template Validation

Thank you for reporting this issue! However, there are some problems with the issue template:

• Please ATTACH the log file instead of pasting it. See instructions in the template.

Please update your issue with the missing information. Providing complete information helps us resolve issues faster. See the Troubleshooting Guide for more details.