Hi Alex,
I have encountered an issue with your otherwise awesome widget. My X10S keeps reporting “motors armed” and “motors disarmed” in rapid succession in flight and if on the ground the current flight mode repeatedly.
I also think I know the cause, because it started doing this after I have connected a mavlink based parachute system to the UAV. This device has the same sysID as the FC and only a different compID. I suspect the following is happening: your widget processes both streams at the same time and my device reports 0 for the MAV_MODE_FLAG but the FC uses this flag properly. Your widget must use the last heartbeat message, regardless of sysID/compID to determine the armed state and thus the rapid armed-disarmed messages.
I am still running an older version (1.8.1), but haven´t seen anything related in the changelogs since. I don´t know how cour code handles different mavlink systems and components, but it would be nice if the widget would only process data from the actual autopilot.
You could achieve this by only processing data from a specific sysID and compID, that you determine from the heartbeat messages. You could check for a valid autopilot by looking at the MAV_AUTOPILOT value inside heartbeat packages for supported autopilots.
Is this something you could/would implement, or should I search for alternative solutions for my problem?