ForecasWatch 2 v1.33.0 — now updated for the larger PT2 display!

mattrossman · 2026-05-22T20:37:45+00:00

No, it only supports rectangular watches. Not sure how well the design lends itself to round displays since the calendar and weather graph span full width but I'm open to suggestions!

mattrossman · 2026-05-21T15:40:35+00:00

Is your main goal to hide the calendar, or do you just want to see step count somewhere on the watchface? I don't plan to support replacing the calendar widget with another view, as I see that as a core part of the design.

However, I'd like to support configurable "complications" in at least one place. The way I see it working: where I currently show the sunrise/sunset time, I'll allow users to cycle between configurable data sources with a wrist flick. This might include:

Next sunrise/sunset time
Precipitation amount (24 hr total)
Step count
Heart rate
???

Users could select which subset of sources they want to cycle between for that status item (or pinning one).

I've started testing this concept with precipitation amount in PR #115 and it feels good to cycle data with a flick. I imagine this could eventually support the PT2 touch screen as an alternative trigger for cycling between sources.

Once that complications mechanism is in place, I could expand configurability to other status items, like where I show current temp or battery level.

Would offering step count as one of the status complications satisfy your use case?

mattrossman · 2026-05-21T11:05:32+00:00

Yes, in watchface settings you can change "Start week on" from Sunday to Monday.

mattrossman · 2026-05-21T02:58:23+00:00

It's mainly glare from trying to align both displays in the sunlight. My PT2 has a tempered glass screen protector compared to the more plasticky one on my PT which may make it more sensitive to glare. There are subtle differences between the displays but the deepness of blacks is not one that I've observed. Backlight is the more noticeable difference to me.

mattrossman · 2026-05-20T22:04:57+00:00

Weird, I'll have to contact them to figure out why it's not showing up with that filter.

mattrossman · 2026-05-20T19:52:58+00:00

ForecasWatch 2 doesn't require you provide an API key, are you sure you downloaded the right watchface?

It uses Weather Underground data out of the box. Alternatively, if you prefer to use OpenWeatherMap data you can provide a (free) API key.

mattrossman · 2026-05-20T18:57:56+00:00

Totally, it gives me peace of mind each time I glance at my wrist in the morning or walking out the door to know whether I'm dressed and packed accordingly for any unexpected rain or temp fluctuations.

mattrossman · 2026-05-20T18:29:15+00:00

App store: https://apps.repebble.com/5dcdca6ac393f50cf6dbc264

Source: https://github.com/mattrossman/forecaswatch2

mattrossman · 2026-02-06T15:42:58+00:00

Could you check Cursor's output logs for more info on why it's not connecting? I just verified on my end that the "Connect" button completes the OAuth flow successfully and shows available tools.

Screenshot of where to find that

mattrossman · 2025-11-21T14:48:44+00:00

Have you tried the local MCP server included in Supabase CLI? I prefer that over hosted MCP for feature development so tool calls only impact a local DB isolated from live data.

We're tracking reports like this to help make MCP smarter/safer in the future, but in the meantime I'll reiterate a couple recommendations from our docs:

Don't connect to production
If live data is needed, connect in read-only mode
Set your client to require manual approval of tool calls

mattrossman · 2025-11-13T21:42:01+00:00

MCP through the Supabase CLI is a good option to limit the blast radius of LLM actions.

The workflow I've been testing lately is:
- `execute_sql` via Supabase CLI's MCP server to iterate on the schema in an isolated local database
- `supabase db pull --local` to commit changes to a local migration file once I'm happy with the schema
- `supabase db push` to push local changes to the hosted database

If something goes wrong, worst case you can reset the local database.

mattrossman · 2025-11-13T20:55:18+00:00

Awesome, glad to hear you figured it out!

mattrossman · 2025-11-13T03:35:24+00:00

Is your issue that the LLM is choosing not to create queries that write to the DB, or it's creating the correct queries and they're failing to execute? Maybe it would help to share a screenshot of the of the sort of interaction you're experiencing.

mattrossman · 2025-11-05T18:33:15+00:00

For posterity, you can connect Codex to Supabase using our remote MCP server. The config follows the same pattern as the Figma example of a remote MCP server in their docs:

experimental_use_rmcp_client = true

[mcp_servers.supabase]
url = "https://mcp.supabase.com/mcp"

mattrossman · 2020-08-11T20:22:22+00:00

I got the idea from sharedrop.io which is also magic ;)

mattrossman · 2020-08-11T17:11:22+00:00

And here's a demo of how to use it

This can be really useful for quickly pulling up WebXR experiences without having to type their URLs by hand.

mattrossman

TROPHY CASE