Bugzilla – Bug 11341
Clock loses accuracy when Boom not connected to network
Last modified: 2012-02-27 17:33:31 UTC
The RTC on my Boom doesn't maintain its accuracy. I'm running 7.3.2 with firmware 43. It only seems to happen after the Boom is connected to SqueezeNETWORK and is then turned off for a few days. Doesn't seem to be an issue if connected to SqueezeCenter, only SqeezeNetwork. After the Boom has been off for a few to several days the clock can sometimes be slow by 30 minutes to an hour. As soon as I turn it back on the time is corrected. Trying to figure out how to check if the Boom has lost its network connection, but apparently there is no way to tell connection status when the device is off. (btw - agree with comments in Bug 9331 that flashing the : once a second would be a good way to signal loss of connectivity when the device is off.) -Tim
When boom is disconnected from SqueezeCenter or SqueezeNetwork and it is using the backup clock boom should display AM or PM as uppercase. When boom is connected to SqueezeNetwork am or pm should be lowercase. This might help in knowing if you are still connected or not when boom is in an off state. Do you happen to remember the case?
I had the Boom's clock set on 24hr format, but I've changed it now for both SqueezeCenter (h:mm pm) and SqueezeNetwork (h:mm:ss pm), so should be abe to tell what's happening now. Will let you know results (might take several days for problem to manifest again). Thanks.
Since there's now a planned 7.3.3 release, bugs which won't make the cut-off are being moved to the next target out. If you feel that this bug needs to be addressed more (or less) urgently than the 7.4 release, please cc chris@slimdevices.com and leave a comment in the bug to that effect so we can review it. Thanks.
It's intermittent and I'm finding it difficult to reproduce the problem consistently, so not a major problem for me if it is pushed out to the next release. I have narrowed the issue down a bit. The Boom only seems to lose time after I have controlled it via the SqueezeCenter web interface on the computer. FYI - Possible triggers I'm still investigating: 1) When Boom is on SqueezeNetwork and I change it to be on SqueezeCenter via the web interface. 2) When I rescan the music library via the web interface.
Tim, do you still see this issue? Changing target to investigating for now.
The problem hasn't shown up for a while now. Will let you kow if it crops up again. Thanks.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.