Re: [SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
For anyone finding this thread with similar issues... Well, tired of hitting my head against a brick wall I finally took the plunge and updated my system. Rather than sticking with Ubuntu I've reinstalled the operating system, choosing Lubuntu (14.04) because of its much smaller footprint. I also upgraded to Logitech Media Server 7.8 (note that the last 'official' release 7.7.x won't work on Trusty Tahr 14.04) And Triode's Spotify plug-in now works great. I didn't have to change any network settings in my router, or set-up any special port-forwarding rules. Just worked right away. So I expect the issue was somehow with Squeezboxserver version 7.5.1 running on Ubuntu 10.04. Go figure. Thanks for a great plug-in Triode - great to finally have Spotify on all my Squeezeboxes :) http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=99281 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
Can anyone please help me solve this connection problem (caused by Firewall? Network?) As explained above it appears that the players can't connect to the Helper app, but having tried I can (I'm a bit out of my depth when it comes to network configs and Ubuntu) I could do with some step by step advice about what to do next. My router is a Linksys E4200, the Squeezbox server is Version: 7.5.1 running on Ubuntu 10.04 (I'm wary of upgrading either of these as the set-up works just fine for me) In the router I've tried Single Port Forwarding, Port Range Forwarding, Port Range Triggering and DMZ (see screencaptures below) without really knowing what any of those do. [192.168.0.102 is the IP address of the box running the server and 9005 is the port used by the Heklper App as defined on the plug-in page in the server settings) 16224 I've also tried completely disabling the firewall on the router (something I'm wary of doing!): 16225 Still not working. On the Ubuntu box (i'm a linux newbie so blindly followed lots of googled advice) I've set the path /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotify/Bin/i386-linux/ to allow read/write access from anyone (not recommended, I know but I'm trying anything I can). This includes recursively changing all files in that folder (including spotifyd.exe) I've also checked that this version of Ubuntu does not run a firewall. I'm out of ideas! Could anyone please provide me with some instructions as to how to debug this? Many thanks. :confused: jerome +---+ |Filename: 2014-08-07_1412.jpg | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=16225| +---+ http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=99281 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
Triode wrote: OK this is good - it shows you can connect to the helper app. So the question would be do you see any debug entries when a player tries to connect? If not is the player actually connected to the same network? Hi Triode, I'm sure you've got plenty of more important things to do... :) bt would be very grateful for any advice on this. Many thanks! http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=99281 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
Triode wrote: When you connect to port 9005 do you get an entry in the helper app log - if not then you are not connecting to the help app and you need to look at what you are connecting to! I still suspect a network/firewall issue - please check that this actually connects to the helper app. Hi again Triode. Much appreciate your help with this. Fair comment! I've done my best to confirm that the PaPing utility is indeed connecting to the Helper App... First off I tried on port 9006 (paping 192.168.0.102 -p 9006 -c 4) and got a 'no connection' response, so I then changed the port in the plug-in settings to 9006 and tried again and this time got a successful connection. I then tried (paping 192.168.0.102 -p 9005 -c 4) and got a no connection response - just to confirm that some other app wasn't active on the plug-in's default port. I then returned the plug-in back to its default on port 9005, and once more tried (paping 192.168.0.102 -p 9005 -c 4) and this time it connected once more. I'd say that's pretty certain that it is connecting to the Helper App. For each connection, the helper app log shows the following three lines: [21:19:18.012051] main:539 new connection [21:19:18.012195] main:591 req: (null) res: (null) par: (null) prot: (null) auth: (null) [21:19:18.012234] main:1600 bad request for socket or no track So I do seem to be able to connect but I'm not sure if the log is telling me very much apart fro mthe fact that the connection made isn't what the Helper App is expecting - which in this case makes sense as its just being 'pinged'. Can you recommend anything else? http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=99281 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
Triode wrote: OK this is good - it shows you can connect to the helper app. So the question would be do you see any debug entries when a player tries to connect? If not is the player actually connected to the same network? Not sure which of the lines are debug entries (I've set the Helper App Logging to Streaming debug) Here's what appears when running the test: During the Streaming from spotify phase, the log shows a number of entries under 'music delivery' (with obviously many more frames than copied below): ... [22:02:08.219358] music_delivery:427 called with num_frames: 2048 [22:02:08.219396] music_delivery:577 streamed frames: 12533760 can't write: 0 rate: 67055 / 44100 [22:02:08.220450] music_delivery:427 called with num_frames: 2048 [22:02:08.220486] music_delivery:577 streamed frames: 12535808 can't write: 0 rate: 67066 / 44100 [22:02:08.411757] music_delivery:427 called with num_frames: 2048 [22:02:08.411864] music_delivery:577 streamed frames: 12537856 can't write: 0 rate: 67008 / 44100 [22:02:08.412934] music_delivery:427 called with num_frames: 2048 [22:02:08.412975] music_delivery:577 streamed frames: 12539904 can't write: 0 rate: 67019 / 44100 [22:02:08.413983] music_delivery:427 called with num_frames: 1949 [22:02:08.414019] music_delivery:577 streamed frames: 12541853 can't write: 0 rate: 67029 / 44100 [22:02:08.414072] music_delivery:427 called with num_frames: 22 [22:02:08.414140] music_delivery:577 streamed frames: 12541875 can't write: 0 rate: 67029 / 44100 ... Then in the next, final test phase, when it displays Player can't connect then Unable to stream, the following entries appear: [22:02:08.414206] end_of_track:632 end of track [22:02:08.414237] _streambuf_flush:363 state STREAMING - FLUSHING [22:02:08.414322] _streambuf_reset:84 state FLUSHING - IDLE [22:02:08.421049] main:539 new connection [22:02:08.421310] main:591 req: streamtest.json res: spotify:track:4m1B88bynbZIVnrDsUINYc par: (null) prot: HTTP/1.1 auth: (null) [22:02:08.421419] main:898 streambuf_newstream: streamtest (2) [22:02:08.421453] streambuf_newstream:154 newstream - streamtest (2) [22:02:08.421483] streambuf_newstream:158 state IDLE - WAITING [22:02:08.421600] main:1631 Now playing: Big Pimpin' [22:02:08.453910] main:539 new connection [22:02:08.525527] main:591 req: browse.json res: spotify:track:4m1B88bynbZIVnrDsUINYc par: (null) prot: HTTP/1.0 auth: (null) [22:02:08.525720] main:1050 queuing track browse [22:02:08.525783] process_track:1229 process track [22:02:08.525977] process_track:1253 browse track: ok [22:02:08.576385] music_delivery:427 called with num_frames: 2048 [22:02:08.576512] music_delivery:427 called with num_frames: 2048 [22:02:08.704420] music_delivery:427 called with num_frames: 2048 [22:02:08.706235] music_delivery:427 called with num_frames: 2048 [22:02:08.707947] music_delivery:427 called with num_frames: 2048 [22:02:08.709666] music_delivery:427 called with num_frames: 2048 [22:02:08.709751] music_delivery:427 called with num_frames: 2048 [22:02:08.910069] music_delivery:427 called with num_frames: 2048 [22:02:09.103457] music_delivery:427 called with num_frames: 2048 [22:02:09.302853] music_delivery:427 called with num_frames: 2048 [22:02:09.503249] music_delivery:427 called with num_frames: 2048 [22:02:09.702655] music_delivery:427 called with num_frames: 2048 [22:02:09.903051] music_delivery:427 called with num_frames: 2048 [22:02:10.103478] music_delivery:427 called with num_frames: 2048 [22:02:10.302888] music_delivery:427 called with num_frames: 2048 [22:02:10.503283] music_delivery:427 called with num_frames: 2048 [22:02:10.702655] music_delivery:427 called with num_frames: 2048 [22:02:10.903058] music_delivery:427 called with num_frames: 2048 [22:02:11.103461] music_delivery:427 called with num_frames: 2048 [22:02:11.315809] music_delivery:427 called with num_frames: 2048 [22:02:11.503197] music_delivery:427 called with num_frames: 2048 [22:02:11.721170] music_delivery:427 called with num_frames: 2048 [22:02:11.902992] music_delivery:427 called with num_frames: 2048 [22:02:12.124263] music_delivery:427 called with num_frames: 2048 [22:02:12.302660] music_delivery:427 called with num_frames: 2048 [22:02:12.523174] music_delivery:427 called with num_frames: 2048 [22:02:12.702571] music_delivery:427 called with num_frames: 2048 [22:02:12.903000] music_delivery:427 called with num_frames: 2048 [22:02:12.903133] music_delivery:445 streamtest - player did not connect within timeout [22:02:12.903248] music_delivery:564 error writing [22:02:12.903300] music_delivery:566 state WAITING - WRITEERROR [22:02:12.903374] music_delivery:577 streamed frames: 2048 can't write: 0 rate: 0 / 44100 [22:02:12.905768] music_delivery:427 called with num_frames: 2048 [22:02:12.905883] music_delivery:577 streamed frames: 4096 can't write: 0 rate: 0 / 44100 [22:02:12.908405] music_delivery:427 called with num_frames: 2048 [22:02:12.908526] music_delivery:577 streamed frames: 6144 can't write: 0
[SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
Been through many similar posts but can't find a solution... hoping someone can help :) I've installed the Triode plug-in for Spotify and although log-in, metadata and other functionality seems to work fine (i.e. if I select one of my playlists it shows all tracks including album art) but doesn't play. In fact, clicking on the play button moves the 'current track' to the last song in the list - but no audio plays for any of the tracks. Running the self-test shows the following (debug log file attached) 15028 Self Test - Complete Helper App Running: PASS Logged In: PASS Spotify Metadata OK: PASS Streaming from Spotify OK: PASS Then the last test shows: Player unable to connect Then: Unable to stream to player: FAIL Player did not connect to helper app - check your firewall allows the helper app to receive incoming connections from players on the helper app port defined above I've checked my router (Lynksys E4200) to see if it's allowing port 9005 (I even added this port to my list of port forwarding - on the server's IP address - although my understanding was that this was for external traffic comming in, not internal from within the LAN) I've used PaPing (https://code.google.com/p/paping/) to check that I can access the server on port 9005 and see no problem there. The server IP on the Helper App port shows a connection with no errors. The Ubuntu Firewall is disabled. Server details: Version: 7.5.1 - r30836 @ Tue Jun 1 05:57:28 PDT 2010 Hostname: jdp-revo Server IP Address: 192.168.0.102 Server HTTP Port Number: 9000 Operating system: Debian - EN - utf8 Platform Architecture: i686-linux Perl Version: 5.10.1 - i486-linux-gnu-thread-multi MySQL Version: 5.1.70-0ubuntu0.10.04.1 Total Players Recognized: 5 I have also disabled FLAC for Spotify in Advanced File Types, as some people suggested that worked for them. Any ideas? +---+ |Filename: spotifyd.log.txt | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=15028| +---+ http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=99281 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] Triode Spotify plug-in Player can't connect, Unable to stream
Triode wrote: This looks like a network or firewall issue - the player is not connecting to the helper app. Can you check that you can access it from a network connected device on the same network as the player? What do you see if you run wireshark on the server - do you see a player trying to connect? Thanks for the prompt reply. As I mentioned, I've successfully connected to the server on port 9005 from a network connected device on the same network - running PaPing on a windows machine on the same network I get this: C:\paping 192.168.0.102 -p 9005 -c 4 paping v1.5.5 - Copyright (c) 2011 Mike Lovell Connecting to 192.168.0.102 on TCP 9005: Connected to 192.168.0.102: time=2.00ms protocol=TCP port=9005 Connected to 192.168.0.102: time=2.00ms protocol=TCP port=9005 Connected to 192.168.0.102: time=2.00ms protocol=TCP port=9005 Connected to 192.168.0.102: time=2.00ms protocol=TCP port=9005 Connection statistics: Attempted = 4, Connected = 4, Failed = 0 (0.00%) Approximate connection times: Minimum = 2.00ms, Maximum = 2.00ms, Average = 2.00ms where 192.168.0.102 is my squeezeserver's IP address. Re. wireshark. I've never used it before but a quick google suggests it's used by hackers to intercept packets (!) What should I do with it? What am I looking for? Any instructions would be great, thanks :) http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=99281 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
[SlimDevices: Plugins] Advanced Alarm / Timer plug-in
Can anyone tell me if there's a thirty party plug-in that will automate different squeezebox devices (either turning them on and off or setting their volume to 100 and 0) according to the time of day? Here's my usage scenario: I have a squeezebox in my bedroom. I listen to music at night (sleep timer turns it off and morning alarm turns it back on). This device is the syncmaster for another squeezebox in my bathroom so that when I get out of bed and have a shower the music is already playing in there too. My problem is that my music is playing in the bathroom during the night - unless I manually turn it off (but I then have to turn it back on again in the morning...) Ideally this plug-in would be a mix of Sleep Timer and Alarm so that for different days of the week I could automate the times that my various devices turned themselves on and off. Any help or advice much appreciated! -- baroquedub http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=82393 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
Re: [SlimDevices: Plugins] SqueezeControl for Android announcement and support thread
A big thank you for this great app! Also working well on HTC Desire with SqueezeServer Version: 7.5.0 - r30464. Operating system: Debian - EN - utf8 Platform Architecture: i686-linux Perl Version: 5.10.1 - i486-linux-gnu-thread-multi MySQL Version: 5.1.41-3ubuntu12 Four players all recognised and being controlled: 2x Squeezebox Classic 1x Duet Receiver 1x SqueezePlay I've read through all the posts and would agree with the following (plus a couple of thoughts of my own): * 'tab at the side' browsing of long lists would be excellent * a volume control like the Controller (for visual feedback) * a preferences setting for where the files are downloaded * (mentioned before) menu\save to phone saves the file with .null as the extension. (although download after long press works fine) * better download notification - percentage ? More evident 'download complete notification ? * after keyboard search, closing the keyboard doesn't close the search string overlay - so that the results are obscured. (I realise the back button on the phone makes it disappear but it seems an unnecessary additional button press) * and the killer feature: streaming functionality on 3G (Yes please!) Would all this need at the client end be to route incoming traffic to the wifi router to the server IP (on Port 9000) ? If so why is it not yet possible? Has anyone tried this and can give instruction? I'm probably not a good enough programmer to get involved directly but am more than happy to bug test, etc. Would be happy to rework some of the UI graphic elements elements too. I'm not 100% convinced about the green icons (but I guess that's down to personal taste!). Just say if you need help with anything. Thanks again. great work :) -- baroquedub http://baroquedub.co.uk/ baroquedub's Profile: http://forums.slimdevices.com/member.php?userid=20938 View this thread: http://forums.slimdevices.com/showthread.php?t=62581 ___ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
