owntone
Chromecast and mdns errors with JBL Charge 5 wi-fi
Device appears in the Apple Remote app. But when I click on play, it disappears and no sound is ever played. - I haven't deactivated ipv6 nore played with raop.
Here is the log:
[2025-03-17 21:37:33] [ LOG] [ worker (-1)] dacp: Player returned an error for start after pause [2025-03-17 21:37:47] [ LOG] [ worker (-1)] daap: Error: Request to remove non-existent or ad-hoc session. BUG! [2025-03-17 21:38:26] [ LOG] [ player (-1)] cast: Device 'JBL Charge 5 Wi-Fi' could not launch app id '85CDB22F' nor '0F5096E8' - aborting [2025-03-17 21:38:26] [ LOG] [ player (-1)] player: The Chromecast device 'JBL Charge 5 Wi-Fi' failed to activate [2025-03-17 21:38:39] [ LOG] [ player (-1)] cast: Device 'JBL Charge 5 Wi-Fi' could not launch app id '85CDB22F' nor '0F5096E8' - aborting [2025-03-17 21:38:39] [ LOG] [ player (-1)] player: The Chromecast device 'JBL Charge 5 Wi-Fi' failed to activate [2025-03-17 21:38:39] [ LOG] [ worker (-1)] dacp: Speakers de/activation failed! [2025-03-17 21:44:53] [ LOG] [ owntone (-1)] mdns: Avahi Resolver failure: service 'JBL Charge 5 Wi-Fi' type '_airplay._tcp' proto 0: Timeout reached [2025-03-17 21:44:53] [ LOG] [ owntone (-1)] mdns: Avahi Resolver failure: service '94B3F7B1F20D@JBL Charge 5 Wi-Fi' type '_raop._tcp' proto 0: Timeout reached
@dr-leo your issue isn't the same as #1465, so I've moved it here.
@chme I notice the thread no. says -1 - do you know why that might be?
Thanks for your reaction.
I have a pi 4B, Buster, owntone 28.11. Dependencies should be current. I hope that old Buster does not screw up Airplay-2. - Well, this may even be irrelevant...
By way of background: I want to control owntone through Apple Remote app on IOS devices, not just the web interface. So airplay-2 should be the only choice, and Cromecast does not seem to be of interest.
I don't see why Owntone attempts to connect to the JBL speaker via Cromecast in the first place. Does it mask Cromecast devices as Airplay? - Can I tell Owntone to ignore any Cromecast device?
And as I tried to talk to the JBL speaker via Airplay only, I thought the original issue was a better place to discuss this.
I no nothing about "thread no. says -1" you are referring to.
In the meantime, I disabled ipv6 which results in a different log, and the JBL speaker remains visible in the Apple Remote app even when I press play; but it does not play anything.
Besides, I tried to disable RAOP (= Airplay-1?). But Owntone did not even start then. My JBL Speaker is Airplay-2, I think; could be backwards-compatible though... So I wonder if "disable RAOP" is a prerequisite to use this speaker...
Here's the new log:
[2025-03-19 09:19:41] [ LOG] [ player (-1)] laudio: Failed to open PCM or Master mixer element [2025-03-19 09:19:41] [ LOG] [ player (-1)] laudio: Could not open mixer 'default' ('(null)') [2025-03-19 09:19:57] [ LOG] [ player (-1)] cast: Device 'JBL Charge 5 Wi-Fi' could not launch app id '85CDB22F' nor '0F5096E8' - aborting [2025-03-19 09:19:57] [ LOG] [ player (-1)] player: The Chromecast device 'JBL Charge 5 Wi-Fi' failed to activate [2025-03-19 09:19:57] [ LOG] [ worker (-1)] dacp: Speakers de/activation failed! [2025-03-19 09:24:25] [ LOG] [ player (-1)] cast: Device 'JBL Charge 5 Wi-Fi' could not launch app id '85CDB22F' nor '0F5096E8' - aborting [2025-03-19 09:24:25] [ LOG] [ player (-1)] player: The Chromecast device 'JBL Charge 5 Wi-Fi' failed to activate
By way of background: I want to control owntone through Apple Remote app on IOS devices, not just the web interface. So airplay-2 should be the only choice, and Cromecast does not seem to be of interest.
Your controller has nothing to do with what protocol is used for streaming to the speaker.
Does it mask Cromecast devices as Airplay? - Can I tell Owntone to ignore any Cromecast device?
No, OwnTone shows what the speaker is announcing. Some speakers announce both Airplay and Chromecast, then you should see it twice - in the web UI one will be with an Airplay icon, the other with Chromecast. You can hide Chromecast on a speaker level with the "exclude" setting: https://github.com/owntone/owntone-server/blob/master/owntone.conf.in#L381
I no nothing about "thread no. says -1" you are referring to.
My question wasn't to you
Besides, I tried to disable RAOP (= Airplay-1?). But Owntone did not even start then. My JBL Speaker is Airplay-2, I think; could be backwards-compatible though... So I wonder if "disable RAOP" is a prerequisite to use this speaker.
You don't need to change any of this. The reason OwnTone didn't start is probably that you made a syntax error in the config file when you tried disabling it.
The gist of it is that if you aren't seeing the speaker with an Airplay icon in the web UI, then it means that OwnTone isn't receiving an Airplay speaker announcement. No changes you make to OwnTone will fix that.
Got it. So no change to airplay settings. Here is the new log:
[2025-03-19 11:57:17] [ LOG] [ owntone (-1)] cast: Excluding Chromecast device 'JBL Charge 5 Wi-Fi' as set in config [2025-03-19 11:57:50] [ LOG] [ player (-1)] raop: ANNOUNCE request failed in session startup: 403 Forbidden [2025-03-19 11:57:50] [ LOG] [ player (-1)] player: The AirPlay 1 device 'JBL Charge 5 Wi-Fi' failed to activate [2025-03-19 11:57:50] [ LOG] [ worker (-1)] dacp: Speakers de/activation failed! [2025-03-19 11:58:20] [ LOG] [ player (-1)] raop: ANNOUNCE request failed in session startup: 403 Forbidden [2025-03-19 11:58:20] [ LOG] [ player (-1)] player: The AirPlay 1 device 'JBL Charge 5 Wi-Fi' failed to activate [2025-03-19 11:58:20] [ LOG] [ worker (-1)] dacp: Speakers de/activation failed! [2025-03-19 12:03:03] [ LOG] [ player (-1)] raop: ANNOUNCE request failed in session startup: 403 Forbidden [2025-03-19 12:03:03] [ LOG] [ player (-1)] player: The AirPlay 1 device 'JBL Charge 5 Wi-Fi' failed to activate
Any idea what to do to make airplay work or to track down the issue?
If airplay is a no go, one could still consider the Chromecast option at the cost of dropping Apple Remote app access. The web interface would then still be viable. But to do this, we would need to get rid of the laudio / mixer errors shown in my previous comment.
In an exceptionally bold move, I disabled RAOP for the JBL speaker. And now it works!
Even the volume slider in the Apple Remote app is adjusted when I change the volume on the speaker device.
Thanks so much for your help!
I have been using owntone/forked-daap for about 5 years now on a daily basis. Your great work is invaluable to me.
Good to hear it works with Airplay 2. Sounds like the speaker is announcing Airplay 1 (raop) without actually supporting it. Strange, don't think I have come across that before.