Incorrect Health-information with MAVSDK-Python 3.0.1

[ans1kel]

Using the latest version (MAVSDK-Python 3.0.1), I'm getting some incorrect values in mavsdk.telemetry.Health from a PX4 device

Erroneous behavior

For example, the is_accelerometer_calibration_ok field value is False in the following:

Health: [is_gyrometer_calibration_ok: True, is_accelerometer_calibration_ok: False, is_magnetometer_calibration_ok: True, is_local_position_ok: True, is_global_position_ok: False, is_home_position_ok: False, is_armable: False]

Sometimes, also the is_gyrometer_calibration_ok and/or is_magnetometer_calibration_ok have been seen showing incorrect values.

Expected behavior

When running an earlier version (MAVSDK-Python 1.4.9) the field value is correct:

Health: [is_gyrometer_calibration_ok: True, is_accelerometer_calibration_ok: True, is_magnetometer_calibration_ok: True, is_local_position_ok: True, is_global_position_ok: False, is_home_position_ok: False, is_armable: False]

It is expected that same values would be received with the latest version of MAVSDK-Python.

Environment

• MAVSDK-Python
  • Python 3.10.12
  • running in Ubuntu 22.04 -based container
  • using Docker version 24.0.5 (x86_64)
• PX4
  • version 1.15.4
  • Holybro Durandal v1

Logs

Attached logs of examples of running MAVSDK Server, and a simple Python script using MAVSDK-Python to read mavsdk.telemetry.Health information from the PX4 device:

• mavsdk-python-1.4.9.log
• mavsdk-python-3.0.1.log

[julianoes]

This is probably related to mavlink/MAVSDK#2521 and we should update the Python wrapper...

[julianoes]

I'm doing a release but I have to work through everything that broke in CI...

#756