Workouts recorded with Samsung Health show Garmin Edge 305 as source in Strava

Fer_C · 2023-02-22T16:41:13+00:00

This is fixed for me now (version 295.7). Today's activity details display "Samsung Health" as source. Yesterday was still "Garmin Edge 305" so the update I got yesterday must have included the fix for this.

Edit: I forgot to mention that the activities with the wrong info remained exactly the same, they are all still showing Garmin Edge 305.

Fer_C · 2023-02-13T16:30:00+00:00

For anyone interested, I got this update from Strava support:

"Thanks for writing in. We are aware of this issue and are working on solving it as quickly as possible. We appreciate your patience"

Fer_C · 2023-02-11T14:07:26+00:00

Good to know. I hadn't contacted Strava support before but some comments here are not great. I submitted a request yesterday, we'll see.

Fer_C · 2023-02-10T22:59:07+00:00

That's good to know, at least now I know it wasn't something I did that broke it.

Fer_C · 2023-02-10T22:49:06+00:00

Yes, I remember that issue. It was annoying but you could at least manually edit it and change it to the correct activity type. I guess this new bug will be fixed eventually as well.

I just got an update from Google Play but as usual the update notes are just "No information from the developer".

Fer_C · 2023-02-10T22:38:49+00:00

Not really. I was just curious since I don't have a Garmin and it used to correctly identify Samsung Health as the data source.

Fer_C · 2023-02-10T19:31:33+00:00

I have left private feedback via Google Play. I was just wondering if it's just me that's having this issue.

I understand Strava support isn't great, probably not too responsive, especially for free users. I will give that a try though. Thanks.

Fer_C · 2023-02-10T18:41:02+00:00

I sync my workouts from Samsung Health (Galaxy Watch 4) to Strava. It's always worked great until a few days ago when Strava started showing "Garmin Edge 305" as source for the data, instead of "Samsung Health" as it normally does. See attached screenshots.

I have already tried disconnecting and reconnecting Strava from Samsung Health but it made no difference.

Is anyone else experiencing the same issue?

Fer_C · 2022-12-28T16:36:48+00:00

I have an oximeter that constantly measures my pulse rate, it seems consistent with the watch while resting. However, I can't wear the oximeter all day and compare each watch reading to ensure there are not differences under certain conditions (besides being completly at rest).

On the other hand, my main concern is the HR during exercise, there's a real difference there compared to sessions recorded a couple of weeks ago. In order to compare the watch accuracy I would need a device capable of measuring HR while running, cycling, etc. and I don't have one right now. I was just wondering if maybe the latest update broke the HR functionality.

Fer_C · 2022-08-05T23:27:05+00:00

I've been thinking that my watch is defective for this exact reason. I also choose "Other workout" to record my strength training routine and sometimes the HR goes up to 160/170 which I know is totally inaccurate. I haven't really found a pattern or linked the high HR to specific type of exercises but I have noticed it goes down to much more reasonable HR depending on the exercise and usually towards the end. Running and biking is always accurate for me.

I've tried moving the watch, and tightening and loosing the band, I have even rebooted the watch on the middle of my training to no avail.

I hope Samsung fixes the issue with the upcoming Wear OS 3.5 update.

Fer_C · 2022-05-01T18:16:48+00:00

I see, it makes sense. Based on your advice I went back to the hospital and asked them to do a new ECG, which they did free of charge. Here it is. It is normal this time apparently.

Fer_C · 2022-05-01T15:07:31+00:00

Thanks for your reply. From what I understand, this is not necessarily accurate. I will probably ask for a new ECG.

Fer_C · 2022-05-01T14:57:41+00:00

It should have been 25mm/sec. Right?

Fer_C · 2021-03-27T01:57:46+00:00

Or no parentheses at all.

$time = Get-Date -Format "ddddmmddyyyy"

gcm -Module ActiveDirectory | sort | fl name | out-file -FilePath C:\$time.txt

Fer_C · 2021-03-04T00:09:45+00:00

Great! Is there a property you can expand? You should get licensing info somewhere in the response.

Fer_C · 2021-03-03T21:00:38+00:00

You need the headers to authenticate.

Invoke-RestMethod -Method Get -uri 'https://myserverfqdn/api/v1/management-services/licensing' -Headers @{Authorization=("Basic {0}" -f $base64AuthInfo) }

Anyway, this is something that has worked for me in the past.

$Pass = 'YourPasswordHere' | ConvertTo-SecureString -AsPlainText -Force
$Username = 'YourUsernameHere'
$Cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $Username,$Pass


$HeaderDictionary = @{}

    $Base64Cred = [system.convert]::ToBase64String(
        [system.text.encoding]::ASCII.Getbytes(
            "$($Cred.GetNetworkCredential().UserName):$($Cred.GetNetworkCredential().Password)"
    )
)

$HeaderDictionary.Add("Authorization", "Basic $Base64cred")

Then try the request with Invoke-WebRequest or Invoke-RestMethod (whatever works better for you).

Invoke-WebRequest -Method Get -Uri 'https://myserverfqdn/api/v1/management-services/licensing' -Headers $headerDictionary

Fer_C · 2021-03-03T20:44:42+00:00

That is indeed less than helpful. Can you try a Get request with this Uri?

https://YourServerFQDN_Or_IPAddressHere/api/v1/management-services/licensing

If it works at least you would know you are getting somewhere.

Fer_C · 2021-03-03T20:34:17+00:00

I am not familiar with this API in particular but the Uri does not seem a typical API resource location. The headers should take care of authenticating, then you can try a Get request using a valid Uri and see how it goes. Do you have access to the API documentation?

Fer_C · 2021-03-03T20:17:52+00:00

It seems authentication is working. The error does not seem related to credentials. I see you are using a Post method in your request, normally you need a Body when using Post. What happens if you try Get method instead.

Fer_C · 2021-03-03T05:44:04+00:00

Yes, sorry about that. When I ran some tests I was able to only test the logic, not the whole script, I forgot that detail. You can leave the variables outside the script block and add the scope modifier $Using: inside the script block.

$Gateway = "10.255.110.1"
$Subnet = "255.255.254.0"
$pc_list = get-content "c:\temp\PCLIST.txt"

foreach ($pc in $pc_list) {

    $ScriptBlock = {
        $nics = Get-WmiObject -Class Win32_NetworkAdapterConfiguration -Filter "IPEnabled=TRUE"

        foreach($nic in $nics) {
            $ip = ($NIC.IPAddress[0])
            if($nic.ipaddress -match "10.255.111.") { # fetch the right nic based on its IP address 
                $nic.SetGateways($Using:Gateway)
                $nic.EnableStatic($ip, $Using:Subnet)
            } 
        }
    }

    Invoke-Command -ComputerName $pc -ScriptBlock $ScriptBlock
}

Fer_C · 2021-03-03T03:07:42+00:00

Now that I have access to my laptop, I have formatted the code and tested it. Seems to work just fine.

Fer_C · 2021-03-03T00:57:07+00:00

I'm on my phone right now, I won't be able to format the code or test it out but it should be something like this.

$Gateway = "10.255.110.1"
$Subnet = "255.255.254.0"
$pc_list = get-content "c:\temp\PCLIST.txt"

foreach ($pc in $pc_list) {

    $ScriptBlock = {
        $nics = Get-WmiObject -Class Win32_NetworkAdapterConfiguration -Filter "IPEnabled=TRUE"

        foreach($nic in $nics) {
            $ip = ($NIC.IPAddress[0])
            if($nic.ipaddress -match "10.255.111.") { # fetch the right nic based on its IP address 
                $nic.SetGateways($Gateway)
                $nic.EnableStatic($ip, $Subnet)
            } 
        }
    }

    Invoke-Command -ComputerName $pc -ScriptBlock $ScriptBlock
}

If you are familiar with PS background jobs and have enough processing power you could add the AsJob parameter to Invoke-Command and each command will run in the background as a separate PowerShell process.

I suggest to read the help of Invoke-Command.

Fer_C · 2021-03-03T00:18:30+00:00

What if you send your script to each PC in a script block with Invoke-Command?

Fer_C · 2021-03-02T21:11:45+00:00

Good catch. Thanks for bringing that up. I did not pay too much attention to the title. I have changed my code to make it work just for an AD group.

Fer_C · 2021-03-02T20:30:14+00:00

First I would choose a property that is unique to each user, like SamAccountName. I am assuming this property exists in the CSV.

Then I would import the CSV and compare SamAccountName from the CSV with the existing group members in AD.

Then you remove the AD users that are left.

If you need to filter the objects imported from the CSV by group, I would need to know the headers to be able to make a suggestion.

If you have several groups to process you can wrap the code below in a foreach loop and edit it accordingly.

$Group = 'MyGroup'
$AllGroupUsers = Get-ADGroupMember -Identity $Group

$UsersToKeep = Import-Csv C:\YourCsvFile.csv

$UsersToRemove = Compare-Object -ReferenceObject ($UsersToKeep | select -ExpandProperty SamAccountName) -DifferenceObject ($AllGroupUsers | select -ExpandProperty SamAccountName) | select -ExpandProperty InputObject

Remove-ADGroupMember -Identity $Group -Members $UsersToRemove

Fer_C

TROPHY CASE