well, still hasn't failed with the latest 4.0.0. So good? :)
eradicatore's Profile: http://forums.slimdevices.com/member.php?userid=2553
View this thread: http://forums.slimdevices.com/showthread.php?t=111884
__
mherger wrote:
> > I checked your log and don't see any reason why that should fail...
> the
> > file as logged looks perfectly fine, I can parse it no problem. I have
>
> > no clue why that fails :-(.
>
> I just released Spotty 4.0 which would handle this case slightly
> differently. It's m
mherger wrote:
> >
> {"username":"myusername","auth_type":1,"auth_data":"QVFER283Vm.k="}
>
> Would you mind sharing the full log file with me? Non edited and all?
> I'd like to understand why your data would fail to parse as JSON.
>
> --
>
> Michael
sure, sent
---
the credentials I was expecting to see preserved. But this time there
are none in Cache/spotty/*
Admin@MyNaS:/volume1/@appstore/SqueezeCenter/Cache/spotty/files$ ls
Admin@MyNaS:/volume1/@appstore/SqueezeCenter/Cache/spotty/files$ cd ..
Admin@MyNaS:/volume1/@appstore/SqueezeCenter/Cache/spotty$
Ok, I just linked two players together while one was playing spotify and
that may have been the cause of this failure. It failed right away
after that.
Log here:
[20-04-01 10:45:07.6046] Plugins::Spotty::AccountHelper::getCredentials
(284) Corrupted credentials file discovered. Removing config
dang, interesting that it hasn't failed yet. Keep checking every day.
eradicatore's Profile: http://forums.slimdevices.com/member.php?userid=2553
View this thread: http://forums.slimdevices.com/showthread.php?t=111884
__
mherger wrote:
> You don't need the helper plugin. It's for AARCH64 CPUs only, but you're
> using x86_64, aren't you?
I'm running LMS on this:
DS1511+ Intel Atom D525 Dual Core 4 Yes X86 DDR2 1 GB
Not sure if that's 64 bit?
Still no failures, go figure.
so far this morning, still looks to be working...
eradicatore's Profile: http://forums.slimdevices.com/member.php?userid=2553
View this thread: http://forums.slimdevices.com/showthread.php?t=111884
___
mherger wrote:
> > I don't know of any backups of this in Synology unfortunately. Yea,
> I
> > would agree. This looks like the new auth json. Can you give me a
> test
> > build to keep the old corrupt one around? I can wait for it to fail
> > again.
>
> Please add http://www.herger.net/sli
slartibartfast wrote:
> This is a problem I used to see fairly regularly. The configuration file
> gets removed so there is no way to know how it got corrupted. It has
> been quite a while since I experienced this though.
>
> Sent from my Pixel 3a using Tapatalk
Note my LMS (synology) is NOT t
mherger wrote:
> > It looks like fine json (I stubbed out the auth data just in case for
> > now, but just lots more chars)
> >
> > {"username":"mynamehere","auth_type":1,"auth_data":"QVFxyzxyz="}
>
> I guess that's the new credentials you got, not the broken one? Would
> you have backups you
mherger wrote:
> > This is a problem I used to see fairly regularly. The configuration
> file
> > gets removed so there is no way to know how it got corrupted. It has
> > been quite a while since I experienced this though.
>
> Hmm... I should probably change the code to keep the previous versio
mherger wrote:
> > I'm not really sure what file I'm looking for or where to look. I'm
> > ssh'ed in though. Here is a list of all files in that area.
> Anything
> > you see of interest?
>
> It would be in Cache/spotty/*/credentials.json.
>
>
> --
>
> Michael
It looks like fine json (I
mherger wrote:
> > "Plugins::Spotty::Plugin::getCredentials (518) Corrupted credentials
> > file discovered. Removing configuration."
>
> Could you see whether you have a backup copy of that file? I'd be
> interested in understanding in what way that file was corrupted.
>
> --
>
> Michael
Note that was when I was just working to reauth my spotty again with the
spotify app. Right now spotty is auth'ed and working on all players I
checked.
One thing that I was unsure of. When I go into spotify, I get lots of
options of what player to authorize, and one of those is a generic one
Here is an interesting line:
"Plugins::Spotty::Plugin::getCredentials (518) Corrupted credentials
file discovered. Removing configuration."
See below log
Code:
[20-03-27 10:42:04.0051] Slim::Utils::Timers::__ANON__ (273) Error: Timer
Plugins::Spotty::Connect::Daemon
mherger wrote:
> > Has anyone seen this issue where the Spotty plugin will work for a
> > few days, but then need you to reauthorize it again? Here is my log,
> > and my LMS information. I run it on a synology NAS, and I have a mix
> of
> > real SB's and some piCorePlayers. I am using Spotty
Hi,
Has anyone seen this issue where the Spotty plugin will work for a
few days, but then need you to reauthorize it again? Here is my log,
and my LMS information. I run it on a synology NAS, and I have a mix of
real SB's and some piCorePlayers. I am using Spotty version 3.1.3
Logitech Media
Thanks for all the hard work on this player, I needed to replace my
dying SB Duets so I decided to do this for the main audio distribution
area I have.
29817
+---+
|Filename: box.jpg
I've used nmap and mdns (avahi) to find pi's before, but I can't seem to
do this with picoreplayer. Is there something I'm missing? It doesn't
look like the picoreplayer tinycore image is running any mdns? or if it
is what is the type I should be searching for?
Justin
--
I purchased this device for $15:
https://www.amazon.com/gp/product/B00MDW602K/ref=ppx_od_dt_b_asin_image_s00?ie=UTF8&psc=1
And I cannot seem to find a way with picoreplayer 5.0.0 to boost the
audio output of this i2s device. This seemed like a similar post:
https://www.raspberrypi.org/forums/
Hi,
I have recently started having pandora give the error
"PANDORA_Unknown error: 1034" on my 3 picoreplayer's. Pandora works
great on my other 10+ regular Squeezebox'es, and I logged in to check
that pandora was set to "enabled" in mysqueezebox.com for these players.
It was. The 1034 error read
22 matches
Mail list logo
