dbaba
commented
7 years ago Thank you for the comment. Your suggestion sounds good and I try to implement the feature. The reason why the node frequently tries to connect to all known peripherals is to collect as many notify events as possible from many devices (more than 10). However, as you said, if you don't want the node to propagate the notify events, it's indeed desirable that the node does nothing unless it receives any trigger input message.
Here is a list of expected scenarios for the enhancement:
- The node doesn't connect to a peripheral when a user mute notify events from the peripheral
- The node connect to a peripheral when Read/Write operation message arrives at the node
- The node connect to a peripheral when "Poll Notify Events" operation message arrives at the node (this is not a GATT operation though)
If you have any suggestions regarding the above list, let me know.
Hi, this is an interesting project. I'm trying to use it to harvest information from some BLE sensors that I've strewn about my work area. Their intent is to be low powered (i.e., sleeping most of the time) and only wakeup to provide sensor data when needed.
For example, I have a sensor that sleeps at about 0.37mA but when it takes in a connection it'll jump up to about 4mA to provide data. Once the central disconnects, it'll reset back down to its 0.37mA low power state.
This node however seems to connect quite frequently and on its own. Is there any way to tune this so it happens when triggered via another node like a timer/manual/etc...