Let's Control It

hi,
can i send a file directly to the esp without using the buildin fliebrowser?
i'd like to send a dashbord.htm via app.

I never tried it, but it should be possible using POST.
Note that some files cannot be overwritten like this, but any file with .htm extension does not have a protection filter.

tnx, ill try it

Yes, POST request to http://<ESPEasy Ip>/upload uploads a file to filesystem. Besides, you can update the firmware using /update path.

same for rules....

you can upload rules with curl

for rule 1 filename has to be rules1.txt and so on....

riker1 wrote: ↑14 Nov 2019, 09:08

Code: Select all

curl -v -F upload=@"/path/filename"  http:<IP>/upload/

Shouldn't there be a "//" between http:<IP>
?

Hi

of course you are right:

Hi! im playing with app inventor and espeasy. Is there a way to POST rules (like rules1.txt) with URL commands?
i know its possible with curl. but with url?
Thanks in advance!

You can have a look with the 'inspect' window of your browser to see how the rules are now saved from the web interface.
It is now using a JavaScript to "upload" the rules file you try to save.
In the past we used a POST command containing the entire rules for that file, but that POST message was kept in memory a few times and thus causing issues.
Some experienced a max of 15xx bytes, some had issues with truncated files at 17xx bytes.
Now that we upload the files it is working fine, but that means you can also upload it the same way using some tool like CURL.

i will try at home later! thanks!

well, i try as you suggested and switching between rules in can see this:

http://192.168.1.30/rules?set=2&rules=% ... ndon%0D%0A

First time works, but when i try today nothing happens...

That's a HTTP GET request.
I find it hard to believe this GET url does actually create a rules file with the contents suggested in the URL.

Like I said, the handling of the content of the rules file in either a GET url or a POST request must be stored in RAM and this will cause issues like lost data or even a completely empty rules file.
So you should use the upload as is also done in the JavaScript, which you can see using the inspect window of your browser and then looking at the "Network" tab of it.

Just to explain the differences:
- HTTP GET url is an URL you can bookmark. Everything is in the URL.
- HTTP POST request is used to send data to the ESP to create/update settings. Typically the content of a web form is sent via HTTP POST.

The /upload page on ESPEasy does have a handler for GET, but that's only to show the web page.
There is also a handler for POST on that url, which is using specific headers to signal an upload.
See for some examples: https://stackoverflow.com/a/28193031
But I strongly suggest to check what's being sent when you submit something on the rules page by using the Network tab on the inspect window of your browser (right mouse button => inspect)