Updated https://github.com/openshwprojects/OpenBK7231T_App/pull/1471 with this idea:
Moved defines for file extension to obk_config.h as #define OBK_OTA_EXTENSION "<file extension>" for all platfoms with OTA
Replaced "#if NO_PLATFORM_OTA" with "#ifndef OBK_OTA_EXTENSION"
Good to hear it's kind of useful maybe @divadiow I can ask for your support again to do some testing on my new try to separate NTP and clock as a requirement to use other clock sources.
Its https://github.com/openshwprojects/OpenBK7231T_App/pull/1483
Since it involves changes to many files, it's getting merge conflicts very fast meaning I have to do the PR again ans again...
This PR should only relocate and rename functions and only do one simple change to the system: The "clock" is present even if it's not synced or ntp driver not started.
This allows to drop the special handling, e.g. in json_interface.c implementing a "fake" NTP returning 0 in case NTP is not present.
This implementation (e.g. "Clock_GetCurrentTime()") will always report time 0 as time in this case, so we can drop this code.
I also fixed code which I believe was in wrong "#ifdef"s in cmd_if.c: there was a mix up of bl0937 and ntp code, no problem if both is defined but not working, if only ntp is active.
Prominent example: $yesterday and $today - they sound like ntp functions and where in NTP section, but they will return the energy consumption for yesterday/today, so they belong to the BL0397 section...
So if you could do some tests if all time related functions still work as expected?
Especially the advanced features like sunrise/sunset and events?
Thanks to @p.kaczmarek2 we have some basic tests already done be selftests, so it's not totally wrong
The discussion revolves around the challenges and solutions related to Over-The-Air (OTA) updates for devices, particularly focusing on the LN882H and XR809 models. Users encountered issues with OTA stability when using the Firefox browser, attributed to SDK code discrepancies. The conversation explores whether a web app is necessary for OTA updates, especially in scenarios without internet access. Suggestions for improving the OTA process include implementing filename checks, providing feedback during updates, and ensuring compatibility with various platforms. The need for a structured approach to file naming and validation is emphasized to prevent device bricking. Additionally, there are discussions about the implementation of OTA features across different platforms, including Beken and BL602 devices. Summary generated by the language model.