LYNX/AIDEX Issue with Sensor Reset after regular Expiry.

[Mtxaudio8]

My Aidex sensor expired in the Linx app. They told me that the app would still read it as long as the battery works. I’ve tried several things already, but nothing changed — the Jog Us still says the sensor has expired.[

[NeoMod]

I noticed the same thing with my latest sensor: previously, it was possible to reach the expiration date and then use the RESET option to reset the sensor. Now it seems that the option no longer works correctly: the procedure appears to be initialised by the app, but the sensor doesn't actually reset. A disconnect/reconnect cycle is initiated, and when the app reconnects to the sensor, the historical data is downloaded, but the sensor isn't reinitialised.

Also, possibly unrelated: with this sensor, when it switches from "Fetching" to "Storing" after reconnection, the app crashes and becomes unresponsive. (Infinite cycle of reconnect - fetch - storing - crash)

I suspect something has changed with this latest batch of sensors: the previous set I had (orange pack), when arrived at the end of period 1 (15 days) allowed resetting without any problems. This sensor (purple packaging) seems to enter "read-only" mode when period 1 ends; I imagine—but this is just my guess—that the reset must be performed before the duration timer actually expires (perhaps around 14 days and 12 hours...).

I also tried downgrading the app and changing devices, but the problem persisted.

EDIT: If I may, a better title could probably be something like "[LYNX/AIDEX] Issue with Sensor Reset after regular Expiry"

[Mtxaudio8]

Thank you for the information.
I wanted to use Juglocco for the first time, because here the sensor is unrealistically expensive for only 15 days.
Although this app also leaves a lot to be desired, because the graph function is a joke and poorly thought out — not to mention the language limitations.
So I think until there is a solution, I will use a new sensor.
I also have several others that are still active even after 60 days, I can still find them via Bluetooth. Thank you for the suggestion, I have also updated the title.

[ctqvva]

Are both you using newest 1.8.3 firmware sensors? In which case it seems they wont respond to clearstorage command as they used to, so there's that for now…

[ctqvva]

because the graph function is a joke and poorly thought out

What to you mean?

Feel free to give more input, always appreciated.

[NeoMod]

newest 1.8.3 firmware sensor

Oh dear... I feel a bit silly for not checking this detail first.

Yes, I can confirm that in my case it’s firmware v.1.8.3.

It’s a real shame; I suppose there’s not much that can be done about a firmware that’s flashed during production before the whole sensor is sealed.

If I can be of any help by providing further details about the sensor (serial number, batch, ID, etc.), I’m happy to do so. Thank you for all your hard work.