Invert sense of GOVEE_LAN_NO_MULTICAST environment variable #243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The docs say that `GOVEE_LAN_NO_MULTICAST=true` should *disable* multicast discovery. This requires inverting the sense of the environment variable.
|
Ah, good catch, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The docs say that
GOVEE_LAN_NO_MULTICAST=trueshould disable multicast discovery:https://github.com/wez/govee2mqtt/blob/main/docs/CONFIG.md#lan-api-control
However, because the sense of the environment variable was not inverted, you actually had to do
GOVEE_LAN_NO_MULTICAST=falseto get this effect.(If you're curious, the reason I wanted this was because I have no LAN-capable devices anyway, and this is one way to bypass the time spent on scanning for LAN devices.)