E404 issue #202
Comments
Tomgitom
added a commit
to Tomgitom/Glance
that referenced
this issue
Feb 3, 2025
Changed wording for the custom endpoint example.
The URL leads to a dead Heroku app so seems redundant now.
Changed to an example {URL} that differentiates between the /pebble endpoint and the users url.
The snapshot that Fitbit has included on the gallery for the versa 4 does not include the fixes in Rytiggy#202 I hope that this would help clear up some confusion for users using this device.
This may still benefit from further clarification, but I think this small change will help to some degree
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
New Fitbit app 4.1 is not sync the data with watch versa 2
I am using versa 2 watch and Samsung Phone M34, tomato app installed in this samsung phone.
Last month onwards versa 2 not shown CGM value . It show E404.
I changed the mobile, it is not working.
Old fitbit apps also not working in any of the mobile. Let me know someone fixed this or any workaround for this issue
The text was updated successfully, but these errors were encountered: