search

prusa3d / Prusa-Firmware-ESP32-Cam

Firmware for ESP32 Cam modules to be used in Prusa Connect
GNU General Public License v3.0
97 stars 10 forks source link

User Friendly Upload #33

Open ALD-Models opened 1 month ago

ALD-Models commented 1 month ago

To make the install process easy for users I've created a website that users can go to to easily install the firmware. It uses esp-web tools and contains a user friendly interface which also show errors and logs

This is the website: https://ald-models.github.io/Prusa-ESP32-Cam-Web-Upload/

Hopefully this should be useful!

Jake

BugsBunny1403 commented 1 month ago

It's great, I'm going to test it right now and it's easy to upload the firmware. Just one problem, wifi management by esp web tool is apparently unavailable. I think it has something to do with an improv wifi and web serial function.

ALD-Models commented 1 month ago

Thanks. I've not yet enabled the WiFi setup but i might play around with it tomorrow!

Jake

johnyHV commented 1 month ago

Awesome! It is possible in the future added support for multiple different MCU version ? Or configuration the WiFi network, token and something else ?

johnyHV commented 1 month ago

I see that currently, the binary files are stored in your GIT repository. This can raise suspicion and distrust. Would it be possible to use the binary files directly from the release?

BugsBunny1403 commented 1 month ago

If you create own site with esp tool yes. Envoyé depuis mon appareil Galaxy -------- Message d'origine --------De : Miroslav Pivovarsky @.> Date : 29/05/2024 14:16 (GMT+01:00) À : prusa3d/Prusa-Firmware-ESP32-Cam @.> Cc : BugsBunny1403 @.>, Comment @.> Objet : Re: [prusa3d/Prusa-Firmware-ESP32-Cam] User Friendly Upload (Issue #33) I see that currently, the binary files are stored in your GIT repository. This can raise suspicion and distrust. Would it be possible to use the binary files directly from the release?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

ALD-Models commented 1 month ago

Yes that is a good point and I guess it would also make sense to keep with the latest update.

I'm not quite sure how to make the link

Is their a easy method to do this?

Jake

ALD-Models commented 4 weeks ago

The password should be 12345678. If the problem persists, try turning mobile data off or connecting via a laptop/computer.

Jake

From: cwylie11 @.> Sent: Monday, June 3, 2024 11:22:37 PM To: prusa3d/Prusa-Firmware-ESP32-Cam @.> Cc: Jake Lofthouse @.>; Author @.> Subject: Re: [prusa3d/Prusa-Firmware-ESP32-Cam] User Friendly Upload (Issue #33)

can't connect to the esp's wifi when using this method of installing onto the ESP32. Is the password supposed to be the same?

The ESP network shows up, but just says "can't connect to this network" when it tries to authenticate and connect.

Any suggestions?

— Reply to this email directly, view it on GitHubhttps://github.com/prusa3d/Prusa-Firmware-ESP32-Cam/issues/33#issuecomment-2146226610, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATB3LPZ2BTAQJDBBVWOYW23ZFTUC3AVCNFSM6AAAAABINHA3KKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBWGIZDMNRRGA. You are receiving this because you authored the thread.Message ID: @.***>

Anheledir commented 4 weeks ago

You should either clear the esp32 by default, or add a separate button to do so. The error that you cannot login to the AP happens usually when flashing the esp32 for the first time or some old data is not overwritten. Doing a clear before flashing should solve that issue and takes just a few more seconds.

Also, would it be viable to add that site also to this repository, so everything related is in one place? Not necessary, but would be nice 👀

Anheledir commented 4 weeks ago

I'm not quite sure how to make the link

Is their a easy method to do this?

I'm not aware of a direct call for the latest release, but I used some script or backend-code in other projects. For example:

# Fetch the latest release information
latest_release=$(curl -s https://api.github.com/repos/prusa3d/Prusa-Firmware-ESP32-Cam/releases/latest)

# Extract the download URLs
download_urls=$(echo $latest_release | grep -oP '"browser_download_url": "\K(.*)(?=")')

# Download each asset
for url in $download_urls; do
    wget $url
done

Within the for-loop you could filter only the .bin files. Not the most elegant solution, but should work 🫣

ALD-Models commented 4 weeks ago

Also, would it be viable to add that site also to this repository, so everything related is in one place? Not necessary, but would be nice 👀

That would be brilliant!

I've sorted the WIFI issues so it erases the ESP by default as you only really need to use my website once & just in the process of sorting the firmware link.

Many Thanks

ALD-Models commented 4 weeks ago

I'm not quite sure how to make the link Is their a easy method to do this?

I'm not aware of a direct call for the latest release, but I used some script or backend-code in other projects. For example:

# Fetch the latest release information
latest_release=$(curl -s https://api.github.com/repos/prusa3d/Prusa-Firmware-ESP32-Cam/releases/latest)

# Extract the download URLs
download_urls=$(echo $latest_release | grep -oP '"browser_download_url": "\K(.*)(?=")')

# Download each asset
for url in $download_urls; do
    wget $url
done

Within the for-loop you could filter only the .bin files. Not the most elegant solution, but should work 🫣

I've managed to get a workflow working so it retrieves and updates the bin files and version code on the manifest. When you release an update i'll just have to start the workflow and it should be all automated from their!

Zero-Circle commented 2 weeks ago

What a fantastic update for this project thanks for building this tool. I tried to do it myself as I know my way around it with WLED, not a code wizard though. This tool is fantastic hopefully this is built into this repo as the default install method. Thanks for making it @ALD-Models.

johnyHV commented 2 days ago

Hello @ALD-Models I have new challenge. It is possible added multi board compatibility ?

ALD-Models commented 2 days ago

Hi @johnyHV

Do you mean like different bin files for the different ESP boards?

That would definitely be possible! Might be able to get it done within a few days.

I've just got an error email from the workflow because the new releases have the bin files in zips now so i need to work on a way to unzip and extract the bin for each of the boards in the workflow. This would hopefully be resolved soon!

Jake

johnyHV commented 2 days ago

Hello @ALD-Models

Yes, I means different bin files for the different ESP boards.

Yes, unfortunately, currently the firmware for each board is packed in a ZIP archive. This makes it more organized and easier to identify which file belongs to which board. At the same time, there aren't that many bin files in the release, so the release is more organized.

ALD-Models commented 2 days ago

Hi @johnyHV

I would get that sorted

Would the zip file for the individual boards be named the exact same per release?

Just means that the workflow can easily identify the bin files per board

ALD-Models commented 2 days ago

That should work now!

If anyone can test it and give me feedback that would be really appreciated!

Also just a side note that the repository automatically syncs to the latest release at 00:00 meaning that when an update has been pushed it wont be synced until that time.