You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-19Lines changed: 12 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,20 +12,19 @@ A simple Linux python script to query the Raspberry Pi on which it is running fo
12
12
13
13

14
14
15
-
This script should be configured to be run in **daemon mode** continously in the background as a systemd service (or optionally as a SysV init script). Instructions are provided below.
16
-
15
+
This script should be configured to be run in **daemon mode** continuously in the background as a systemd service (or optionally as a SysV init script). Instructions are provided below.
17
16
18
17
## Table of Contents
19
18
20
19
On this Page:
21
20
22
21
-[Features](#features)- key features of this reporter
23
-
-[Prerequisites](#prerequisites)
22
+
-[Prerequisites](#prerequisites)
24
23
-[Installation](#installation) - install prerequisites and the daemon project
25
24
-[Configuration](#configuration) - configuring the script to talk with your MQTT broker
26
25
-[Execution](#execution) - initial run by hand, then setup to run from boot
27
26
-[Integration](#integration) - a quick look at what's reported to MQTT about this RPi
28
-
-[Troubleshooting](#troubleshooting) - having start up issues? Check here for common problems
27
+
-[Troubleshooting](#troubleshooting) - having start up issues? Check here for common problems
29
28
30
29
Additional pages:
31
30
@@ -34,7 +33,6 @@ Additional pages:
34
33
-[The Associated Lovelace RPi Monitor Card](https://github.com/ironsheep/lovelace-rpi-monitor-card) - This is our companion Lovelace Card that makes displaying this RPi Monitor data very easy
35
34
-[ChangeLog](./ChangeLog) - We've been repairing or adding features to this script as users report issues or wishes. This is our list of changes
36
35
37
-
38
36
## Features
39
37
40
38
- Tested on Raspberry Pi's 2/3/4 with Jessie, Stretch and Buster
@@ -111,7 +109,7 @@ The monitored topic reports the following information:
111
109
|`throttle`|| reports the throttle status value plus interpretation thereof |
112
110
|`timestamp`|| date, time when this report was generated |
113
111
114
-
_NOTE: cpu load averages are divided by the number of cores_
112
+
NOTE: _cpu load averages are divided by the number of cores_
**NOTE**: *for users of Arch Linux the number of updates available will NOT be reported (will always show as '-1'.) This is due to Arch Linux not using the apt package manager.*
147
+
**NOTE**: _for users of Arch Linux the number of updates available will NOT be reported (will always show as '-1'.) This is due to Arch Linux not using the apt package manager._
150
148
151
149
### With these extra packages installed, verify access to network information
152
150
@@ -185,7 +183,7 @@ wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
185
183
186
184
```
187
185
188
-
If you are seeing output from the `ifconfig` tool then continue on with the following steps. If you don't you may have missed installing `net-utils` in an earlier step.
186
+
If you are seeing output from the `ifconfig` tool then continue on with the following steps. If you don't you may have missed installing `net-utils` in an earlier step.
189
187
190
188
### Now finish with the script install
191
189
@@ -436,10 +434,7 @@ An example:
436
434
"load_5min_prcnt": 0,
437
435
"load_15min_prcnt": 0
438
436
},
439
-
"throttle": [
440
-
"throttled = 0x0",
441
-
"Not throttled"
442
-
],
437
+
"throttle": ["throttled = 0x0", "Not throttled"],
443
438
"temperature_c": 25.8,
444
439
"temp_gpu_c": 25.8,
445
440
"temp_cpu_c": 25.8,
@@ -450,11 +445,10 @@ An example:
450
445
}
451
446
```
452
447
453
-
**NOTE:** Where there's an IP address that interface is connected. Also, there are new `tx_data` and `rx_data` values which show traffic in bytes for this reporting interval for each network interface.
448
+
**NOTE:** Where there's an IP address that interface is connected. Also, there are new `tx_data` and `rx_data` values which show traffic in bytes for this reporting interval for each network interface.
454
449
455
450
This data can be subscribed to and processed by your home assistant installation. How you build your RPi dashboard from here is up to you!
456
451
457
-
458
452
## Troubleshooting
459
453
460
454
### Issue: Some of my RPi's don't show up in HA
@@ -467,7 +461,7 @@ We occasionaly have reports of users with more than one RPi on their network but
467
461
468
462
Most often fix: _reboot the missing RPi._
469
463
470
-
When you remove a sensor from Home Assistant it tells the MQTT broker to 'forget' everything it knows about the RPi. Some of the information is actually `stored by the MQTT broker` so it is available while the RPi is offline. Our Daemon script only broadcasts this `stored` information when it is first started. As a result the RPi will not re-appear after delete from Home Assistant until you reboot the RPi in question. (or, alternatively, stop then restart the script.). You may find reboot easier to do.
464
+
When you remove a sensor from Home Assistant it tells the MQTT broker to 'forget' everything it knows about the RPi. Some of the information is actually `stored by the MQTT broker` so it is available while the RPi is offline. Our Daemon script only broadcasts this `stored` information when it is first started. As a result the RPi will not re-appear after delete from Home Assistant until you reboot the RPi in question. (or, alternatively, stop then restart the script.). You may find reboot easier to do.
471
465
472
466
To reboot:
473
467
@@ -510,13 +504,12 @@ I find [MQTT Explorer](http://mqtt-explorer.com/) to be an excellent tool to use
510
504
511
505
Alternatively I also use **MQTTBox** when I want to send messages by hand to interact via MQTT. it is affered as a web extension or a native application.
512
506
513
-
514
507
#### Viewing the Daemon logs
515
508
516
509
When your script is being run as a Daemon it is logging. You can view the log output since last reboot with:
**NOTE**: *the -b says 'since last boot' the --no-pager says just show it all without breaking it up into pages and requiring the enter key press for each page.*
523
+
**NOTE**: _the -b says 'since last boot' the --no-pager says just show it all without breaking it up into pages and requiring the enter key press for each page._
*NOTE* the message in the `{action} rqst via MQTT` message is logged in `/var/log/auth.log` so one can keep track of when commands are executed via MQTT.
@@ -109,7 +109,7 @@ the sudoers configuration file:
109
109
110
110
# add the following lines at the bottom.
111
111
# note that every service that we want to allow to restart must be specified here
0 commit comments