When the charger goes offline, a session starts and stops entirely offline, and the device resets while still offline — on reconnect, only StopTransaction.req is sent. The corresponding StartTransaction.req is never resent, so the session is never properly correlated server-side. Filesystem/persistence itself is confirmed working (other files persist fine across reset).
Question: I see in the changelog that #345 introduced the Operation store (op-*.jsn, opstore.jsn) and explicit txNr tracking (txstore.jsn), and #355 migrated persistent storage. Since my checkout predates these:
Is this StartTransaction-loss-on-reset behavior expected/known in code prior to #379, and resolved by upgrading?
Or should offline StartTransaction queuing have worked correctly even in the older code, via some config flag I might be missing (e.g. related to TransactionMessageAttempts/TransactionMessageRetryInterval, or something in the older operation-queue mechanism before #379)?
If it's the latter, can you point me to which config or callback governs offline tx-queue persistence in pre-#345 code?
When the charger goes offline, a session starts and stops entirely offline, and the device resets while still offline — on reconnect, only StopTransaction.req is sent. The corresponding StartTransaction.req is never resent, so the session is never properly correlated server-side. Filesystem/persistence itself is confirmed working (other files persist fine across reset).
Question: I see in the changelog that #345 introduced the Operation store (op-*.jsn, opstore.jsn) and explicit txNr tracking (txstore.jsn), and #355 migrated persistent storage. Since my checkout predates these:
Is this StartTransaction-loss-on-reset behavior expected/known in code prior to #379, and resolved by upgrading?
Or should offline StartTransaction queuing have worked correctly even in the older code, via some config flag I might be missing (e.g. related to TransactionMessageAttempts/TransactionMessageRetryInterval, or something in the older operation-queue mechanism before #379)?
If it's the latter, can you point me to which config or callback governs offline tx-queue persistence in pre-#345 code?