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
shelly plus 1PM stuck in 1.1.0 #1351
Comments
I have the same issue. I cannot downgrade nor flash any other firmware on the device. |
My positive Update on this one: |
@silverter i may be going crazy but I don’t see a file to download or url to firmware via the link in your post. |
This is the direct link to the 0.14.x. Firmware for the Shelly Plus 1PM: https://shelly-infra1-eu.shelly.cloud/stable-firmware/Plus1PM/fw-signed.zip You should be able to see that in the link I provided... there are many other Firmware for the Gen2 devices. |
Unfortunately this downgrade link is not the solution (anymore?). I tried to downgrade my Shelly 1 Plus. https://shelly-infra1-eu.shelly.cloud/stable-firmware/Plus1/fw-signed.zip But, thanks to #1347, I could downgrade my Shelly 1 Plus to firmware V1.0.8. This firmware still supports the update to the respective Apple Home firmware |
I had that same issue, that 's why I wrote "after many attempts". |
@silverter YES! it worked! thanks a lot! I made what you have suggested to downgrade a shelly Plus 1PM stuck in firmware version 1.1.0 to 0.14.1 firmware version, and than flashed it via OTA to Shelly homeklit 2.12.2 firmware.
3 When the updating firmware process bar showed 95%, and right after the Shelly device led stopped blinking, I POWERED OFF THE DEVICE cutting the main power to Live and Neutral entries.
NOTE 1: TRY AT YOUR OWN RISK (AS I DID ;) ) NOTE 2: I THINK this trick should work with any shelly device stuck on 1.1.0 fw (just copy&past the right firmware link from firmware section!)... in the waiting of an official updating bugfix for this 1.1.0 firmware bug that I think Allterco itself will/should make in the near future (or at least I hope so) NOTE 3: I really love the shelly homekit firmware and I have about 50 shelly devices running it without any problem for years... how I wish it will continue to be developed and maybe ported to the new mini and plus gen3 devices! Best Regard Lalo |
@lalolerry |
does not work for me. I guess the "new" shelly that come with a strange built firmware dont work |
works for me .. thanks a lot! |
Note, you DO NOT need to pull the power. You can just quickly click the "Reboot" button when you're ~95% through the downgrade. I'm glad this worked out for me, since my Shelly is already installed inside of a junction box. And...I didn't feel like flipping breakers. |
@lalolerry Ive tried this methood 20 times now trying to time it. |
Hi @z0lle, Last solution, flash it with old firmare non via OTA but via UART and PINOUT. Not so easy I know. |
The 1.2.0 firmware is the absolute worst that I have seen on a Shelly 1PM! Loosing network connection after a couple of hours all the time, no problem until the 1.1.0 FW. |
I have the same problem with my 1PM and 2PM. Do You have any instruction how to go back to 1.1.0? |
There is no list of available FWs for Gen2 devices, 1.10 is not available, but for 1PM you can find the 1.08 FW here: #1347 (comment) For 2PM, you can find 0.14 FW (its from 2023, dont get fooled about the version naming) here: https://www.shelly-support.eu/forum/thread/21939-downgrade-links-to-0-14-x/ To downgrade, login to the shelly, go to settings, firmware and upload the zip. Good luck |
I also had this issue, but my Shelly +1PM was on firmware version 1.2.2 and couldn't downgrade to 0.14.1. -> So I edited the zip file and tried to update / downgrade the Shelly and surprisingly it worked. Don't blame me if your Shelly is bricked afterwards. I apologize for my broken or not perfect english, since english is not my first language! If you encounter any problems, maybe try sharing your log files here? Then maybe somebody can help? Down below I have attached the update file I used to update my Shelly +1PM. |
Can you explain more detailed what is changed in this file? |
Sure I can try. I was trying to flash the old firmware (0.14.1) and got this error in the logs: So I did a quick google search and found this issue on the Tasmota GitHub: This User also mentioned how to fix this error:
tasmota/mgos32-to-tasmota32#31 (comment) So I opened WinRAR and drag and dropped the files one by one just like they were specified in the manifest.json and uploaded the file into the Shelly Web Interface. Unfortunately that didn't work, I got following error I scrolled down a bit and found this
tasmota/mgos32-to-tasmota32#31 (comment) So I drag and dropped the files one by one into WinRAR again, but this time specified that the files compression method should be "store". I hope that helps. Sorry if this is hard to read/understand since English is not my first language! |
@TheGHubBoy thanks for your explanation (which is understandable perfectly) and the bravery to try it out :) It can confirm that downgrading to 0.14 using your fixed FW file worked for me! Afterwards, I was able to upgrade to the HomeKit firmware using the regular OTA process. |
@TheGHubBoy Thank you! This has been the only solution to work for me. |
Because this firmware will not be updated anymore, I'm using HAA firmware that works with Plus 1PM. I followed these steps to flash Shelly for Homekit: https://www.youtube.com/watch?v=06YHkRkwJE4 |
@TheGHubBoy
That worked beautifully for me :) Now the next issue is, where do i find the powerconsumption in the homekit app? ^^ Edit So aparently the Apple Home app dont have this function. That is very suprising tbh. How can such a basic function not be supported? Its the most important function for me with the Shelly plug. |
Edited fw worked for me too. Thank you 🫶🏻 |
If you want, you can try HAA firm. I flashed my Shelly Plus 1PM and it works like a charm. There is a new video with subs explaining all: |
please help me downgrade. i am stuck and the buttons take no action when trying to downgrade firmware. i tried on multiple browsers
anyone have ideas?
The text was updated successfully, but these errors were encountered: