f34rdotcom
commented
1 year ago I have a bunch of uncommitted changes for the stsdk module I need to commit and also fix the build. I have another branch I am working on travis building so we can confirm everything builds that would include the stsdk binary.
The key can be changed via command line but the onboarding_config.json is fixed and I 100% agree this needs to be added to the configuration file. I will keep this open to track that change.
The older releases here do contain the stsdk version for manual flashing. If I can resolve some of these build issues it would be good to get it back into the current releases. Any help appreciated so be prepared to help me test :c)
Best SM
jslcom
This is a great project and I have some high hopes for doing some interesting integrations once I get it working.
I tried to get this going in February, but got stuck with some problems and dropped it for a while. I picked it up again a few days ago and started fresh. I'm trying to build this using command-line tools and no IDE. This should be possible. Below are a few of the issues I encountered while building on Ubuntu: 1) The build script encounters shell script syntax errors because the default system shell on Ubuntu is dash not bash. Rectified with: sudo dpkg-reconfigure dash 2) Directory empty at AlarmDecoder-IoT/components/twilio/lib/fmt. Obtained required source tree and manually placed it there. 3) Build failure from missing component: https://github.com/brofield/simpleini The platformio.ini file references this, but it's not clear to me how it integrates into the AlarmDecoder-IoT source tree. (I copied SimpleIni.h and ConvertUTF.h to main and it seems happy.) 4) Reference to undefined structure element: ../main/alarmdecoder_main.cpp: In function 'bool _show_pretty_process_list()': ../main/alarmdecoder_main.cpp:605:60: error: 'TaskStatus_t' {aka 'struct xTASK_STATUS'} has no member named 'xCoreID' (unsigned int)pxTSArray[x].xCoreID, ^
~~ 5) Undefined identifiers (STSDK_CONFIG_SECTION and STSDK_SUBCMD_ENABLE): ../main/alarmdecoder_main.cpp:1165:33: error: 'STSDK_CONFIG_SECTION' was not declared in this scope ad2_get_config_key_bool(STSDK_CONFIG_SECTION, STSDK_SUBCMD_ENABLE, &stEN); ^~~~~~~~ ../main/alarmdecoder_main.cpp:1165:33: note: suggested alternative: 'AD2PART_CONFIG_SECTION' ad2_get_config_key_bool(STSDK_CONFIG_SECTION, STSDK_SUBCMD_ENABLE, &stEN); ^~~~~~~~ AD2PART_CONFIG_SECTION ../main/alarmdecoder_main.cpp:1165:55: error: 'STSDK_SUBCMD_ENABLE' was not declared in this scope ad2_get_config_key_bool(STSDK_CONFIG_SECTION, STSDK_SUBCMD_ENABLE, &stEN); ^~~~~~~ ../main/alarmdecoder_main.cpp:1165:55: note: suggested alternative: 'STSDK_ENABLE' ad2_get_config_key_bool(STSDK_CONFIG_SECTION, STSDK_SUBCMD_ENABLE, &stEN); ^~~~~~~I'm going to keep plowing away at this. Last time I tried, I was able to get an image built and installed, but I encountered some other issues that may have been resolved since then. No filesystem was available to host the needed configuration files for the webui build. My platform has no microSD card and the internal flash-based filesystem didn't work. (I will have a microSD card on my platform after this Wednesday when the parts I ordered arrive.) Last time, I was able to flash new binaries from Nutech OTA, but they had the same filesystem deficiency and did not work.
The documentation describes two build types: webui and stsdk. The webui build does not include SmartThings integration and the stsdk build does not include the web interface. Is it possible to make a build with both of these features enabled? It does seem to be possible to create such a configuration with menuconfig, but I don't know if it will work.
Despite being unable to build this, I was able to load the pre-built binary (webui 1101) and try a few things. As expected, the web interface displays the following: "file not found. Connect a uSD card with a FAT32 partition and the html content in the root directory before the device starts." (I expect to have uSD capability on my target sometime soon after the parts I ordered from Amazon arrive.) After performing an OTA "upgrade", my version was downgraded to webui 1100. The "top" command is now missing, and the target can no longer access the OTA server: AD2IOT # upgrade webui AD2IOT # Starting OTA update with build flags 'webui'.
AD2IOT # !IOT: E (1914865) esp-tls: Failed to connnect to host (errno 113) !IOT: E (1914865) esp-tls: Failed to open new connection !IOT: E (1914865) TRANS_SSL: Failed to open a new connection !IOT: E (1914875) HTTP_CLIENT: Connection failed, sock < 0 !IOT: E (1914875) AD2OTA: ota_https_update_device: Failed to open HTTP connection: 28674 !IOT: E (1914885) AD2OTA: Firmware Upgrades Failed (28674) !IOT: E (1914885) AD2OTA: Exiting task due to fatal error... AD2IOT #
I noticed that the stsdk pre-built binary is unavailable here, but I was able to load it via OTA. I'm wondering if the developer key is present in the binary blob. If so, it would be great if the key were instead stored apart from the binary (somewhere in flash) so that image could be distributed too.
Thanks!
Jeff