forecastHours and forecastDays

Looking for any advice regarding the weather forecast tags.

First, Samsung’s documentation is a bit lacking and refers to the tags as “ForecastHour” and “ForecastDay”, I saw a post here that guided me.

So, I’ve added several weather icons to my watch face as images. Weirdly, I was not able to use tags in the “opacity” setting for the images, but I got it to work using tags in the “Color” section.
For example, on a sunny day, I have an image of a sun with this tag:

(([WTHR_COND]==1)+([WTHR_COND]==8))*([WTHR_IS_DAY])==1?0:-100

for a thunderstorm:
[WTHR_COND]==9?0:-100

This works great. I have a stack of images with similar tags for different weather conditions, as well as moon phases and the appropriate one is showing in both Watch Face Studio and on my Watch7.

But, when I tried to do the same using either “forecastHours” or “forecastDays”, I’m running into problems. In the preview on Watch Face Studio, it shows correctly, with just the appropriate image visible (I double checked by using a text box showing the return for forecastDays or forecastHours). However, on the watch the entire stack of images is visible.

Here are some examples of the tags I’m using:
(((forecastHours(4, “COND”))==1)+((forecastHours(4, “COND”))==8))*([WTHR_IS_DAY])==1?0:-100

((forecastHours(4, “COND”))==9)?0:-100

(((forecastDays(1, “COND_DAY”))==2)+((forecastDays(1, “COND_DAY”))==3)+((forecastDays(1, “COND_DAY”==13))))?0:-100

In Watch Face Studio, I can see that these are returning a “0” or “1”, so I think my tag syntax is correct. These are essentially the equivalent of the current weather condition tags I’m using above which are working, but for the forecasts, it’s displaying all the images.

Would appreciate any ideas

Thanks!

i am getting similar results. Its not just related to the Weather Conditions. It seems to stem with the images.

I too have a sack of images and there is no visibility in the portion where changes are made… only the watch face.

This may be irrelevant, but I don’t think that opacity of -100 is a legitimate value.

1 Like

It’s odd, because the images display perfectly with the weather condition tags.
Interestingly, the forecastDays and forecastHours tags do not show in the tag list in the application, but it’s in Samsung’s documentation, so I was hopeful. It works perfectly in the app, just not the watch

In the “Color” setting. there is a “100+” just to the left of the box where you write your tag expression, so in that case, a “0” means 100% opacity and the -100 makes it invisible. Again, the expressions work fine for current weather, just not for the forecast tags.

I already mentioned this issue in this topic: Weather forecast tags - #5 by matheus
It seems, that forecast tags “tem”, “cond-day” etc are in string format. Meanwhile WFS shows these tags correct. So that’s a problem with watch firmware.
I’ve already created a support ticket, hope that this issue will be fixed soon

Hmm…
I wonder if the tag expressions would work if I put “” around the result.
such as:
(forecastHours(4, “COND”))==“1”) instead of (forecastHours(4, “COND”))==1)

Would the watch consider the “1” as a string instead of a number and if that matches the forecast tag result string, return true? (and therefore, work?

I’ll have to try when I get home tonight

Thanks

I see what you mean. Thanks.

The answer is No. Doesn’t work. Sounds like we need to wait for them to patch the watch firmware

I dont have any issues.
In my example I have a group of partly cloudy icons. each will display based on the temp values of the forecast.

(forecastHours(1,“TEM”)>15?(forecastHours(1,“TEM”)<=25?100:0):0)

the group of icons is turned on and off with the weather condition

forecastHours(1, “COND”)==8?100:0

What i have come across is that the value of the weather only comes across in C not F. Yes i have tried to toggle the settings switch



oh…
on a new text selecting the tag button and scrolling all the way down

True. I’m having the same problem, I thought I’m doing something wrong.

I don’t know if F maybe works on real watch? I can test it only in C.
Can someone in USA test it on the watch?

If WTHR_TEM_UNIT works, you might be able to use that to determine whether to convert.

WTHR_TEM_UNIT does work, but how to combine it with: (forecastHours(1,“TEM”)?

Old weather tags like (WTHR_TEM), (WTHR_DAY_TEM_LOW) show C or F, we can see it in the preview.

New weather tags like (forecastHour(1, “TEM”), (forecastHour(1, “TEM_LOW”) show only temp in C.

Now, the question is: is it error only in preview and works on real watch or
is it error in preview and error on real watch?

Unfortunately new tags, at this moment (as far as I know), can be tested only on Samsung watch 7 / ultra.

Maybe r.liechty_SDR can share some light regarding this? Or anyone else?

1 Like

Testing could be done using a Wear OS Simulator (link). But this is tricky; you need to be comfortable with adb.

1 Like

I’m sorry to say: I’m not. :wink: :grinning:

1 Like

Sadly Ron has been retired some time now .

1 Like

Here is what I have done.

Grouped
Text field
Forecast - F (forecastHours(1,“TEM”)*9/5+32)F
Forecast - C (forecastHours(1, “TEM”))C

Color
Forecast - F ([WTHR_TEM_UNIT]==2?100:0)
Forecast - C ([WTHR_TEM_UNIT]==1?100:0)

Toggle i the control between C and F

GDC 607_02 Earth_20241001_18212011
GDC 607_02 Earth_20241001_18213858

I have also taken all 15 i know there 16 weather conditions, and have stacked 8 images each represent a different temperature range. The Weather Icons are then color coded… Kinda stupid that it could be 100 and the snow be in the color red. But… lol

GDC 607_02 Earth_20241001_18221543
GDC 607_02 Earth_20241001_18253822
GDC 607_02 Earth_20241001_18222663

I’m a Boomer that grew up in 79 with an apple ii. Lived in Singapore in the 70s when National Semiconductor was putting out 5 function LED watches. Hours, Mins, Secs, Day, Date. That was HS back in the day. Then LCDs came out.

My Dad is in awe of what we are doing with watch faces now.

I do this as a hobby. If anyone would like the workings of this weather feature im happy to share.

Graham

2 Likes

Nicely done!

So, it is an error in WFS, we have to calculate F from C.

2 Likes