Closed hdfox closed 7 months ago
Need to leave this open. Don't have a PM Mini Gen3 for doing tests. Device can't be simulated on usual c3 dev boards since 8MB flash is needed.
Same except different error message
After updating the shelly to 1.2.2 the error changed:
Please try https://github.com/tasmota/mgos32-to-tasmota32/releases/download/v13.4.1/mgos32-to-tasmota32-MiniPMG3.zip If this version does not work i am out of ideas. Just to be shure. You have downloaded the zip and drag and drop them in the firmware update area?
I am sorry at least on my part it is user error I retried with v13.4.0 mgos32-to-tasmota32-MiniPMG3.zip and it worked. Before I used mgos32-to-tasmota32-PlusPMMini.zip I did not consider the other since there was no plus in the name.
So I sadly can't tell you if 13.4.1 works :D
Ok so this is not the end of it however. Flashing the mentioned image worked. I used autoconfigure but again for PlusPMMini (since I didn'd find MiniPMG3) That "worked" it rebooted but only displayed the temperature sensor. So autoconfigure again this time something with PMG3. But now the device is completely dead, no led no wifi ap no nothing.
I am usually not that inept with tasmota, but this hole mini G3 stuff is somewhat confusig :D
I have now tried with Shelly PM mini Gen3 and version 13.4.1 but the same error occurs
Without the device i can't investigate.
I managed to get the device working again, by flashing it wia wire. Autoconfig also worked this time.
Anything I can dump you /log output from the device that would help you?
@Qowy Full serial log when Shelly firmware is running (updated to latest version) and convert package.zip is applied may help to get an idea what goes wrong
@Jason2866 Can I revert to stock shelly? I can get the Image from https://[updates.shelly.cloud/update/MiniPMG3](https://updates.shelly.cloud/update/MiniPMG3) but can I flash that back? If so how? The web installer only takes a single factory image.
@Qowy Not possible to build a full identic firmware which has been on the device from the update package. And the rebuild from the update package is a manual putting together of "the pieces".
Ok then I guess I will leave it be for now. Especially since your method worked for me, I just bricked the bootloader but I have a feeling that was my own fault, from flashing the wrong image /autoconfigure first). So I could never reproduce hdfox issue in the first place (apart from using the wrong image)
@Qowy Thx for Trying!
@hdfox Can you please try following. Download the Shelly update package for your device from here. https://updates.shelly.cloud/update/MiniPMG3 Provide the update file to the device by drag & drop in the update are. Start update. If device does the update, wait until finished and the Shelly page is back. Do the update again. Yes a second time. When the device is back online it is fully recovered to Shelly firmware. Now do provide the convert package in the drag&drop update area. Follow exactly the described steps.
Thank you so much. it worked, now I can use tasmota on the miniPMG3
@Qowy: some questions regarding flashing via serial:
Thx!
@jotwg It is a PM mini Gen3 without relay. However the pinout seems to be identical to other mini devices (with or without Gen3) I used the pinout from here: https://devices.esphome.io/devices/Shelly-Plus-PM-Mini
I activated the mode by holding down a Wire on the marked GPIO0 and GND during power on
@Qowy Did you first flash mgos32-to-tasmota32-MiniPMG3.zip over Serial and dollowed on with auto-config and Partition Wizard Or did you flash Tasmota directly by using Tasmota-Web-Flasher or something similar?
@Bodengriller As far as I remember the Serial flash was done using Web Flasher
The ota flash starts but then it is almost immidiately stops without any error except one in the console: