------------------------------------------------------------------------ A poll associated with this post was created, to vote and see the results, please visit http://forums.slimdevices.com/showthread.php?t=116649 ------------------------------------------------------------------------ Question: On what player types does the alarm fail for you? - Squeezebox Radio (official firmware 7.x) - Squeezebox Radio (community firmware 8.x) - Squeezebox Touch (official firmware 7.x) - Squeezebox Touch (community firmware 8.x) - SB Classic/Boom/Receiver/Transporter - Other (eg. Raspberry Pi based) ------------------------------------------------------------------------
KeBul wrote: > Sorry just popped out to see ABBA Voyage :) > Wow, you guys are amazing, is there anything else I can do to help > further? > Would it be worth switching on a higher level of debug for > network.cometd? > Happy to remove Material at some stage to perhaps prove the point, but > would like to run the alarm test a bit longer to get a better feel for > the rate of failure. > What I remember from Apple is that they tend to be continuously looking for other devices. Simply closing the lid may not make it go into full sleep and the MacBook could still be monitoring the network in the background. As a consequence this might make the browser receive notifications as well although it beats me why it would then respond with an alarm off command. This is not something I can replicate in my system (tried with both a Linux desktop and an Android phone). My guess though is that the alarm will fire as intended if you close the browser prior to switching the machine to what should be standby. ------------------------------------------------------------------------ gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
