This issue looks like it covers your problem. There is also a post on this subreddit about it... I guess I'm going to pin it.
there's another app you can use for smart scales, it's called openScale
i haven't used it as i don't own a smart scale, but you might want to give it a shot
it seems to support weight history among other things
I am using Amazfit just fine on Notify. You can check the supported amazfit devices here. https://play.google.com/store/apps/details?id=com.mc.amazfit1&gl=US
>All Amazfit supported: Bip, Bip S, GTR, GTS, GTR 2, GTS 2, T-Rex, Zepp E Circle, Zepp E Square, Ares, Neo, Verge Lite, GTR Lite, Bip Lite, Cor, Cor 2, Arc, Pace*, Stratos*, Verge*, ...Official app is not required Additional info
There are few that are not supported though.
> Fossil Hybrid HR series
https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Fossil-Hybrid-HR
Unfortunately the device is pretty locked down and it is neccessary to use the official app at least once.
Does the GTS3 work when added as a GTS2?
There now seems to be description of this in the wiki: https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Home#testing-an-unsupported-device
I do not think that anyone had a chance to try yet. It would be great if you can try and report in the bugtracker if this particular watch can be used with the code that is used to support GTS2. There is a new feature aimed exactly at this case:
- install latest version from FDroid (0.64.0)
- press "Connect new device" + button. In the "Discovery and Pairing options" at the bottom of this screen, select "Discover unsupported devices", go back to the scanning screen and start the discovery
- once you see the GTS 3 listed, long press on it and in the popup dialog, choose the Amazfit GTS 2.
Note: if the device requires special pairing, you need to make sure you follow the manual. Also, you have to make sure that MiFit/Amazfit is not running. (But you do not unpair from it, this would erase the secret key, which you need for the pairing: https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Huami-Server-Pairing )
Right now it checks for the following names:
name.startsWith("M6") || name.startsWith("M4") || name.equals("LH716"))
I suggest to try the newly released 0.63.0, maybe it will work. If not, use something like "NRf connect" app and see what is the name that comes up in it. It looks like this:
​
Then, ideally report the name to Gadgetbridge repo, they might pick it up.
I got it working.
New version of GB, I got the MAC and auth_key from the python script here: https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Huami-Server-Pairing
It didn't work until I had entered both of these in. PM me if you need help with it.
I assume you're reading this page. It lists 3 methods of getting the token that Gadgetbridge needs. Only the first involves Python. The second is similar to the first, but someone created an APK file that you can install on your phone and run the script.
The last one I believe is a modded/hacked version of Zepp that will save the token as a file on your phone. That was the method I used with my GTR. It's definitely not recommended but it worked for me. Use at your own risk, and good luck!
Not implemented yet :)
We are already tracking this as issue https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/2041
PRs welcome :)
This sounds like some strange Android 10/flavor issue. I am not sure what else to suggest. Try to catch logs and provide, via ticket, to the issue tracker.
Read this: https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Pairin
Ideally, use huami-token solution or https://codeberg.org/vanous/huafetcher
which uses huami-token but is packaged for Android.
These settings are done in the Weather Notifications app. Have you looked at the wiki?
https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Weather
Potentially yes, with some more complex configuration: https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Huami-Device-Actions
I got the Fossil Hybrid HR and that is a very similar situation to the Mi Band 4 in terms of pairing.
It looks like the Mi Band 4 is only not recommended because the process is convoluted. If you make it past the initial setup, it should be smooth sailing (assuming you never update the firmware).
If you are a person who tinkers, I would say that the process should be simple. Looks like you have to pair with the official Amazfit app, and then you just follow the instructions here to get the Auth Key, and then you just plug that key into Gadgetbridge.
On Gadgetbridge's homepage, they have a list of watches that are compatible, so check there if these round about ways of pairing makes you queasy.