Paul Webster wrote:
> Download and install PuTTY
> https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
> Then run it and open a session (login) to your pCP IP address.
> Login using the default pCP credentials (change the password via pCP
> Beta mode ... Main/Security page).
Thank y
Paul Webster wrote:
> The user is tc not admin
> See https://docs.picoreplayer.org/how-to/access_pcp_via_ssh/
Thank you again Paul. Typing 'date' now gives me 1st Jan 1970, both
before and after - no surprises there.
But how to force correct date/time?
Paul Webster wrote:
> Download and install PuTTY
> https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
> Then run it and open a session (login) to your pCP IP address.
> Login using the default pCP credentials (change the password via pCP
> Beta mode ... Main/Security page).
Thank y
Paul Webster wrote:
> By default (at least it is how mine is setup and I do not think I
> changed it) pCP gets the time via ntp from pool.ntp.org
>
> It does this via a script /usr/bin/getTime.sh
>
> If your networking is taking a very long time to come up when rebooting
> pCP then this can fa
expectingtofly wrote:
> There is obviously a problem with your LMS install. Probably
> corruption. I'm not sure what the answer is. I would wipe the sd card
> and install all picoreplayer from scratch again. Although I presume you
> have already done that?
>
> It might be worth creating a ne
garym wrote:
> what do you see when you go to the piCorePlayer webGUI> main page,
> Diagnostics button >> select "Rasberry Pi" in the top line menu, then
> scroll to the bottom. You should see this if you're reaching the
> internet.
>
> 35034
This is what I get and similar to yours - so all s
Many thanks to everybody who has come up with useful suggestions on
'rebooting', 'restart' and more which I have now followed. I have even
re-downloaded piCorePlayer/LMS to my Raspberrypi - unfortunately still
with no success in solving the following 'warning' at the top of the
Plugin Tab page -
expectingtofly wrote:
> Looks like something has gone wrong with your LMS, it can't open a
> socket to call out to the internet.
> Have you tried rebooting your server?Hopefully its as simple as
> that, however it may be something has got corrupt and you need to
> reinstall LMS
Sorry to be
bpa wrote:
> A common reason for connection timeout is LMS or OS not up to date with
> SSL.
>
> What version of LMS and what version of IO::Socket::SSL as shown in
> WebUI Settings/Information (should be about 2.06)
>
> edit:
> In a Dec 2020 post you say updated to LMS 8.0 - that may be margin
Paul Webster wrote:
> That could be a temporary networking problem but it might be a more
> fundamental problem with https support in your setup.
> Probably best to start a new thread and include system info from LMS
> Settings/Information page ... in particular the OS and SSL info.
Have follow
Been successfully using BBC Sounds plugin, via RaspberryPi/piCorePlayer
and SQB radio, for months until recently when I get a "Connect timed
out" on accessing 'Stations & Schedules' through iPeng.
If I bypass iPeng and access the LMS web screen directly via the
piCorePlayer, I notice that if I op
Paul Webster wrote:
> Unlikely to be an iPeng issue but you can check by using the regular LMS
> web interface.
> If it fails there then enable logging on plugin.bbcsounds and post the
> output in BBC sounds thread.
>
> If it only fails when being initiated from iPeng then will need some
> iPen
Have been using iPeng, RaspberryPI/piCorePlayer, BBC Sounds plugin with
a SQB radio for months now with no problem - until today
I am getting a 'Connect timed out' each time I go for 'Stations &
Schedules'. Does anyone have a solution please?
BUG FIXES:
- Fixed an issue preventing some streams not playing outside of the
UK
Wonderful - thank you for your quick action.
fmanchu's Profile: http://forums.slimdevices.com/member.php?userid=33960
View this
slartibartfast wrote:
> What are you trying to play? I just tried the Six O'clock news from 2016
> and that played.
>
> Sorry. I should have been more specific.
>
> 'Natural Histories-Fleas' from today (Sunday) on BBC 4. However, I find
> that this is a repeat from November 2015 which is where
I have recently updated my hardware to a rPi4B and LMS to v8.0 and am
enjoying the new possibilities, for me, of BBC Sounds, now that BBC
iPlayer is apparently nearing its end.
All is well except for one strange defect under 'listen again'.
Programmes from around 2016 (according to my limited res
[]Triode laid the groundwork, I maintained it in his absence.
Yes, a sad day for us BBC iPlayer (& extras) dependents. Now I really am
forced to update to LMS v8 (and BBC Sounds) which for me, also will
require a hardware update. Such is life!¨
Thank you again for your most excellent work in keep
slartibartfast wrote:
> It never ceases to amaze me how you and other plugin developers keep on
> top of all the changes the BBC and others inflict on us. It is much
> appreciated.
>
> Sent from my Pixel 3a using Tapatalk
All, once again, just fine with BBC iPlayer Extras - wonderful. Thank
yo
bpa wrote:
> Details always help.
>
> It means I waste less time locating the issue.
>
> So details like OS, what you did in detail, uk/non-UK, menus etc speed
> things up.
>
> Menus seem to work but playing an item results in 404 - is that what you
> are seeing ?
>
> It looks like BBC ha
>>After BBC made changes and to improve the plugin I took it over but
created a separate repository for new BBCiPlayer versions currently
1.6.8<<
No problem for months but today BBC iPlayer Extras is returning a 404
error. I am running LMS 7.9.1 and BBC iPlayer Extras v3.2.0 and have not
updated
bpa wrote:
> Should be there now - not sure why the previous upload didn't stick.
> Maybe finger trouble rushing things (it's a bank holiday weekend here
> and real life is intruding).
>
> Many thanks for your super quick response, bpa, and on a bank holiday!
> All smiles again here. Great stu
bpa wrote:
> This is the problem documented by mavit 2 posts earlier. Just checking
> whether there is more to the change and whether the suggested patch
> covers all types of program.
>
> I hope to have a quick fix late tonight.
Thank you very much, bpa for your very prompt efforts to get u
Many, many thanks bpa. Once again you have, by some magic, restored my
possibility for listening to BBC iPlayer and iPlayer extra. Your help in
keeping it all running is invaluable. I just needed to update to the
latest LMS version and it was once again smiles all round. Thank you.
Sb42 wrote:
> What is the 'matchbox sized receiver' that you are using?
it is a Speedlink TRAP audio link designed by Jöllenbeck, Germany and
made, of course, in China.
fmanchu's Profile: http://forums.slimdevices.com/mem
bpa wrote:
> The BBC primary business is not supporting 3rd party users of their
> info. BBC sees their user interface as primary and if maintaining old
> feeds takes resources - they will no longer maintain them.
>
> The BBCiPlayer plugin uses an official BBC feed which only provides 7
> days
bpa wrote:
> I have created a test version (1.6.3) BBCiPlayer to solve the issue of
> "Listen Again "programs which don't play and are listed as podcast only
> such as 5Live Fighting Talk and R4's Infinite Monkey Cage.
> To install test version - replace the BBCiPlayer betarelease-repo.xml
> re
bpa wrote:
> If you have HLS as the primary setting for Listen Again preference
> change it to "DASH > HLS > MP3 > FlashAAC".BBC made a change last
> week which broke the HLS part for Listen Again.
Many, many thanks bpa. Now all is OK again. You have been most helpful -
as always. Regards F
VFRBOB wrote:
> [/B][B]
>
> So the BBCiplayer has been working marvelously up until last week. I
> tried to listen to the Folk show on Radio 2 Wednesday evening and the
> Touch just sat at "connecting" status for about five minutes until I
> gave up. I thought it might just be one of those thing
Man in a van wrote:
> a search in thread always helps, I used
>
>
>
> and top of the list was
>
> http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0/page71
>
> Scroll down the page to post#704
>
>
> Ronnie
>
> It looks like Putty was used to ssh into the nas, but I
Bery wrote:
> I had to edit Sources.list for 'apt'. I'm up and running now.
I am having the same problem with my ReadyNAS Ultra 2. However, I need
help with your solution. Could you please elaborate a little on how to
"edit Sources.list for 'apt'"? Thank you.
--
30 matches
Mail list logo