(no title)

Withings to Garmin Connect – resurrection

Jarek 2019-01-302019-01-30 Gadgets & hobbies No Comments

After dropping “legacy” APIs on Withings page, the script stopped to work…

It took quite a while to adjust it to OAuth2 but finally – it’s done!

Go to https://github.com/jaroslawhartman/withings-garmin-v2 to download the script.

References

Based on withings-garmin by Masayuki Hamasaki, improved to support SSO authorization in Garmin Connect 2.
SSO authorization derived from https://github.com/cpfair/tapiriik

Pre-requisites

Python 3
‘Requests: HTTP for Humans’ (http://docs.python-requests.org/en/latest/)

$ sudo easy_install requests

1	$ sudo easy_install requests

simplejson

$ sudo easy_install simplejson

1	$ sudo easy_install simplejson

Usage

Usage: $python sync.py [options]

Options:
  -h, --help            show this help message and exit
  --garmin-username=&lt;user>, --gu=&lt;user>
                        username to login Garmin Connect.
  --garmin-password=&lt;pass>, --gp=&lt;pass>
                        password to login Garmin Connect.
  -f &lt;date>, --fromdate=&lt;date>
  -t &lt;date>, --todate=&lt;date>
  --no-upload           Won't upload to Garmin Connect and output binary-
                        string to stdout.
  -v, --verbose         Run verbosely

Usage: $python sync.py [options]

Options:

-h, --help show this help message and exit

--garmin-username=<user>, --gu=<user>

username to login Garmin Connect.

--garmin-password=<pass>, --gp=<pass>

password to login Garmin Connect.

-f <date>, --fromdate=<date>

-t <date>, --todate=<date>

--no-upload Won't upload to Garmin Connect and output binary-

string to stdout.

-v, --verbose Run verbosely

Obtaining Withings Authorization Code

When running for a very first time, you need to obtain Withings authorization:

$ ./sync.py -f 2019-01-25 -v
Can't read config file config/withings_user.json
***************************************
*         W A R N I N G               *
***************************************

User interaction needed to get Authentification Code from Withings!

Open the following URL in your web browser and copy back the token. You will have *30 seconds* before the token expires. HURRY UP!
(This is one-time activity)

https://account.withings.com/oauth2_user/authorize2?response_type=code&amp;client_id=183e03e1f363110b3551f96765c98c10e8f1aa647a37067a1cb64bbbaf491626&amp;state=OK&amp;scope=user.metrics&amp;redirect_uri=https://wieloryb.uk.to/withings/withings.html&amp;

Token : _

$ ./sync.py -f 2019-01-25 -v

Can't read config file config/withings_user.json

***************************************

* W A R N I N G *

***************************************

User interaction needed to get Authentification Code from Withings!

Open the following URL in your web browser and copy back the token. You will have *30 seconds* before the token expires. HURRY UP!

(This is one-time activity)

https://account.withings.com/oauth2_user/authorize2?response_type=code&client_id=183e03e1f363110b3551f96765c98c10e8f1aa647a37067a1cb64bbbaf491626&state=OK&scope=user.metrics&redirect_uri=https://wieloryb.uk.to/withings/withings.html&

Token : _

You need to visit the URL listed by the script and then – copy Authentification Code back to the prompt.

This is one-time activity and it will not be needed to repeat.

Tips

You can hardcode your usernames and passwords in the script (`sync.py`):

GARMIN_USERNAME = ''
GARMIN_PASSWORD = ''

1 2	GARMIN_USERNAME = '' GARMIN_PASSWORD = ''

For advanced users – registering own Withings application

The script has been registered as a Withings application and got assigned Client ID and Consumer Secret. If you wish to create your own application – feel free!

First you need a Withings account. Sign up here.
Then you need a a Withings developer app registered. Create your app here.

Note, registering it is quite cumbersome, as you need to have a callback URL and an Icon. Anyway, when done, you should have the following identifiers:

Identfier	Example
Client ID	`183e03.................765c98c10e8f1aa647a37067a1......baf491626`
Consumer Secret	`a75d65.................4c16719ef7bd69fa7c5d3fd0ea......ed48f1765`
Callback URI	`https://jhartman.pl/withings/notify`

Configure them in config/withings_app.json, for example:

{
    "callback_url": "https://wieloryb.uk.to/withings/withings.html",
    "client_id": "183e0******0b3551f96765c98c1******b64bbbaf491626",
    "consumer_secret": "a75d65******1df1514c16719ef7bd69fa7*****2e2b0ed48f1765"
}

{

"callback_url": "https://wieloryb.uk.to/withings/withings.html",

"client_id": "183e0******0b3551f96765c98c1******b64bbbaf491626",

"consumer_secret": "a75d65******1df1514c16719ef7bd69fa7*****2e2b0ed48f1765"

}

TimeZones v2.4

Jarek 2018-12-162018-12-16 Gadgets & hobbies 7 Comments

You can toggle your city and pin to the top – to make it a favourite.

Download from https://jhartman.pl/download/alfred-timezone-workflow/

Time Zones v2.1

Jarek 2018-11-082018-11-08 Gadgets & hobbies 2 Comments

Fixed issues with adding new cities. Also removed dependency on Growl.

You can download the workflow: Alfred-TimeZones

(more…)

Oracle Coherence – description of federation member states

Jarek 2018-10-10 Telco and IT No Comments

States of Oracle Coherence federation are not very well described in the documentation. So I thought it would be good to ask at the source. Thanks for Patrick F for all these explanations!

Stopped states – Federation is not federating data to the destination, nor is it keeping a backlog of changes to send to the destination. A “start” operation must be performed to start federating data again:

STOPPED – A stop operation was issued, or federation was set to start in the stopped state. Stopped states – Federation is not federating data to the destination, nor is it keeping a backlog of changes to send to the destination. A “start” operation must be performed to start federating data again:
ERROR – An error occurred from which federation was unable to continue federating data

Paused state – Federation is not federating data, but is keeping a (growing) backlog of changes to be sent once a “start” operation is issued:

PAUSED – A pause operation was issued, or federation was set to start in the paused state.

Normal states – Federation is federating data:

INITIAL – default startup state. A Coherence node will stay in this state until there is data to be federated
IDLE – federation is active and connected to the destination. There is no data currently to send
READY – federation is transitioning out of CONNECTING, or YIELDING, or BACKLOG_NORMAL and will go to SENDING
SENDING – federation has data to send
CONNECTING – federation is connecting to the destination cluster
CONNECT_WAIT – federation is disconnected and will make a new connect attempt. There may be a delay before making the next attempt depending on the circumstances under which federation was disconnected
YIELDING – federation has data to send, but is pausing briefly, likely due to a BACKLOG_EXCESSIVE event
DISCONNECTED – federation was disconnected from the remote destination. If there is no data to send, federation may stay in this state. NB: DISCONNECTED is a “normal” state. It means that a member of the cluster lost its federation connection to the remote cluster (probably because the remote member it was connected to was shut down). If the member in the DISCONNECTED state has no data to send, it will stay in the DISCONNECTED state – basically the same as being IDLE. Once there is some data for this member to send it will issue a new connection.

The following states do not exist – although they may have in 12.2.1.0.0 (federation should not be used with this version):

BACKLOG_EXCESSIVE
BACKLOG_NORMAL

Shrinking VirtualBox VMs

Jarek 2018-09-302018-09-30 Gadgets & hobbies No Comments

This article is note to self, as I just gather information from other sites:

Time Zones v2.0

Jarek 2018-09-222018-11-08 Uncategorised No Comments

Major fix for issue preventing adding new cities! Replaced calls to Google Map API by a local file.

You can download the workflow: Alfred-TimeZones

(more…)

Proxmox: enp0s31f6: Detected Hardware Unit Hang

Jarek 2018-08-06 Telco and IT 1 Comment

Since a few weeks, my Proxmox lab has started having issues with on-board network. The adapter enters in “hang” state, the logs are full of recurring errors like below:

[89276.274556] e1000e 0000:00:1f.6 enp0s31f6: Reset adapter unexpectedly
[89276.306147] vmbr0: port 1(enp0s31f6) entered disabled state
[89280.269563] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[89280.269626] vmbr0: port 1(enp0s31f6) entered blocking state
[89280.269631] vmbr0: port 1(enp0s31f6) entered forwarding state
[89282.226613] e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
                 TDH                  <0>
                 TDT                  <1>
                 next_to_use          <1>
                 next_to_clean        <0>
               buffer_info[next_to_clean]:
                 time_stamp           <10153702e>
                 next_to_watch        <0>
                 jiffies              <101537150>
                 next_to_watch.status <0>
               MAC Status             <80083>
               PHY Status             <c8db>
               PHY 1000BASE-T Status  <a39b>
               PHY Extended Status    <ffff>
               PCI Status             <10>

[89276.274556] e1000e 0000:00:1f.6 enp0s31f6: Reset adapter unexpectedly

[89276.306147] vmbr0: port 1(enp0s31f6) entered disabled state

[89280.269563] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

[89280.269626] vmbr0: port 1(enp0s31f6) entered blocking state

[89280.269631] vmbr0: port 1(enp0s31f6) entered forwarding state

[89282.226613] e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:

TDH <0>

TDT <1>

next_to_use <1>

next_to_clean <0>

buffer_info[next_to_clean]:

time_stamp <10153702e>

next_to_watch <0>

jiffies <101537150>

next_to_watch.status <0>

MAC Status <80083>

PHY Status <c8db>

PHY 1000BASE-T Status <a39b>

PHY Extended Status <ffff>

PCI Status <10>

Initially I was suspecting a hardware issue but after replacing the motherboard, the problem still persisted.

Next, I’ve found this thread in Proxmox forum. Workaround which is suggested there seems to be working, below how I’ve implemented it:

One time fix

root@wieloryb-pve:/etc/rc.d/init.d# /sbin/ethtool -K enp0s31f6 tx off rx off
Cannot get device udp-fragmentation-offload settings: Operation not supported
Cannot get device udp-fragmentation-offload settings: Operation not supported
Actual changes:
rx-checksumming: off
tx-checksumming: off
    tx-checksum-ip-generic: off
tcp-segmentation-offload: off
    tx-tcp-segmentation: off [requested on]
    tx-tcp6-segmentation: off [requested on]

root@wieloryb-pve:/etc/rc.d/init.d# /sbin/ethtool -K enp0s31f6 tx off rx off

Cannot get device udp-fragmentation-offload settings: Operation not supported

Actual changes:

rx-checksumming: off

tx-checksumming: off

tx-checksum-ip-generic: off

tcp-segmentation-offload: off

tx-tcp-segmentation: off [requested on]

tx-tcp6-segmentation: off [requested on]

Preserve the change across reboots

root@wieloryb-pve:~# cat /etc/network/if-up.d/ethtool2
#!/bin/sh

/sbin/ethtool -K enp0s31f6 tx off rx off

root@wieloryb-pve:~# chmod 755 /etc/network/if-up.d/ethtool2

root@wieloryb-pve:~# cat /etc/network/if-up.d/ethtool2

#!/bin/sh

/sbin/ethtool -K enp0s31f6 tx off rx off

root@wieloryb-pve:~# chmod 755 /etc/network/if-up.d/ethtool2

Reboot and verify

root@wieloryb-pve:/etc#  shutdown -r now

root@wieloryb-pve:/etc/rc.d/init.d# /sbin/ethtool -k enp0s31f6
Features for enp0s31f6:
Cannot get device udp-fragmentation-offload settings: Operation not supported
rx-checksumming: off                   <--------- SHOULD BE OFF, HERE AND A FEW OTHER PLACES
tx-checksumming: off

root@wieloryb-pve:/etc# shutdown -r now

root@wieloryb-pve:/etc/rc.d/init.d# /sbin/ethtool -k enp0s31f6

Features for enp0s31f6:

Cannot get device udp-fragmentation-offload settings: Operation not supported

rx-checksumming: off <--------- SHOULD BE OFF, HERE AND A FEW OTHER PLACES

tx-checksumming: off

How to prepare bootable USB stick for BIOS flashing

Jarek 2018-07-312018-07-31 Gadgets & hobbies No Comments

This post is actually a note to self how I’ve done it…

Steps taken from:

Kos Cycling – Day 4

Jarek 2018-07-17 Gadgets & hobbies No Comments

Zobacz trasę w Traseo

Kos Cycling – Day 3

Jarek 2018-07-17 Gadgets & hobbies No Comments

Zobacz trasę w Traseo

« Previous

Withings to Garmin Connect – resurrection

References

Pre-requisites

Usage

Obtaining Withings Authorization Code

Tips

You can hardcode your usernames and passwords in the script (`sync.py`):

For advanced users – registering own Withings application

TimeZones v2.4

Time Zones v2.1

Oracle Coherence – description of federation member states

Shrinking VirtualBox VMs

Time Zones v2.0

Proxmox: enp0s31f6: Detected Hardware Unit Hang

One time fix

Preserve the change across reboots

Reboot and verify

How to prepare bootable USB stick for BIOS flashing

Kos Cycling – Day 4

Kos Cycling – Day 3

Shortcuts…

Archives

References

Pre-requisites

Usage

Obtaining Withings Authorization Code

Tips

You can hardcode your usernames and passwords in the script (sync.py):

For advanced users – registering own Withings application

One time fix

Preserve the change across reboots

Reboot and verify

Shortcuts…

Tags

Archives

You can hardcode your usernames and passwords in the script (`sync.py`):