-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: MCP23S17 control #36
Comments
I haven’t included that module in the back end rsg98/node-wiring-pi - but not sure that would help here, as this plugin also uses the SysFS GPIO interface to do some bits and pieces. However, there does look to be device tree support for your expansion board: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README In theory, if you set that up, they should just get mapped as “normal” GPIO pins and therefore be controllable by this plugin without any further changes. Let us know how you get on! |
I used the DT overlay to map the port expander as a 'normal' GPIO pin. After that I was able to control the gpio496 via sysfs from bash shell. Unfortunately I was not able o control the gpio496 from homebridge app correctly. Every push on the button in the homebridge app triggers an ON-state in the app for a few seconds, and after that the button falls back to OFF-state. But the GPIO pin state does not change. Do you have any idea?
|
Hmmm... didn't realise it would get allocated such a high range of pin numbers. I think (although I need to do more checks) that WiringPi has a built in limit to those it considers "built in" rather than extensions - which means we may need to add support for that module to the backend node-wiring-pi and figure out a way of addressing properly... will have a further dig around the WiringPi code. |
I did some basic test, and its possible to get the pin up and down with javascript fs.writeFile()
|
I was not able to control gpio 496 via wiringpi gpio utility
|
Thanks for the tests. Can you check whether you can still control it via the I can look at adding the module support back into node-wiring-pi and then figuring out an option for getting this module to control it - but it would (currently) require both device tree and the WiringPi extension. |
with the device tree configured, I'm not able to control the port expander via
|
Hi,
first of all, really nice module, works great. Thank you for this.
Is it possible to controll a MCP23S17 via homebridge-gpio-wpi2?
WiringPi gpio command use an extension module for this: gpio -x mcp23s17:base:spi:devId …
The text was updated successfully, but these errors were encountered: