Omnipod Eros fails comm after 1d

[frankaxela]

Since moved to 3.2.0.4 of AAPS, the pods are failing communication earlier than 3 days.
The issue happens when trying to deliver Insulin or changing the temp basal, message is:
communication failed: nonce resume failed

I couldn't find any issue similar, let me know if there's a walk around or a fix,

tha ks in advance!

build: 5d3e33c-28.02.2024
my setup is:

• Omnipod Eros
• Orange link pro with latest firmware
• xdrip+
• G6

AndroidAPS_LOG_1710794405126.log.zip

[vanelsberg]

Looks like comms problems (Phone-RL-device-Pod):
Next time this happens, try switching off and then on again your RL-device. If this does not solve restart the phone.
If the problem then still persists, try removing and re-registering your RL.

(Btw: always make sure you export AAPS settings for the currently active Pod so worse case you can reconnect to the active Pod when things fail and you need to reinstall)

[frankaxela]

hi @vanelsberg thanks for the recommendations, I tried everything you mentioned for every pod that failed and nothing changed. Also, this issue didn't appear with the previous version of AAPS, 2.8.
These issues are happening with the latest.
I still think this is an issue

[andyrozman]

If pods work in the beggining and they just run out of "juice" and are nor reachable anymore, then there could be 2 possible explanation:

1. We communicate to much which drains battery (which I don't think is the case)
2. Your pods battery has too low voltage for some reason (faulty pods or something)

If you compare code from 2.8 with 3.1, there were major architectural changes in whole application, so there could be million reasons...

Now question is, do other Eros users encounter the same problems, if not, then this could be your local setup problem, although from what you have written, your setup seems to be standard one, that should work... Would it be possible that you have a series of faulty pods?

[vanelsberg]

Yes. Agree.

If pods work in the begining and they just run out of "juice" ...

ad2. Reason can be poor batteries are to old, which is the case when Pod's are beyond the expiration date.

[frankaxela]

I thought that too, so I opened a different package and still had the same issue.

I will revert to the old algorithm as I changed to start using SMBs, maybe there's an increase in calls because of this too.

In the meantime, had another faulty pod, this time after 1d 20h. Which is early.
Tried the restart and disconnect the OL something is going on with the pods, will try to get some DASHs

AndroidAPS_LOG_1712131187366.log.zip