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.
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.
There are 3 tiers of supported devices:
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
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
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
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
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:
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.
Pairing Issues
Pairing works for myself, sometimes I have to try twice. If pairing doesnt work at all, then try:
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
Todo
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.
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:
2.0.3
2.0.2 - Now for 4.1
2.0.0 (incl unreleased 1.9.9)
1.9.8
1.9.7
1.9.6
1.9.5 (includes unreleased changes for otehr distros)
1.9.0
1.8.7
1.8.6 (not release for sailfish)
1.8.5
1.8.2
1.8.1 - Includes 1.8.0 which was skipped
1.7.1
1.7.0
1.6.8
1.6.7
1.6.6.
1.6.5
1.6.1
1.6.0
1.5.6
1.5.5
1.5.1
1.5.0
1.4.5
1.4.0
1.3.1
1.3.0
1.2.0
1.1.3
1.1.2
1.1.1
1.1.0
1.0.0
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
erdzas
Thu, 2020/02/06 - 20:59
Permalink
Hi @piggz.
I found some small bugs with my GTS and the 1.1.0-1:
First of all, I get two notifications on the watch for one on the phone.
Second, I have a button to mark the notification as read, but in the majority I don’t have it.
Thirdly the time format displayed on the watch is in 12Hrs while in the settings I selected 24Hrs (bug also present on my miband2)
Sanpo
Sat, 2020/02/01 - 21:15
Permalink
So, everytime I reboot my xperia 10+, I have to pair my Bip again..
carmenfdezb
Thu, 2020/01/30 - 21:25
Permalink
Hi @piggz!
I'm trying to analize the database but I don't understand some values (for example, a lot of values in 'heartbeat' are '255' in my database). I'll be very grateful if you explain here or in github the meaning of fields in database.
Thanks in advance!
MihailSafonov
Thu, 2020/01/30 - 09:02
Permalink
С Mi Band 4 будет работать?
erdzas
Mon, 2020/01/27 - 23:29
Permalink
Hi @piggz.
First, nice app, it work well for cor and miband 2.
Is theire any workaround to pair with GTS, for now?
Or must we wait the next realase?
Now when I try to pair, the app stay at "connecting to watch" stage
piggz
Tue, 2020/01/28 - 00:06
Permalink
Wait fo rnext release :)
jpn9s
Sat, 2020/01/25 - 11:00
Permalink
Good morning. I have Amazfit Cor plus Amazfish together XA2 SFOS 3.2.1.20. Everything works perfect, but the calendar alarms in the phone are not shown in my Amazfit Cor. Calls and messages are shown. Also putting on Android support is shown in my Cor. What do I have to do that also calendar alarms are shown, or are they not allowed yet? Thank you for your Amazfish and for your help.
alex000090
Wed, 2020/01/22 - 08:30
Permalink
Dear piggz,
There is the problem with newest version of the program or my firmware. I can't switch on/off alarms from the clock. So, if in the program alarm is on and I switch off it from the clock it again switch on itself afrer some time.
Georgiy
Sun, 2020/01/19 - 17:00
Permalink
I can not understand the reason, then connect then not, firmware 1.1.6.36
Georgiy
Sat, 2020/01/18 - 19:21
Permalink
I will test,I have no choice, I left Android
piggz
Sat, 2020/01/18 - 19:37
Permalink
File an issue on github containing logs from journal, eg, as root, journalctl | grep amazfish
Georgiy
Sat, 2020/01/18 - 19:10
Permalink
Updated the watch to version 1.1.6.35 today, via Android on another phone, stopped connecting at all.
alex000090
Thu, 2020/01/23 - 22:25
Permalink
I've update to 1.1.6.36 from android. There is no problem with connection to amazfish. But first of all I remove my watch from mi fit with rebooting the watch.
piggz
Sat, 2020/01/18 - 19:17
Permalink
You might have made it incompatible (for the moment) ... some newer devices use a server based pairing mode, and there is some comment that older devices with newer fw also use this pairing method. I am writing such support for the amazfit GTS, but not tried on a Bip yet on the latest FW.
Georgiy
Fri, 2020/01/17 - 21:08
Permalink
Sorry for bad english.
Georgiy
Fri, 2020/01/17 - 21:07
Permalink
Not working.
Georgiy
Fri, 2020/01/17 - 20:53
Permalink
All right,we need an automatic reconnect.
piggz
Fri, 2020/01/17 - 21:02
Permalink
it does, it checks once a minute and has worked fine for quite some time. What is not working?
ronny_b
Wed, 2020/01/15 - 21:06
Permalink
Dear Adam,
since the last update, the alarm clocks can be switched on and off on the BIP, but the app will overwrite them again. Has anything been changed here?
Ronny
piggz
Wed, 2020/01/15 - 21:17
Permalink
I dont _think_ I changed anything. It should only overwrite when you click the save button on the alarms page. There doesnt seem to be a way to read the alarms back from the watch. I will double check that alarms arnt being written at other times.
ronny_b
Wed, 2020/02/05 - 21:27
Permalink
The problem only seems to occur when the connection between the watch and the mobile phone is lost. Once the watch is back in range and connected to the phone, the alarms on the watch are overwritten. I have seen this happen several times now on both our mobile phones.
Ronny
piggz
Wed, 2020/02/05 - 23:23
Permalink
I found the problem
ronny_b
Thu, 2020/02/06 - 20:14
Permalink
Thanks, that was quick! I'm going to test it.
D_R
Tue, 2020/01/14 - 10:08
Permalink
Dear Adam,
It's working now. You made my day! Thank you very much for your personal assistance!!!
D_R
Mon, 2020/01/13 - 16:14
Permalink
Thank you for your response.
I have 5mins too for HRM intervall. When I'm running journalctl as user memo I'm getting: No journal files found. As root ther is something loged. But my graphs are still empty.
piggz
Mon, 2020/01/13 - 22:03
Permalink
can you supply the logs you get as root
D_R
Tue, 2020/01/14 - 00:16
Permalink
Here is the log:
[root@Sailfish nemo]# journalctl -f |grep amazfish
Jan 13 22:10:38 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jan 13 22:10:57 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - AbstractDevice::reconnectionTimer
Jan 13 22:10:59 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000007-0000-3512-2118-0009af100700" "0c76120000610c000036000000"
Jan 13 22:10:59 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...Got realtime steps: 13
Jan 13 22:10:59 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - slot_informationChanged AbstractDevice::Info(INFO_STEPS) "4726"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last sync was -3600000 QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last activity sync was QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - UTC offset it 3600
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - converted date QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00) to "\xB2\x07\x01\x01\x00\x00\x00\x04"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000005-0000-3512-2118-0009af100700"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000004-0000-3512-2118-0009af100700"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "0101b207010100000004"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "02"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100104"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Unexpected activity metadata: "\x10\x01\x04"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100204"
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - No data left to fetch
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:10 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last sync was -3600000 QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last activity sync was QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - UTC offset it 3600
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - converted date QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00) to "\xB2\x07\x01\x01\x00\x00\x00\x04"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000005-0000-3512-2118-0009af100700"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000004-0000-3512-2118-0009af100700"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "0101b207010100000004"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "02"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100104"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Unexpected activity metadata: "\x10\x01\x04"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100204"
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - No data left to fetch
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:11:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:11:38 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jan 13 22:11:41 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00002a37-0000-1000-8000-00805f9b34fb"
Jan 13 22:11:41 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00002a39-0000-1000-8000-00805f9b34fb" : "150100"
Jan 13 22:11:41 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00002a39-0000-1000-8000-00805f9b34fb" : "150201"
Jan 13 22:11:55 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - HRM Changed: "00002a37-0000-1000-8000-00805f9b34fb" "\x00""D"
Jan 13 22:11:55 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ..got HR measurement
Jan 13 22:11:55 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - slot_informationChanged AbstractDevice::Info(INFO_HEARTRATE) "68"
Jan 13 22:11:57 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - AbstractDevice::reconnectionTimer
Jan 13 22:11:57 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - HRM Changed: "00002a37-0000-1000-8000-00805f9b34fb" "\x00""C"
Jan 13 22:11:57 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ..got HR measurement
Jan 13 22:11:57 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - slot_informationChanged AbstractDevice::Info(INFO_HEARTRATE) "67"
Jan 13 22:11:58 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000007-0000-3512-2118-0009af100700" "0c76120000610c000036000000"
Jan 13 22:11:58 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...Got realtime steps: 13
Jan 13 22:11:58 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - slot_informationChanged AbstractDevice::Info(INFO_STEPS) "4726"
Jan 13 22:12:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 0 0
Jan 13 22:12:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Setting profile "Denis" 65917399 0 175 82 QDate("1973-10-11")
Jan 13 22:12:27 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000008-0000-3512-2118-0009af100700" : "4f0000b5070a0b00af005200d7d1ed03"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 1 1
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000008-0000-3512-2118-0009af100700" : "1000001027000000"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 2 2
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000003-0000-3512-2118-0009af100700" : "06060001"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 5 5
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000003-0000-3512-2118-0009af100700" : "06050000"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 3 3
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Setting HRM monitoring to 5
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00002a39-0000-1000-8000-00805f9b34fb" : "1405"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Stopping notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000003-0000-3512-2118-0009af100700" "1006060001"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000003-0000-3512-2118-0009af100700" "1006050001"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 4 4
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Setting HRM sleept support to true
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00002a39-0000-1000-8000-00805f9b34fb" : "150001"
Jan 13 22:12:28 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Stopping notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:38 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 0 0
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Setting profile "Denis" 65917399 0 175 82 QDate("1973-10-11")
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000008-0000-3512-2118-0009af100700" : "4f0000b5070a0b00af005200d7d1ed03"
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 1 1
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000008-0000-3512-2118-0009af100700" : "1000001027000000"
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 2 2
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000003-0000-3512-2118-0009af100700" : "06060001"
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 5 5
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000003-0000-3512-2118-0009af100700" : "06050000"
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 3 3
Jan 13 22:12:46 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Setting HRM monitoring to 5
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00002a39-0000-1000-8000-00805f9b34fb" : "1405"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Stopping notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000003-0000-3512-2118-0009af100700" "1006060001"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000003-0000-3512-2118-0009af100700" "1006050001"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Apply setting: 4 4
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Setting HRM sleept support to true
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00002a39-0000-1000-8000-00805f9b34fb" : "150001"
Jan 13 22:12:47 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Stopping notify for "00002a39-0000-1000-8000-00805f9b34fb"
Jan 13 22:12:57 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - AbstractDevice::reconnectionTimer
Jan 13 22:12:57 Sailfish i[12023]: [D] unknown:0 - QUrl("https://nominatim.openstreetmap.org/reverse.php?format=json&zoom=6&lat=4...")
Jan 13 22:12:57 Sailfish i[12023]: [D] unknown:0 - QUrl("https://nominatim.openstreetmap.org/reverse.php?format=json&zoom=6&lat=4...")
Jan 13 22:12:58 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000007-0000-3512-2118-0009af100700" "0c76120000610c000036000000"
Jan 13 22:12:58 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...Got realtime steps: 13
Jan 13 22:12:58 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - slot_informationChanged AbstractDevice::Info(INFO_STEPS) "4726"
Jan 13 22:12:59 Sailfish i[12023]: [D] unknown:0 - QUrl("https://nominatim.openstreetmap.org/reverse.php?format=json&zoom=6&lat=5...")
Jan 13 22:12:59 Sailfish i[12023]: [D] unknown:0 - QUrl("https://nominatim.openstreetmap.org/reverse.php?format=json&zoom=6&lat=5...")
Jan 13 22:12:59 Sailfish i[12023]: [D] unknown:0 - QUrl("https://nominatim.openstreetmap.org/reverse.php?format=json&zoom=6&lat=5...")
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last sync was -3600000 QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last activity sync was QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - UTC offset it 3600
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - converted date QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00) to "\xB2\x07\x01\x01\x00\x00\x00\x04"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000005-0000-3512-2118-0009af100700"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000004-0000-3512-2118-0009af100700"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "0101b207010100000004"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "02"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100104"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Unexpected activity metadata: "\x10\x01\x04"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100204"
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - No data left to fetch
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:19 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last sync was -3600000 QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last activity sync was QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - UTC offset it 3600
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - converted date QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00) to "\xB2\x07\x01\x01\x00\x00\x00\x04"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000005-0000-3512-2118-0009af100700"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000004-0000-3512-2118-0009af100700"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "0101b207010100000004"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "02"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100104"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Unexpected activity metadata: "\x10\x01\x04"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100204"
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - No data left to fetch
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:26 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last sync was -3600000 QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - last activity sync was QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00)
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - UTC offset it 3600
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - converted date QDateTime(1970-01-01 00:00:00.000 UTC+01:00 Qt::TimeSpec(TimeZone) UTC+01:00) to "\xB2\x07\x01\x01\x00\x00\x00\x04"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000005-0000-3512-2118-0009af100700"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Starting notify for "00000004-0000-3512-2118-0009af100700"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "0101b207010100000004"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Writing to "00000004-0000-3512-2118-0009af100700" : "02"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 2
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100104"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - Unexpected activity metadata: "\x10\x01\x04"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - MiBand Changed: "00000004-0000-3512-2118-0009af100700" "100204"
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - ...got metadata
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - No data left to fetch
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is firmware operation running: 0
Jan 13 22:13:31 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - is miband operation running: 0
Jan 13 22:13:38 Sailfish harbour-amazfishd[14225]: [D] unknown:0 - DeviceInterface::onRefreshTimer
piggz
Tue, 2020/01/14 - 00:20
Permalink
Ok, somehow your settings are messed up and its trying to sync an invalid date. try:
dconf reset /uk/co/piggz/amazfish/device/lastactivitysyncmillis
D_R
Mon, 2020/01/13 - 08:06
Permalink
No unfortunately not. The graphs are empty and when I try to download data I get always 'No data to transfer'
piggz
Mon, 2020/01/13 - 10:00
Permalink
under settings, user, have you enabled 'all day hrm'? my interval is 5. also, the real logs i need are fron the journal, preferably after a stop/start of the service . use joirnalctl for this
Pages