mirror of
https://github.com/dasrecht/deye-firmware.git
synced 2025-12-10 07:45:37 +02:00
adding digest files and solis ginglong firmware https://www.photovoltaikforum.com/thread/191598-fw-update-offline-deye-sun600g3-eu230-und-baugleiche/?postID=2974824#post2974824
This commit is contained in:
BIN
0_D0002_18/MW3_15U_5406_1.47.bin
Normal file
BIN
0_D0002_18/MW3_15U_5406_1.47.bin
Normal file
Binary file not shown.
1
0_D0002_18/MW3_15U_5406_1.47.bin.DIGEST
Normal file
1
0_D0002_18/MW3_15U_5406_1.47.bin.DIGEST
Normal file
@@ -0,0 +1 @@
|
||||
102c8a22c5d5348d2c336486ae81ead386b307e51ae8369e45c15c153eece3bb MW3_15U_5406_1.47.bin
|
||||
BIN
0_D0002_18/MW3_15U_5406_1.49R.bin
Normal file
BIN
0_D0002_18/MW3_15U_5406_1.49R.bin
Normal file
Binary file not shown.
1
0_D0002_18/MW3_15U_5406_1.49R.bin.DIGEST
Normal file
1
0_D0002_18/MW3_15U_5406_1.49R.bin.DIGEST
Normal file
@@ -0,0 +1 @@
|
||||
46f0c17a9e75ee98ae1941b8f7a9b9f264915f87d71e119ce50a5792ab3c6c7f MW3_15U_5406_1.49R.bin
|
||||
1
0_D0002_18/MW3_15_0501_1.21.bin.DIGEST
Normal file
1
0_D0002_18/MW3_15_0501_1.21.bin.DIGEST
Normal file
@@ -0,0 +1 @@
|
||||
c43a676513cd40874709ea8f3fc02905148a889247fd228a1cee7bd37930db68 MW3_15_0501_1.21.bin
|
||||
1
0_D0002_18/MW3_15_0501_1.23.bin.DIGEST
Normal file
1
0_D0002_18/MW3_15_0501_1.23.bin.DIGEST
Normal file
@@ -0,0 +1 @@
|
||||
aba5ff99c67d47a9b230c3662405204d1c03ee6dbdb926147fe6389e3c6be5e7 MW3_15_0501_1.23.bin
|
||||
30
README.md
30
README.md
@@ -5,7 +5,7 @@
|
||||
|
||||
If you brick your device that's your problem. ;)
|
||||
|
||||
Installed on a Deye SUN600G3-EU-230 and it worked fine.
|
||||
Installed on a Deye SUN600G3-EU-230 and it worked fine (5406 in the filename).
|
||||
|
||||
My feeling is that the firmware files and IP info can be released out into the wild as it's not hidden and the fact
|
||||
that there is specifically no HTTPS connection used would suggest that the manufacturer does not care about securing those files.
|
||||
@@ -20,11 +20,21 @@ It looks like behind this IP is the firmware update Server of Deye. At least I g
|
||||
Based on a few forum entries and the answer from Deyes support the Inverters should auto-update to the latest version
|
||||
when being up and running for 30 minutes.
|
||||
|
||||
## Filenames
|
||||
|
||||
| Filename | Brand |
|
||||
|----------|----------------|
|
||||
| 0501 | Solis Ginglong |
|
||||
| 5406 | Deye |
|
||||
|
||||
## URL Structure
|
||||
|
||||
```bash
|
||||
http://47.254.36.66/0_D0002_18/MW3_15U_5406_1.471.bin
|
||||
http://47.254.36.66/0_D0002_18/MW3_15U_5406_1.49R.bin
|
||||
http://47.254.36.66/0_D0002_18/MW3_16U_5406_1.53.bin
|
||||
http://47.254.36.66/0_D0002_18/MW3_15_0501_1.21.bin
|
||||
http://47.254.36.66/0_D0002_18/MW3_15_0501_1.23.bin
|
||||
```
|
||||
|
||||
You can use the DIGEST files to verify that those files here are the same as the ones on the server.
|
||||
@@ -34,6 +44,24 @@ shasum -c MW3_15U_5406_1.471.bin.DIGEST
|
||||
shasum -c MW3_16U_5406_1.53.bin.DIGEST
|
||||
```
|
||||
|
||||
or verify all DIGEST files
|
||||
|
||||
```bash
|
||||
for filename in *.bin.DIGEST; do
|
||||
shasum -a 256 -c $filename
|
||||
done
|
||||
```
|
||||
|
||||
Create your own DIGEST files
|
||||
|
||||
```bash
|
||||
for filename in *.bin; do
|
||||
# create a file called $filename.DIGEST
|
||||
shasum -a 256 $filename > $filename.DIGEST
|
||||
done
|
||||
```
|
||||
|
||||
|
||||
## Call for help
|
||||
|
||||
If you have more information or insights into the firmware update process, alternative URLs or other information let me know.
|
||||
|
||||
Reference in New Issue
Block a user