-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTA update via platformio not working and Preferences.h questions #72
Comments
I would also like to have this feature implemented... It was sooo easy to use it before Asynwebserver... |
For me it works like this with the extra script, note the URL:
Edit: Wait, no. It just gives an "OK" but the firmware isn't written 😕 |
ive had the same problem. For me it helped to use these platformio.ini configurations
and i had to modify the platformio_upload.py file, and excuse me, i haven't been programming very long. It's not pretty but it works for me.
|
@mindsuru The internal API of ElegantOTA indeed got changed to provide a much better & stable experience. Your fix looks promising! It was a community PR that added it in past that's why it wasn't updated with V3. If you don't mind, can you open a PR that fixes the |
Thanks, I changed the python file slightly. Now you can use it with the old configuration in your platformio.ini |
@mindsuru For me the version you have here does not work. It gives the following error, then quits:
Seems to me that it cannot find the OTA page... This is the relevant part of my
As you can see I have an extra script running, but I don't suppose that would be an issue as the behavior is that same when I remove it. |
@mindsuru @ayushsharma82 When can we expect PR and merge? |
@viktak is your device reachable with this ip you‘ve choosen in your platformio.ini file? |
It has been merged but yet to be released. |
I guess he's using authentication that's why response code was '401' which means 'Unauthorized'. The script might need adjustments to work with authentication enabled. |
Yes, the device is reachable, all other functions of the asyncwebserver and elegantota are all working. |
Yessss, I definitely use authentication. But the authentication is added on a per page basis, i.e. for each of the protected pages (not all of them are) I add this line:
So the pages that don't use authentication should work just fine. In fact, those pages of mine that do not require authentication work fine. |
Okay good to know. I will have a look on it. But unfortunatly i‘m ill right now. It may take a bit. |
Get well soon, that's the priority! |
i think thats it. now both upload methods should work. regardless of whether you use the encrypted or non-encrypted method. |
@mindsuru Yes, it is now working.
|
One more request, perhaps it is possible to rename the expected variables from this:
to this:
This is to get rid of those pesky PlatformIO warning:
|
sure and thanks for this information |
I have been using the updated script for a couple of months now on various projects. Here are my observations:
or it complains about the magic byte (I can't remember the exact message...) |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I still have this issue. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I still have this issue. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I still have this issue. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I still have this issue. |
Hi,
I'm using platformio (on VSC) and Win10 for programming of my device.
In my platformio.ini file I have placed the following code:
[env:WiFi]
upload_protocol = espota
upload_port = 10.100.8.60
When I try to build and upload, I get the following error:
Uploading .pio\build\WiFi\firmware.bin
14:18:41 [DEBUG]: Options: {'esp_ip': '10.100.8.60', 'host_ip': '0.0.0.0', 'esp_port': 3232, 'host_port': 48565, 'auth': '', 'image': '.pio\build\WiFi\firmware.bin', 'spiffs': False, 'debug': True, 'progress': True, 'timeout': 10}
14:18:41 [INFO]: Starting on 0.0.0.0:48565
14:18:41 [INFO]: Upload size: 1284432
Sending invitation to 10.100.8.60 ..........
14:18:41 [ERROR]: No response from the ESP
*** [upload] Error 1
If I browse to the device e.g. http://10.100.8.60/update, the ElegantOTA web page is displayed.
Any ideas on how to get this to work through the platformio environment?
I read somewhere on the RNT website that ElegantOTA overwrites the spiffs and Preferences (NVS) flash storage.
In platformio is there a way of limiting where ElegantOTA writes to?
Thanks,
Neil.
The text was updated successfully, but these errors were encountered: