[Solved] OpenBK v1.17.xx Update: Settings Reset, Backup/Restore, Managing Devices, MQTT & Firmware Updates

Hey all!

Got a few questions that I was hoping someone could help with.

1) Was it expected that when upgrading some devices (1.15.xxx to 1.17.xxx) they lose all of their settings? I have to reconnect to the fallback AP and reconfigure everything...

2) Is there an easy backup/restore for these settings? (names/mqtt/inputs/etc.) - I know there is a backup/restore fsblock section on the webapp, but I am not sure what is included in fsblock?

3) Any best practices for managing a number of devices? - right now I have used the secondary "Group Topic" MQTT with a common name depending on the model (e.g., I have a number of wall dimmer switches all with the same name), this has allowed me to execute common commands across them (e.g., toggle LED) as well as batch update. But when I have some 5-10 different device types, that's a lot of executing to update firmwares.... should I be using just the "beken_t" / "beken_n" groups which seemed to now be default?

4) Lastly - am I missing a change log summary on GitHub? I know each .xxx nightly release usually has a one or two-line description, but are major changes (and especially breaking changes) tracked somewhere? Given the amazing development progress, documentation seems to be one of the next missing pieces - it's already come a long way, and will go towards being in a stable place (FWIW, I'd love to be of help if needed.)

Sorry to bombard with everything! I've been actively on the lookout for new Beken-based devices, and I expect to have a couple more teardowns coming soon!

Thanks!

Hello, thank you for your continued support to our firmware!

1) there was indeed a silly error that was breaking config if you didn't do a gradual updates, it only affected when you were going from an old version to one of the newest versions, it's fixed now, but older builds are still affected ( I may just remove them from github). When you update now, go straight to latest version

2) fsblock is LittleFS, but there is also option to download CFG partition (4KB file) on Web App as well and that will include almost all of your settings (well, maybe except MAC which is per--device and resides in RF partition)

3) What exactly would you like to do? Are you using Windows? We're working on a IP scanner and generic tool for both Tasmota and OBK, it's currently within our Windows flasher

4) Unfortunatelly, you are right. There is no good log summary except the commits history. If you have any idea how to improve it, let us know.
Our docs are currently here:
https://github.com/openshwprojects/OpenBK7231T_App/blob/main/docs/README.md
and they are partially autogenerated from code.
You can also check our tutorials section:
https://www.elektroda.com/rtvforum/forum517.html

Thanks! Always appreciate the supportive team here.

1) I'll give the latest FW a shot!

2) So if I understand this, using the "Download OBK Config" link and the "Start CFG write" form on the "Flash" Tab of the web app would work as a backup/restore function for the pins, mqtt config?

3) Just thinking about the best way to bulk update and manage devices. I had used the group topic to align to different devices (to enable other commands), but I am thinking that I should probably reset that to just "bekens_t" or "bekens_n" - since that seems to be the best way to bulk update firmwares... Will have to download the latest Flasher app and check it out.

4) Maybe it might help to have a running list of "significant" changes - either breaking or major improvements on a single page somewhere. Could be either on the forum here, or on GitHub. Thinking about things like "implemented HA discovery" as a major enhancement vs. the smaller nightly fixes. That way people who may have missed a few nightly builds can quickly see what changed. Just some ideas.

mattj wrote:

2) So if I understand this, using the "Download OBK Config" link and the "Start CFG write" form on the "Flash" Tab of the web app would work as a backup/restore function for the pins, mqtt config?

It will backup everything except:
- the RF partition (calibration data for WiFi)
- MAC address
- LittleFS files

mattj wrote:

3) Just thinking about the best way to bulk update and manage devices. I had used the group topic to align to different devices (to enable other commands), but I am thinking that I should probably reset that to just "bekens_t" or "bekens_n" - since that seems to be the best way to bulk update firmwares... Will have to download the latest Flasher app and check it out.

Well, this is an open source project, unless you need some feature, there is usually no need to mass update stuff. It's maintained mostly by me, since some time also @DeDaMrAz helps on a daily basis, but that's it. Mistakes can happen. I don't recommend mass updating if everything works OK.

mattj wrote:

4) Maybe it might help to have a running list of "significant" changes - either breaking or major improvements on a single page somewhere. Could be either on the forum here, or on GitHub. Thinking about things like "implemented HA discovery" as a major enhancement vs. the smaller nightly fixes. That way people who may have missed a few nightly builds can quickly see what changed. Just some ideas.

It's a good idea but requires some manpower to maintain. Regarding breaking changes - I am actively trying to avoid them. I really can't think of any at the moment... well, maybe except the fact that adding not-yet-finished SSID2 field made OTA to older version lose device config.

There was a bug with the prior update. It has since been fixed in the latest releases.