RPI-Monitor Adapter for ioBroker
RPI-Monitor implementation for integration into ioBroker. It is the same implementation as for iobroker.rpi, but with GPIOs.
ioBroker needs special permissions to control GPIOs. On most Linux distributions this can be achieved by adding the ioBroker user to the gpio group.
For gpio to work, you need to install libgpiod in version 2.x, before installing the adapter (see below)!
Caution
Version 3.x.x of this adapter supports and requires Debian trixie. Do not update if you are using older o/s.
After installation you have to configure all required modules via administration page.
After start of iobroker.rpi, all selected modules generates
an object tree in ioBroker within rpi..
e.g. rpi.0.cpu
Be sure, that python and build-essential are installed:
sudo apt update
sudo apt install -y build-essential python
sudo apt install -y libgpiod-dev(the last one is only necessary, if you want to work with GPIOs)
Following Objects are available after selection:
- cpu_frequency
- load1
- load5
- load15
- cpu_voltage
- mem_arm
- mem_gpu
- memory_available
- memory_free
- memory_total
- net_received
- net_send
- sdcard_boot_total
- sdcard_boot_used
- sdcard_root_total
- sdcard_root_used
- swap_total
- swap_used
- soc_temp
- uptime
- wifi_received
- wifi_send
On configuration page you can select following modules:
- CPU
- Raspberry
- Memory
- Network
- SDCard
- Swap
- Temperature
- Uptime
- WLAN
Since adapter version 2.3.2 you can read NVMe temperature. To do this, you need to install nvme-cli package on your system.
You can do this with the following command: sudo apt-get install nvme-cli. You will also need to add the command to the ioBroker
sudoers file /etc/sudoers.d/iobroker. Open it with an editor, for example nano: sudo nano /etc/sudoers.d/iobroker and add the following line to the bottom:
iobroker ALL=(ALL) NOPASSWD: /usr/sbin/nvme smart-log /dev/nvme0
You can read and control GPIOs too. All what you need to do is to configure in the settings the GPIOs options (additional tab).
After some ports are enabled following states appear in the object tree:
- rpi.0.gpio.PORT.state
The numeration of ports is BCM (BroadComm pins on chip). You can get the enumeration with gpio readall.
For instance PI2:
+-----+-----+---------+------+---+---Pi 2---+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| | | 3.3v | | | 1 || 2 | | | 5v | | |
| 2 | 8 | SDA.1 | ALT0 | 1 | 3 || 4 | | | 5V | | |
| 3 | 9 | SCL.1 | ALT0 | 1 | 5 || 6 | | | 0v | | |
| 4 | 7 | GPIO. 7 | IN | 1 | 7 || 8 | 0 | IN | TxD | 15 | 14 |
| | | 0v | | | 9 || 10 | 1 | IN | RxD | 16 | 15 |
| 17 | 0 | GPIO. 0 | IN | 0 | 11 || 12 | 0 | IN | GPIO. 1 | 1 | 18 |
| 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | |
| 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | 0 | IN | GPIO. 4 | 4 | 23 |
| | | 3.3v | | | 17 || 18 | 0 | IN | GPIO. 5 | 5 | 24 |
| 10 | 12 | MOSI | IN | 0 | 19 || 20 | | | 0v | | |
| 9 | 13 | MISO | IN | 0 | 21 || 22 | 1 | IN | GPIO. 6 | 6 | 25 |
| 11 | 14 | SCLK | IN | 0 | 23 || 24 | 1 | IN | CE0 | 10 | 8 |
| | | 0v | | | 25 || 26 | 1 | IN | CE1 | 11 | 7 |
| 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 |
| 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | |
| 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | IN | GPIO.26 | 26 | 12 |
| 13 | 23 | GPIO.23 | IN | 0 | 33 || 34 | | | 0v | | |
| 19 | 24 | GPIO.24 | IN | 0 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 |
| 26 | 25 | GPIO.25 | OUT | 1 | 37 || 38 | 0 | IN | GPIO.28 | 28 | 20 |
| | | 0v | | | 39 || 40 | 0 | IN | GPIO.29 | 29 | 21 |
+-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
| BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM |
+-----+-----+---------+------+---+---Pi 2---+---+------+---------+-----+-----+
You can read from DHT11, DHT22 and AM2302 temperature/humidity sensors.
Connect such a sensor to a GPIO pin as described on the node-dht-sensor package page. Multiple sensors can be connected to multiple pins (this is not a bus system) as discussed.
- (copilot) Adapter requires node.js >= 22 now
- (copilot) Adapter requires admin >= 7.7.22 now
- (mcm1957) Dependencies have been updated.
- (copilot) ENHANCED: Added
temperature.fan_activityobject to monitor fan RPM via/sys/devices/platform/cooling_fan/...; falls back to0when unavailable.
- (@klein0r) Check for required libgpiod-dev package version
- (@klein0r) Updated logo, workflows and documentation
- (@klein0r) admin 7.6.17 and js-controller 6.0.11 (or later) are required
- (@klein0r) NodeJS 20.x (or newer) is required
- (@klein0r) Updated opengpio to v2 (works on Debian trixie)
- (Garfonso) read the current state of GPIO outputs during adapter startup.
- (Garfonso) re-read GPIO input, if set by the user (with ack=false).
- (Garfonso) add an option to invert true/false mapping to 1/0.
- (Garfonso) Allow multiple instances of this adapter per host.
- (Garfonso) tried to improve initialization of GPIO inputs.
- (asgothian) added support for NVMe temperature (needs additional configuration, see README)
- (Garfonso) fixed inital values for outputs.
Older changelogs can be found there
MIT License
Copyright (c) 2026 iobroker-community-adapters iobroker-community-adapters@gmx.de
Copyright (c) 2024-2025 Garfonso garfonso@mobo.info
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.