search

jdeneef / ha_gpiod

gpiod based RPI gpio switches and sensors
https://github.com/jdeneef/ha_gpiod
MIT License
21 stars 4 forks source link

GPIO 0 (zero) not recognised any more after update #9

Closed majbah-ha closed 2 months ago

majbah-ha commented 3 months ago

Hello,

After the last update, I got an error that GPIO 0 not been recognised any more and I should use the numbers between 1 to 40. It was already working before update. In your configuration you advised using the list of sensor IO ports (Raspberry Pi BCM mode pin numbers) which zero one of them.

jdeneef commented 2 months ago

Fwiw, when using RPI the gpiod and path part in the config (first part of the config in the README) are not required anymore, gpio is autodiscovered. If removing and restarting homeassistant does not work please report the debugging logs. See bottom of README on how to add debug logging.

majbah-ha commented 2 months ago

I followed your instruction

Here is the part of log specific for the error

Other than what I mentioned before it says apply a number between 1 to 39 there is no zero.

2024-07-02 10:19:57.408 ERROR (MainThread) [homeassistant.config] Invalid config for 'switch' from integration 'gpiod' at configuration.yaml, line 97: value must be one of [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39] for dictionary value 'switches->4->port', got 0, please check the docs at https://github.com/jdeneef/ha_gpiod

If I change the port number to any other number from 1-39 it will work, but I need the zero because I already have used all other ports.

jdeneef commented 2 months ago

right, I get it, not the gpio device but the switch port. I possibly limited it too much, fixed it, port is now validated against cv.positive_int again, which is sufficient for 0. Fix pushed.

majbah-ha commented 2 months ago

Yes, it is working again Thanks, and keep up the good work

jdeneef commented 2 months ago

thanx for sharing, closing