Amazfish

piggz's picture
Submitted by piggz on Sun, 2021/07/11 - 01:29
Rating: 
4.734175
Your rating: None Average: 4.7 (79 votes)

Donations: https://paypal.me/piggz

Companion application for Huami Devices (such as Amazfit Bip, Cor, MiBand2/3 and GTS and GTS), Pinetime Infinitime and Bangle.js.

Amazfish from 2.0.3 s now ONLY distributed in the "chum" repository!

Updated Installation Instructions (Aug 2021)

This application requires several supporting packages.  Until Aug 2021, these were available on openrepos for the latest SailfishOS release.  Updating these libs is a big pain, so they have now moved to SailfishOS::Chum.  If you dont know what that is, read this https://build.merproject.org/project/show/sailfishos:chum:testing

To install Amazfish, first install the "chum" repository from the link above and "pkcon refresh" then install Amazfish.

I apologise about thie extra step, but it makes updates much easier.  Pacakges in chum are automatically built for each SailfishOS release and instantly available.  In the future, Amazfish may also be distributed this way, but for now, it can still be installed from here, for the current SailfishOS release.

If you already have Amazfish installed, and need to update, you will also need chum, but you may have to drop to a command line and "zypper dup" and accept and changes to the package vendor.

Supported Devices

There are 3 tiers of supported devices:

Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:
* Amazfit Bip
* Amazfit GTS
* Pinetime Infinitme
* Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:
* Amazfit BipS
* Amazfit Bip Lite
I do not promise not to break funcaionality in these, but will fix where I can

Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device.  Your mileage may vary with these devices.
* MiBand 2/3/4
* AMzfit Cor
* Amazfit GTR

***BUILT FOR 3.4 PLEASE READ OLDER USERS***

Amazfish needs to be built on OBS against a defined set of libraries.  Becuase there is a delay between a Sailfish release and that release being available on OBS, there will be a delay to supporting the latest versions.

For releases of the current version built against other Sailfish releases, use the repositories at :

https://build.merproject.org/project/show/home:piggz:harbour-amazfish and
https://build.merproject.org/project/show/home:piggz:kf5

***PLEASE READ for 1.7.0 Update***

The new sport display feature requires the MapBox component.  The easiest way to get this is by installing PureMaps from rinigus repository.

Powered by KEXI

As of version 0.5.1, actiivity data is retrieved into an sqlite database.  Becuase I think it is important to allow individuals to be in control of their own data, and that they should have the ability to analyse it themsleves, I have chosen to store data in a KEXI compatible database.  This will allow you to copy the database from the phone, and open it up inside KEXI on Linux/Windows/Mac and perform queries and reports on it.  This added ability means i link to a couple of KDE libraries, which should be installed automatically.

Firmware Download - READ FIRST - I am not liable if you brick your watch ;)

Read this for info about which files to flash https://github.com/Freeyourgadget/Gadgetbridge/wiki/Amazfit-Bip-Firmware...

App has been tested using an amazfit bip and GTS, downloading the latest (0.1.1.45) official firmware.

The firmware is split into multiple files on these devices.  With the official MiFit app, all are downloaded at once, and everything works fine.  With this app, you have to send each file individually.  The firmwares are available by extracting the MiFit apk, and looking in the assets/ folder for files named Mili_chaohu.*.  When you select a file, its type and version will be determined, and you will be prevented from sending invalid files.

The firmware (.fw) requires a matching fotn (.ft) and resource (.res).  Send the firmware first, the app will send a reboot command at the end of the transfer, and the watch will boot up into a mode where it needs the matching font and resource sent.  Just wait for the app to connect again, then send the font and resource. 

The following types of file exist:

firmware, resource, a-gps data, fonts

So, to re-iterate, the firmware flashing order is:

  • .fw
  • .ft
  • .res

Server Side Pairing Code

The newer devices (GTS, BipS etc) requires a server-side pairing key which requires inital pairing with an android device.  To get the key, follow the instructions here and enter into Amzafish when prompted, WITHOUT 0x at the beginning.

See https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Amazfit-GTS

AGPS Download/Transfer

The official amazfit app can download and transfer the AGPS files to the watch automatically.  The amazfit web site limits download of the files to those with accounts.  A python script has been developped that can download the AGPS files, these can then be transferred to your phone, and downloaded to the watch using the normal "Download File" option.

  • Obtain the script from https://github.com/argrento/huami-token
  • Download the AGPS files using the -g paramter, this will download 2 .zip file.  The only one required is cep_alm_pak.zip
  • Extract the zip and transfer the 2 .bin files to the phone
  • Send the files gps_alm.bin and cep_pak.bin to the watch.

Pairing Issues

Pairing works for myself, sometimes I have to try twice.  If pairing doesnt work at all, then try:

  • keep the app open, and pair again in the BT settings page of sailfish
  • in the sailfish BT settings page, delete all entries and try again
  • turn off/on BT on the phone
  • factory reset the watch

Check if after all this, pairing works from the sailfish BT settings page.  It should pair and connect just fine from there.  f that doesnt work, my app wont either.

Not all features currently implemented

***May not work on all devices***

Uses Bluetooth Low Energy to communicate with the watch, this is known to be problematic on some devices.  it is known to work on the Xiaomi Mido.  Probably also works on the FP2.  Official devices unknown.

Implemented

  • Pairing
  • Notifications
  • Calls
  • Some settings
  • Retrieving activities
  • Heartrate Chart
  • Alarms
  • Watchface download
  • Firmware upload
  • Activity Sync

Todo

  • More Settings
  • Support other devices (maybe eg MiBand2, as it is similar)

Tip:
On your device, create a symlink in /home/nemo to /home/nemo/.local/share/harbour-amazfish
This way, you can easilty copy the database off the phone using MTP.

Button Actions

Bip and GTS notify when the watch button is pressed. This is captured by amazfish which allows running actions on theses presses. An action can be ran on 2,3 or 4 presses. To confiure the actions, goto Settings > Application > Button Actions.

A custom script can be used, the script must be called harbour-amazfish-script.sh and be in the home folder. Example which sends a OTP code to the watch as a message:

#!/bin/sh
if [ "$1" == "4" ]; then
    CODE=`python3 -c 'import pyotp;totp = pyotp.TOTP("XXXX Authenticator code here XXXX");print(totp.now())'`
    dbus-send --session --print-reply --dest=uk.co.piggz.amazfish /application uk.co.piggz.amazfish.sendAlert string:'' string:'Google OTP' string:$CODE boolean:true
fi;

Source: https://github.com/piggz/harbour-amazfish

Credits to:

  • The gadgetbridge devs, which gave me a lot of hints and inspiration from their device code.
Screenshots: 

Category:

Keywords:

Application versions: 
AttachmentSizeDate
File harbour-amazfish-0.1-1.armv7hl.rpm112.29 KB17/04/2018 - 23:12
File harbour-amazfish-0.2-1.armv7hl.rpm119.54 KB28/04/2018 - 00:35
File harbour-amazfish-0.3-1.armv7hl.rpm131.01 KB07/05/2018 - 23:54
File harbour-amazfish-0.4-1.armv7hl.rpm137.54 KB18/05/2018 - 23:22
File harbour-amazfish-0.4.1-1.armv7hl.rpm137.63 KB20/05/2018 - 00:15
File harbour-amazfish-0.4.5-1.armv7hl.rpm148.71 KB22/05/2018 - 22:02
File harbour-amazfish-0.4.6-1.armv7hl.rpm149.08 KB22/05/2018 - 22:55
File harbour-amazfish-0.4.7-1.armv7hl.rpm149.42 KB24/05/2018 - 00:35
File harbour-amazfish-0.5.1-1.armv7hl.rpm158.56 KB30/05/2018 - 00:22
File harbour-amazfish-0.5.5-1.armv7hl.rpm164.27 KB02/06/2018 - 22:11
File harbour-amazfish-0.5.8-1.armv7hl.rpm168.1 KB04/06/2018 - 21:07
File harbour-amazfish-0.5.9-1.armv7hl.rpm170.27 KB05/06/2018 - 22:24
File harbour-amazfish-0.6.0-1.armv7hl.rpm171.68 KB06/06/2018 - 00:17
File harbour-amazfish-0.6.5-1.armv7hl.rpm179.96 KB23/06/2018 - 11:28
File harbour-amazfish-0.6.7-1.armv7hl.rpm185.47 KB26/06/2018 - 21:55
File harbour-amazfish-0.6.8-1.armv7hl.rpm186.04 KB28/06/2018 - 21:19
File harbour-amazfish-0.7.0-1.armv7hl.rpm238.07 KB15/07/2018 - 12:13
File harbour-amazfish-0.7.1-1.armv7hl.rpm237.48 KB19/07/2018 - 16:51
File harbour-amazfish-0.7.3-1.armv7hl.rpm239.17 KB23/07/2018 - 23:19
File harbour-amazfish-0.7.5-1.armv7hl.rpm673.84 KB26/08/2018 - 11:02
File harbour-amazfish-0.8.0-1.armv7hl.rpm673.94 KB25/11/2018 - 16:33
File harbour-amazfish-0.8.1-1.armv7hl.rpm674.27 KB29/11/2018 - 00:32
File harbour-amazfish-0.8.2-1.armv7hl.rpm674.21 KB01/12/2018 - 16:29
File harbour-amazfish-0.8.5-1.armv7hl.rpm679.46 KB12/01/2019 - 18:02
File harbour-amazfish-0.8.7-1.armv7hl.rpm681.18 KB23/01/2019 - 01:38
File harbour-amazfish-0.8.8-1.armv7hl.rpm681.32 KB04/04/2019 - 20:58
File harbour-amazfish-0.8.9-1.armv7hl.rpm682.44 KB05/04/2019 - 01:11
File harbour-amazfish-0.9.0-1.armv7hl.rpm703.9 KB18/05/2019 - 00:30
File harbour-amazfish-0.9.1-1.armv7hl.rpm702.06 KB21/05/2019 - 22:37
File harbour-amazfish-0.9.2-1.armv7hl.rpm703.2 KB12/06/2019 - 23:28
File harbour-amazfish-1.0.0-1.armv7hl.rpm703.32 KB05/01/2020 - 17:44
File harbour-amazfish-1.1.0-1.armv7hl.rpm1.8 MB06/02/2020 - 01:11
File harbour-amazfish-1.1.1-1.armv7hl.rpm1.48 MB07/02/2020 - 23:21
File harbour-amazfish-1.1.2-1.armv7hl.rpm1.49 MB16/02/2020 - 12:31
File harbour-amazfish-1.1.3-1.armv7hl.rpm1.6 MB29/02/2020 - 14:09
File harbour-amazfish-1.2.0-1.armv7hl.rpm1.6 MB01/03/2020 - 14:03
File harbour-amazfish-1.3.0-1.armv7hl.rpm1.6 MB04/03/2020 - 12:39
File harbour-amazfish-1.3.1-1.armv7hl.rpm1.6 MB04/03/2020 - 21:22
File harbour-amazfish-1.4.0-1.armv7hl.rpm1.62 MB12/04/2020 - 12:39
File harbour-amazfish-1.4.5-1.armv7hl.rpm1.62 MB13/04/2020 - 15:49
File harbour-amazfish-1.5.0-1.armv7hl.rpm1.61 MB22/04/2020 - 15:23
File harbour-amazfish-1.5.1-1.armv7hl.rpm1.61 MB26/04/2020 - 22:58
File harbour-amazfish-1.5.5-1.armv7hl.rpm2.45 MB15/05/2020 - 11:48
File harbour-amazfish-1.5.6-1.armv7hl.rpm2.45 MB16/06/2020 - 15:48
File harbour-amazfish-1.6.0-1.armv7hl.rpm3.17 MB28/06/2020 - 16:43
File harbour-amazfish-1.6.1-1.armv7hl.rpm3.17 MB30/06/2020 - 22:29
File harbour-amazfish-1.6.5-1.armv7hl.rpm3.18 MB08/07/2020 - 11:17
File harbour-amazfish-1.6.6-1.armv7hl.rpm3.18 MB17/07/2020 - 11:30
File harbour-amazfish-1.6.7-1.armv7hl.rpm3.18 MB22/09/2020 - 00:25
File harbour-amazfish-1.6.8-1.armv7hl.rpm3.18 MB22/09/2020 - 11:29
File harbour-amazfish-1.7.01.7.0.20201010190441.8409c73-1.5.1.jolla_.armv7hl.rpm3.25 MB10/10/2020 - 22:34
File harbour-amazfish-1.7.11.7.1.20201013113553.5d4533a-1.6.1.jolla_.armv7hl.rpm3.25 MB13/10/2020 - 15:03
File harbour-amazfish-1.8.1-1.10.1.jolla_.armv7hl.rpm3.35 MB17/12/2020 - 01:24
File harbour-amazfish-1.8.2-1.11.1.jolla_.armv7hl.rpm3.35 MB18/12/2020 - 23:28
File harbour-amazfish-1.8.5-1.12.1.jolla_.armv7hl.rpm3.38 MB07/01/2021 - 20:31
File harbour-amazfish-1.8.7-1.13.1.jolla_.armv7hl.rpm3.41 MB20/01/2021 - 00:00
File harbour-amazfish-1.9.0-1.14.1.jolla_.armv7hl.rpm3.45 MB21/01/2021 - 12:44
File harbour-amazfish-1.9.5-1.15.1.jolla_.armv7hl.rpm3.56 MB11/02/2021 - 01:40
File harbour-amazfish-1.9.6-1.16.1.jolla_.armv7hl.rpm3.56 MB13/02/2021 - 01:40
File harbour-amazfish-1.9.7-1.18.1.jolla_.armv7hl.rpm3.56 MB02/03/2021 - 19:30
File harbour-amazfish-1.9.8-1.19.1.jolla_.armv7hl.rpm3.56 MB06/03/2021 - 00:09
File harbour-amazfish-2.0.0master.20210510082230.b199678-1.3.armv7hl.rpm3.56 MB10/05/2021 - 11:55
File harbour-amazfish-2.0.2-1.30.1.jolla_.armv7hl.rpm3.57 MB11/07/2021 - 01:29
File harbour-amazfish-2.0.2-1.30.1.jolla_.aarch64.rpm3.58 MB11/07/2021 - 01:29
Changelog: 

2.0.3

  • Support for SailfishOS 4.3 (dropped support for SFOS <= 4.0)
  • Support for Infinitime motion service (immediate step count)
  • Potential support for GTS2 and GTR2
  • Potential fix for calendar issue

2.0.2 - Now for 4.1

  • Minor fixes
  • OBS build fixes

2.0.0 (incl unreleased 1.9.9)

  • Check if service is running on open, and start if nescessary
  • Remove start service button from UI
  • Much improved date/TX handlng.  Fixes all known issues regarding missing or duplicate activity/step data
  • Dont display useless weather condition string message
  • Possibly fix missing BipS menu items
  • Aarch64 fixes
  • Code cleanups
     

1.9.8

  • Add the new button handling function to GTS (see docs)

1.9.7

  • Bip users get customisable button actions
  • Infintime call handling and fixes

1.9.6

  • Fix daemon crash when sending buffered notifications
  • Better BipS support

1.9.5 (includes unreleased changes for otehr distros)

  • Initial support fo Bangle.JS
    • Music, Notification, Call, Weather, Status
  • Some app icon fixes for newer Sailfish applications
  • Support a new deviceEvent dbus message
  • Translation updates
  • Support Infinitime music service on fw > 11
  • Service updates for non-sailfish

1.9.0

  • Added strava upload support
  • Allow activities to be deleted from database
  • Fix dbus interface
  • Fix navigation in kirigami

1.8.7

  • Code refactor to make adding more huami devices easier
  • Fixed setting display items / order for Bip
  • Fixed horrible display items screen
  • Fixed alarms page
  • Fixed call notification

1.8.6 (not release for sailfish)

  • Build fixes for other platforms

1.8.5

  • Support for flashing the PInetime Infinitime firmware
  • Support for setting and re-arranging GTS menu items
  • Activities are now saved as TCX, aswell as GPX.  This allows indoor activities to be saved.
  • XML is no longer stored in the database, instead the filename/path is saved.

1.8.2

  • Fix file selection in download page
  • Translation updates
  • Some contributed build fixes

1.8.1 - Includes 1.8.0 which was skipped

  • Reqrite the entire application to use rinigus QML components, enabling cross platform
  • Expermental navigation instructions from Pure Maps
    • On GTS instructions come through the music app
    • On other, instructions are by notifications (may be spammy!)
    • Fix GTS GPS data with duplicate sime stamps
    • Lots of code cleanups

1.7.1

  • Implement AGPS download for Bip/Lite/GTS (See description)
  • Translation updates

1.7.0

  • Added parsing for sport summary data and record data in database
  • Added new sport info page with all activity data and map of route
  • Fixed buttonPressed dbus-signal (contribution from jgibbon)
  • Added untested basic bip-s support

1.6.8

  • Fix application notifications not shown in UI

1.6.7

  • Add support for the activity data format in later GTS firmware
  • Pinetime-JF renamed InfiniTime
  • Add music control for InfiniTime
  • Fix sending goal to watch

1.6.6.

  • Fix uI crash when daemon not running
  • Minor backend fixes

1.6.5

  • Fixed GTS/GTR auth with new firmware (please feedback if still issues)
  • Major re-write, mostly non user visible, moving the following to libwatchfish
    • Calendar
    • Notification
    • Calls

1.6.1

  • Fixed repeating alarms

1.6.0

  • Basic GTR support
  • GTS/GTS music app inplemented
  • Moved button based mucis control to daemon
  • Only send connect notification if there are no buffered messages
  • Start using libwatchish where applicable

1.5.6

  • Fix daemon crash when pairing

1.5.5

  • Fixed sending weather to GTS
  • Refactored weather code
  • Initial support for Pinetime-JF

1.5.1

  • Be more stringent about allowing firmwares to be downloaded
  • Fix timestamps in GPX files

1.5.0

  • Fixed file transfers (watchface/fw) to the Bip
  • Watchface transfer to Bip Lite confirmed working
  • Added file transfer support for the GTS
    • Watchface confirmed working on XA2/Mido
    • FW confirmed working on Mido

 

1.4.5

  • Added heartrate analysis page
  • Moved raw graphs to mene

1.4.0

  • Large contribution from Petr Tsymbarovich
    • Reworked pairing
    • Updated first page
    • Updated config storage
    • Updated device selection
    • Use nemo notifications
  • Add indoor cycling activity type
  • Fix syncing data when in DST(hopefully!)

1.3.1

  • Darker paercentage circle
  • Fixed service Stop button
  • Load steps on startup for quicker display
  • Translation updates

1.3.0

  • UI improvements thanks to @AlphaX2
  • Note added to sleep page

1.2.0

  • Hopefully fix reading calendar
  • Translation update
  • Start using the supported-features system to hide some UI components when not applicable

1.1.3

  • Improve coverpage information and actions
  • Fix labels on graphs
  • Fix auth with bip lite / band
  • Fix bug for time format selection
  • Add support for sending calendar events to supprorted devices
  • Request alarm info from watch on init
  • Fix display of steps showing x10 sometimes

1.1.2

  • Fix initial pairing with Bip, Miband 3 and maybe others

1.1.1

  • Add support for Bip Lite
  • Allow connection of MiBand3 and Cor (untested, uses the Bip backend)
  • Translation updates

1.1.0

  • Fix alarms being overwritten
  • Initial (beta) support for Amazfit GTS
  • New pairing page and improved pairing

1.0.0

  • Added support for flashing newer firmwares
  • Added disconnect notification option
  • Fix buffered notifications when the watch is not connected (they never worked)
  • Added workaround for data not syncing when in DST
  • Added low battery notification

0.9.2
Stop notification when call answered
Fix sending weather on interval
Add more languages for watch (only works if supported by FW)

0.9.1
Fixed crash for new users
Weather UI fixes
Whitelisted some more firmware
Translation updates
Bugfixes for daemon/ui split

0.9.0
***ONLY FOR SAILFISHOS >= 3.0.3***
Daemon/UI split
Reworked some pages to streamline them

0.8.9
Add buffer for 10 notifications when watch disconnected

0.8.8
Added deep sleep value to page
Save GPX files in data location not cache location
May install on SFOS 3.0.3 when available

0.8.7
New UI layout
Sleep statistics

0.8.5
Added step summary chart showing steps over previous 20 days from the selected day
Added auto-sync of activity data which occurs each hour

0.8.2
Fixed applying settings from the UI

0.8.1
Hopefully fixed crash introduced in 0.8.0

0.8.0
Major code restructure to better allow support for other devices (devs needed!)
Whitelist new Bip frmwares
Hopefully fixed GPS issue with new firmwares

 

0.7.5
Implemented sending weather
Fixed app displaying correct status when watch disconnects
Use correct icon for depecher
Fix layout of HR button

 

0.7.3
Updated translations
Fixed user profile settings page not opening

Comments

Branja's picture

Branja

Thu, 2019/12/05 - 10:33

Amazing! I know it's a noobish question but, how can I do that?

 

edit: I successfully connected Mi Band 2 but I still can't connect BIP Lite. It says authfailed. I read about it online a little bit (on the Gadgetbridge wiki) and it turns out that all the newer devices, including BIP Lite, need an official app in order to pair because they require a server-based pairing. Now, there is an easy way to obtain a pairing key on an Android-based phone via a cracked Mi Fit app. Is there a way that You can implement pairing keys into your app or should I sell my BIP Lite and order an original BIP watch? p.s. Sorry for bothering you and demanding certain things. I am just a noob who feels love for this kind of technology. I will help you out however I can.

piggz's picture

piggz

Thu, 2019/12/05 - 14:18

ive just read up on server based pairing, and i should be able to implement it, but you will have to expect to wait a little while.

Branja's picture

Branja

Thu, 2019/12/05 - 15:16

Not a problem, kind sir. I will wait as long as it takes. Please, let me know if I need to test something out.

alex000090's picture

alex000090

Sun, 2019/11/24 - 09:37

Good morning!

I try flash new firmware for watch, but when I open FW.latin file (first), the program write "Invalid" in type string. I use last version of the program.

Branja's picture

Branja

Tue, 2019/11/19 - 22:46

Guys, I am planning to buy a Sony Xperia XA2 and an Amazfit BIP Lite. Can somebody confirm that these two will work together?

jpn9s's picture

jpn9s

Fri, 2019/11/22 - 09:42

I can confirm that Amazfit Cor with Amazfisf app works quite well in my XA2 Sfos 3.2.0.12. I suppose Cor might be quite near Bip, but I do not know Bip Lite.

Branja's picture

Branja

Mon, 2019/12/02 - 12:32

Thank you for your reply. I am a bit worried because I read that those new devices (BIP Lite, Mi Band 4, Amazfit GTR) require a server-based paring at first. This means that one needs to pair either of these devices with a Mi Fit app and then obtain a pairing key (at least, that's the case on Android). I ordered an Amazfit BIP Lite, and I want to buy an Xperia XA2 and to run Sailfish on it. I would be hugely disappointed in case I cannot do that, and that I need to return to Android.

foffo's picture

foffo

Wed, 2019/10/02 - 22:06 

Does it work with a Band I 4?
ronny_b's picture

ronny_b

Mon, 2019/09/30 - 20:34

I no longer get my AmazfitBIP paired. Amazfish runs on the XperiaX with Sailfish 3.1.0.11. The clock is displayed in the Bluetooth settings under paired devices. It is also found by the app and the following text is displayed:

Connecting to watch...
/org/bluez/hci0/dev_F0_1A_...
pairing

That's all there is to it.

 
What have I already tried...

- Switch Bluetooth off and on again
- In the settings of the "Stop and Start Service" app

When I connect the clock in the shell via bluetoothctl, I get the following:

[Amazfit Bip Watch]# info F0:1A:...
Device F0:1A:... (random)
Name: Amazfit Bip Watch
Alias: Amazfit Bip Watch
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific

Besides, the clock now shows connected, only the app unfortunately does not.

Here is an excerpt from the journal:
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::stopDiscovery
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::StopDiscovery: ""
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::matchDevice:looking for: "Amazfit"
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - Found: QVariant(QString, "Jolla-xxx")
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - Found: QVariant(QString, "Xperia X")
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - Found: QVariant(QString, "Amazfit Bip Watch")
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::deviceName:looking for: "/org/bluez/hci0/dev_F0_1A_..."
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::pair: "Amazfit Bip Watch" "/org/bluez/hci0/dev_F0_1A_..."
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: "Amazfit Bip Watch"
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - QBLEDevice::setDevicePath
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - true
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - AbstractDevice::pair
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::onConnectionStateChanged "pairing"
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::onConnectionStateChanged "pairing"
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - QBLEDevice::pair
Sep 30 19:07:19 Sailfish i[5258]: [D] pair:102 - Pair result: 
Sep 30 19:07:19 Sailfish i[5258]: [D] expression for onConnectionStateChanged:202 - pairing
Sep 30 19:07:19 Sailfish i[5258]: [D] expression for onConnectionStateChanged:202 - pairing
Sep 30 19:08:00 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::onRefreshTimer

What else can I try? On the PC with Android emulator and "Gadgetbridge" it can be connected without problems.

Thanks Ronny

piggz's picture

piggz

Wed, 2019/10/02 - 22:46

Does the device mac address match in all cases?  You could try fully resetting the application with

dconf reset -f /uk/co/piggz/amazfish

 

ronny_b's picture

ronny_b

Sat, 2019/10/05 - 17:41

Thanks for the answer. I reserve that as my last option.

I have tried pairing the phone with another device. After I have removed this connection, the Amazfish app connects automatically. Unfortunately, the activity data does not arrive completely in the database. After about 25 hours no more lines are created in the Kexi-file and nothing is displayed in the diagram. In the home directory 7.4GB are still free.

So I probably can't get around it...

Ronny

piggz's picture

piggz

Sat, 2019/10/05 - 19:39

Yeah, i have a known issue with how times are saved for the last sync, ill be working on it soon

EEvnos's picture

EEvnos

Mon, 2019/09/30 - 20:06

This is amazing software and works VERY well.

The one issue I'm having is that when setting the Distance Unit to Imperial (under Device Settings) it does not seem to save the settings.

The settings on the watch don't change and the app is defaulted back to Metric when going back into the settings.

piggz's picture

piggz

Wed, 2019/10/02 - 22:43

Thanks for the feedback.  Could you you rasie an Issue on github?

localhorst's picture

localhorst

Thu, 2019/09/19 - 09:33 

Very nice app for my Amazfit Bip. The connection to the app works, but the data transfer only works sometimes. When I first retrieve the data it works, the second time it stops working. And if he has loaded the data the first time, then he does not display it in the diagram. I'm looking forward to more updates.
mugshot's picture

mugshot

Mon, 2019/09/16 - 13:48

The sleep data seems to be not working... Claims I've slept from 15.9. to 24.9. ~14 hours each night and today is 16.9...

Okerampa's picture

Okerampa

Wed, 2019/08/07 - 16:34

Hello, I have a strange issue where I factory reset the watch, then update with mii (latest version), then amazfish seems not to connect... So I removed the pairing and tried again.
But then, the phone is in a loop (seems infinite) when I try to pair with bluetooth settings... And in amazfish, even if I unpaired it tries to connect to the watch, not seeing there is nothing paired.

Is there a way to force remove the watch in amazfish ? Or is it linked to paired devices and I have a bug with sailfish last version (I'm on 3.1 on xperia X)

Thanks... 

slava's picture

slava

Sun, 2019/07/28 - 19:52 

Fatal error: nothing provides libKDb3.so.4 needed by harbour-amazfish-0.9.2-1.armv7hl
slava's picture

slava

Mon, 2019/07/29 - 00:25

I mean, if I spent a bit more time on it, I would probably find rpm providing libKDb3.so.4 or even built one myself but it would be so much friendlier if everything (which is not part of the platform) necessary to build and install the app would be in one package and one git repo... And if I could build and debug this thing myself, it would be so much more likely that I would contribute something. When I tried to build this thing in OBS it gave me nothing provides kdb-devel >= 3.1.0, nothing provides kcoreaddons-devel >= 5.31.0". Bummer!

piggz's picture

piggz

Mon, 2019/07/29 - 17:21

Lets talk in #sailfishos!

carmeloferso's picture

carmeloferso

Sun, 2019/07/28 - 16:34

Can't install on XA2 running 3.1.0.11, log below:

carmeloferso's picture

carmeloferso

Thu, 2019/08/01 - 20:17

app installed on 3.1.0.11 after:

pkcon refresh && pkcon install zypper

zypper refresh

Mariusmssj's picture

Mariusmssj

Fri, 2019/07/19 - 17:59

For those strugling to connect to the watch after a reboot what seems to work for me is:

  1. Connect via system bluebooth setting to the watch
  2. Open the Amazfish app and select Connect to watch
  3. Select Pair with watch and wait the app to find the watch and start pairing
  4. Open system bluetooth settings again and disconnect from the watch and reconnect
  5. Open amazfish app again and go back to home page and it should finish the pairing process and connect to the watch properly
nobodyinperson's picture

nobodyinperson

Thu, 2019/07/18 - 08:36

Yes, that seems to be the case:

https://together.jolla.com/question/8589/proper-bluetooth-le-support/?an...

Maybe you could put a little warning in the Amazfish description that it doesn't work for the Jolla 1 for now. With Mi Fit being uninstallable, the Bip rather degrades to a „dumbwatch” with a Jolla 1. Well, at least battery life will be at max :-)

nobodyinperson's picture

nobodyinperson

Wed, 2019/07/17 - 22:30

Is this supposed to work with a Jolla 1? No matter what I do, my freshly bought and via Mi Fit updated Amazfit Bip (FW 1.1.5.56) just won't show up even in Jolla Bluetooth settings... :-(

piggz's picture

piggz

Wed, 2019/07/17 - 22:57

i would giess the J1 doesnt support BLE if it doesnt even show in the BT settings .

timeral's picture

timeral

Fri, 2019/07/12 - 15:10

Great work.
Any plan for amazfit verge lite?

aerique's picture

aerique

Thu, 2019/07/11 - 15:28

First of all: thanks for your great work!

Pairing is a pain in the ass, but once it works it's awesome.

Secondly, for me "Sync activity data every hour" does not seem to work. (This is on an XA2 device.)

Mariusmssj's picture

Mariusmssj

Mon, 2019/07/01 - 10:29

Hello,

Been having real issues connecting back the watch after a phone reboot, my procedure after reboot:

- Using phone settings connect to the amazfit bip via bluetooth

- Phone says connected and watch says connected

- Open the app and pull to option "Connect to watch", the "Start service" button apears for 5 seconds and then dissapears

- This is the output from journalctl:

[root@Sailfish nemo]# journalctl | grep amazfish
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - Starting amazfish daemon
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - BluezAdapter::BluezAdapter
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - amazfish-daemon: succesfully registered to dbus sessionBus
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - Registered notifications listener for device
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: ""
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceFactory::createDevice: no suitable devices found, creating a Bip device as default
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DRIVERS:  ("org.kde.kdb.sqlite")
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - KDbConnection object created.
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - KDbConnection::connect() OK.
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - ("mi_band_activity", "sports_data")
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - VoiceCallsChanged
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - ActiveVoiceCallChanged
Jul 01 07:35:01 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - no notification service, buffering notification
Jul 01 07:35:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:36:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:37:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:38:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:39:03 Sailfish i[7294]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:39:04 Sailfish lipstick[4099]: [D] onCompleted:263 - coverActionIndicators created harbour-amazfish-ui.desktop
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::connectToDevice: ""
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - QBLEDevice::setDevicePath
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: process 4858: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed
in file dbus-message.c line 1367.
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: This is normally a bug in some application using the D-Bus library.
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: D-Bus not built with -rdynamic so unable to print a backtrace
Jul 01 07:39:18 Sailfish systemd[3414]: harbour-amazfish.service: Main process exited, code=killed, status=6/ABRT
Jul 01 07:39:18 Sailfish systemd[3414]: harbour-amazfish.service: Unit entered failed state.
Jul 01 07:39:18 Sailfish systemd[3414]: harbour-amazfish.service: Failed with result 'signal'.
Jul 01 07:39:23 Sailfish systemd[3414]: harbour-amazfish.service: Service hold-off time over, scheduling restart.
Jul 01 07:39:23 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - Starting amazfish daemon
Jul 01 07:39:23 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - BluezAdapter::BluezAdapter
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - amazfish-daemon: succesfully registered to dbus sessionBus
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - Registered notifications listener for device
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: ""
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DeviceFactory::createDevice: no suitable devices found, creating a Bip device as default
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DRIVERS:  ("org.kde.kdb.sqlite")
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - KDbConnection object created.
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - KDbConnection::connect() OK.
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - ("mi_band_activity", "sports_data")
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - VoiceCallsChanged
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - ActiveVoiceCallChanged
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DeviceInterface::connectToDevice: ""
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - QBLEDevice::setDevicePath
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: process 7579: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed
in file dbus-message.c line 1367.
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: This is normally a bug in some application using the D-Bus library.
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: D-Bus not built with -rdynamic so unable to print a backtrace
Jul 01 07:39:49 Sailfish systemd[3414]: harbour-amazfish.service: Main process exited, code=killed, status=6/ABRT
Jul 01 07:39:49 Sailfish systemd[3414]: harbour-amazfish.service: Unit entered failed state.
Jul 01 07:39:49 Sailfish systemd[3414]: harbour-amazfish.service: Failed with result 'signal'.
Jul 01 07:39:54 Sailfish systemd[3414]: harbour-amazfish.service: Service hold-off time over, scheduling restart.
Jul 01 07:39:54 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - Starting amazfish daemon
Jul 01 07:39:54 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - BluezAdapter::BluezAdapter
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - amazfish-daemon: succesfully registered to dbus sessionBus
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - Registered notifications listener for device
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: ""
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - DeviceFactory::createDevice: no suitable devices found, creating a Bip device as default
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - DRIVERS:  ("org.kde.kdb.sqlite")
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - KDbConnection object created.
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - KDbConnection::connect() OK.
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - ("mi_band_activity", "sports_data")
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - VoiceCallsChanged
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - ActiveVoiceCallChanged

 

 

 

What am I doing wrong?

fravaccaro's picture

fravaccaro

Mon, 2019/06/17 - 22:03

Is support for Mi Band 4 planned?

Pages