Local development about ruuvicollector

[Scrin]

When I'm doing development on one of my Linux machines, I use hcitool and hcidump directly as it's by default. When I happen to do development on my Windows machine, I have initially enabled WSL on the machine, generated a SSH key and added that key to other Linux machines (and raspberry pi's). This should probably work with some command-line windows ssh client too, but I use WSL for other reasons too so it was the easiest choice.

Then finally I have this in my collector config:

command.dump=bash -c "ssh [email protected] hcidump --raw"

which effectively runs hcidump over ssh from another Linux computer/rpi through WSL. Before this I used to have a text file containing a dump gathered from another machine and then as the dump command I just read the file (command.dump=cmd /c "type hcidump.txt"), but it became a bit cumbersome as it all pops all the data instantly and it's the same data over and over again.

I have also put an empty command.scan= to disable the scan command, and instead run hcitool lescan --duplicates --passive manually on the device where hcidump actually runs on, as this allows me to simulate situations where there's a pause in the data flow by stopping the hcitool command and starting it again, although it could be done over ssh the same way as the dump.

I don't have any macs, but the same hcidump-over-ssh trick should work equally fine on macs

[matthewgardner]

Awesome - thanks :)