Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GPIO Button alway closed #32

Open
vzlgdu opened this issue Sep 17, 2017 · 9 comments
Open

GPIO Button alway closed #32

vzlgdu opened this issue Sep 17, 2017 · 9 comments

Comments

@vzlgdu
Copy link

vzlgdu commented Sep 17, 2017

Hi, I'm using your fantastic plugin and it work great to manage some leds, but I would try to use also to read the status fo some buttons; the problems is that the status is always closed, also changing parameters like pull up/dow/off and invert; do you have some suggests? Thanks in advance.

Guido

@rsg98
Copy link
Owner

rsg98 commented Sep 17, 2017 via email

@vzlgdu
Copy link
Author

vzlgdu commented Sep 17, 2017

Hi,
thanks for your feedback; about your suggest:

  • checked with GPIO utility the button status and it changes from 1 to 0 when it is pressed, so the circuit ok.
    . cancelled the cache as suggested by you in a previous post and restarted hombridge, but the problem persiste: the status is always closed also if I press the button.
    Following my definitions:

"platform" : "WiringPiPlatform",
"name" : "Pi GPIO (WiringPi)",
"overrideCache" : "true",
"autoExport" : "true",

{"name" : "GPIO8", "pin" : 2, "enabled" : "true","mode" : "in", "pull" : "up", "inverted" : "false","duration" : 0,"polling" : "false"},

Let me know.

Thanks

@rsg98
Copy link
Owner

rsg98 commented Sep 17, 2017 via email

@vzlgdu
Copy link
Author

vzlgdu commented Sep 17, 2017

Hi,
the pin is 3 (I'm using this borad: http://www.tecnofilo.es/tienda/raspberry-pi/235-placa-de-expansion-para-raspberry-similar-a-berryclip.html and led3 and buzzer are working excluding the 2 buttons).
Don't forget that when I using GPIO tool and I press buttons, I can see that the state changes from 1 to 0.

Let me know.

Thanks

@vzlgdu
Copy link
Author

vzlgdu commented Sep 17, 2017

Following the log:
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] Loading cached GPIO pins complete
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] New GPIO from config.json: GPIO8 (2)
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] GPIO8 Configure GPIO Pin 9d812b72-55e7-4cbe-bafe-6c4248d37429
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] Setting up interrupt callback
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] New GPIO from config.json: GPIO9 (3)
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] GPIO9 Configure GPIO Pin 5340bf88-027e-47d2-b5c8-021221816879
[2017-9-17 22:07:27] [Pi GPIO (WiringPi)] Setting up interrupt callback

@rsg98
Copy link
Owner

rsg98 commented Sep 18, 2017 via email

@vzlgdu
Copy link
Author

vzlgdu commented Sep 18, 2017

Hi,
thanks for explanation, I will try to execute the test asap and I will update you.
Thanks

@vzlgdu
Copy link
Author

vzlgdu commented Oct 5, 2017

Hi, tests executed: I can confirm that with other GPIOs everything works fine, so, pheraps, there is some conflict using I2C pins.
Thanks

@rsg98
Copy link
Owner

rsg98 commented Oct 5, 2017 via email

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants