iBeacon: Flag to use UUID in topic or presence (and fixes) #1226
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:
Inspired by issue #1139
Replaces PR #1220
Add compilation flags to use UUID in topic, instead of sender (random) mac address:
FLAG
useBeaconUuidForTopic
to use UUID in topicFLAG
useBeaconUuidForPresence
to use UUID in presenceThis features is disabled by default, usual behavior is maintained
The question of whitelisting/blacklisting by UUID for a iBeacon, as exposed in the issue, is not approached in this commit.
(WhtL/BlkL is filtered prior to
pubBTMainCore()
function, so it does not seems to be as simple as this PR)Change introduced regarding MQTTDecodeTopic and code refactor
Fix jsonPublishing (regarding #1141?) there is an #ifdef left here that should be an #if
Checklist:
Thanks, Bad