Skip to content
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

Can't Load Plugin homebridge-gpio-device #99

Open
SK8081 opened this issue Sep 28, 2020 · 5 comments
Open

Can't Load Plugin homebridge-gpio-device #99

SK8081 opened this issue Sep 28, 2020 · 5 comments

Comments

@SK8081
Copy link

SK8081 commented Sep 28, 2020

I have the lastest Raspberry Pi release from Homebridge.io. Installed wiringpi 2.46. Loaded the latest homebridge-gpio-device and as soon as I start homebridge, I receive this error.

[9/28/2020, 12:19:51] ERROR LOADING PLUGIN homebridge-gpio-device:
[9/28/2020, 12:19:51] Error: Could not locate the bindings file. Tried:
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/build/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/build/Debug/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/build/Release/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/out/Debug/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/Debug/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/out/Release/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/Release/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/build/default/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/compiled/12.18.4/linux/arm/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/addon-build/release/install-root/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/addon-build/debug/install-root/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/addon-build/default/install-root/nodeWiringPi.node
→ /usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/lib/binding/node-v72-linux-arm/nodeWiringPi.node
at bindings (/usr/local/lib/node_modules/homebridge-gpio-device/node_modules/bindings/bindings.js:126:9)
at Object. (/usr/local/lib/node_modules/homebridge-gpio-device/node_modules/node-wiring-pi/index.js:1:37)
at Module._compile (internal/modules/cjs/loader.js:1137:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
at Module.load (internal/modules/cjs/loader.js:985:32)
at Function.Module._load (internal/modules/cjs/loader.js:878:14)
at Module.require (internal/modules/cjs/loader.js:1025:19)
at require (internal/modules/cjs/helpers.js:72:18)
at Object. (/usr/local/lib/node_modules/homebridge-gpio-device/index.js:3:11)
at Module._compile (internal/modules/cjs/loader.js:1137:30)

Doe anyone have a fix?

@LangBalthazar
Copy link

I have the same issue tried multiple things following previous reports of this issue.

I have wiring pi working from terminal but the plugin in hombrigde renders the same error

`pi@NFCbridge:/wiringpi $ gpio -v
gpio version: 2.60
Copyright (c) 2012-2018 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

Raspberry Pi Details:
Type: Pi 3A+, Revision: 00, Memory: 512MB, Maker: Sony

  • Device tree is enabled.
    *--> Raspberry Pi 3 Model A Plus Rev 1.0
  • This Raspberry Pi supports user-level GPIO access.
    `

@ajhubs
Copy link

ajhubs commented Nov 16, 2020

Anyone find a fix for this ? I have the same issue.

@SK8081
Copy link
Author

SK8081 commented Nov 16, 2020

I was using this for my garage door opener and have since migrated away from it because of this issue. No fix that I am aware of..

@ajhubs
Copy link

ajhubs commented Nov 17, 2020

Thanks - Iv done the same using this instead, #99 - works well :)

@danalvi
Copy link

danalvi commented Nov 28, 2020

Same issue persists!

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

No branches or pull requests

4 participants