search

Rytiggy / Glance

Mg/dL and mmol/L Fitbit watchface for CGM in the Cloud Group
https://glancewatchface.com
GNU General Public License v3.0
98 stars 68 forks source link

E404 error with xdrip+ and Fitbit #98

Open simonish opened 5 years ago

simonish commented 5 years ago

Everything has been working fine, fitbit app on android seems to have updated overnight and this morning all it shows is E404, I have tried a few other cgm faces and non will communicate so I am suspecting the fitbit app... any advice?

I have tried restarting everything

jbuckhi commented 5 years ago

I can confirm this. I observed exactly the same behaviour. The error appeared after yesterdays update of the fitbit app to version 3.9.1 (20243443).

In addition I tested to switch the data source to my nightscout instance: no change - same error. By the way: my xDrip+ is unchanged (d7689af-2019.11.02).

I tried to get the previous version of the Fitbit App from our local Fitbit support, without success: a rollback is not intended.

gitanO0 commented 5 years ago

Seems to be http://127.0.0.1:17580/sgv.json not working any more. When I use sgv.json from my nightscout site (https://_xxx_.herokuapp.com/api/v1/entries/sgv.json) i get data again. So, something has been changed in the way the fitbit app is able to fetch data. I tried the xdrip ssl https (127.0.0.1:17581) as well with no success.

This would really suck if we have to use the web rather than local web service to get xdrip data. I'm out of cell reception a lot so relying on the web just completely blows.

norbertzpb commented 5 years ago

I can confirm this. After Fitbit update E404 Error on Versa2.

simonish commented 5 years ago

This is on the Fitbit Versa 1 with Android 10 and Xdrip+

jimk9 commented 5 years ago

Hi, I think it may be more than that. I have huawei p20, still on 9 with xdrip+. All has been stable for months. As of last night I am now getting this error. No settings/software updated bar fitbit app. Looks like it updated during the night to version 3.9.1 (20243443), as noted above. Watch is versa 2

simonish commented 5 years ago

Yes likewise, fully stable until the overnight fitbit app update, now I am (thankfully still have it) using my old ticwatch e until it all works again

jimk9 commented 5 years ago

Might be worth a look at issue #97 for possible workaround

MichelaBelluta commented 2 years ago

Help! I'm keep having the e404 error pn fitbit versa 2 despite trying all the troubleshooting I've found here. Im using xdrip

Rytiggy commented 2 years ago

It's a Fitbit app issues, they have yet to confirm exactly what it is but something similar happened a few years back. They are supposed to allow local http calls to work but accidentally broke it in the last update for Android, they said the next update will fix it.

MasterPlexus commented 2 years ago

I tried to use interims my own nightscout instance, unfortunately it looks like the Watchface created [objects] for bgs in the Json response (the original json looks fine... Really sad, that no way is currently possible...