------------------------------------------------------------------------ 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) ------------------------------------------------------------------------
cpd73 wrote: > I'm going to release an update to Material soon. Should I remove the > unsubscribe? Will that work-around the issue? Or should I leave Material > as is and wait for the fix in LMS itself? Hi Craig, Checking back on your posts you say you introduced this method of unsubscribe in July 22 - what was the reason for that introduction? What would be the potential impact of removing the unsubscribe (apart from maybe a fix for the alarm problem)? Michael doesn't seem to believe Material is to blame - however, I have tested several times without Material installed and not had any alarm failures, but there's a caveat to that - the only way I can "reliably" induce failures during testing is by playing around and changing between players in Material - with no Material installed I can't do that. Having said that, the testing I did with your MaterialSkin vTest, which had the unsubscribe removed, was quite extensive with lots of changing between players but no alarm failures were seen. Michaels ignore 'playerprefs' fix in Alarm.pm resolves or at least drastically improves the problem where an alarm fails to trigger, but seems to have made another issue worse - "using a remote device to pause or stop an alarm". Although I agree with him this is considerably less of an issue than an alarm failing to trigger, so we are in a better place at the moment. My testing also seems to indicate, without Material installed pause works every time, i.e. the alarm is successfully shutdown, once Material is installed the issue for me becomes prevalent, pause regularly fails to completely shutdown an alarm. I haven't tested MaterialSkin vTest against this issue, if you would like me to do so let me know, but from what I'm seeing in the logs I would be surprised if removing the unsubscribe didn't also help with this. In short, albeit from a pure testing evidential standpoint rather than in-depth knowledge of Material and LMS and the protocols/code/interactions between them etc.. I think that Material currently is a trigger for whatever is going wrong within the player and alarm handling, from the testing with MaterialSkin vtest, it looks like removing the unsubscribe either stops that trigger or greatly reduces it. I think it's also worth noting that Michael started this thread and first reported he was having strange alarm issues early Aug, about 2 weeks after your unsubscribe change. ~Insert smoking gun emoji here~ :D Kev ------------------------------------------------------------------------ KeBul's Profile: http://forums.slimdevices.com/member.php?userid=32883 View this thread: http://forums.slimdevices.com/showthread.php?t=116649 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
