Ok, then we need logs from watches to understand why it's nacking appmsg. The message is fairly simple - simple scalar value, nothing what could potentially be wrongly serialized.
Does anyone have annotated firmware disassembly accidentally? To look for possible reasons to nack.