Hey there,
We’ve got a large fleet of devices overall working fine. The Notehub UI changed recently, maybe within the last month or two. One page that changed significantly is the Host Firmware page for a particular device. We use this page to initiate IAP updates for our customers.
It used to only show the current status, and now it shows a history of status changes. That’s nice. However, there now seems to be a problem with correctly displaying the current version. Also, the view there claims the update is still pending, even though the devices successfully completed updates days ago.
We’ve noticed this with several devices now. Our own telemetry, as well as what’s reported by the device in _health.qo and shows up in the Device Health log based on setting the version in a dfu.status request — all of that shows the correct host firmware version.
However, the version on the Host Firmware tab for a specific device, under the heading “Firmware Running on Device” is wrong and stays wrong despite any changes reported by the device.
The notecard firmware of the development device I’m using to test is version 7.2.1.16425.
This has been inhibiting the ability of our support department to manage customer communication for these updates. For the moment, we resolved to use the page to initiate updates, but then to subsequently not trust what it says, looking to other sources of data.
- Is there something different we need to be doing in firmware that changed recently?
- What’s the expected trail of breadcrumbs we could look for in the events for a device that would tell the story of a successful update or an update that’s having issues? (We’re often dealing with devices at the edge of connectivity or, you know, covered in seaweed or barnacles.
) Sometimes we see changes to _env.dbsbut haven’t dug in deeply. The way the env vars change seems to have changed over time. - Anyone else notice this?
- Let me know if there’s info you need to efficiently debug.
Cheers!
Zachary
Thanks much!