readRaw() and writeRaw() not supported by the Libre 2

[gui-dos]

The custom NFC commands A3 and A4 to read from any 16-bit address and to gain write access to the FRAM are not supported by the Libre 2.

The overhead introduced by the nested handlers at https://github.com/creepymonster/LibreDirectApp/blob/d1a94370ed8465234d967729fea277df121cc665/LibreDirectLibrary/Modules/Libre2/Libre2PairingService.swift#L95-L97 can be therefore avoided.

[creepymonster]

Hi gui-dos, thanks for your message. I will look at your tip tomorrow and adjust and test the code. The customization sounds fine and would make the code more readable. I would like to make the code more readable again for the Libre2 in the near future and this would be a first step.

Many greetings

[creepymonster]

Hi gui-dos, thanks for your message. I will look at your tip tomorrow and adjust and test the code. The customization sounds fine and would make the code more readable. I would like to make the code more readable again for the Libre2 in the near future and this would be a first step.

Many greetings

Hi gui-dos, I implemented your recommendation and it works wonderfully. Thanks a lot :)

[creepymonster]

I rewrote my NFC.swift class by using async / await and gathered the Libre 1 “hacks” in the separate NFCTools. The code is still messy and I still have to solve all the warnings caused by the new Actors isolations...

May I ask you whether you already tried to support scanning the sensor to retrieve manually the last 8-hour data and to integrate the new Swift 5.5 Tasks in your Redux custom implementation?

I'm eagerly following your adjustments in the NFC class. I think async/await will improve the readability by a lot - I will look the next few evenings.

I had already thought about the 8 hours of data, but I didn't tackle the issue to avoid the problem of duplicate data (with small differences, maybe not exactly the same data) being uploaded to Nightscout.

[creepymonster]

I rewrote my NFC.swift class by using async / await and gathered the Libre 1 “hacks” in the separate NFCTools. The code is still messy and I still have to solve all the warnings caused by the new Actors isolations...

May I ask you whether you already tried to support scanning the sensor to retrieve manually the last 8-hour data and to integrate the new Swift 5.5 Tasks in your Redux custom implementation?

I must say that the 8-hour values have often bothered me in the past with Diabox. For example, when switching from xdripswift to Diabox, I had two curves over the last few hours in my Nightscout.

[creepymonster]

I had also seen your hint at xdripswift where it was about rawValue == 0. I have logged that at least. I had fortunately exactly at the time the problem that I got only 0 values from my sensor (connected but no more values through the 0 filter).

WORK_VOLTAGE, SENSOR_SIGNAL_LOW

[creepymonster]

You are absolutely right - grrr, only the first lines in the eye had and the last lines carelessly numbered through.

INVALID_DATA = 32768 is not 1 << 12 but 1 << 15

Thanks gui-dos - I will correct the error.

[creepymonster]

I rewrote my NFC.swift class by using async / await and gathered the Libre 1 “hacks” in the separate NFCTools. The code is still messy and I still have to solve all the warnings caused by the new Actors isolations...

May I ask you whether you already tried to support scanning the sensor to retrieve manually the last 8-hour data and to integrate the new Swift 5.5 Tasks in your Redux custom implementation?

I tried the NFC scan once with async/await. Actually looks quite good and works quite well in my tests.