4.6 finally solves the restarting daemons issue still apparent in 4.5:
Problem in 4.5 was:
- Choosing SB Radio as Spotify Connect target: Works
- Choosing iPhone as Spotify Connect target: Works
At this point of time the daemon of the SB Radio becomes restarted
4.5 mostly solves a long standing issue I had using Spotify Connect from
iPhone. Still daemons become restarted but this should no longer cause
issues in practical usage.
What I experience now:
- Choosing SB Radio as Spotify Connect target: Works
- Choosing iPhone as Spotify Connect target:
mherger wrote:
> >>
> I'm in the process of (trying to) update spotty to the latest librespot.
>
> Let's hope some of these issues will be fixed once I get there.
Any luck with adopting the latest librespot?
Thanks,
Tom
jotap_66 wrote:
> Did you set the ports correctly in lms Docker package?
> Did you set the puid and pgid correctly? It depends on your Synology
> users account. This is very important for accessing some files. In my
> case my FLAC songs library.
>
Thanks, JP! I set puid to more powerful users
I tested now a bit more:
I can dispatch Spotify audio between any of my six SB radios without any
problem. Only if I dispatch to my iPhone and then back to the Radio I
get an issue (restarting daemon).
My theory is - just a guess:
- In the moment I dispatch audio output to my iPhone the
jotap_66 wrote:
> The issue is when playing a radio o when playing a Squeezebox Radio.?
>
Thanks, JB. I have six Squeezebox Radios, no SB3 like you. So although
we share the same Synology Intel platform and use the same LMS Docker
image something must be different. My family was using Spotify
jotap_66 wrote:
> As I have an Intel Synology, I installed a ”dockerized” version of LMS
> 8.1.1. It is impressive. The integration with streaming (I am using
> Spotify) is perfect. As you tell, It works very well.
>
JP,
As I wrote I'm now as well on Synology Intel Docker. So can you do me
Had a frustrating night with my effort to downgrade Spotty - run into
permission problems, tried to fix but finally still did not get it
working.
And after reading more in the forums I realized it is not worth the
effort as DSM7 will eventually upgrade Perl to an LMS incompatible
version and I
Well, the only folder with "Plugins" is the one I should not mess
around: Cache/InstalledPlugins/Plugins/
I have been running "find . -name Plugins -print" so I'm sure I did not
miss a folder.
The info page of LMS mentions
- Folder for Extras
mherger wrote:
> > What is the best way to install an old plugin manually?
>
> Uninstall the current version using the plugin manager - the settings
> will not be removed.
>
> > Just replace everything below
> >
> /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty
> >
Thanks, Michael.
What is the best way to install an old plugin manually?
Just replace everything below
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty
with the content of Spotty.zip?
Thanks,
Tom
mherger wrote:
> What do you consider a crash? The log says the plugin was restarting the
>
> daemon as it was still running, but seemingly no longer connected to
> Spotify's servers.Then I was mistaken. I assumed the restarts to happen
> because of earlier
crashes.
mherger wrote:
>
slartibartfast wrote:
> Did you try my last suggestion?
> https://forums.slimdevices.com/showthread.php?p=1019859
Yes, thanks. Checking the box to enable monitoring of the Spotty Helpers
does not change the behavior.
The Spotty Helpers are in my case restarted even without this checkbox.
In
I'm still fighting with crashing daemons after upgrading to LMS v8.1.1.
Considering now to roll back to 7.9.
How I can reproduce:
- Start LMS
- Switch LMS to Spotty debug mode
- Switch iPhone in Spotify to Squeezebox Radio: Works as expected
- Switch iPhone back to iPhone audio: iPhone
Hi Michael,
mherger wrote:
> Did you create your own client ID and enter it in the Spotty settings?
Yes. And I can see in the Spotify Developer dashboard that Spotty is
successfully using it.
Thanks,
Tom
loopguru's
I saw my Client ID was not entered so I hit rate limiting. Fixed this.
But main problem persists, seems the Spotty Helpers are crashing.
Attached again a log but enabled Debug mode for Spotty.
+---+
|Filename: LMS81server.log.zip
After Synology upgraded my Perl I had to downgrade it again and used the
opportunity to upgrade LMS to v8.1.1 (Spooty v4.4.9)
Now I get frequent crashes when using Spotify Connect with my SB
Radios.
Last message in the log is "Connect daemon is running, but not
connected". Full log attached.
mherger wrote:
> I'd recommend you update your LMS, see pinkdot's great work
> https://forums.slimdevices.com/showthread.php?108960)
Reinstalled LMS, this time using pinkdot's distribution (had no idea how
simple that is): Everything works again :)
I have not the slightest idea what screwed up
loopguru wrote:
> No other media server running except the Synology one.
I invested some more hours without success. Stopped now all packets on
my Synology except LMS, same issue.
So I do not know where a conflict with another application using
bonjour/avahi should result from.
Without s
Thanks, Michael!
mherger wrote:
> Some other media server, like a DLNA server or similar? Synology NAS
> come with their own.
No other media server running except the Synology one.
mherger wrote:
> The root cause most likely is a conflict with some other application
> using bonjour/avahil
mherger wrote:
> Did you enable media server features on your NAS?
Yes - the standard Synology Media Server is running.
mherger wrote:
> Are you using multiple accounts?
Yes, I configured several Spotify accounts within Spotty
Is there a log file from the Spotty daemon somewhere in the file
I do not know what triggered it, maybe an minor upgrade of my Synology
operating system - but Spotify Connect does not work at all anymore for
me.
My players are vanishing automatically and one option of Spotty
activates itself: "Squeezebox Player im Spotify Connect Modus nicht im
lokalen
Connect works again :)
Synology Intel Pentium N3710
LMS v7.9.1, perl 5.024000 - x86_64-linux
Spotty Helper spotty-x86_64 (v0.12.0)
Spotify share price dropped nearly 5% May 18. Maybe share holders with
Squeezeboxes dropped their investment in anger ;)
mherger wrote:
> > I see that https://api.spotify.com is sometimes hanging on my NAS,
> > regardless what URL path follows. Could it be Spotify blocks me?.
> Could
> > I workaround by getting my own Client Id?
> Spotify seems to have had issues last night (and a few days before,
> too):
>
I see that https://api.spotify.com is sometimes hanging on my NAS,
regardless what URL path follows. Could it be Spotify blocks me?. Could
I workaround by getting my own Client Id?
loopguru's Profile:
To resolve the issue I tried to delete and readd my Spotify account in
the 'LMS Plugins' page. Deleting was possible, but when I wanted to add
my account the web page was hanging for one minute and LMS became
unusable. So I guess this might be caused by the same api.spotify.com
connect issue.
I just logged on to my Synology NAS to see whether it really cannot
resolve api.spotify.com
Two tests:
Code:
> curl https://api.spotify.com/v1/me
{
"error": {
"status": 401,
"message": "No token provided"
}
So this works quick like
After some time using Spotty daily I upgraded today to 2.3.0.
Now playing via Spotify Connect kills LMS, it is simply hanging for a
minute or so.
Same happens if I use Spotty from within iPeng: The Spotty screen in
iPeng shows empty and then LMS hangs for about a minute.
The content in the log
Can't find any flaw in 2.14 :)
Switching from non LMS based devices works with exception of switching
back from Yamaha Musiccast to Spotty. But this seems to be an issue
with Yamaha, if I switch to Raumfeld back and forth it works perfectly.
Brilliant work!
Did I say I just bought three more
In my Spotify App pressing 'Pause' doesn't stop the music.
The log shows no new entry when Pause is pressed.
Tom
--
Spotify on iPhone
Spotty 2.11
LMS v7.9.1- x86_64-linux / Synology
loopguru's Profile:
tfec wrote:
> But switching back to the formerly stopped Squeezeplayer it stays
> muted.
Sounds a bit similar to what I experience. Can you bring the muted
player back by skipping to the next song?
loopguru's Profile:
Can confirm this: 2.1.9 fixed the volume issue. The failure when
switching to non-LMS devices stays as expected.
Tom
loopguru's Profile: http://forums.slimdevices.com/member.php?userid=67725
View this thread:
mherger wrote:
> Hmm... working just fine here. Do you see the same behavior when using
> the Spotify app as a playback target, too? Eg. switching from playing on
> the phone to the Radio and back?
Switching from iPhone to Squeezebox Radio and vice versa works fine.
Except that volume gets set
mherger wrote:
> >- Switching from a non LMS based Spotify Connect enabled player to
> a
> > Squeezebox Radio does not work.
>
> I'm rather sure this isn't true, or I'd have many more complaints.
> Because this would basically mean Connect didn't work at all.
>
> > Instead of
2.1.7 feedback:
- Fixed is the issue that a Radio continues to play after it became
deselected.
- Still open:
- Switching from a non LMS based Spotify Connect enabled player to a
Squeezebox Radio does not work. Instead of continue to play Spotify
stops, chooses "This
Spotty 2.1.6 (like 2.1.5) is severely broken.
- If you select via iPhone Spotify app a Squeezebox Radio, and after
that any other device (iPhone or another Squeezebox Radio) then both
devices are playing. If I jump through my 4 Squeezebox Radios are all
playing.
Here a switch to a
loopguru wrote:
> Switching back to the initial Squeezebox Radio leaves both (!)
> Squeezebox Radios playing.
This is reproducible for me. It even happens if I switch from a
Squeezebox Radio to my Raumfeld Spotify Connect enabled streamer: The
Squeezebox Radio continues to play al
ElFishi wrote:
> since a few days I have problems starting Spotify Connect in the
> morning.
> I need 4 - 5 attempts to connect to my squeezebox with the "connect to a
> device" function of the Windows app.
> [...]
> I the earlier attempts the player name in the menu goes grey for a few
>
mherger wrote:
> v2.1.2 tries to fix the "pause after local track plays" issue. Please
> test.
Fixed now! :)
Tom
loopguru's Profile: http://forums.slimdevices.com/member.php?userid=67725
View this thread:
What's new in 2.2.1?
Tom
loopguru's Profile: http://forums.slimdevices.com/member.php?userid=67725
View this thread: http://forums.slimdevices.com/showthread.php?t=108561
___
slartibartfast wrote:
> What do you have as "stopped" screensaver?
None
loopguru's Profile: http://forums.slimdevices.com/member.php?userid=67725
View this thread: http://forums.slimdevices.com/showthread.php?t=108561
devilsfun wrote:
> after updating to version 2.0.0 (now 2.1.0) the automatic power off
> function doesn't work anymore. Situation bevor updating: after playing
> an audiobook on the squeezebox player it shuts off automatical
> (hibernate) and shows the clock. now the picture of the played audio
mherger wrote:
> > - Only advertise Squeezeboxes anonymously. Playing on a remote
> >Squeezebox seems to have no meaningful use case. Even worse you
> cannot
> >switch off the Squeezebox remotely if you streamed to it in error.
> Unfortunately this isn't possible, as some platforms don't
mherger wrote:
> > Can I enable my Squeezebox Radios as local device only. So Radios
> >vanish in the Spotify app when I leave my LAN?
> No, unfortunately this won't work.
>
> > - If a guest chooses a Radio while being at my home: Can he stream to
> >my Radios even if he is gone?
>
>
Thanks Michael for introducing the multi account feature. Works great!
I have another question where I would need some education
- I realized my Squeezebox Radios at home are still listed as Spotify
Connect devices when I'm traveling abroad. More disturbingly they
really work: I really
BillatLakeGeorge wrote:
> I am not sure what version to use I tried 2 different ones and LMS would
> not let me.
As you are using Synology DS: Here is how you can install 7.9 instead of
the older versions Synology ships by default.
- Navigate to Package Center
- Choose Settings, Beta, Yes I
Feedback to Spotty 1.99.5 and Spotify Connect.
Spotify accounts become somehow screwed up:
- Often Squeezeboxes are not advertised in the Spotify app using
account B although the Radios have been switched from account A to
account B.
- When switching a Radio from Account B to account A
47 matches
Mail list logo
