Bugzilla – Bug 9827
Regardless of Network or Server connectivity, the Boom should still work as a functional Clock
Last modified: 2009-09-08 09:22:52 UTC
Filing this bug for a customer. He strongly feels that regardless of the Boom's connectivity to the Server or Network, the Boom should still fully function like a standard Clock/Alarm Clock. Meaning that so long as there is power to it, it should not lose its accuracy and functionality as a clock/alarm clock. I am filing this as a bug and not as an enhancemnet per the customer's request.
In what way doesn't it? It has an RTC which is set by the server when connected. The firmware stores the next alarm time (probably doesn't have the ability to track DST changes, however). The firmware has a built in alarm tone as a fallback.
perhaps this is a case of bug 9818
Maybe the customer also expects to be able to set an alarm while not connected to a server? You certainly couldn't say the device fully functions as a standard alarm clock unless you could set or clear an alarm. A standard alarm clock would have just one such alarm and it would either be On or Off. No multiple alarms, day of week, etc. What you'd do with that alarm when the device connects again to a server is anyone's guess. Two way sync? :)
Julius: Can you please explain in more detail what features are missing when the boom is in disconnect mode?
The customer feels that regardless of connectivity to a server or network, the Boom should keep accurate time. He stated in our conversations that at times, when his Boom would lose connection to either the network or the server, the Boom would lock up at a certain time and would lose its accuracy. He was dissatisfied with the reliability of the Squeezebox Boom as just a Clock/Alarm Clock.
Dean: your comments on this? what does the spec say regarding RTC
I think we need more specifics from this customer. The RTC is very accurate, but you can't _set_ the alarm. Can you get more details, Julius?
Changing target to next release
No further information has come in from customer or TS. Marking bug as Invalid for now. If more information comes in, please reopen the bug and provide details.
Hi, The RTC on my Boom doesn't maintain its accuracy. I'm running 7.3.2 with firmware 43. It it only seems to happen when it's connected to SqueezeNetwork and then turned off for a few days. I have yet to be able to reproduce it if it's connected to SqueezeCenter before I turn it off, but still testing. After it 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 it's lost its network connection, but apparently there is no way to tell when the device is off. (btw - agree with comments in Bug 9331 that flashing the : once a second would be a good way to show loss of connectivity.) I think this may be related to this bug entry which has been marked invalid, so I added the information here rather than opening a new bug report. Thanks Tim