Open Jacksonbm1 opened 2 years ago
The first error you got was because noble (the Bluetooth package this plugin uses) is using bindings to communicate with bluetooth, however these bindings have to be recompiled every time you update node, even for minor versions.
The seconds errors you were getting were because something changed in NPM with install git packages, I've changed how @abandonware/noble is included in the package, this should solve the install issues.
However I've decided to officially deprecate the plugin because it's hard to get bluetooth working stable using either Node or Python, instead I'm now using a ESP32 based bridge. You can read more about it here: https://github.com/renssies/homebridge-am43-blinds/issues/41#issuecomment-1186548675
Hey, yeah I get that. Thanks for your support up till this point. Helped me support pretty janky shades for a year or so. Honesty, I just switched to the mqtt esp32 solution and it's just way more stable. I think pi's just seem to not do super well with Bluetooth and I don't think that's your fault. Noble is weird. Also, yeah am43 Bluetooth is pretty garbage. I ordered some zigbee am43 earlier and I'm happy that they're coming in even if I currently am stable.
I had been getting:
So I tried uninstalling the plug in and reinstalling. That's when the real trouble started:
There were some issues with my npm having two separate installations, but I resolved those and still was getting the error.
I saw a few other bugs that told me to run it unsafe, so I ran: sudo npm install -g --unsafe-perm=true --allow-root homebridge-am43-blinds@0.3.0
This yielded:
The entire log file is massive and I can send it over later, but it looks like some weird git hub authentication. I'm starting to think there's an issue with abandonware or something. I have also tried: https://github.com/renssies/homebridge-am43-blinds/issues/40#issuecomment-987732496
anyone else facing this? Any solutions?