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.
Yes, I believe Material is only triggering an issue in LMS. But to ignore _notifications_ in the alarm code seems the right thing to me. They usually echo an action taken elsewhere. And we should only act on actual input, not on notification (unless we subscribe to them, of course).
Why that introduces another issue, I have no clue. I remember Felix, and old Squeezebox buddie of the time, who had to work on Alarm code at a later stage, once mentioned he would never use it. The Alarm code combined (LMS & firmware) was just too complicated, dealing with too many possible failures...
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
It was the return to school time - we hadn't used the alarm for several weeks :-).
_______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
