[Announce] Community Firmware for Squeezebox Radio/Touch/Controller and LMS 8

[ralphy]

Just posting that it doesn't work for you helps no one.

Those having issues, please set the Player.Firmware logging level to Debug in LMS and wait until the server attempts to download the firmware again.

Then go to the Settings->Information Tab in LMS and at the bottom click the Zip Archive at the end of the Logitech Media Server Log File line and attach the zipfile to a post.

I've found this error happens when the checksum doesn't match after downloading the firmware file and corrects itself after the next attempt.

[ralphy]

Correct. I just had to turn off LMS to check that ! The blue icon looks rather clearer than I remembered...

I still think it would be a useful addition to the new firmware.

Sent from my Pixel 3a using Tapatalk

We can certainly apply that change for the next release. Where was this discussed?

We should start getting into the habit of creating issues on github, either in the SqueezeOS-SqueezePlay Issues or SqueezeOS Issues section.

I'm not prepared to rebuild the firmware, for every cosmetic change request. For now, I will wait until either a significant issue is identified, or until there are a several outstanding changes waiting.

[kidstypike]

Just posting that it doesn't work for you helps no one.

Those having issues, please set the Player.Firmware logging level to Debug in LMS and wait until the server attempts to download the firmware again.

Then go to the Settings->Information Tab in LMS and at the bottom click the Zip Archive at the end of the Logitech Media Server Log File line and attach the zipfile to a post.

I've found this error happens when the checksum doesn't match after downloading the firmware file and corrects itself after the next attempt.

Well how would a non geek know what to do if things didn't go as per you instructions?

Maybe you should append your instruction post with a "What to do if things don't go according to plan" section?

I'll leave this for the geeks.

Thanks.

[ralphy]

Well how would a non geek know what to do if things didn't go as per you instructions?

Maybe you should append your instruction post with a "What to do if things don't go according to plan" section?

I'll leave this for the geeks.

Thanks.

Thanks for the suggestion. I've updated the initial post.

My comment was not directed at any one member, just a general observation, that happens in the forums here all too often.

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> Me too. Trying to update a Squeezebox Radio and running LMS on PiCore
> player.

Is everybody having these problems running LMS on pCP?

--

Michael

[slartibartfast]

We can certainly apply that change for the next release. Where was this discussed?

We should start getting into the habit of creating issues on github, either in the SqueezeOS-SqueezePlay Issues or SqueezeOS Issues section.

I'm not prepared to rebuild the firmware, for every cosmetic change request. For now, I will wait until either a significant issue is identified, or until there are a several outstanding changes waiting.

It was discussed here

https://forums.slimdevices.com/showthread.php?p=993485

Sent from my Pixel 3a using Tapatalk

[kidstypike]

> Me too. Trying to update a Squeezebox Radio and running LMS on PiCore
> player.

Is everybody having these problems running LMS on pCP?

--

Michael

Me, yes, see sig.

[slartibartfast]

> Me too. Trying to update a Squeezebox Radio and running LMS on PiCore
> player.

Is everybody having these problems running LMS on pCP?

--

Michael

Looks like this one was Ubuntu.

https://forums.slimdevices.com/showthread.php?p=1000242

I updated my Controller successfully with LMS on Raspbian (or whatever they call it now)

Sent from my Pixel 3a using Tapatalk

[slartibartfast]

Me, yes, see sig.

Does the player revert to the original firmware when the update fails? If so I'll try updating my Touch.

Sent from my Pixel 3a using Tapatalk

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

>> Me, yes, see sig.Does the player revert to the original firmware when the update fails?
> If so I'll try updating my Touch.

Failed update would be a no-op. Disabling the plugin should get rid of
the notification, too.

--

Michael

[kidstypike]

Does the player revert to the original firmware when the update fails? If so I'll try updating my Touch.

Sent from my Pixel 3a using Tapatalk

Yes, just press the back arrow, mine reverted back to 7.8.0 r16754.

You may need to reboot the Touch to get audio.

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

>> Me too. Trying to update a Squeezebox Radio and running LMS on PiCore
>> player.
>
> Is everybody having these problems running LMS on pCP?

Ralphy - I'm pretty sure these FW updates fail on pCP because it tries
to tell the players to download the firmware directly, whereas LMS in
most other environments would download the file first, then serve it
from LMS to the player. The problem is that these firmwares are https
downloads. And the players can't handle https.

https://github.com/piCorePlayer/lms-update-script/pull/2

I believe I suggested doing the direct download at the time to save the
precious diskspace in a pCP environment.

--

Michael

[mherger]

[Announce] Community Firmware forSqueezebox Radio/Touch/Controller and LMS 8

> I believe I suggested doing the direct download at the time to save the
> precious diskspace in a pCP environment.

Is there a way to tell pCP to exclude some files from being backed up? I
know there's filetool or something to tell it what to _include_. But
exclude?

--

Michael

[Bipox]

Then go to the Settings->Information Tab in LMS and at the bottom click the Zip Archive at the end of the Logitech Media Server Log File line and attach the zipfile to a post.

I've found this error happens when the checksum doesn't match after downloading the firmware file and corrects itself after the next attempt.

When will the next attempt happen? Or do you mean an attempt on the user's side?
for now the only line concerning the firmware I see is

[20-12-21 21:33:08.3098] Slim::Utils::Firmware::need_upgrade (354) baby doesn't need an upgrade (has: 7.7.3 r16676, server has: 7.7.3 16676)

(I was on 7.8 but tried going back to 7.7 to see if it changed anything)

Is everybody having these problems running LMS on pCP?

--

Michael

No I'm running LMS on Ubuntu 20.04, trying to update the firmware on a Squeezebox Radio.



EDIT: and now suddenly it seems to work. 5th attempt or so. I haven't changed anything, except activating debugging log.

EDIT 2: the update specified 8.0.1 but after reboot I'm still on 7.7.3

[PaulinPosset]

Just posting that it doesn't work for you helps no one.

Those having issues, please set the Player.Firmware logging level to Debug in LMS and wait until the server attempts to download the firmware again.

Then go to the Settings->Information Tab in LMS and at the bottom click the Zip Archive at the end of the Logitech Media Server Log File line and attach the zipfile to a post.

I've found this error happens when the checksum doesn't match after downloading the firmware file and corrects itself after the next attempt.

Had a second and third attempt with no joy. The download attempt lasted around a second before the ‘attempt failed’ message displayed with nothing downloaded.

Log attached....hopefully!