Bug 14082 – firmware update not showing correct information (custom.baby.*)

Bug 14082 - firmware update not showing correct information (custom.baby.*)

Summary:

firmware update not showing correct information (custom.baby.*)

Status:	NEW

Product:	SB Radio
Classification:	Unclassified
Component:	Settings
Version:	Include FW version in comment
Platform:	PC Other

Importance:	P5 minor (vote)
Target Milestone:	Future
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-16 10:09 UTC by Ben Klaas
Modified:	2012-03-05 21:30 UTC (History)
CC List:	4 users (show)

See Also:
Category:	Bug

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ben Klaas 2009-09-16 10:09:00 UTC

put r7061 as a custom.baby.* in the correct server cache folder

started up SBS, and see that it knows my baby needs an update:
[09-09-16 12:04:44.0324] Slim::Utils::Firmware::need_upgrade (328) baby needs upgrade! (has: 7.4.0 r7568, needs: 7.4.0 7601)

baby pushes a window that says:
"The software for this Squeezebox is up to date. If you'd like to reinstall r7526, choose Begin Update"

and provides one option for updating to r7526 (at least that's what the menu item says)

If this only affects custom.baby.* it's not a P1

Comment 1 James Richardson 2009-09-16 10:16:13 UTC

Ross: Haven't you reported this behavior (or something close to it) in the past?

Comment 2 Ross Levine 2009-09-16 12:15:01 UTC

Yes almost every day, just reboot baby and it will see the right update, which doesn't show a version number. This bug is annoying but easily worked around.

Comment 3 Michael Herger 2012-03-05 07:06:44 UTC

Ben - did you ever investigate anything in this direction? I'm going to work on the update notification code. This might be another candidate to fix while I'm at it...

Comment 4 Michael Herger 2012-03-05 07:07:38 UTC

*** Bug 13256 has been marked as a duplicate of this bug. ***

Comment 5 Ben Klaas 2012-03-05 21:30:15 UTC

I did investigate it, and it required more effort than I deemed worth doing. Right now squeezeplay never receives the data from SBS side to know what revision is available.

If a solution would be desired for this, my recommendation is that if you can get away with not doing any code change on the squeezeplay side, that's the least risky route to go. Make it so SBS can figure out the correct message to send to make squeezeplay just do the right thing and display the revision that is available. If you mess with FirmwareUpdateApplet.lua, badthings are more possible.