Bugzilla – Bug 17418
Alarm did not sound on both Radios
Last modified: 2011-08-09 04:15:14 UTC
No alarm wakeup - today, BOTH of my Radios failed to activate their alarms. Bradley has supplied me with a second Radio to see if the Dual Issue reoccured. I have both setup side-by side next to my bed with the same settings. This morning, Neither Radio alarms activated. I pressed the Alarm button to insure I had Friday's alarm set and was given an error screen (see attached). (A "No valid IP" error.) Both devices had this same error. I suspect that this was at the core of why the alarm did not activate but cannot confirm. It makes no sense to me that the alarm or alarm settings would be tied to internet access. Circumstances probably connected to MySqueezebox.com only, firmware 7.6.0 r9458.
Hey Felix, any explanation for "no valid IP" in this instance and connected to MySB.com?
not really, no I've tested an alarm with no network available (i.e. Ethernet cable removed) and that triggered the backup alarm just fine. I also tested an alarm with no ethernet cable attached and that triggered the backup alarm ok. I then tested a case where I removed the network cable and manually (via console) made the device loose it's IP address and again the backup alarm went off. In all three cases I've never seen the "No valid IP" screen. Only when I went into Diagnostics and run Network Health I would see this.
I've looked through SP source code and there are about three places where this message would be presented to the user: - DiagnosticsApplet - SlimBrowserApplet - SlimMenusApplet However I was not able reproduce the issue and make this message show except when manually selecting Diagnostics without a network present. (Ethernet cable disconnected.) Now for the reason this message appeared: Either the device really had no valid ip address at the time, i.e. DHCP server not responding / renewing the ip address or it could have been a false positive. Although I doubt that since both SB Radios had the same issue which points to a local network problem. In any case I don't see a reason why the alarm should not have gone off unless the 'no valid ip' situation already existed 24 hours before the alarm was due which then would have caused mysb.com not being able to store it in the device.