Move Example resources to Troubleshooting for easier readability of NUT (#38502)

* Move Example resources section into Troubleshooting

* Change example to shell

* Remove extra blank line
This commit is contained in:
tdfountain 2025-04-14 23:47:50 -07:00 committed by GitHub
parent e8f3cff89a
commit 18a5b7a6a5
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -332,12 +332,19 @@ automation:
message: "The UPS lost power and is now on battery"
```
## Example resources
## Troubleshooting
Given the following example output from NUT (your variables may differ):
### Using NUT to list all variables
```yaml
$ upsc ups_name@192.168.11.5
The NUT server provides "variables" about your power device. If you
have command line access to the system running your NUT server, you
can query NUT directly using the `upsc` command.
Below is an example where the NUT server is configured with a device
named `my_ups`:
```shell
$ upsc my_ups
ups.timer.reboot: 0
battery.voltage: 27.0
ups.firmware.aux: L3 -P
@ -373,11 +380,6 @@ output.voltage: 121.50
output.voltage.nominal: 120
```
Use the values from the left hand column. Support is included for most
values with `ups`, `battery`, `input` and `output` prefixes.
## Troubleshooting
### Using NUT to list all commands
The NUT server provides commands for controlling your power device. If