Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
Command Interface:
NRFPAGE x , shows x sensors per page (default 4)
NRFIGNORE x, ignore sensor type x (1 - Flora, ..., 6 - CGD1), x=0 will ignore nothing
NRFSCAN x, scan for BLE-advertisments -> x=0: new scan list, x=1: append to scan list, x=2: stop scan, all will stop a running beacon.
List-example in the console:
15:16:31 MINRF: Beacon 00: AABBCCDDEEFF Cid: 004C Svc: 0000 UUID: 0000
15:16:31 MINRF: Beacon 01: AABBCCDDEEFF Cid: 004C Svc: 0000 UUID: 0000
15:16:31 MINRF: Beacon 02: AABBCCDDEEFF Cid: 004C Svc: 0000 UUID: 0000
(Note: Cid 004c is Apple, so MAC changes every few minutes anyway -> not feasible as "simple" beacon)
NRFBEACON x, x="1-3 digits" use entry from list above, x="12 characters" read as (uppercase!) MAC-String, both will start simple beacon function with support for RULES and mqtt with upcounting value every second. RULE-JSON after 2 seconds: {NRF:{"Beacon": 2}}, will reset with every received packet.
This chip is still no and will never be a real BLE-device, but it can do quite a lot for the price.
Checklist: