Tide table on vertical 2

MarkG

@Egika
Also yes to all. Still just giving location as ‘Scotland’ I’m actually not that far from Fort William mentioned earlier.
I’ve just compared it with local tide tables and it’s about 40 minutes and 0.3m wrong on the low tide forecast for Mallaig which is just up the coast. Not big errors but potentially critical for threading a sea kayak through various local channels.
For example - close to me there is an island (Eilean Ighe for those who know the area) separated from the mainland by a narrow channel. I know I can paddle through this when the height of the tide at Mallaig is 3.5m. If I get this wrong then it’s normally straightforward to go round the outside of the island. But if the weather is severe (or unexpectedly deteriorates) timing for the channel to avoid the conditions is important. Now of course I can use other resources to plan this but it’s a shame if the watch can’t give me that information. An example would be a leisurely long day, no weather or tidal stream issues, arriving nearby at an unplanned time and just deciding the best route back by making a quick check to see if the channel is open or not.

MikeC30

Tide widget started working again today. Watch hasn’t left the house in the last 48 hours so I’m not sure what has changed. Perhaps Suunto has been working behind the scenes to fix it?

Still not sure where they are getting their tide data from as it differs a bit from the tide tables of both my nearest ports. High and low tide times are out by between 10 and roughly 20 minutes on the widget. Still gives my location as Scotland, UK.

MikeC30

That’s the tide widget not working again in my location. After its update on Sunday it has not updated any data since then.

bruno.tanqueray

@MikeC30 Hi, I have exactly the same problems than you, living at 200 meters from the sea in Brittany (France).

It will be nice to understand how this applet is working. Is there an API authorized to refresh the tides table only for a (too !) short period ?
Can someone explain how should work this applet ? Can we verify and understand the sources somewhere in Github ?
Regards

Ze Stuart

@bruno.tanqueray what do you need to know? Data source and refresh window?

Suunto might use Github as their code repo, but we’ll probably never see it, as it’s proprietary code containing their trade secretes.

Egika

there are some things special with tides.
But basically, if you open the widget, it should at least trigger a sync, that then should update tides the next time, the phone syncs.
Provided, you have location permission for SA in your phone on.

MikeC30

@Egika

Sadly, this does not work, again. Given that other people are also having this issue, it makes me think it is probably a Suunto issue that needs fixed by them and not a user issue.

Egika

@MikeC30 this is well possible.

bruno.tanqueray

@Ze-Stuart Yes: data source and refresh window, plus the trigger logic.

To be clear, I am not asking for the source code, I know it is proprietary. I am asking for the documented behaviour of the widget, which is not a trade secret.

Why it matters: this thread is going in circles. We are all asked “location permission? tapped update? synced?”, we all answer yes, and then it stops. Without knowing what the widget is supposed to do, we cannot test anything, and Suunto cannot get a useful bug report from us.

My case: Brittany, France, 200 m from the sea. Sometimes tides load during a normal sync, right after the weather. Most of the time nothing loads. Same phone, same place, same procedure : the result is random. And when the widget is empty it offers to sync with my Iphone, but the app does nothing because the watch is “busy”, so that button seems useless.

What we need to know:

Which provider supplies the tide data?
Is the tide computed for my GPS position, or for a reference port that may be far away? (The watch only shows a region name.)
What triggers a refresh : opening the widget, a phone sync, a background schedule?
Is there a cache duration or a request limit per day? That alone could explain why it works once and then stops for days.
What is the official watch/app sequence? If we follow it and it still fails, it is a bug, not user error.

Thanks.

bruno.tanqueray

bruno.tanqueray said:

@Ze-Stuart Yes: data source and refresh window, plus the trigger logic.

To be clear, I am not asking for the source code, I know it is proprietary. I am asking for the documented behaviour of the widget, which is not a trade secret.

Why it matters: this thread is going in circles. We are all asked “location permission? tapped update? synced?”, we all answer yes, and then it stops. Without knowing what the widget is supposed to do, we cannot test anything, and Suunto cannot get a useful bug report from us.

My case: Brittany, France, 200 m from the sea. Sometimes tides load during a normal sync, right after the weather. Most of the time nothing loads. Same phone, same place, same procedure : the result is random. And when the widget is empty it offers to sync with my Iphone, but the app does nothing because the watch is “busy”, so that button seems useless.

What we need to know:

Which provider supplies the tide data?

Is the tide computed for my GPS position, or for a reference port that may be far away?

What triggers a refresh : opening the widget, a phone sync, a background schedule?

Is there a cache duration or a request limit per day? That alone could explain why it works once and then stops for days.

What is the official watch/app sequence? If we follow it and it still fails, it is a bug, not user error.

Thanks.

Egika

@bruno.tanqueray I understand your questions.
Just you know this is a user forum, so everyone can only share what he/she knows.
I know that it works for me.
When the watch is connected to the phone (iphone in my case) and SA is running at least in the background, tapping the refresh button in the widget shows that tide data is being updated and it also shows success.

I have no clue about your other questions. and I don’t know if anyone has.