-
Notifications
You must be signed in to change notification settings - Fork 3
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
Pause commands aren't received and/or passed to Spotify from HomePod mini or Apple TV #15
Comments
Yes, that would be worth a log because "pause" command from remote should be handled |
While testing I've observed three distinct states after I start playing. Here are the states and the results when I tap the top of the HomePod in an attempt to pause:
I don't know what triggers state 1; 2 and 3 are the most common. Most of the time it starts up in state 2 and I can generally get from state 2 to 3 by skipping a track. If things are in state 2, it won't change to state 3 during normal playback -- the track skip is required. Unfortunately I don't see anything happening in the logs the moment I tap the top of the HomePod unless it's in state 1. When I run in For what it's worth, all my devices are on the same subnet, so I don't think there should be any routing issues. I also don't have any special firewall configuration on the Raspberry Pi. Any thoughts on what else I can do to figure out why these commands aren't being received? Log 1
|
I'm a bit confused about the "states" and the logs. What happens if you just do a play and do not touch the HomePod? What type of log do you have? |
Sorry about that, I must not have done a good job of explaining. The states in the table refer to the behavior of the HomePod after I start playing to it via SpotConnect. I noticed while testing that the behavior wasn't consistent, which is why I ended up with that list.
To be clear, I'm always starting playback fresh from the devices menu in Spotify; I haven't gotten to the point of trying to resume playback by tapping the HomePod since I can't yet tap it to pause.
I'm obtaining logs by interactively running Hopefully that clarifies things, but let me know if you still have questions. 🙂 |
It does but that's surprising to see a few fails/log errors when just trying to play. Do you have other devices like an AirPort express? What are logs on your ATV? |
Ah, no, that log exerpt is from the one time I tried to pause and Siri activated. Normally there aren't errors when I just start playing.
The only other first-party devices I have are Apple TVs (and Macs). I also have Aether Cones, which support AirPlay. I'll do some testing with those and provide info on whether pausing works and any differences in logging. |
Ok, so just to be 100% when playback in normal case, there is nothing weird in the log? Sorry, this is confusing 😄 |
No worries! During normal playback, the debug log looks perfectly ordinary to me, and if I search for "error", nothing turns up. |
I just tested with the Apple TV 4K (the only Apple TV I can test with at the moment since I can't pair the ATV HDs yet 😉) and pausing doesn't work with it either. Just like the HomePod, when I hammer on the pause button, absolutely nothing appears in the log to indicate any awareness of the action. |
I was able to test with an Aether Cone today and something was actually recorded in the log! However, playback didn't pause. (I also opened #17 because the audio never played correctly… no idea whether that's related to the lack of response to the playpause event.)
📃 Longer log excerpt
|
Version 0.1.4 should address the Aether Cone play/pause |
Definite progress with 0.1.4! However, I'm consistently only able to pause/resume once. After resuming playback by tapping on the Cone's button a second time, SpotRaop resumes playback but gets into a weird state where:
For both logs, once commands from the Cone stopped being received after the pause/resume, I disconnected via the Spotify devices menu and eventually had to break to quit. The difference is what I did immediately after disconnecting:
📃 Log 1
📃 Log 2
|
You're right indeed, I've been a bit careless with that part of the code where there was a deadlock due to use of recursive mutex (if that sort of things rings a bell for you). Should be fine in 0.1.5 |
0.1.5 is working great with the Cone! I retested with the HomePod just in case but everything is exactly the same as in the original report. Nothing is ever logged when I tap the top of the HomePod. |
When I tap the top of the HomePod mini, I expect the stream to pause. However, SpotConnect currently just keeps playing. (The playing indicator light turns off until the next track starts.)
For what it's worth, volume up/down is handled correctly.
Please let me know if you need any logs or other information. Thanks!
The text was updated successfully, but these errors were encountered: