DIY lywsd03mmc OTA with changed manufacturer code #447
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
|
thanks! |
|
@devbis hi! it is possible to flash LYWSD03MMC with pvvx fw (installed_version: 19083265) to yours? how to do it right? I've tried several ota_index options, but couldn't change the firmware to yours. Thanks! |
|
@mrmaximas You can use a file from this comment devbis/z03mmc#118 (comment) and use local OTA json file |
|
@devbis thanks! it's works! are you planning to implement the measurement interval setting like pvvx? |
I don't have such plans, it is incompatible with zigbee reporting configuration in general |
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.
During the last OTA I changed manufacturer code to custom to avoid struggling for image type numbers for updates.
My suggestion is to put multiple DIY manufacturers to the same folder, I doubt there will be many of them.
I also considered using
DIY_devbisas a folder, but decided that it is redundant here.Firmware here is the same as in Telink folder with a correct manufacturer type in header to mute errors about missing OTA in the repo.