feat(firmware): make EzData integration optional via CONFIG_USE_EZDATA#22
Open
Flo5k5 wants to merge 1 commit intom5stack:mainfrom
Open
feat(firmware): make EzData integration optional via CONFIG_USE_EZDATA#22Flo5k5 wants to merge 1 commit intom5stack:mainfrom
Flo5k5 wants to merge 1 commit intom5stack:mainfrom
Conversation
Introduce a Kconfig boolean, defaulted to y, that gates the installation of the EzData Mooncake app in main.cpp. When disabled, the firmware never instantiates AppEzdata, so it never calls Hal::startEzDataService() and therefore never opens the MQTT connection to uiflow2.m5stack.com nor the HTTPS upload to ezdata2.m5stack.com. The default is y to preserve the existing production behaviour: builds that do not touch the new option keep shipping EzData as today. This is useful for self-hosted deployments that want zero outbound traffic to M5Stack cloud services, and for privacy-sensitive builds where cross-device parameter sync is not needed. The startEzDataService implementation itself is left untouched so the API surface stays stable for any downstream code that references it.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Introduce a Kconfig boolean, defaulted to y, that gates the installation
of the EzData Mooncake app in main.cpp. When disabled, the firmware
never instantiates AppEzdata, so it never calls
Hal::startEzDataService() and therefore never opens the MQTT connection
to uiflow2.m5stack.com nor the HTTPS upload to ezdata2.m5stack.com.
The default is y to preserve the existing production behaviour: builds
that do not touch the new option keep shipping EzData as today.
This is useful for self-hosted deployments that want zero outbound
traffic to M5Stack cloud services, and for privacy-sensitive builds
where cross-device parameter sync is not needed.
The startEzDataService implementation itself is left untouched so the
API surface stays stable for any downstream code that references it.