thinger-io / vscode-extension Goto Github PK

On push to master create a new release, build the vsix and publish it to a release. Also publish the vsix to the vscode marketplace.

Create a log after the OTA process to verify if it was completed successfully (eg generate a .TXT file; Or process messages in VS Code’s Serial Monitor). Justification: The OTA process takes time to complete (eg: In the updates I made using a GSM connection, the OTA completed after 15 minutes) and at the end of the process, no persistent warning is generated that allows the user to verify that everything went well(Or identify errors during the OTA). (Note: The current pop-up in VS CODE, which informs you of the success of the update, quickly disappears after the OTA is completed)

Include a check and warning to alert (or prevent) when the Firmware sent to the Device via OTA has a “USERNAME”, “DEVICE_ID”, “DEVICE_CREDENTIAL” or “THINGER_SERVER” (and “APN_NAME”, “APN_USER”, “APN_PSWD”, and “SSID”, “SSID_PASSWORD”) different from the current Firmware that is in the device.
This functionality is important to prevent (or alert) the Developer from updating a Firmware of Device “A” with the Firmware of a Device “B” that has a different configuration or identification (“USERNAME”, “DEVICE_ID”, “DEVICE_CREDENTIAL” or “ THINGER_SERVER", and “APN_NAME”, “APN_USER”, “APN_PSWD”, and “SSID”, “SSID_PASSWORD”).

If this occurs, Device “A” may go offline and not be able to connect to the Thinger Server. This issue is even more critical when Device “A” is somewhere far away and difficult to access.
Ex: “USERNAME”, “DEVICE_ID”, “DEVICE_CREDENTIAL”, “THINGER_SERVER”, “APN_NAME”, “APN_USER”, “APN_PSWD”, “SSID”, “SSID_PASSWORD”