-
Notifications
You must be signed in to change notification settings - Fork 130
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
2.13.0 Upgrade for Plus Devices #1547
Comments
Looks more Like Browser Cache? What happens if you just refresh? |
Nothing happens. Unfortunately the only way to proceed was for me to physically access the Shelly and reset it using the little button on the back. This was the case on two separate Shelly Plus 1PMs 👍🏼 |
Ok strange then. I mean it sounds like there's some part of your config that stock does not like. If you reset in Shelly HomeKit before reverting then it should not happen. But then you loose your config... but this avoids the physical interaction |
It’s happened on two separate relays so far, so could be my config potentially, yes. Either way when it comes to having to choose between taking all of my relays out of the wall to update them or reconfigure my automations, less than ideal. Just wanted to make it known 👍🏼 |
Yeah. Let's see if others face this as well. I guess we cannot do much about it though. From the issues somehow +1PM seems to be the most picky... I wonder why 😀 |
I’ve got a mix in my setup: 2.5, +2PM, 1, +1, 1PM, +1PM, and other than what was mentioned in the release notes the update was fine with everything else 🥳 |
Same here! +1 Didnt reset on the HomeKit OS as to not loose my config and now I am stuck at the "Connecting Screen". I rlly dont want to pull it out of the wall and press the reset button... but I guess thats my only option... right? |
@markirb I can try with my other Plus series devices if you think this is a Plus 1PM specific issue, let me know! |
I currently do not think it is a general problem. Might be related to: I think it can only be related to one file.
I can see if anything is strange there. Then you might try to do the process, to tell me if it does work or not. Make it with a Shelly that is easily accessible incase you need to access It physically. If it does not work I would also be interested to see any error messages in the browser console. I mean the Shelly seems to be in a state where it does not seem to give the Webif.
|
Hi @markirb, the First +1 (Shelly A) I did try to update was not accessible today. Not even conneted to my WiFI anymore. Maybe it timed out and shut down? I cycled the power and am now at the point I was when I made my first comment here.
Update: So maybe in the current state of my and @kloibs (?) shellys this file is defective or somehow not correcty accessible? Ill try to reset one via the web UI only since that could give us a way to solve the issue without needing physical access... |
I should have some time to test it this week. Cheers! |
I figured out the RPC has to be lower case so
That is really strange. Also that this should work after reset....
Yes this is somehow likely. We have to find out why. I think it is also linked to the other issue I already linked
|
Shelly A:
Just making sure: Doing it with the " at the end always brings me in dquote no matter what IP I use. So that was a typo? Let me know in case I should try anything else :) |
Typo... |
Same Problem here. 1 ShellyPlus1 worked. With http://a.b.c.d/rpc/Shelly.FactoryReset the same as above: {"code":500,"message":"unauthorized"} |
I am a bit lost with this update. I am using Gen 1 Shelly 1 devices. As I read this back to stock and upgrade thing is only valid for Plus devices. So for Gen 1 Shelly 1 I can just simply upgrade them with upgrade button? Thanks for any feedback. |
After i reseted my second ShellyPlus1 the Update worked. Now with my third ShellyPlus1 th Problem changed: The Shelly is at original firmware v1.4.4 but cant update to shelly-homekit firmware it boots always back to stock webUI. |
Exactly |
Yet another case. |
I tried a factory reset, different browsers and multiple times to update. It comes always back to the stock webUI. |
I have reseted and updated three Plus1 (Shelly C and others) successfully without needing physical access AND W/O needing to reconfigure it in Homekit!
This makes the process a bit tideous but possible w/o phyiscal interaction. I wonder if this could be automated? |
Did you have a password set? |
Also happened to both of my Shelly Plus1. Had to reset by getting them out of the wall, since the other reset methods on the shelly website (turning off power 1 time and pressing switch 5 times / turning off power 5 times) did not work either. Was then able to upgrade the Shelly firmware and then install the shelly-homekit update. |
No password. |
Please anyone if we want to have the reason for this give me the content of this call before performing any updates. Send content via email in my GitHub profile. curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}' |
Done! |
So there seems to be another case:
In this case a simple reboot was observed to help. |
I could not revert to stock firmware, with pressing the reset button, so I installed a new shelly plus 1 now. |
I think the general problem is that the Stock firmware thinks that we are not authorized. For every call it seems to return 500. Again, it thinks that because of some string in the file conf9.json which some of you have on your Plus devices |
Hi there,
I‘m having trouble updating my Plus devices to 2.13.0. Yes, I read the release notes regarding reverting to stock first, but unfortunately that’s where my issue lies.
When I use the revert to stock option in the UI my Shelly will reboot and show the following screen indefinitely (see attached)
I am unable to add the Shelly in the Shelly app or flash it back to Shelly HomeKit firmware without physical access to the relay itself.
Is there something wrong with the revert to stock UI button? I prefer to keep all of my Shellys up to date but if that’s the case then I’ll avoid it for as long as possible.
Thank you to everyone for the revived development!
The text was updated successfully, but these errors were encountered: