Well hopefully this is something specific to a firmware or rules that a few of us just happen to have and not something that everyone has to deal with. I did do a work around to this. I programmed a rule that speaks 500ms of silence right before the reactivation of non alarm message so that silence is the last thing in the queue. Then when the system first speaks after a mute, instead of a jumbled mix of two messages, there is the slightest barely noticible pause which is an acceptable work around for me.
