Open Jacksonbm1 opened 3 years ago
This is probably unavoidable due to the way noble works where it's a shared resource: if plugin A starts listening for discovered devices & plugin B starts discovering devices then plugin A will be notified about the ones discovered in plugin B's discovery step.
Since noble is still the best node cross platform BLE library, even though the original developers abandoned it, all BLE homebridge plugins will likely suffer from some level of cross-talk & the bugs that present themselves from that.
So if you were to have one plug in (like yours) with multiple devices, do you think this issue would persist? I imagine people often want more than one device and aren’t using a dedicated pi for each device
"Each device" being an AM43 motor or "each device" being different BLE devices?
This plug-in can support as many AM43 devices as whatever's hosting your Homebridge can support (which for the Pi's built in Bluetooth is 10 I think).
If you're talking about different devices then yeah, until someone writes a better low level library for communicating to BLE from node JS then I think there's always going to be cross-talk causing bugs that are very hard to replicate.
Running separate child Homebridges on one device might be enough but if noble works the way I think it does then I doubt it'd help much.
Hello, I'm using the plugin right now, but every time I turn it and my switchbot plugin on, I start getting errors. Turning off one or the other allows this the plugins to work correctly.
Here's the switchbot plugin I'm running.
CONFIG (redacted irrelevant parts):
Logs