subscribe/unsubscribe usage about node-poweredup HOT 5 CLOSED

Aaannd it does. A single blink and the device goes off. No attempt to connect to anything else. :)

I'll look to publishing a new version with this functionality a bit later today.

from node-poweredup.

The subscribe/unsubscribe methods are used at connection time of a new device (color sensor, tilt sensor, etc) to tell the sensor what mode to put itself in. They are automatically called by this library when it detects a new device/sensor.

For example, the "color and distance sensor" shipped with the Boost tookit has several modes - one where it only reports color values, one where it only reports distance values, one where it reports both, etc. There are a couple more.

The reason they exist is that by only reporting the values the receiver cares about, it can save BLE bandwidth by not sending out the rest of the data that the receiver has indicated it doesn't care about.

For simplicity's sake, this library automatically puts the Boost sensor into "color and distance" mode, as you can just ignore the values you don't care about, and I've yet to run into any issues (or hear of anyone running into issues) with BLE bandwidth limits.

This is the function that sets the default modes: https://github.com/nathankellenicki/node-poweredup/blob/master/src/hub.ts#L415-L432

If you want (and the reason these methods are public rather than private), you can set the sensors into different modes - but, WARNING! :) I have not tested the sensor message parsing code with other modes other than the defaults I've set, and as they currently don't check, it may break!

Regarding your second question - you will only reconnect if you are still scanning. So you should call stop() on your PoweredUP instance before you disconnect your Hub instance.

However I believe the power off talked about in that thread is a hard power off - immediate shutdown, no blinking lights, no attempt to reconnect. Almost like flicking a switch. But I haven't tested it yet.

from node-poweredup.

thanks, now it makes more sense :) I had a feeling that it is something low level

from node-poweredup.

Yes, you can stop scanning, but if you have hub and remote control and you want to disconnect them, they will then find each other and connect, so hard shut down would be good to have

from node-poweredup.

Well that would only happen if a) both devices were disconnected at the same time, and b) both the remote and the hub had been paired together at some point in the past, but agreed, a hard shutdown would be good, as it would stop other devices/people who are scanning from connecting to it.

Hopefully it works as advertised. :)

from node-poweredup.