Amazfish

Rating: 
4.743905
Your rating: None Average: 4.7 (82 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: 
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

erdzas's picture

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's picture

So, everytime I reboot my xperia 10+, I have to pair my Bip again..

carmenfdezb's picture

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's picture

С Mi Band 4 будет работать?

erdzas's picture

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's picture

Wait fo rnext release :)

jpn9s's picture

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's picture

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's picture

I can not understand the reason, then connect then not, firmware 1.1.6.36

Georgiy's picture

I will test,I have no choice, I left Android

piggz's picture

File an issue on github containing logs from journal, eg, as root, journalctl | grep amazfish

Georgiy's picture

Updated the watch to version 1.1.6.35 today, via Android on another phone, stopped connecting at all.

alex000090's picture

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's picture

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's picture

Sorry for bad english.

Georgiy's picture

Not working.

Georgiy's picture

All right,we need an automatic reconnect.

piggz's picture

it does, it checks once a minute and has worked fine for quite some time.  What is not working?

ronny_b's picture

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's picture

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's picture

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's picture

I found the problem

ronny_b's picture

Thanks, that was quick! I'm going to test it.

D_R's picture

Dear Adam,
It's working now. You made my day! Thank you very much for your personal assistance!!!

D_R's picture

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's picture

can you supply the logs you get as root

D_R's picture

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's picture

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's picture

No unfortunately not. The graphs are empty and when I try to download data I get always 'No data to transfer'

piggz's picture

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