Amazfish

piggz's picture
Submitted by piggz on Sun, 2021/07/11 - 01:29
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: 

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

vige's picture

vige

Mon, 2020/04/20 - 12:09

Sorry, I can't remember anymore :/ I'd say it's quite likely that I had not deleted the old device before the first attempt.

jpn9s's picture

jpn9s

Fri, 2020/04/24 - 10:35

One strange thing in Amazfish 1.4.5: At the moment I have as active two alarms just on Thursday. However these alarms are alarming me every day at set time values. It seems that 'Save settings' - buttoms are stuck somehow inside Alarm-sheet. Is this a bug or what? Otherwise everything works as it should. I have Amazfit Cor & Xperia XA2 SFOS 3.3.0.14.

Addition: I have rebooted twice until now.

Addition: Still continuing after 1.5.0.

sashikknox's picture

sashikknox

Tue, 2020/04/14 - 09:04

With 1.4.5-1 its show my data about sleep, pulse and training just once, in first start of new version , now juts show empty pages without any data
Sailfish 3.3.0.14, MiBand 3
and it not show weather icon in settings

sashikknox's picture

sashikknox

Tue, 2020/04/14 - 09:21

Downgrade to 1.4.0, 1.3 not helps, now all pages with data are empty, seems like all data lost... sad )

piggz's picture

piggz

Tue, 2020/04/14 - 11:23

unlikely that the upgrade broke anythng.... have to rebooted?  can you check the database contents using sqlite3?  any logs?

sashikknox's picture

sashikknox

Thu, 2020/04/16 - 16:09

After reboot, its now show all again, exclude day, when it was updated... Seems like amazfish service is was stoped after update.
Now it work normal

rdomschk's picture

rdomschk

Sun, 2020/04/12 - 21:28

Hello piggz - Thank you verry much! Now it's work perfect and the DST bug is solved! It is a great easter gift. Stay healthy...

jpn9s's picture

jpn9s

Sun, 2020/04/12 - 19:54

Dear piggz,

Thank you. Cor with XA2 SFOS 3.3.0.14 works now excellently after 1.4.0 update. Great!

jpn9s's picture

jpn9s

Sun, 2020/04/05 - 16:25

Also weather on Amazfit Cor shows ? on cloud. When the weather icon is opened on the watch , there is shown "Connect app to update". Does LUKS prevent this? Good luck for updating. 

Update: Since two days from starting the error and since a couple of hours of writing the above, weather of Amazfit Cor started suddently syncronising. :) : )

rdomschk's picture

rdomschk

Sat, 2020/04/04 - 09:18

The same by me on Sony Xperia 10 Dual SFOS 3.2.1! + Amazfit GTS - no views in all sheets sind 30.03.2020. I deleted all Data and reinstall but its not solved. Any ideas?

piggz's picture

piggz

Sat, 2020/04/04 - 11:26

Yes, wait patiently me for me to fix DST handling :)

rdomschk's picture

rdomschk

Sat, 2020/04/04 - 15:33

Many thanks in advance - I have just dealt with DST and now understand what it will be. That will not be easy. I wish you every success and a nice weekend.
Stay healthy!

jpn9s's picture

jpn9s

Wed, 2020/04/01 - 15:54

I have Amazfit Cor + X XA2 3.2.1.20. I noticed just that Amazfish app does not show anymore steps, heart beats and intensity in the graphs anymore since March 30th? What are the problems?

Addition: If I enable encryption LUKS when SFOS 3.3.0 shall come, does this have influence in the operability of Amazfit Cor & Amazfish app? At the moment everything works without any encryption. Thank you for any help.

Addition: Restarting of Cor does not help anything. Something error due to change from winter time to summertime, +1 hour jump forward on Sunday 29th March? Only direct line on the graphs on Sunday.

ronny_b's picture

ronny_b

Thu, 2020/04/02 - 19:16

Hi,
I have the same problem with my Bip. Here's an extract from the database:

INSERT INTO mi_band_activity VALUES(731125,1585465140,'2020-03-29T07:59:00',xxxxxxxxx,xxxxxxxx,0,0,112,67);
INSERT INTO mi_band_activity VALUES(731126,1585465200,'2020-03-29T08:00:00',xxxxxxxxx,xxxxxxxx,0,0,112,255);
INSERT INTO mi_band_activity VALUES(731127,1585465260,'2020-03-29T08:01:00',xxxxxxxxx,xxxxxxxx,17,0,112,84);
INSERT INTO mi_band_activity VALUES(731128,1585465320,'2020-03-29T08:02:00',xxxxxxxxx,xxxxxxxx,2,0,112,255);
INSERT INTO mi_band_activity VALUES(731129,1585465380,'2020-03-29T08:03:00',xxxxxxxxx,xxxxxxxx,0,0,112,79);
INSERT INTO mi_band_activity VALUES(731130,1585465440,'2020-03-29T08:04:00',xxxxxxxxx,xxxxxxxx,0,0,112,255);
INSERT INTO mi_band_activity VALUES(731131,1585465500,'2020-03-29T08:05:00',xxxxxxxxx,xxxxxxxx,0,0,112,74);
INSERT INTO mi_band_activity VALUES(731132,1585465560,'2020-03-29T08:06:00',xxxxxxxxx,xxxxxxxx,0,0,112,255);
INSERT INTO mi_band_activity VALUES(731133,1585465620,'2020-03-29T08:07:00',xxxxxxxxx,xxxxxxxx,0,0,112,75);
INSERT INTO mi_band_activity VALUES(731134,1585465680,'2020-03-29T08:08:00',xxxxxxxxx,xxxxxxxx,20,0,122,255);
INSERT INTO mi_band_activity VALUES(731135,1585465740,'2020-03-29T08:09:00',xxxxxxxxx,xxxxxxxx,20,0,122,77);
INSERT INTO mi_band_activity VALUES(731136,1585465800,'2020-03-29T08:10:00',xxxxxxxxx,xxxxxxxx,0,0,112,255);
INSERT INTO mi_band_activity VALUES(731137,1585465860,'2020-03-29T08:11:00',xxxxxxxxx,xxxxxxxx,0,0,112,78);
INSERT INTO mi_band_activity VALUES(731138,1585465920,'2020-03-29T08:12:00',xxxxxxxxx,xxxxxxxx,19,0,112,255);
INSERT INTO mi_band_activity VALUES(731139,1585465980,'2020-03-29T08:13:00',xxxxxxxxx,xxxxxxxx,61,0,121,75);
INSERT INTO mi_band_activity VALUES(731140,1585466040,'2020-03-29T08:14:00',xxxxxxxxx,xxxxxxxx,20,0,112,255);
INSERT INTO mi_band_activity VALUES(731141,1585466100,'2020-03-29T08:15:00',xxxxxxxxx,xxxxxxxx,3,0,121,84);
INSERT INTO mi_band_activity VALUES(731142,1585466160,'2020-03-29T08:16:00',xxxxxxxxx,xxxxxxxx,6,0,112,255);
INSERT INTO mi_band_activity VALUES(731143,1585466220,'2020-03-29T08:17:00',xxxxxxxxx,xxxxxxxx,20,0,122,75);
INSERT INTO mi_band_activity VALUES(731144,1585466280,'2020-03-29T08:18:00',xxxxxxxxx,xxxxxxxx,20,0,122,255);
INSERT INTO mi_band_activity VALUES(731145,1585466340,'2020-03-29T08:19:00',xxxxxxxxx,xxxxxxxx,0,0,112,79);
INSERT INTO mi_band_activity VALUES(731146,1585466400,'2020-03-29T08:20:00',xxxxxxxxx,xxxxxxxx,4,0,112,255);
INSERT INTO mi_band_activity VALUES(731147,1585466460,'2020-03-29T08:21:00',xxxxxxxxx,xxxxxxxx,20,0,122,78);
INSERT INTO mi_band_activity VALUES(731148,1585466520,'2020-03-29T08:22:00',xxxxxxxxx,xxxxxxxx,3,0,112,255);
INSERT INTO mi_band_activity VALUES(731149,1585466580,'2020-03-29T08:23:00',xxxxxxxxx,xxxxxxxx,13,0,112,77);
INSERT INTO mi_band_activity VALUES(731150,1585466640,'2020-03-29T08:24:00',xxxxxxxxx,xxxxxxxx,12,0,112,255);
INSERT INTO mi_band_activity VALUES(731151,1585466700,'2020-03-29T08:25:00',xxxxxxxxx,xxxxxxxx,20,0,122,81);
INSERT INTO mi_band_activity VALUES(731152,1585466760,'2020-03-29T08:26:00',xxxxxxxxx,xxxxxxxx,2,0,112,255);
INSERT INTO mi_band_activity VALUES(731153,1585466820,'2020-03-29T08:27:00',xxxxxxxxx,xxxxxxxx,0,0,112,78);
INSERT INTO mi_band_activity VALUES(731154,1585466880,'2020-03-29T08:28:00',xxxxxxxxx,xxxxxxxx,31,0,112,255);
INSERT INTO mi_band_activity VALUES(731155,1585466940,'2020-03-29T08:29:00',xxxxxxxxx,xxxxxxxx,16,0,112,81);
INSERT INTO mi_band_activity VALUES(731156,1585467000,'2020-03-29T08:30:00',xxxxxxxxx,xxxxxxxx,5,0,112,255);
INSERT INTO mi_band_activity VALUES(731157,1585467060,'2020-03-29T08:31:00',xxxxxxxxx,xxxxxxxx,6,0,112,62);
INSERT INTO mi_band_activity VALUES(731158,1585467120,'2020-03-29T08:32:00',xxxxxxxxx,xxxxxxxx,7,0,112,255);
INSERT INTO mi_band_activity VALUES(731159,1585467180,'2020-03-29T08:33:00',xxxxxxxxx,xxxxxxxx,49,0,112,85);
INSERT INTO mi_band_activity VALUES(731160,1585467240,'2020-03-29T08:34:00',xxxxxxxxx,xxxxxxxx,49,0,121,77);
INSERT INTO mi_band_activity VALUES(731161,1585467300,'2020-03-29T08:35:00',xxxxxxxxx,xxxxxxxx,20,0,121,255);
INSERT INTO mi_band_activity VALUES(731162,1585467360,'2020-03-29T08:36:00',xxxxxxxxx,xxxxxxxx,70,0,112,94);
INSERT INTO mi_band_activity VALUES(731163,1585467420,'2020-03-29T08:37:00',xxxxxxxxx,xxxxxxxx,9,0,96,81);
INSERT INTO mi_band_activity VALUES(731164,1585467480,'2020-03-29T08:38:00',xxxxxxxxx,xxxxxxxx,10,0,92,255);
INSERT INTO mi_band_activity VALUES(731165,1585467540,'2020-03-29T08:39:00',xxxxxxxxx,xxxxxxxx,6,0,80,255);
INSERT INTO mi_band_activity VALUES(731166,1585467600,'2020-03-29T08:40:00',xxxxxxxxx,xxxxxxxx,35,0,80,255);
INSERT INTO mi_band_activity VALUES(731167,1585467660,'2020-03-29T08:41:00',xxxxxxxxx,xxxxxxxx,50,0,80,64);
INSERT INTO mi_band_activity VALUES(731168,1585467720,'2020-03-29T08:42:00',xxxxxxxxx,xxxxxxxx,5,0,80,255);
INSERT INTO mi_band_activity VALUES(731169,1585467780,'2020-03-29T08:43:00',xxxxxxxxx,xxxxxxxx,46,0,80,255);
INSERT INTO mi_band_activity VALUES(731170,1585467840,'2020-03-29T08:44:00',xxxxxxxxx,xxxxxxxx,60,12,80,97);
INSERT INTO mi_band_activity VALUES(731171,1585467900,'2020-03-29T08:45:00',xxxxxxxxx,xxxxxxxx,15,0,16,255);
INSERT INTO mi_band_activity VALUES(731172,1585467960,'2020-03-29T08:46:00',xxxxxxxxx,xxxxxxxx,22,0,80,255);
INSERT INTO mi_band_activity VALUES(731173,1585468020,'2020-03-29T08:47:00',xxxxxxxxx,xxxxxxxx,21,0,80,93);
INSERT INTO mi_band_activity VALUES(731174,1585468080,'2020-03-29T08:48:00',xxxxxxxxx,xxxxxxxx,24,0,80,255);
INSERT INTO mi_band_activity VALUES(731175,1585468140,'2020-03-29T08:49:00',xxxxxxxxx,xxxxxxxx,37,0,80,255);
INSERT INTO mi_band_activity VALUES(731176,1585468200,'2020-03-29T08:50:00',xxxxxxxxx,xxxxxxxx,28,0,96,255);
INSERT INTO mi_band_activity VALUES(731177,1585468260,'2020-03-29T08:51:00',xxxxxxxxx,xxxxxxxx,19,0,80,255);
INSERT INTO mi_band_activity VALUES(731178,1585468320,'2020-03-29T08:52:00',xxxxxxxxx,xxxxxxxx,70,38,1,111);
INSERT INTO mi_band_activity VALUES(731179,1585468380,'2020-03-29T08:53:00',xxxxxxxxx,xxxxxxxx,20,0,26,109);
INSERT INTO mi_band_activity VALUES(731180,1585468440,'2020-03-29T08:54:00',xxxxxxxxx,xxxxxxxx,2,0,16,255);
INSERT INTO mi_band_activity VALUES(731181,1585468500,'2020-03-29T08:55:00',xxxxxxxxx,xxxxxxxx,4,0,80,255);
INSERT INTO mi_band_activity VALUES(731182,1585468560,'2020-03-29T08:56:00',xxxxxxxxx,xxxxxxxx,4,0,80,255);
INSERT INTO mi_band_activity VALUES(731183,1585468620,'2020-03-29T08:57:00',xxxxxxxxx,xxxxxxxx,14,0,80,100);
INSERT INTO mi_band_activity VALUES(731184,1585468680,'2020-03-29T08:58:00',xxxxxxxxx,xxxxxxxx,33,0,80,255);
INSERT INTO mi_band_activity VALUES(731185,1585468740,'2020-03-29T08:59:00',xxxxxxxxx,xxxxxxxx,17,0,80,255);
INSERT INTO mi_band_activity VALUES(731186,1585468800,'2020-03-29T09:00:00',xxxxxxxxx,xxxxxxxx,38,0,80,255);
INSERT INTO mi_band_activity VALUES(731187,1585468860,'2020-03-29T09:01:00',xxxxxxxxx,xxxxxxxx,36,0,80,255);
INSERT INTO mi_band_activity VALUES(731188,1585468920,'2020-03-29T09:02:00',xxxxxxxxx,xxxxxxxx,47,0,96,68);
INSERT INTO mi_band_activity VALUES(731189,1585468980,'2020-03-29T09:03:00',xxxxxxxxx,xxxxxxxx,58,0,80,70);
INSERT INTO mi_band_activity VALUES(731190,1585469040,'2020-03-29T09:04:00',xxxxxxxxx,xxxxxxxx,56,0,80,70);
INSERT INTO mi_band_activity VALUES(731191,1585469100,'2020-03-29T09:05:00',xxxxxxxxx,xxxxxxxx,38,0,80,255);
INSERT INTO mi_band_activity VALUES(731192,1585469160,'2020-03-29T09:06:00',xxxxxxxxx,xxxxxxxx,35,0,96,255);
INSERT INTO mi_band_activity VALUES(731193,1585469220,'2020-03-29T09:07:00',xxxxxxxxx,xxxxxxxx,37,0,80,83);
INSERT INTO mi_band_activity VALUES(731194,1585469280,'2020-03-29T09:08:00',xxxxxxxxx,xxxxxxxx,45,0,80,85);
INSERT INTO mi_band_activity VALUES(731195,1585469340,'2020-03-29T09:09:00',xxxxxxxxx,xxxxxxxx,38,0,96,255);
INSERT INTO mi_band_activity VALUES(731196,1585469400,'2020-03-29T09:10:00',xxxxxxxxx,xxxxxxxx,45,0,80,72);
INSERT INTO mi_band_activity VALUES(731197,1585469460,'2020-03-29T09:11:00',xxxxxxxxx,xxxxxxxx,28,0,80,81);
INSERT INTO mi_band_activity VALUES(731198,1585469520,'2020-03-29T09:12:00',xxxxxxxxx,xxxxxxxx,20,0,106,255);
INSERT INTO mi_band_activity VALUES(731199,1585469580,'2020-03-29T09:13:00',xxxxxxxxx,xxxxxxxx,29,0,80,255);
INSERT INTO mi_band_activity VALUES(731200,1585469640,'2020-03-29T09:14:00',xxxxxxxxx,xxxxxxxx,30,0,80,255);
INSERT INTO mi_band_activity VALUES(731201,1585469700,'2020-03-29T09:15:00',xxxxxxxxx,xxxxxxxx,6,0,80,255);
INSERT INTO mi_band_activity VALUES(731202,1585469760,'2020-03-29T09:16:00',xxxxxxxxx,xxxxxxxx,14,0,96,255);
INSERT INTO mi_band_activity VALUES(731203,1585469820,'2020-03-29T09:17:00',xxxxxxxxx,xxxxxxxx,113,19,1,96);
INSERT INTO mi_band_activity VALUES(731204,1585469880,'2020-03-29T09:18:00',xxxxxxxxx,xxxxxxxx,117,51,17,96);
INSERT INTO mi_band_activity VALUES(731205,1585469940,'2020-03-29T09:19:00',xxxxxxxxx,xxxxxxxx,54,12,16,63);
INSERT INTO mi_band_activity VALUES(731206,1585470000,'2020-03-29T09:20:00',xxxxxxxxx,xxxxxxxx,17,0,96,255);
INSERT INTO mi_band_activity VALUES(731207,1585470060,'2020-03-29T09:21:00',xxxxxxxxx,xxxxxxxx,20,0,90,255);
INSERT INTO mi_band_activity VALUES(731208,1585470120,'2020-03-29T09:22:00',xxxxxxxxx,xxxxxxxx,46,0,80,255);
INSERT INTO mi_band_activity VALUES(731209,1585470180,'2020-03-29T09:23:00',xxxxxxxxx,xxxxxxxx,121,0,80,71);
INSERT INTO mi_band_activity VALUES(731210,1585466640,'2020-03-29T08:24:00',xxxxxxxxx,xxxxxxxx,12,0,112,255);
INSERT INTO mi_band_activity VALUES(731211,1585466700,'2020-03-29T08:25:00',xxxxxxxxx,xxxxxxxx,20,0,122,81);
INSERT INTO mi_band_activity VALUES(731212,1585466760,'2020-03-29T08:26:00',xxxxxxxxx,xxxxxxxx,2,0,112,255);
INSERT INTO mi_band_activity VALUES(731213,1585466820,'2020-03-29T08:27:00',xxxxxxxxx,xxxxxxxx,0,0,112,78);
INSERT INTO mi_band_activity VALUES(731214,1585466880,'2020-03-29T08:28:00',xxxxxxxxx,xxxxxxxx,31,0,112,255);
INSERT INTO mi_band_activity VALUES(731215,1585466940,'2020-03-29T08:29:00',xxxxxxxxx,xxxxxxxx,16,0,112,81);
INSERT INTO mi_band_activity VALUES(731216,1585467000,'2020-03-29T08:30:00',xxxxxxxxx,xxxxxxxx,5,0,112,255);
INSERT INTO mi_band_activity VALUES(731217,1585467060,'2020-03-29T08:31:00',xxxxxxxxx,xxxxxxxx,6,0,112,62);
INSERT INTO mi_band_activity VALUES(731218,1585467120,'2020-03-29T08:32:00',xxxxxxxxx,xxxxxxxx,7,0,112,255);
INSERT INTO mi_band_activity VALUES(731219,1585467180,'2020-03-29T08:33:00',xxxxxxxxx,xxxxxxxx,49,0,112,85);
INSERT INTO mi_band_activity VALUES(731220,1585467240,'2020-03-29T08:34:00',xxxxxxxxx,xxxxxxxx,49,0,121,77);
INSERT INTO mi_band_activity VALUES(731221,1585467300,'2020-03-29T08:35:00',xxxxxxxxx,xxxxxxxx,20,0,121,255);
INSERT INTO mi_band_activity VALUES(731222,1585467360,'2020-03-29T08:36:00',xxxxxxxxx,xxxxxxxx,70,0,112,94);
INSERT INTO mi_band_activity VALUES(731223,1585467420,'2020-03-29T08:37:00',xxxxxxxxx,xxxxxxxx,9,0,96,81);
INSERT INTO mi_band_activity VALUES(731224,1585467480,'2020-03-29T08:38:00',xxxxxxxxx,xxxxxxxx,10,0,92,255);
INSERT INTO mi_band_activity VALUES(731225,1585467540,'2020-03-29T08:39:00',xxxxxxxxx,xxxxxxxx,6,0,80,255);
INSERT INTO mi_band_activity VALUES(731226,1585467600,'2020-03-29T08:40:00',xxxxxxxxx,xxxxxxxx,35,0,80,255);
INSERT INTO mi_band_activity VALUES(731227,1585467660,'2020-03-29T08:41:00',xxxxxxxxx,xxxxxxxx,50,0,80,64);
INSERT INTO mi_band_activity VALUES(731228,1585467720,'2020-03-29T08:42:00',xxxxxxxxx,xxxxxxxx,5,0,80,255);
INSERT INTO mi_band_activity VALUES(731229,1585467780,'2020-03-29T08:43:00',xxxxxxxxx,xxxxxxxx,46,0,80,255);
INSERT INTO mi_band_activity VALUES(731230,1585467840,'2020-03-29T08:44:00',xxxxxxxxx,xxxxxxxx,60,12,80,97);
INSERT INTO mi_band_activity VALUES(731231,1585467900,'2020-03-29T08:45:00',xxxxxxxxx,xxxxxxxx,15,0,16,255);
INSERT INTO mi_band_activity VALUES(731232,1585467960,'2020-03-29T08:46:00',xxxxxxxxx,xxxxxxxx,22,0,80,255);
INSERT INTO mi_band_activity VALUES(731233,1585468020,'2020-03-29T08:47:00',xxxxxxxxx,xxxxxxxx,21,0,80,93);
INSERT INTO mi_band_activity VALUES(731234,1585468080,'2020-03-29T08:48:00',xxxxxxxxx,xxxxxxxx,24,0,80,255);
INSERT INTO mi_band_activity VALUES(731235,1585468140,'2020-03-29T08:49:00',xxxxxxxxx,xxxxxxxx,37,0,80,255);
INSERT INTO mi_band_activity VALUES(731236,1585468200,'2020-03-29T08:50:00',xxxxxxxxx,xxxxxxxx,28,0,96,255);
INSERT INTO mi_band_activity VALUES(731237,1585468260,'2020-03-29T08:51:00',xxxxxxxxx,xxxxxxxx,19,0,80,255);
INSERT INTO mi_band_activity VALUES(731238,1585468320,'2020-03-29T08:52:00',xxxxxxxxx,xxxxxxxx,70,38,1,111);
INSERT INTO mi_band_activity VALUES(731239,1585468380,'2020-03-29T08:53:00',xxxxxxxxx,xxxxxxxx,20,0,26,109);
INSERT INTO mi_band_activity VALUES(731240,1585468440,'2020-03-29T08:54:00',xxxxxxxxx,xxxxxxxx,2,0,16,255);
INSERT INTO mi_band_activity VALUES(731241,1585468500,'2020-03-29T08:55:00',xxxxxxxxx,xxxxxxxx,4,0,80,255);
INSERT INTO mi_band_activity VALUES(731242,1585468560,'2020-03-29T08:56:00',xxxxxxxxx,xxxxxxxx,4,0,80,255);
INSERT INTO mi_band_activity VALUES(731243,1585468620,'2020-03-29T08:57:00',xxxxxxxxx,xxxxxxxx,14,0,80,100);
INSERT INTO mi_band_activity VALUES(731244,1585468680,'2020-03-29T08:58:00',xxxxxxxxx,xxxxxxxx,33,0,80,255);
INSERT INTO mi_band_activity VALUES(731245,1585468740,'2020-03-29T08:59:00',xxxxxxxxx,xxxxxxxx,17,0,80,255);
INSERT INTO mi_band_activity VALUES(731246,1585468800,'2020-03-29T09:00:00',xxxxxxxxx,xxxxxxxx,38,0,80,255);
INSERT INTO mi_band_activity VALUES(731247,1585468860,'2020-03-29T09:01:00',xxxxxxxxx,xxxxxxxx,36,0,80,255);
INSERT INTO mi_band_activity VALUES(731248,1585468920,'2020-03-29T09:02:00',xxxxxxxxx,xxxxxxxx,47,0,96,68);
INSERT INTO mi_band_activity VALUES(731249,1585468980,'2020-03-29T09:03:00',xxxxxxxxx,xxxxxxxx,58,0,80,70);
INSERT INTO mi_band_activity VALUES(731250,1585469040,'2020-03-29T09:04:00',xxxxxxxxx,xxxxxxxx,56,0,80,70);
INSERT INTO mi_band_activity VALUES(731251,1585469100,'2020-03-29T09:05:00',xxxxxxxxx,xxxxxxxx,38,0,80,255);
INSERT INTO mi_band_activity VALUES(731252,1585469160,'2020-03-29T09:06:00',xxxxxxxxx,xxxxxxxx,35,0,96,255);
INSERT INTO mi_band_activity VALUES(731253,1585469220,'2020-03-29T09:07:00',xxxxxxxxx,xxxxxxxx,37,0,80,83);
INSERT INTO mi_band_activity VALUES(731254,1585469280,'2020-03-29T09:08:00',xxxxxxxxx,xxxxxxxx,45,0,80,85);
INSERT INTO mi_band_activity VALUES(731255,1585469340,'2020-03-29T09:09:00',xxxxxxxxx,xxxxxxxx,38,0,96,255);
INSERT INTO mi_band_activity VALUES(731256,1585469400,'2020-03-29T09:10:00',xxxxxxxxx,xxxxxxxx,45,0,80,72);
INSERT INTO mi_band_activity VALUES(731257,1585469460,'2020-03-29T09:11:00',xxxxxxxxx,xxxxxxxx,28,0,80,81);
INSERT INTO mi_band_activity VALUES(731258,1585469520,'2020-03-29T09:12:00',xxxxxxxxx,xxxxxxxx,20,0,106,255);
INSERT INTO mi_band_activity VALUES(731259,1585469580,'2020-03-29T09:13:00',xxxxxxxxx,xxxxxxxx,29,0,80,255);
INSERT INTO mi_band_activity VALUES(731260,1585469640,'2020-03-29T09:14:00',xxxxxxxxx,xxxxxxxx,30,0,80,255);
INSERT INTO mi_band_activity VALUES(731261,1585469700,'2020-03-29T09:15:00',xxxxxxxxx,xxxxxxxx,6,0,80,255);
INSERT INTO mi_band_activity VALUES(731262,1585469760,'2020-03-29T09:16:00',xxxxxxxxx,xxxxxxxx,14,0,96,255);
INSERT INTO mi_band_activity VALUES(731263,1585469820,'2020-03-29T09:17:00',xxxxxxxxx,xxxxxxxx,113,19,1,96);
INSERT INTO mi_band_activity VALUES(731264,1585469880,'2020-03-29T09:18:00',xxxxxxxxx,xxxxxxxx,117,51,17,96);
INSERT INTO mi_band_activity VALUES(731265,1585469940,'2020-03-29T09:19:00',xxxxxxxxx,xxxxxxxx,54,12,16,63);
INSERT INTO mi_band_activity VALUES(731266,1585470000,'2020-03-29T09:20:00',xxxxxxxxx,xxxxxxxx,17,0,96,255);
INSERT INTO mi_band_activity VALUES(731267,1585470060,'2020-03-29T09:21:00',xxxxxxxxx,xxxxxxxx,20,0,90,255);
INSERT INTO mi_band_activity VALUES(731268,1585470120,'2020-03-29T09:22:00',xxxxxxxxx,xxxxxxxx,46,0,80,255);
INSERT INTO mi_band_activity VALUES(731269,1585470180,'2020-03-29T09:23:00',xxxxxxxxx,xxxxxxxx,121,0,80,71);
INSERT INTO mi_band_activity VALUES(731270,1585466640,'2020-03-29T08:24:00',xxxxxxxxx,xxxxxxxx,12,0,112,255);
INSERT INTO mi_band_activity VALUES(731271,1585466700,'2020-03-29T08:25:00',xxxxxxxxx,xxxxxxxx,20,0,122,81);
INSERT INTO mi_band_activity VALUES(731272,1585466760,'2020-03-29T08:26:00',xxxxxxxxx,xxxxxxxx,2,0,112,255);
INSERT INTO mi_band_activity VALUES(731273,1585466820,'2020-03-29T08:27:00',xxxxxxxxx,xxxxxxxx,0,0,112,78);
INSERT INTO mi_band_activity VALUES(731274,1585466880,'2020-03-29T08:28:00',xxxxxxxxx,xxxxxxxx,31,0,112,255);
INSERT INTO mi_band_activity VALUES(731275,1585466940,'2020-03-29T08:29:00',xxxxxxxxx,xxxxxxxx,16,0,112,81);
INSERT INTO mi_band_activity VALUES(731276,1585467000,'2020-03-29T08:30:00',xxxxxxxxx,xxxxxxxx,5,0,112,255);

After 09:23:00 we jump to 08:24:00 again and again.

2020-03-29T09:23:00
2020-03-29T08:24:00

Until 29.03.2020 everything was still good. Probably a problem with setting the time to summer time?

Ronny

piggz's picture

piggz

Thu, 2020/04/02 - 20:07

Hi, known problem with DST changes....
In the debug menu, there is a setting A: with a -+, press the + a few times to jog it on a few hours and sync data agaYou may have to repeat a few times, let me know if this works around it?

jpn9s's picture

jpn9s

Fri, 2020/04/03 - 12:30

Dear piggz,
Thank you for the advice. Did repeat few times, but unfortunately no results. Now we have SFOS 3.3.0.19..

jpn9s's picture

jpn9s

Sat, 2020/04/04 - 12:40

+ I installed encryption LUSK ... It was like an resetting whole phone. No effect on the mal function of Amazfish sofar.

piggz's picture

piggz

Fri, 2020/04/03 - 12:35

Are you in a timezone which is UTC+2 at the moment?

Markkyboy's picture

Markkyboy

Fri, 2020/04/03 - 14:46

I don't use your app, but while attempting to update SFOS last night and having to reset, i stopped at 3.2.0 and realised that the time was out by 2 hours (behind) and upon trying to set the date and time, it kept reverting to the date from 2 days ago and the time being 2 hours behind. i finally updated to 3.3.0 and now the time and date are correct when set.

jpn9s's picture

jpn9s

Fri, 2020/04/03 - 13:21

Usually +2 h to GMT / UTC at winter time, but +3 h to GMT at summer time. Very mixing indeed.

ronny_b's picture

ronny_b

Mon, 2020/04/13 - 16:55

Hello,

with the update to V1.4.0-1 the DST bug with my BIP is fixed, thanks! Have a nice Easter Monday!

Ronny

alex000090's picture

alex000090

Thu, 2020/03/19 - 15:44

Dear autor,

I try ubuntu touch on my phone now. Do you know something about compatibility of you program (with recompilation) with Ubuntu Touch?

Branja's picture

Branja

Tue, 2020/03/17 - 17:18

I recently realized that we could use the button on the BIP (BIP Lite in my case) to switch tracks while listening to music (tested on a native player as well as QuasarMX Pro). Two fast clicks to skip tracks forwards, three quick clicks to skip track backward. Another amazing feature.

vige's picture

vige

Mon, 2020/04/20 - 12:12

Wow, I had not noticed this before! This is so awesome, my setup for jogging (XA2 + Jabra Clipper + Bip) is now perfect! :)

And it works with Spotify as well! :)

sashikknox's picture

sashikknox

Tue, 2020/03/10 - 22:22

Now it works with MiBand 3
but still a very inconvenient menu for connecting the device: when there are many identical MiBand 3 next to each other, it is simply impossible to make the pairing, you need to go down to the underground bunker, which will have a bluetooth signal only from your device - so I did ;-).

akikk88's picture

akikk88

Tue, 2020/03/10 - 21:19

What you need to know? 0.0.8.56 is my firmware versio and phone is xperia 10 with sailfish os. Clock try to connect but thats it. 

piggz's picture

piggz

Tue, 2020/03/10 - 22:05

logs from journal, devel-su, journalctl | grep amazfish

Have you got auth key from android?

akikk88's picture

akikk88

Tue, 2020/03/10 - 16:26

Can't connect amazfit gts

piggz's picture

piggz

Tue, 2020/03/10 - 20:34

thats not helpful

Georgiy's picture

Georgiy

Sat, 2020/03/07 - 17:47

Hi piggz!

I have a problem when using Xiaomi Amazfit Bip with Amazfish. Regularly Amazfish looses connection to device and does not reconnect to it. What could be a cause of this issue? How can I solve it?

Pages