ThirdReality ota file

[ThirdReality]

Hi, Mike @mike.maxwell @bobbyD
Thank you for your uploading the ota file. We have tested it and they can be OTA to the latest version.
But, for motion sensor and door sensor. When they have updated to the latest, and then click "update firmware" again, they still can OTA.
You can the screenshot below, when update to the latest version 31, click "update", it still show update from 1F to 31. This looks like a problem caused by different decimal systems.
And other products don't have this problem.
A few weeks ago, we solved the problem of duplicate OTA and update the firmware.
Can you help to update the firmware, and i have sent the ota file to you via e-mail. Thank you.

[ThirdReality]

Hi, @mike.maxwell , I have received your reply for uploading new ota file.
And i test it. This problem still exist.
I have some questions to ask.
In our firmware, the file version is hexadecimal, like 1F.
But when OTA, in live logs, i see "update from 0000001F to 00000031". The current version of the device is 1F, and the next version is 31. But the two versions are the same. The decimal of 1F is 31.
Because of the different decimal display, OTA is still available.
So what I want to ask is how does the file version display when hubitat processes OTA? @mike.maxwell @bobbyD
Some packet capturing information and logs are for reference

[mike.maxwell]

0x1F == 31 decimal, 0x31 == 49 decimal.
Since the previous firmware was tagged in the firmware header as 0x31 and the current version is 0x1F, 49 is bigger than 31 and 49 is currently cached on the local hub, that version is being used vs the intended version.
Currently there isn't a way to clear cached firmware updates.
We will look at adding this into a future release.

[ThirdReality]

@mike.maxwell I have sent OTA file about our door sensor(latest version: 33), motion sensor(latest version: 33) and water leak sensor(latest version: 34) to you via e-mail. Can you help to add these files on hubitat. Thank you.