Include a button to “uncheck” the device.
This functionality is important, otherwise a device will always be tagged, and the developer may confuse the “Upload by Serial USB” buttons with the “Upload by OTA/internet” buttons when updating a firmware.
It is also interesting not to select any device when resetting the VS CODE. Otherwise, the developer may mistake and “Upload by OTA” by mistake when trying to “Upload by Serial”.
I also suggest changing the device’s background color from blue to green, to draw the developer’s attention, avoiding “Upload by Serial” instead of “Upload by OTA”.
I would test what happens for ESP8266, but in theory a reboot is issued at the end of flash both for ESP32 and ESP8266 to apply the update.
Will check how to solve it.
In theory it keeps selected the latest flashed device for that project. So, if you change between projects, the flashed device will change. With the ability to deselect a device it should be solved.
VSCode Studio does not allow setting arbitrary colors on the toolbar… a “normal state” is without any background color. You can only set backgrounds for warnings, errors, etc…
Is “remote console” definitively abandoned, or do you have a schedule to get it working?
I can successfully telnet into my ESP32 devices within the wlan, but doing that worldwide over thinger.io without requesting a port forwarding would have been ways more sexy…
Saving the distances, It works practically like a linux terminal, each character is echoed back to the web terminal to ensure the message arrived fine to the device.
I think it can be released tomorrow. I need to do some more testing.
I have already used this service from Visual Studio Code, I have a private instance. But now it seems that it has stopped working, it is not listing the devices, the token is the same that I have used in the past.
This does not look good, RIGHT NOW IT BRINGS ME A LOT OF PROBLMES !! The dependency on Visual Studio Code does not make it scalable and if vulnerable to third parties. Perhaps documentation on the OTA update process with Thinger.io will help to implement a solution via REST API (Not everything has to be done by you), with this I would think about sending updates to my fleet of devices and not depending on third parties like Visual Studio Code.
It is out of our hand. You can switch back to previous VSCode version (it is mentioned in this topic); you can test any of the workarounds mentioned; or even, you can try it on Linux where it works perfectly.
We are working on other OTA processes for fleets of devices, but it will take some time.
Loving this OTA option , and it has at last forced me to swap over from using Arduino IDE to using VSC and Platformio, I wasn’t aware what I was missing . Thank you @alvarolb
I am really looking forward to any news about the OTA for fleet updates.
Hi - VSCode/Platformio Extension seems like a great solution for OTA deployments. Worked fine in a simple set up but I have an platformio.ini set up with multiple environments and the extension builds all of them! It would be good to set up an env section specific to the ThingerOTA and only build that one. Would it be possible to add a setting, or option to select which env is built and uploaded?