v0.4.1

[ilyakruchinin]

Changes since v0.4.0

_ZLE-based EDF start alignment

• EDF start time now aligned to the rising edge of AS11's _ZLE (Zero Leak
  Estimate) signal instead of MaskOn, better matching AS11's own export
  behaviour.
• Added find_zle_time() to scan events.snt for the first _ZLE event with
  value=1 (rising edge only). Falls back to MaskOn when no _ZLE event found.
• _ZLE subscription and ValueChange handling added with injected NTP
  timestamp and diagnostic rising/falling-edge logging.

Missing-packet compensation via startTime gap detection

• StreamData notifications now parsed for startTime (ISO8601) in the
  fast-path single-pass scanner — no cJSON overhead, one extra string
  comparison per key.
• Gap detection: compares consecutive startTime values; normal gap is
  ~200ms, threshold 280ms. Handles multi-notification loss (2, 3, 5+).
• Compensation per signal type:
  • BRP (25Hz waveform): inserts -1 sentinels (preserves waveform
    integrity — fabricated data could mimic apnea).
  • SA2 (1Hz vitals): holds previous HR/SpO2 value (changes over
    minutes; gap is clinically negligible).
  • PLD (0.5Hz metrics): holds previous 12-channel row (2-second
    summaries change slowly).
• Decimation counters advanced correctly during gap compensation to
  maintain timeline sync. Midnight rollover handled. Gap capped at 50
  notifications to prevent runaway on BLE reconnection.

Session data quality logging

• Per-gap warning at ESP_LOGW level:
  StreamData gap: <gap>ms (<N> missing notifications), inserting compensation
• Session-end summary at ESP_LOGI level:
  stream quality: <N> notifications received, <N> gap events, <N> missing compensated, loss rate <X.XX>%
• Loss rate shown as percentage with 2 decimal places. 0.00% = no drops;
  0.13% is typical for problematic BLE links.

---

This discussion was created from the release v0.4.1.

[cdbrow]

Sorry if you have answered this already. I have purchased another unit, but this one with the battery. I’m wondering what the best way is to transition from my previous unit to the battery one? Maybe it doesn’t even matter as far as historical information, so maybe I just set it up and move forward?

[ilyakruchinin]

Hey @cdbrow
You can simply move the SD card into the new unit and then set up WiFi and uploader credentials.
That should all cover it (almost everything is on the SD card except for things you see in "Configuration" tab in the Web UI).

[ilyakruchinin]

P.S. I am REALLY surprised they don't sell the just the battery separately.

[irfanguder]

Or you can unplug the battery from the old one and plug it into the new one, it is pretty easy.

[ilyakruchinin]

I've disassembled the ESP.

Here is the battery that's inside.
Pretty sure this type be bought separately elsewhere.

[ilyakruchinin]

Work progressing. Initial support for "graphs" should be expected in the next pre-release (but will take some time, graphs are quite challenging).

[vvkovmDdjhrd]

Dear @ilyakruchinin I wanted to ask how easy it is to also implement displaying (in real time) the current status of incidents (CA,OA, UA ...)/leaks (on LCD) before the completion of therapy or do they come from AS11 later, only after the completion of therapy?

I would also like to be able to wake up the device screen (touch, button) without using the WEB and stopping therapy if it is turned off (otherwise it feels like something is frozen).

I also wanted to ask if it is necessary to turn off the device via the button (when not performing therapy), or can I just turn off the power?

Best regards.

[Asad-Foresite]

I'd like a timer of how long therapy has been going. I believe I added it as a feature request. Good to glance at quickly to know how long I have been sleeping for. I have been working on trying to extending my sleep time in bed and this would help me know if I have reach the amount of time I was aiming for.
Events I agree you can show after therapy ends much like the machine screen does.

[ilyakruchinin]

@Asad-Foresite , do you mean current session or the night total?
Imagine you slept from 23:00 to 1:00 (2 hours), woke up and went to sleep again at 2:00.
Then you woke up at 2:30 (30 minutes later) and looked at the LCD.
What should it show?

Therapy time 02:30 or therapy time 00:30?

[ilyakruchinin]

The LCD is small, we can only fit basic info.
Some people wear glasses and take them off at night. We need to put the basic info only (limited) in a large, visible font (no guarantees of clear vision).

[Asad-Foresite]

I would personally prefer to see the total accumulated time for the night (e.g., 02:30), resetting at similar interval the machine itself resets.

This feature would also be incredibly useful for compliance tracking. For instance, users in the US with specific insurance requirements or pilots as an example often need to prove a minimum number of daily usage hours to maintain coverage or occupational certification.

[vvkovmDdjhrd]

Does this firmware support more stable file systems (other than FAT)?

My use case:
I use automation to turn off the AS11 (and other devices). This happens automatically after therapy is complete (after about ~30 minutes). This time is enough for the device to dry and the data to be transmitted. Other many devices also turn off automatically when I leave the house. Ideally, I'd like the ST to also turn off when the AS11 turns off (or when I leave home). Otherwise, I'd have to turn it off manually every time (which is an additional hassle). My ST doesn't have a battery yet, but that's fixable. Perhaps there's some way to automatically turn it off (safe, without the risk of damaging the flash drive), for example, when it's on battery power for a certain period of time.

Best Regards.

[ilyakruchinin]

Progress update - multiple graphs and better aliasing:

[vvkovmDdjhrd]

Dear @ilyakruchinin, am I correct in understanding that in addition (file Share) to FTP, REST-API is already supported?

Best Regards.

[vvkovmDdjhrd]

Dear @ilyakruchinin,
i think it's also a question of personal boundaries. And a question of whether we're free to choose what to share and what not (especially relevant for the specific nature of this data). Considering that highly detailed graphs will soon appear in the web interface, I'd prefer to have the option to use a password. I think the ability to set a password is a basic feature for most devices (including on a home network).
I can also provide a few more arguments if this isn't enough (legal aspects, hacking, use cases in hotels, etc.).

Otherwise, I'd have to configure FW/ACL (a separate WLAN) on my network, which complicates the operation process.

I'd really like to see this feature. I hope other users will support me.

Best Regards.

[ilyakruchinin]

Thank you, I heard you loud and clear and I definitely understand your concern.
I'd also like to hear what other people think about it as I do not necessarily share the same view (to properly assess the importance of such a change).

Please feel free to open a feature request. However, until I've heard other opinions, I would prefer to not consider this high priority for implementation.

[Asad-Foresite]

Adding my perspective as another tester. I'm not opposed to a password
option existing for those who want it, but personally I don't see a strong
need for my own use case.

AHI numbers and waveforms don't feel like sensitive data to me personally,
anyone I live with or interact with regularly already knows I use CPAP
therapy, and the data itself doesn't contain anything personally
identifiable beyond that. The one scenario I could imagine is something
like a nosy neighbor in an apartment complex, but even then, they'd need
to already be on my home network to reach the web UI in the first place,
which typically means they'd need my WiFi password, not just proximity.

That said, I understand context varies a lot by living situation, network
setup, and personal comfort level with health data, so I don't think this
should be dismissed just because it's not a priority for me. Looking forward to hear others feedback.

[irfanguder]

I agree with @Asad-Foresite for this feature, even if it is implemented there should be an option for not using it for those who doesn't have any issues with this.
Best regards,
Irfan

[vvkovmDdjhrd]

I haven't tested this feature yet (I plan to later), but in one of the comments, @ilyakruchinin wrote that if WiFi is unavailable, the device switches to AP mode (temporarily) or by holding the Boot button for 5 seconds. That's theoretical WiFi could be lost, the button could be accidentally pressed or break. Considering the accumulated data on the device and the inability to set a password, I find this highly questionable. Therefore, in my opinion, the ability to set a login and password for the web browser would be very useful (if configured).

Best Regards.

[ilyakruchinin]

Baby steps..... We'll get there (numbers are a bit off yet, UI needs a cleanup etc).

[irfanguder]

This getting far beyond Cpap data uploader, getting closer to OSCAR/SHQ. Very good progress, thank you.

[ilyakruchinin]

Closing as v0.5.0 has been released: #40