We’ve been putting v133 on all new Tempests for a couple weeks, but have not yet deployed it to Tempests in the field.
Correct, and to be clear: the issues we discovered were not new in v133, but exist in the previous build (v129) as well. We’re testing v134 now, and likely v135 soon. As soon as we confirm all issues are addressed, we’ll push that out to everyone.
It looks like this is an issue with the apps’ mis-interpretation of some new status sensor_status flags. So it’s not a firmware issue, directly, but something we need to fix before rolling it out more broadly.