by Marco Paland, November 14, 2026
Turn Any Website into a Watch Face with the Web Scraper Provider
Turn any web page into live data for your watch face with the Web Scraper Provider.
The data you care about is almost always on some web page. The fuel price at your favourite station, the status of the cloud service your team depends on, the occupancy of your local swimming pool, the latest version of a tool you use every day.
Sometimes there is a nice JSON API for it, and then the REST Provider is the right tool. Often there is none. The value is just there, in plain HTML, waiting to be read.
This is exactly what the tyckr Web Scraper Provider is made for: it loads a web page, finds one element with a CSS selector and hands its value to your watch face or widget.
How It Works
The Web Scraper Provider only needs two things:
-
The URL of the page
-
A CSS selector in Param 1 of the
Valuequery that points to the element you want
tyckr uses the proven jsoup engine to parse the page, so the full CSS selector syntax is available, including some extras like :containsOwn(), :matches() and :eq().
The page is fetched again at the configured Interval. With Ignore Sleep switched off (the default), requests pause while the watch sleeps, which saves battery.
The fastest way to get a selector: open the page in your desktop browser, right-click the value and choose Inspect. Then right-click the highlighted HTML element and choose Copy > Copy selector in Chrome or Copy > CSS Selector in Firefox. Paste it into Param 1 and you are done.
Browser-generated selectors are often long and fragile, though. In the examples below we show short, robust selectors instead.
Real-Life Examples
1. Is the Cloud Down? Status Pages
Thousands of services publish their health on a hosted status page: GitHub, Atlassian, Dropbox, Discord and many more use the same well-known layout. That makes one selector work for all of them.
Setting |
Value |
URL |
|
Selector |
|
Result |
|
Put the result in a small Text Facelet. Now a neat trick: these pages mark the overall state with a CSS class, status-none when everything is fine and status-minor, status-major or status-critical when it is not. So let the selector do the check for you. Add a second query with .page-status:not(.status-none) .status. It only finds an element when there is a problem, so its Status becomes Excellent (1) exactly then. Use it as the visibility condition of a red warning Icon Facelet. When something breaks, you know it before the first support ticket arrives.
Switch the URL to the status page of your own provider and the face keeps working.
2. The Top Story of the Day
Developers love Hacker News, and its simple HTML is a perfect scraping target.
Setting |
Value |
URL |
|
Selector |
|
Result |
The headline of the current top story |
Use .score to show its points as well. Put the headline into a Ticker Facelet and it scrolls across the bottom of your face like a news channel.
3. Never Miss a Release
Want to know when your favourite tool ships a new version? GitHub’s "latest release" URL always redirects to the newest release page. Here is the Hugo static site generator, which also builds the blog you are reading right now:
Setting |
Value |
URL |
|
Selector |
|
Result |
|
|
Tip
|
When a page’s markup changes often, look for something more stable. The title selector returns Release v0.170.0 · gohugoio/hugo · GitHub, and the HTML title of a page rarely changes its structure.
|
A check interval of a few hours is more than enough here. Be nice to the servers you read from.
4. Fuel Prices: Find the Value Next to a Label
Many price pages are simple tables: a label in one cell, the price in the next one. Generated selectors like tr:nth-child(3) > td:nth-child(2) break as soon as the order changes. Instead, find the cell by its text and take its neighbour:
Setting |
Value |
URL |
the page of your fuel station or price comparison site |
Selector |
|
Result |
e.g. |
:containsOwn() finds the label cell no matter where it is in the table, and + td takes the cell right next to it. This pattern works on countless pages: exchange rates, snow depth on ski resort pages, water levels, sports tables.
Because the result is numeric, it can also drive a Gauge Facelet or a value expression, for example to turn the price green when it drops below your limit.
5. How Full Is the Pool?
Many public swimming pools, climbing halls and gyms show a live occupancy counter on their website, often something like:
<div class="occupancy">
<span class="count">87</span> / <span class="capacity">250</span>
</div>
The selector .occupancy .count returns 87. Combine it with a second Web Scraper query for .capacity and a value expression, and a Gauge Facelet shows the occupancy in percent. Check it on your wrist before you pack your swimming bag.
6. Your Own Devices at Home
Routers, NAS systems, solar inverters, heating controllers and weather stations often come with a small built-in web interface but no API. These pages are usually protected with a login. The Web Scraper Provider supports Basic and Bearer Token authentication, and with $USER, $PASS and $PARA you can even place credentials safely in the URL without writing them into the face itself.
Setting |
Value |
URL |
|
Authentication |
Basic, with your device user and password |
Selector |
|
Result |
the current solar power, e.g. |
Remember that local addresses are only reachable when your watch or phone is in your home network. Pair this with the Geofence Provider to show your home dashboard only when you are at home.
Tips for Robust Scraping
-
Prefer IDs and meaningful class names like
#priceor.statusover longnth-childchains. -
Use text anchors like
:containsOwn()when the label is more stable than the layout. -
Watch the Status query: it returns
Excellent(1) when a value was found andFail(5) when parsing failed. Use it as a visibility condition to show a small warning instead of an empty field. -
Static HTML only: the scraper reads the HTML that the server delivers. Values that are added later by JavaScript are not visible to it. If a page loads its data from a JSON endpoint, use that endpoint with the REST Provider and a JsonPath expression. It is faster and more reliable anyway.
-
Respect the source: choose a sensible interval, check the site’s terms of use and prefer an official API when there is one.
What Will You Scrape?
Once you start looking, data is everywhere: the next departure from your bus stop, the daily menu of the canteen, the queue time at the citizen’s office, the score of your local football club. If you can see it in a browser, you can very likely see it on your wrist.
We would love to see your ideas. Share your faces with the community and let us know what you built.
Happy scraping and happy tyckring!