05-20-2022 06:09
05-27-2022 05:54
05-27-2022 05:54
Beyond determining the watch type that the specific build was targeted at likely not.
Maybe try pulling the activity history of the user ActivityHistory and determine how far out it goes. It won't tell you the manufacture date, but it could tell you how long the person has had an account on the watch which would give you a ballpark.
Even this method sounds like a unrealistic proposition as you'd likely have to iterate through time segments to return information, until it didn't return valid information? And then you should have a ballpark.
Again. I wouldn't recommend this personally but I'm not sure what your overall goal is.
05-27-2022 06:28
05-27-2022 06:28
Hi @Anders10100 - thanks for taking the time to respond.
My clock face has battery management and I'm looking to correlate performance with battery age to suggest optimal charging procedures.
Author | ch, passion for improvement.
05-27-2022 06:50
05-27-2022 06:50
I see.
If you went with my idea, only iterate through to find that age upon entering the application.
Then offload the information that you gather to a local file on the watch.
Just access when you need it, and it will persist.
See the following code...
let watchAgeFile = "/private/data/age.txt";
if(! (fs.existsSync(watchAgeFile)))
{
//Gather data
//Offload to file
fs.writeFileSync(watchAgeFile, JSON.stringify("GatheredData"), "json");
}
else
{
//Pull data?
}
05-27-2022 06:59
05-27-2022 06:59
@Anders10100 - thanks but I don't think the account data is watch specific. (A change of watch would not be obviously identifiable). Nice thought though.
I was looking to get access to the watch activation date, visible in the watch Settings.
But as you say, it's probably another one of those things us developers don't have access to.
Author | ch, passion for improvement.