xDrip+ Complication not received readings NULL

[Cryopier]

I have a Samsung Watch 5 and a Samsung Galaxy S22 Ultra running the latest nightly build of xDrip+ and the complication reads NULL, no matter how I refresh both devices.

xDrip+'s Wear OS version was installed utilizing Wear Installer, based on the most recent Nightly build, as well.

I am sourcing glucose data from the Dexcom G7 sensor. Readings are displaying properly on the Samsung Galaxy S22 Ultra.

[Cryopier]

Are you ever going to address my issue?

[IsaacRoitman]

Same issue on Pixel Watch 2, values are displayed properly in the xDrip watch faces. xDrip complications in other watch faces display no BG data, just NULL or NULL NULL.

Pixel 5 running version e5113d9-2024.03.10

[bsw-del]

hey @Navid200 , thanks for all the help, just curious if there is any progress on this, or if I should pursue the tasker route mentioned below? I'd prefer an updated complication, as it is already all setup, and the tasker option seems quite involved. @IsaacRoitman , did you have any success getting this sorted?

[Navid200]

I am not aware of anyone working on making any change to xDrip to address WearOS.

MiBand is the companion watch that is still currently supported by a developer.

[IsaacRoitman]

Unfortunately not yet, I've installed Tasker on my phone but have not had time to get things setup and seems involved. Agreed, the complication would be ideal since it worked perfectly before and almost works now. And we have the ability to input treatments with Wear OS.

@Navid200, anyone we can escalate to in the community?

[bsw-del]

Just an update on my side. I did the tasker and autowear combo described below. Very noticeable battery improvement on my pixel watch. It used to die after about 16 hrs of use. I'm at 30% and 26 hrs right now.
Didn't realize that xdrip was so heavy on wear os until now.

[opasha]

I just thought I'd chime in to help. I have the Ticwatch Pro 5 (Wear OS 3.5) and just got the OnePlus Watch 2 (Wear OS 4.0) today. I also got the famous Null Null nonsense again after the updating the xDrip+ Nightly about 3 updates ago with a running Dexcom G7. The xDrip+ default Watchfaces all work fine as you all have noted.

I use the Marine Commander Watchface on all my watches, and the bottom complication circle is my xDrip+ Complication. I believe I figured out the issue. Maybe it works for you maybe not.

Steps to Fix:

1. Go into the Wear OS xDrip+ Preferences on the watches and uncheck "Refresh on Change"
2. Wait the 1 minute or until it refreshes from your phone to your next reading if it doesn't after the first minute
3. If still nothing yet, go to the xDrip+ phone app's main screen and press the three little dots in the top right corner and select "Resend glucose to watch" and it should force it to refresh on the watch.
4. You can leave it like this or go back in the Wear OS xDrip+ Preferences and re-check "Refresh on Change" again and it should be fully fixed.

At least for me, this fixed the issue on both my watches and updates now as my blood sugar changes.

Let me know if it works for you all. All the best!

Wear Installer 2 still works great for Android 13/14 and Wear OS 3.5/4.0 to push APKs to your Wear OS watch, but you need to actually first Pair your watch with the Pair Code and Port, then go back enter in the full IP Address and Port (this Pairing Port is different from the previous Pairing Port for pairing your watch - this is very important). Here's a good video from the developer:

https://www.youtube.com/watch?v=abgN4jQqHb0

[IsaacRoitman]

This workaround did not work for my Pixel Watch 2. Interested in Tasker until there is a fix, having our BG values on the watch is a huge value. Feel free to link me to instructions or guides on how to, thanks!

[cwpeterson]

This is the thread comment where I learned about it: #2026 (reply in thread)

Here is a direct link to his github and instructions, it's been working great for me. I had to buy the AutoWear and AutoNotification apps. Not a lot of money though considering what you get: https://gist.github.com/oNSXo/0706201d3ac28a99e1855d772e3039eb?permalink_comment_id=4351085#gistcomment-4351085

[bsw-del]

Any updates on the complication updating? I just moved to G7 and lost my complication on Pixel Watch (first gen) FWIW, the Xdrip watchface works, but just the complication is broken..
I'm going to try tasker tonight if can't get sorted.

[cwpeterson]

Tasker method has been working great for me until I had a sensor failure. The complication just never updated once it failed. So I didn't realize that something was going on until my pump started giving audible alarms. But this is still better than nothing. But new sensor and it's back up and running. Would be nice to have the xDrip option back since it shows timeouts and no readings etc.

[oblus]

I just thought I'd chime in to help. I have the Ticwatch Pro 5 (Wear OS 3.5) and just got the OnePlus Watch 2 (Wear OS 4.0) today. I also got the famous Null Null nonsense again after the updating the xDrip+ Nightly about 3 updates ago with a running Dexcom G7. The xDrip+ default Watchfaces all work fine as you all have noted.

I use the Marine Commander Watchface on all my watches, and the bottom complication circle is my xDrip+ Complication. I believe I figured out the issue. Maybe it works for you maybe not.

Steps to Fix:

1. Go into the Wear OS xDrip+ Preferences on the watches and uncheck "Refresh on Change"
2. Wait the 1 minute or until it refreshes from your phone to your next reading if it doesn't after the first minute
3. If still nothing yet, go to the xDrip+ phone app's main screen and press the three little dots in the top right corner and select "Resend glucose to watch" and it should force it to refresh on the watch.
4. You can leave it like this or go back in the Wear OS xDrip+ Preferences and re-check "Refresh on Change" again and it should be fully fixed.

At least for me, this fixed the issue on both my watches and updates now as my blood sugar changes.

Let me know if it works for you all. All the best!

Wear Installer 2 still works great for Android 13/14 and Wear OS 3.5/4.0 to push APKs to your Wear OS watch, but you need to actually first Pair your watch with the Pair Code and Port, then go back enter in the full IP Address and Port (this Pairing Port is different from the previous Pairing Port for pairing your watch - this is very important). Here's a good video from the developer:

https://www.youtube.com/watch?v=abgN4jQqHb0

Hi. I also have OnePlus Watch 2 and I cant get BG on complication. My phone is S10e connected to Libre2EU sensor over BT (xdrip+oop2). Do You still have yours visible?

btw. Im tryin to make my watch work as collector , did You tried that?? I cant connect to sensor with xdrip wear app (even with oop2 installed on watch). I only can connect with juggluco wear app but I dont like TCP type of connection with juggluco in phone.

[Navid200]

Can anyone identify exactly which xDrip Nightly was the very first that caused this problem?

[Navid200]

Do you have a spare phone that is Android 7 or newer?
Can you install xDrip on it and set it up to be the follower of your main xDrip.
Then, you can set up WearOS on it to see if it works or not with a test xDrip I will give you. Regardless of what happens, your main phone will remain untouched.

[PhilTU]

I have a WearOS watch on order and will be able to help with this without compromising anything else.

[heygar]

Any news on this? Best I can tell you is it's still broken on the April 19 build.
I was thinking of taking a stab at fixing it myself, but I think the learning curve might be too much for me just now.
I was also thinking I might take a stab at doing a direct to watch version. But, that was more of a semi-interesting experiment once I learned the code better.

[heygar]

Version from 06/28/2024 seems to have the Complication Issue resolved. It's been running on my watch for a couple of days now...

[oblus]

Not for me. Im on S10e, xdrip+oop2 with Libre2EU on BT and OnePlus Watch 2.
Xdrip watch face wotking fine, but complication says "old Xmin" after set calibration on phone and before was "null null". I have unchecked "Refresh on Change".