Eversense 365 connection issue #2557

Activity

1. k9track commented on Oct 21, 2026

   

   k9track

   on Oct 21, 2026

   More actions

   I had the same "FleetSecret is empty" error with my 365 in Trio. In my case the key vault returned IsKeyAvailable=false because the transmitter's flag was being sent as tx_flags=false. Asking again with tx_flags=true got the certificate and it paired fine after that.

   I opened a PR on EversenseKit for it: bastiaanv/EversenseKit#68

   Loop uses EversenseKit too, so once that's merged and picked up it should hopefully fix this for you as well.
2. brwhealth-sketch commented on Oct 21, 2026

   

   brwhealth-sketch

   on Oct 21, 2026

   Author

   More actions

   Thanks so much for sharing. I thought I was the only one with this issue. I built with Xcode, should I try browser build. I'm not that tech savvy but if I am pointed in the right direction to check the files I am willing to try anything to stay on my omnipod with Eversense 365
3. k9track commented on Oct 21, 2026

   

   k9track

   on Oct 21, 2026

   More actions

   I believe they are going to push out an update to fix this issue. I submitted my fix to them.
4. marionbarker commented on Oct 22, 2026

   

   marionbarker

   on Oct 22, 2026

   Contributor

   More actions

   We have pushed what we think is the fix to LoopWorkspace dev with LoopKit/LoopWorkspace#548.

   Please see this zulipchat post: #development > Loop dev @ 💬

   Please report back if this fixes your issue.
5. k9track commented on Oct 22, 2026

   

   k9track

   on Oct 22, 2026 via email

   More actions

   Thank you all, I fixed my issue with morning with the push that I sent in and its been working fine. Thanks again. *Nathan Solis* ***@***.*** This email is intended for the addressee and may contain privileged information. If you are not the addressee, you are not permitted to use or copy this email or its attachments nor may you disclose the same to any third party. If this has been sent to you in error, please delete the email and notify us by replying to this email immediately.

   …

   On Wed, Oct 21, 2026, at 8:34 PM, Marion Barker wrote: *marionbarker* left a comment (LoopKit/Loop#2557) <#2557 (comment)> We have pushed what we think is the fix to LoopWorkspace dev with LoopKit/LoopWorkspace#548 <LoopKit/LoopWorkspace#548>. Please see this zulipchat post: #development > Loop dev @ 💬 <https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop.20dev/near/633829910> Please report back if this fixes your issue. — Reply to this email directly, view it on GitHub <#2557?email_source=notifications&email_token=ASLH4UNIBUHHURSKOCRZZ7T5VFW3PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMZTGEZDQOBUHE32M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-6331288497>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASLH4UKC3RIZAV5NZO6YDW35VFW3PAVCNFSNUABEKJSXA33TNF2G64TZHM2TSNJTG42DCNZ3JFZXG5LFHM2TOMZUGE3TMNRVGKQXMAQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ASLH4UP7VY2OLB6A24MQ6AT5VFW3PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMZTGEZDQOBUHE32M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ASLH4UJBMXUVIV7IEG7NVBT5VFW3PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTMMZTGEZDQOBUHE32M4TFMFZW63VHMNXW23LFNZ2KKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>