Merge branch 'dev'

docs/widgets/info/glances.md

@@ -16,6 +16,7 @@ The Glances widget allows you to monitor the resources (CPU, memory, storage, te
     cpu: true # optional, enabled by default, disable by setting to false
     mem: true # optional, enabled by default, disable by setting to false
     cputemp: true # disabled by default
+    cpuSensorLabel: Package id # optional additional cputemp sensor label prefix
     unit: imperial # optional for temp, default is metric
     uptime: true # disabled by default
     disk: / # disabled by default, use mount point of disk(s) in glances. Can also be a list (see below)
@@ -24,6 +25,8 @@ The Glances widget allows you to monitor the resources (CPU, memory, storage, te
     label: MyMachine # optional
 ```
 
+The built-in `cputemp` sensor matching already checks common prefixes such as `cpu_thermal`, `Core`, `Tctl`, and `Temperature`. Use `cpuSensorLabel` to add your own Glances sensor label prefix when your system reports CPU temperatures under a different name.
+
 Multiple disks can be specified as:
 
 ```yaml

docs/widgets/services/ntfy.md

@@ -0,0 +1,36 @@
+---
+title: ntfy
+description: ntfy Widget Configuration
+---
+
+Learn more about [ntfy](https://github.com/binwiederhier/ntfy).
+
+This widget shows the latest notification for a ntfy topic, including the title or body, priority level, and when it was received. Works with both self-hosted ntfy instances and the public [ntfy.sh](https://ntfy.sh) service.
+
+Allowed fields: `["title", "message", "priority", "lastReceived", "tags"]`.
+
+Default fields: `["title", "message", "priority", "lastReceived"]`.
+
+If more than 4 fields are provided, only the first 4 are displayed.
+
+## Authentication
+
+ntfy supports both public and private topics. For private instances or access-controlled topics, you can authenticate using either a **Bearer token** (ntfy access token) or **Basic auth** (username/password).
+
+| Auth Method  | Config Fields                  | Notes                             |
+| ------------ | ------------------------------ | --------------------------------- |
+| None         | _(omit key/username/password)_ | For public topics                 |
+| Bearer token | `key`                          | ntfy access tokens (`tk_` prefix) |
+| Basic auth   | `username` + `password`        | Username/password credentials     |
+
+See the [ntfy documentation](https://docs.ntfy.sh/config/#access-control) for details on access control.
+
+```yaml
+widget:
+  type: ntfy
+  url: http://ntfy.host.or.ip:port # required
+  topic: mytopic # required
+  # key: tk_accesstoken # optional — for token auth
+  # username: user # optional — for basic auth
+  # password: pass # optional — for basic auth
+```

docs/widgets/services/pyload.md

@@ -13,4 +13,5 @@ widget:
   url: http://pyload.host.or.ip:port
   username: username
   password: password # only needed if set
+  key: pyloadapikey # only needed if set, takes precedence over username/password
 ```

docs/widgets/services/tailscale.md

@@ -9,7 +9,7 @@ You will need to generate an API access token from the [keys page](https://login
 
 To find your device ID, go to the [machine overview page](https://login.tailscale.com/admin/machines) and select your machine. In the "Machine Details" section, copy your `ID`. It will end with `CNTRL`.
 
-Allowed fields: `["address", "last_seen", "expires"]`.
+Allowed fields: `[ "address", "last_seen", "expires", "user", "hostname", "name", "client_version", "os", "created", "authorized", "is_external", "update_available", "tags" ]`.
 
 ```yaml
 widget:

docs/widgets/services/technitium.md

@@ -14,6 +14,7 @@ widget:
   type: technitium
   url: <url to dns server>
   key: biglongapitoken
+  node: <node dns name or cluster> # optional, defaults to current node
   range: LastDay # optional, defaults to LastHour
 ```
 
@@ -21,6 +22,10 @@ widget:
 
 This can be generated via the Technitium DNS Dashboard, and should be generated from a special API specific user.
 
+#### Node
+
+`node` value determines which Technitium cluster node the statistics are returned for. Specifying a value of `cluster` returns aggregrate stats for all nodes in the cluster. Specify a node domain name to return specific node stats, no value returns stats for the node against which the API is executed.
+
 #### Range
 
 `range` value determines how far back of statistics to pull data for. The value comes directly from Technitium API documentation found [here](https://github.com/TechnitiumSoftware/DnsServer/blob/master/APIDOCS.md#dashboard-api-calls), defined as `"type"`. The value can be one of: `LastHour`, `LastDay`, `LastWeek`, `LastMonth`, `LastYear`.