Stable config with custom sdkconfig #14
Open
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.
Stable build with a custom sdkconfig and required code changes
Build pulls esp-zboss-lib 1.6.4, and the build fails. This PR pins esp-zboss-lib to 1.5.1, rather than allowing higher minor and patch versions via ^1.5.1 #8 - Pin esp-zboss-lib to 1.5.1
ZBOSS must be started sooner so that the NVRAM datasets are loaded before answering incoming requests. Otherwise, Z2M would recognize that the network settings have been reset, and therefore, it would perform network formation again, which would result in all connected devices being lost. #6 - fixes #5
ESP-IDF SDK 5.5
ESP ZBOSS lib 1.6.4
Fix GET_ZIGBEE_CHANNEL_MASK line 117 from original code, which also allowed fixing getting the version, and set version to 5. Includes fixes for the following:
Update the README for flashing
Seems like app_device_version should be 1
Fix ext_pan_id order for Zigbee2MQTT, improve protocol version, remove compile warning
Remove ESP32 boot logging, system logging and console to prevent interference with protocol