[Question] No stupid questions - ask anything here

hitriy

Hey!
I went through the documentation and didn’t find an answer to my question.
Is it possible to fetch data not from watch sensors, but from the phone or internet via phone?
For example get custom notification, currency rates, weather and so on.

orienteerdev

This is actually what I’m curious too related to my previous message. Since the watch has a functionality to download updates via Suunto App and also download offline maps via WiFi, it would be nice to be able to utilize the storage of watch to have some input data for S+ app from external web source.

Basically this to be efficient and comfortable to users, the S+ app should be able to fetch data utilizing Suunto app via bluetooth and then Suunto App would do the web request.

There are quite many security/sandbox etc. issues to consider and we may not be there yet. However, I think this is the enabler for nice innovations and ecosystems.

SailingP

Hello @suuntopartnerteam,
First of all, I’d like to thank you for the opportunity to develop our own SuuntoPlus apps. This is a very pleasant surprise . Thank you very much.

I spent part of the weekend reading the documentation, reviewing examples, and experimenting. I have a request.
The provided documentation and examples are a good start, but could you please share the full documentation so we can develop apps that fully leverage the SuuntoPlus framework’s functionality?

Let me give you a few examples of what I am missing in the reference file, in the provided examples and in the how-to articles, and what I believe will help to develop new applications:

enum values. Few examples:

The graph class has an attribute grid. I found only one documented value “three lines” but the attribute grid can have more values: “none”, “central line” and documented “three lines”.
The graph class has an attribute type. I found the documented values “bar” and “line”. The enum has additional values “dot line” (works) and “separate bars” (~~does not work for me~~ not implemented yet).

class attributes. Examples:

The graph class has more attributes: sampleFilter, windowType, windowSize, marker, fillReference etc.

I would greatly appreciate it if more detailed documentation could be made available . Thank you in advance.

SailingP

said in [Question] No stupid questions - ask anything here:

The graph class has an attribute type. I found the documented values “bar” and “line”. The enum has additional values “dot line” (works) and “separate bars” (does not work for me).

Clarification: I discovered that the enum value “separate bars” exists, but the functionality has not been implemented yet.

ook

@chus1962 ~~I having the same issue with u with my Mac OS,trying to connect with suuntolink via USB and bluetooth also,both not working, discovery is turn on too~~
just find out there is some requirements need to follow and setup in order to connect with bluetooth, now is all work.

Tomas5

@SailingP there is more to it not covered. Example app Graph uses Activity/Log/-1/…… but it doesn’t work for me in simulator or in watch and documentation doesn’t mention what Log values are avalable. I think i didn’t found much explanation for get vs subscribe etc. I hope for some more documentation. And preferably available online so it can be read from phone/tablet while not siting at front of VScode.

assaf1007

@Pottu tnx! (Works just fine)

assaf1007

and if wish to view HRV data?
from the documentation it looks like an object:
**/Hrv/Rmssd
Type: Get/Subscribe

Gets or subscribes to the latest HRV measurements.

Response: Object {HrvData}

timestampLocal: Uint32 - Local timestamp in seconds
rmssd: Uint32 - RMSSD in milliseconds**

so while
{ “name”: “heartrate”, “source”: “/Activity/Move/-1/HeartRate/Current”, “type”: “subscribe” }
works great,
{ “name”: “in_hrv1”, “source”: “/Hrv/Rmssd”, “type”: “subscribe” }
Shows nothing :(. I wonder if its related to the fact the only 95% of the usability is currentry supported.

brechtvb

@SuuntoPartnerTeam is someone using the Accelerometer data?

the onAccelerometer function is not being called, evaluate(…) is correctly called.

This is in the manifest.json

"in": [
  { "name": "HeartRate", "source": "Activity/Move/-1/HeartRate/Current", "type": "subscribe" },
  { "name": "Acceleration", "source": "Fusion/Zapp/Accelerometer", "type": "subscribe" }
],

brechtvb

Hello,

problem solved.

the acceleration information (if in manifest.js declared), is available in the onEvaluate call, there is no need for onAcceleration(…) implementation.

I believe the documentation is outdated.