GPIO Binding "Connecion error"

Dom76 · July 31, 2025, 5:07pm

Hello everyone

I installed version 5 of OpenHab on a Raspberry Pi 5 and imported my backup file from my previous installation.

Everything works perfectly except for the GPIO connection, which is giving me a connection error on my device.



I followed the prerequisites in the documentation, and when I query the status of the service, this is the result:

sudo systemctl status pigpiod
× pigpiod.service - Daemon required to control GPIO pins via pigpio
     Loaded: loaded (/lib/systemd/system/pigpiod.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/pigpiod.service.d
             └─public.conf
     Active: failed (Result: exit-code) since Thu 2025-07-31 18:50:18 CEST; 2min 2s ago
   Duration: 470us
    Process: 5012 ExecStart=/usr/bin/pigpiod (code=exited, status=0/SUCCESS)
   Main PID: 5013 (code=exited, status=1/FAILURE)
        CPU: 1ms

Jul 31 18:50:18 openhabian pigpiod[5013]: 2025-07-31 18:50:18 gpioHardwareRevision: unknown rev code (c04170)
Jul 31 18:50:18 openhabian pigpiod[5013]: 2025-07-31 18:50:18 initCheckPermitted:
Jul 31 18:50:18 openhabian pigpiod[5013]: +---------------------------------------------------------+
Jul 31 18:50:18 openhabian pigpiod[5013]: |Sorry, this system does not appear to be a raspberry pi. |
Jul 31 18:50:18 openhabian pigpiod[5013]: |aborting.                                                |
Jul 31 18:50:18 openhabian pigpiod[5013]: +---------------------------------------------------------+
Jul 31 18:50:18 openhabian pigpiod[5013]: Can't initialise pigpio library
Jul 31 18:50:18 openhabian systemd[1]: Started pigpiod.service - Daemon required to control GPIO pins via pigpio.
Jul 31 18:50:18 openhabian systemd[1]: pigpiod.service: Main process exited, code=exited, status=1/FAILURE
Jul 31 18:50:18 openhabian systemd[1]: pigpiod.service: Failed with result 'exit-code'.

Any ideas?

rlkoshak · July 31, 2025, 6:28pm

I would have expected that the GPIO binding would be used by more people and this would have been caught before now.

Some Googling around brings up this GitHub issue:

It seems that PiGPIO is not compatible with the RPi 5 and there is no indication that it will be anytime soon.

Please file an issue on the openhab-addons repo.

At minimum the binding’s readme needs to be updated to indicate it’s non-compatibility with the RPi 5. Ideally someone will update it to depend on some alternative way to access the pins.

In the meantime, you can use an alternative approach to access the pins. I initially wrote GitHub - rkoshak/sensorReporter: A python based service that receives sensor inputs and publishes them in various ways. expressly for this purpose. It is a separate service (like pigpio) but it can interact with OH directly sending updates and commands to and from your Items or via MQTT and the MQTT binding. I’m certain there are other options out there as well.

Dom76 · August 1, 2025, 6:43am

Thank you for your quick response. Unfortunately, I don’t have the skills to use your work in Python. I only use two GPIO outputs to operate two relays, I will work around the problem.

rlkoshak · August 1, 2025, 1:55pm

If you can install openHAB you can install sensorReporter. We’ve tried to make it as automated and as easy as possible.

Clone the repo: git clone https://github.com/rkoshak/sensorReporter.git
From within the sensorReporter folder run sudo ./setup.sh. It will ask a series of questions. When it asks which dependencies you want enter “gpio,openhab_rest”. I’m assuming no MQTT and instead use of a direct to openHAB connection.
At the end it gives you the commands to enable sensorReporter as a service and run it as a service.
Create and edit the file “sensorReporter.yml” with the following contents (replacing relevant values with your values).

Logging:
    File: /var/log/sensor_reporter/sensorReporter.log
    MaxSize: 67108864
    NumFiles: 10
    Syslog: no
    Level: INFO

# Using openHAB REST API
openHAB:
    Class: openhab_rest.rest_conn.OpenhabREST
    Name: openHAB
    URL: http://localhost:8080 # path to your OH
    RefreshItem: Test_Refresh # When this Item gets an ON command, sensorReporter will publish all current states
    openHAB-Version: 5.0
    API-Token: <API-Token generated from openHAB profile page>
    Level: INFO

# Controls one of the relays
relay1:
    Class: gpio.rpi_gpio.RpiGpioActuator
    Connections:
        openHAB:
            Item: RelayItem # name of the Item that controls this relay
    GpioChip: 0 # if running RPi 5 use 4
    Pin: 35 # control pin for the relay
    InitialState: ON # when sensorReporter comes up it will set the pin to ON or OFF
    SimulateButton: True # when True toggles the pin as if someone pressed and released a momentary button
    Level: DEBUG

# Controls the second relay
relay2:
    Class: gpio.rpi_gpio.RpiGpioActuator
    Connections:
        openHAB:
            Item: Relay2Item # name of the Item that controls this relay
    GpioChip: 0 # if running RPi 5 use 4
    Pin: 10 # control pin for the relay
    InitialState: ON # when sensorReporter comes up it will set the pin to ON or OFF
    SimulateButton: True # when True toggles the pin as if someone pressed and released a momentary button
    Level: DEBUG

From OH, if you command the Item RelayItem to ON it will command the relay to ON. When you command it to OFF it will command the relay to OFF.

I may have typos in there some come back if you go down this path and get stuck.

sudo systemctl restart sensorReporter to pick up the changes. With the above config logs can be found in /var/logs/sensor_reporter/sensorReporter.log

Dom76 · August 2, 2025, 9:41am

Thanks for the information, I’ll try it. However, I use MQTT and not OpenhabREST, which I’ve never used and don’t know.

rlkoshak · August 2, 2025, 3:25pm

I’m “openHAB REST” just means use openHAB’s native API. You use that every time you use MainUI or sitemaps. That’s how the UI communicated with the server.

You basically get it for free.

Dom76 · August 2, 2025, 5:08pm

Ok I need to look into this. If I can’t figure it out, could you tell me how to implement MQTT in your program?

Dom76 · August 2, 2025, 5:14pm

I have a mosquito server, zigbee2mqtt and all my esp objects connected with tasmota. I’m pretty comfortable with that now.

rlkoshak · August 2, 2025, 9:44pm

The examples on the readme are pretty straight forward.

If you can install openHAB you can install sensorReporter. We’ve tried to make it as automated and as easy as possible.

Clone the repo: git clone https://github.com/rkoshak/sensorReporter.git
From within the sensorReporter folder run sudo ./setup.sh. It will ask a series of questions. When it asks which dependencies you want enter “gpio,mqtt”.
At the end it gives you the commands to enable sensorReporter as a service and run it as a service.
Create and edit the file “sensorReporter.yml” with the following contents (replacing relevant values with your values).

Logging:
    File: /var/log/sensor_reporter/sensorReporter.log
    MaxSize: 67108864
    NumFiles: 10
    Syslog: no
    Level: INFO

# MQTT config
Connection1:
    Class: mqtt.mqtt_conn.MqttConnection
    Name: MQTT
    Client: cerberos # unigue id for the connection to the broker
    User: user # username to log into the broker
    Password: password # password to log into the broker
    Host: localhost
    Port: 1883
    TLS: NO
    Keepalive: 60
    RootTopic: sensor_reporter/somename # root topic all the sensors and actuators will read/write to
    Level: INFO

# Controls one of the relays
relay1:
    Class: gpio.rpi_gpio.RpiGpioActuator
    Connections:
        MQTT:
            CommandSrc: relay1/cmd # will subscribe to sensor_reporter/somename/relay1/cmd for ON/OFF and TOGGLE commands, There is an optional StateDest property you can supply to publish the state of the relay
    GpioChip: 0 # if running RPi 5 use 4
    Pin: 35 # control pin for the relay
    InitialState: ON # when sensorReporter comes up it will set the pin to ON or OFF
    SimulateButton: True # when True toggles the pin as if someone pressed and released a momentary button
    Level: DEBUG

# Controls the second relay
relay2:
    Class: gpio.rpi_gpio.RpiGpioActuator
    Connections:
        MQTT:
            CommandSrc: relay2/cmd
    GpioChip: 0 # if running RPi 5 use 4
    Pin: 10 # control pin for the relay
    InitialState: ON # when sensorReporter comes up it will set the pin to ON or OFF
    SimulateButton: True # when True toggles the pin as if someone pressed and released a momentary button
    Level: DEBUG

From OH, if you publish “ON” to /sensor_reporter/somename/relay1/cmd it will command the relay to ON. When you publish “OFF” it will command the relay to OFF.

sudo systemctl restart sensorReporter to pick up the changes. With the above config logs can be found in /var/logs/sensor_reporter/sensorReporter.log

Dom76 · August 4, 2025, 4:40pm

Ok, I installed it and everything went well (dependencies gpio,openhab_rest) .
I created the sensor_reporter.yml file
and updated it with my settings.

Last login: Mon Aug  4 17:49:47 on ttys000

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
MacBook-Pro-DOM-2:~ DOM$ ssh openhabian@192.168.1.20
openhabian@192.168.1.20's password: 
Linux openhabian 6.12.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Aug  4 17:48:21 2025 from 192.168.1.188

###############################################################################
###############  openhabian  ##################################################
###############################################################################
##        Ip = 192.168.1.20
##   Release = Debian GNU/Linux 12 (bookworm)
##    Kernel = Linux 6.12.34+rpt-rpi-2712
##  Platform = BCM43455 37.4MHz Raspberry Pi 3+-0190
##    Uptime = 0 day(s). 00:09:58
## CPU Usage = 17.66% avg over 4 cpu(s) ( core(s) x - socket(s))
##  CPU Load = 1m: 0.43, 5m: 0.56, 15m: 0.44
##    Memory = Free: 0.91GB (23%), Used: 3.11GB (77%), Total: 3.95GB
##      Swap = Free: 2.99GB (100%), Used: 0.00GB (0%), Total: 2.99GB
##      Root = Free: 45.86GB (85%), Used: 8.07GB (15%), Total: 56.84GB
##   Updates = 18 apt updates available.
##  Sessions = 1 session(s)
## Processes = 167 running processes of 4194304 maximum processes
###############################################################################

                          _   _     _     ____   _               
  ___   ___   ___   ___  | | | |   / \   | __ ) (_)  ____   ___  
 / _ \ / _ \ / _ \ / _ \ | |_| |  / _ \  |  _ \ | | / _  \ / _ \ 
| (_) | (_) |  __/| | | ||  _  | / ___ \ | |_) )| || (_) || | | |
 \___/|  __/ \___/|_| |_||_| |_|/_/   \_\|____/ |_| \__|_||_| | |
      |_|                  openHAB 5.0.0 - Release Build          

Looking for a place to get started? Check out 'sudo openhabian-config' and the
documentation at https://www.openhab.org/docs/installation/openhabian.html
The openHAB dashboard can be reached at http://openhabian:8080
To interact with openHAB on the command line, execute: 'openhab-cli --help'

openhabian@openhabian:~ $ cd /opt/sensorReporter
openhabian@openhabian:/opt/sensorReporter $ ls
bin               install_dependencies.sh  README.md
bt                lib                      roku
core              lib64                    sensor_reporter_edit.service
dependencies.txt  LICENSE                  sensor_reporter.py
energymeter       local                    sensor_reporter.service
exec              mqtt                     sensor_reporter.yml
gpio              network                  sensorReporter.yml
heartbeat         one_wire                 setup.sh
i2c               openhab_rest             test_type-checker
include           pyvenv.cfg
openhabian@openhabian:/opt/sensorReporter $ python sensor_reporter.py
No config file specified on the command line! Usage: bin/python sensorReporter.py [config].yml
openhabian@openhabian:/opt/sensorReporter $ bin/python sensorReporter.py [config].yml
bin/python: can't open file '/opt/sensorReporter/sensorReporter.py': [Errno 2] No such file or directory
openhabian@openhabian:/opt/sensorReporter $ bin/python sensor_reporter.py [config].yml
Traceback (most recent call last):
  File "/opt/sensorReporter/sensor_reporter.py", line 317, in <module>
    main()
  File "/opt/sensorReporter/sensor_reporter.py", line 308, in main
    glob_poll_mgr = create_poll_manager(config_file)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/sensorReporter/sensor_reporter.py", line 222, in create_poll_manager
    with open(config_file, 'r', encoding='utf_8') as file:
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '[config].yml'
openhabian@openhabian:/opt/sensorReporter $  bin/python sensor_reporter.py sensor_reporter.yml
2025-08-04 17:56:02,937     INFO - [sensor_reporter] Setting logging level to INFO
2025-08-04 17:56:02,937     INFO - [    PollManager] Starting polling loop
^C2025-08-04 18:09:27,116     INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the process: 2 <frame at 0x7fff3162dc60, file '/opt/sensorReporter/core/poll_mgr.py', line 78, code start>
2025-08-04 18:09:27,616     INFO - [    PollManager] Waiting for all the polling threads
2025-08-04 18:09:27,617     INFO - [    PollManager] Cleaning up the sensors
2025-08-04 18:09:27,617     INFO - [    PollManager] Cleaning up the actuators
2025-08-04 18:09:27,617     INFO - [    PollManager] Disconnecting from connections
openhabian@openhabian:/opt/sensorReporter $ sudo nano sensor_reporter.yml
[sudo] password for openhabian: 
openhabian@openhabian:/opt/sensorReporter $ bin/python sensor_reporter.py sensor_reporter.yml
2025-08-04 18:14:01,954     INFO - [sensor_reporter] Setting logging level to INFO
2025-08-04 18:14:01,954     INFO - [    PollManager] Starting polling loop
^C2025-08-04 18:17:51,334     INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the process: 2 <frame at 0x7ffec48adc60, file '/opt/sensorReporter/core/poll_mgr.py', line 78, code start>
2025-08-04 18:17:51,834     INFO - [    PollManager] Waiting for all the polling threads
2025-08-04 18:17:51,834     INFO - [    PollManager] Cleaning up the sensors
2025-08-04 18:17:51,835     INFO - [    PollManager] Cleaning up the actuators
2025-08-04 18:17:51,835     INFO - [    PollManager] Disconnecting from connections
openhabian@openhabian:/opt/sensorReporter $ bin/python sensor_reporter.py sensor_reporter.yml
2025-08-04 18:18:04,522     INFO - [sensor_reporter] Setting logging level to INFO
2025-08-04 18:18:04,522     INFO - [    PollManager] Starting polling loop
^X^C2025-08-04 18:20:59,431     INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the process: 2 <frame at 0x7fff0dbedc60, file '/opt/sensorReporter/core/poll_mgr.py', line 78, code start>
2025-08-04 18:20:59,932     INFO - [    PollManager] Waiting for all the polling threads
2025-08-04 18:20:59,932     INFO - [    PollManager] Cleaning up the sensors
2025-08-04 18:20:59,932     INFO - [    PollManager] Cleaning up the actuators
2025-08-04 18:20:59,932     INFO - [    PollManager] Disconnecting from connections
openhabian@openhabian:/opt/sensorReporter $ bin/python sensor_reporter.py sensor_reporter.yml
2025-08-04 18:27:12,857     INFO - [sensor_reporter] Setting logging level to INFO
2025-08-04 18:27:12,858     INFO - [    PollManager] Starting polling loop
^C2025-08-04 18:37:02,613     INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the process: 2 <frame at 0x7fff7100dc60, file '/opt/sensorReporter/core/poll_mgr.py', line 78, code start>
2025-08-04 18:37:03,113     INFO - [    PollManager] Waiting for all the polling threads
2025-08-04 18:37:03,114     INFO - [    PollManager] Cleaning up the sensors
2025-08-04 18:37:03,114     INFO - [    PollManager] Cleaning up the actuators
2025-08-04 18:37:03,114     INFO - [    PollManager] Disconnecting from connections
openhabian@openhabian:/opt/sensorReporter $ ls
bin               exec       install_dependencies.sh  mqtt          README.md                     sensor_reporter.yml
bt                gpio       lib                      network       roku                          sensorReporter.yml
core              heartbeat  lib64                    one_wire      sensor_reporter_edit.service  setup.sh
dependencies.txt  i2c        LICENSE                  openhab_rest  sensor_reporter.py            test_type-checker
energymeter       include    local                    pyvenv.cfg    sensor_reporter.service
openhabian@openhabian:/opt/sensorReporter $ sudo nano sensorReporter.yml
[sudo] password for openhabian: 
openhabian@openhabian:/opt/sensorReporter $ sudo nano sensor_reporter.yml

  GNU nano 7.2                                            sensor_reporter.yml                                                      
    MaxSize: 67108864
    NumFiles: 10
    Syslog: no
    Level: INFO

# Using openHAB REST API
openHAB:
    Class: openhab_rest.rest_conn.OpenhabREST
    Name: openHAB
    URL: http://192.168.1.20:8080 # path to your OH
    RefreshItem: Test_Refresh # When this Item gets an ON command, sensorReporter will publish all current states
    openHAB-Version: 5.0
    API-Token: <API-Token generated from openHAB profile page>
    Level: INFO

# Controls one of the relays
relay1:
    Class: gpio.rpi_gpio.RpiGpioActuator
    Connections:
        openHAB:
            Item: GPIO_4_alarm # name of the Item that controls this relay
    GpioChip: 4 # if running RPi 5 use 4
    Pin: 4 # control pin for the relay
    InitialState: OFF # when sensorReporter comes up it will set the pin to ON or OFF
    SimulateButton: True # when True toggles the pin as if someone pressed and released a momentary button
    Level: DEBUG

# Controls the second relay
relay2:
    Class: gpio.rpi_gpio.RpiGpioActuator
    Connections:
        openHAB:
            Item: GPIO_Remote_GPIO_Out_18_Internet # name of the Item that controls this relay
    GpioChip: 4 # if running RPi 5 use 4
    Pin: 18 # control pin for the relay
    InitialState: OFF # when sensorReporter comes up it will set the pin to ON or OFF
    SimulateButton: True # when True toggles the pin as if someone pressed and released a momentary button
    Level: DEBUG




^G Help         ^O Write Out    ^W Where Is     ^K Cut          ^T Execute      ^C Location     M-U Undo        M-A Set Mark
^X Exit         ^R Read File    ^\ Replace      ^U Paste        ^J Justify      ^/ Go To Line   M-E Redo        M-6 Copy



When I launch the program, this happens:

Capture d’écran 2025-08-04 à 18.34.59



But when I activate my items, nothing happens.

Any ideas?

log file :

2025-08-04 17:29:42,806 INFO - [sensor_reporter] Setting logging level to INFO

2025-08-04 17:29:42,807 INFO - [ PollManager] Starting polling loop

2025-08-04 17:35:27,376 INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the proces>

2025-08-04 17:35:27,876 INFO - [ PollManager] Waiting for all the polling threads

2025-08-04 17:35:27,876 INFO - [ PollManager] Cleaning up the sensors

2025-08-04 17:35:27,876 INFO - [ PollManager] Cleaning up the actuators

2025-08-04 17:35:27,876 INFO - [ PollManager] Disconnecting from connections

2025-08-04 17:56:02,937 INFO - [sensor_reporter] Setting logging level to INFO

2025-08-04 17:56:02,937 INFO - [ PollManager] Starting polling loop

2025-08-04 18:09:27,116 INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the proces>

2025-08-04 18:09:27,616 INFO - [ PollManager] Waiting for all the polling threads

2025-08-04 18:09:27,617 INFO - [ PollManager] Cleaning up the sensors

2025-08-04 18:09:27,617 INFO - [ PollManager] Cleaning up the actuators

2025-08-04 18:09:27,617 INFO - [ PollManager] Disconnecting from connections

2025-08-04 18:14:01,954 INFO - [sensor_reporter] Setting logging level to INFO

2025-08-04 18:14:01,954 INFO - [ PollManager] Starting polling loop

2025-08-04 18:17:28,744 INFO - [sensor_reporter] Setting logging level to INFO

2025-08-04 18:17:28,745 INFO - [ PollManager] Starting polling loop

2025-08-04 18:17:51,334 INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the proces>

2025-08-04 18:17:51,834 INFO - [ PollManager] Waiting for all the polling threads

2025-08-04 18:17:51,834 INFO - [ PollManager] Cleaning up the sensors

2025-08-04 18:17:51,835 INFO - [ PollManager] Cleaning up the actuators

2025-08-04 18:17:51,835 INFO - [ PollManager] Disconnecting from connections

2025-08-04 18:18:04,522 INFO - [sensor_reporter] Setting logging level to INFO

2025-08-04 18:18:04,522 INFO - [ PollManager] Starting polling loop

2025-08-04 18:20:59,431 INFO - [sensor_reporter] (SIGTERM/SIGINT) terminating the proces>

2025-08-04 18:20:59,932 INFO - [ PollManager] Waiting for all the polling threads

2025-08-04 18:20:59,932 INFO - [ PollManager] Cleaning up the sensors

2025-08-04 18:20:59,932 INFO - [ PollManager] Cleaning up the actuators

2025-08-04 18:20:59,932 INFO - [ PollManager] Disconnecting from connections

rlkoshak · August 4, 2025, 4:51pm

sensorReporter is configured to run as a service. You start it and stop it using sudo systemctl. The last two lines of the setup.sh script you ran tells you how to enable and run the service.

To use the service, enter:
sudo systemctl enable sensor_reporter.service 
sudo systemctl start sensor_reporter.service

Did you run those commands? If not do that, and it will start sensorReporter as a service. You can see if it’s running with

sudo systemctl status sensor_reporter.service

You can see the logs by looking at /var/log/sensor_reporter/sensorReporter.log.

When it runs this way, it will load sensor_reporter.yml.

Once you got the name of the config file right what you posted shows sensorReporter up and working. But it’s not running as a service so as soon as you ctrl-c sensorReporter stops running. The good news is there’s no errors in the config file.

Dom76 · August 4, 2025, 5:57pm

Yes, I did that correctly, and the service is running.


But there's no effect on the GPIOs, and when I activate the "Test_Refresh" item, nothing happens.

rlkoshak · August 4, 2025, 6:36pm

Show the contents of sensorReporter.log

Hmm, it doesn’t look like the config file is being loaded at all.

The config file is exactly names sensor_reporter.yml and that’s the file you’ve put the config into? That’s the config fie it’s trying to load. sensorReporter will complain if you don’t pass a config file, but if the file is empty it doesn’t complain.

There should be lines in the log talking about creating the openHAB REST connection followed by creating the actuators.

After that you’ll see “Starting polling loop” statement. Nothing is being created or even attempted to be created so it must not be loading the right config file or the config file is empty or something.

Dom76 · August 5, 2025, 6:00am

To check if the file is empty, I deleted the URL and suddenly I have an error in the log file. This therefore suggests that the file is loaded and that it is not empty.

Dom76 · August 5, 2025, 6:05am

I’m going to do a test in Mqtt, should I uninstall the current configuration and if so how? I would also like to add an input on GPIO 17, what should I add in the yml file for this? Thanks in advance.

rlkoshak · August 5, 2025, 2:58pm

This suggests that it’s loading what ever file you deleted (assuming the error message was complaining about a lack of config file) but it says nothing about whether the file is empty or otherwise malformed. The logs clearly indicate that sensorReporter is loading nothing from this file.

If it’s not loading anything from the config file changing to MQTT isn’t going to change anything. There should be entries in the logs for the creation of each communicator and each sensor and actuator defined in that config file. There is nothing at all logged.

You can run setup.sh again and enter “gpio,mqtt” when it asks, or run install_dependencies.sh gpio,mqtt.

You can find examples at sensorReporter/gpio/README.md at main · rkoshak/sensorReporter · GitHub as well as an explanation of each property.

“an input on GPIO 17” is not sufficient to answer the question. An input for what? A reed sensor? DTH11 tem,perature/humidity sensor, momentary button, toggle switch?

I use the following for a reed sensor.

SensorLargeGarageDoor:
    Class: gpio.rpi_gpio.RpiGpioSensor
    Connections:
        MQTT:
            Switch:
                StateDest: garagedoor1/state
    GpioChip: 0
    Pin: 7
    PUD: DOWN
    Btn_Pressed_State: HIGH
    EventDetection: BOTH
    Level: DEBUG

Dom76 · August 5, 2025, 10:26pm

I need an input for an on-off contact

rlkoshak · August 6, 2025, 1:45am

Well, a reed sensor is an on/off sensor and that’s what the above is for.

Dom76 · August 7, 2025, 3:55pm

A little feedback on my MQTT tests, after installation the MQTT client was created but the Gpio contacts do not react to commands. I may have forgotten a few things.

rlkoshak · August 7, 2025, 3:59pm

You’ve yet to show your actual config file you are using. You’ve not shown any recent logs. The logs you’ve shown so far indicate the config file doesn’t contain any connections, sensors, or actuators. You have to give me something to go on.