Skip to content
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

Open
kloibs opened this issue Oct 26, 2024 · 30 comments
Open

2.13.0 Upgrade for Plus Devices #1547

kloibs opened this issue Oct 26, 2024 · 30 comments

Comments

@kloibs
Copy link

kloibs commented Oct 26, 2024

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!
IMG_0138

@markirb
Copy link
Collaborator

markirb commented Oct 26, 2024

Looks more Like Browser Cache? What happens if you just refresh?

@kloibs
Copy link
Author

kloibs commented Oct 26, 2024

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 👍🏼

@markirb
Copy link
Collaborator

markirb commented Oct 26, 2024

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

@kloibs
Copy link
Author

kloibs commented Oct 26, 2024

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 👍🏼

@markirb
Copy link
Collaborator

markirb commented Oct 26, 2024

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 😀

@kloibs
Copy link
Author

kloibs commented Oct 26, 2024

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 🥳

@metallus42
Copy link

metallus42 commented Oct 26, 2024

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?

@kloibs
Copy link
Author

kloibs commented Oct 26, 2024

@markirb I can try with my other Plus series devices if you think this is a Plus 1PM specific issue, let me know!

@markirb
Copy link
Collaborator

markirb commented Oct 27, 2024

I currently do not think it is a general problem.

Might be related to:
#1433

I think it can only be related to one file.
Before you do anything on a new devices can you send me the response of (this does contain private data, you can send it via email in my GitHub profile):

curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}'

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.
It still might be available to a Reset via url (on Stock):

curl http://a.b.c.d/RPC/Shelly.FactoryReset

@metallus42
Copy link

metallus42 commented Oct 27, 2024

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.
Bildschirmfoto 2024-10-27 um 22 45 01

curl http://a.b.c.d/RPC/Shelly.FactoryReset sadly does not work. It gives
Not Found% .

curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}' gives me no output on all of my devices running Shelly HomeKit. I tried with all my +1 and it worked for none of them.

Update:
Reseted another one of the +1 (Shelly B) via the Button and then again via the Web UI, then connected back to my WiFI. Homekit Config is lost but I now have the output of curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}'. I have sent it per email!
This time the reset worked and I was able to update stock from 1.3.3 to 1.4.4 and then update to shellyhomekit 1.13.

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...

@kloibs
Copy link
Author

kloibs commented Oct 27, 2024

I currently do not think it is a general problem.

Might be related to: #1433

I think it can only be related to one file. Before you do anything on a new devices can you send me the response of (this does contain private data, you can send it via email in my GitHub profile):

curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}'

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. It still might be available to a Reset via url (on Stock):

curl http://a.b.c.d/RPC/Shelly.FactoryReset

I should have some time to test it this week. Cheers!

@markirb
Copy link
Collaborator

markirb commented Oct 28, 2024

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. Bildschirmfoto 2024-10-27 um 22 45 01

curl http://a.b.c.d/RPC/Shelly.FactoryReset sadly does not work. It gives Not Found% .

I figured out the RPC has to be lower case so curl http://a.b.c.d/rpc/Shelly.FactoryReset ?

curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}' gives me no output on all of my devices running Shelly HomeKit. I tried with all my +1 and it worked for none of them.

That is really strange. Also that this should work after reset....
Does
http://a.b.c.d/rpc/FS.List work?

Update: Reseted another one of the +1 (Shelly B) via the Button and then again via the Web UI, then connected back to my WiFI. Homekit Config is lost but I now have the output of curl http://a.b.c.d/RPC/FS.Get -d '{"filename": "conf9.json"}'. I have sent it per email! This time the reset worked and I was able to update stock from 1.3.3 to 1.4.4 and then update to shellyhomekit 1.13.

So maybe in the current state of my and @kloibs (?) shellys this file is defective or somehow not correcty accessible?

Yes this is somehow likely. We have to find out why. I think it is also linked to the other issue I already linked

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...

@metallus42
Copy link

I figured out the RPC has to be lower case so curl 'http://a.b.c.d/rpc/Shelly.FactoryReset' ?

Shelly A: {"code":500,"message":"unauthorized"}%

Does 'http://a.b.c.d/rpc/FS.List"' work?

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?
Doing it without:
Shelly A: {"code":404,"message":"No handler for FS.Lis"}
Shelly B: '{"code":404,"message":"No handler for FS.Lis"}'
Shlly C (Untouched ShellyPlus1 running Shelly Homekit 2.12.2 for months): '{"code":404,"message":"No handler for FS.Lis"}'

Let me know in case I should try anything else :)

@markirb
Copy link
Collaborator

markirb commented Oct 28, 2024

Typo...

@lindingerm
Copy link

Same Problem here.

1 ShellyPlus1 worked.
The other ShellyPlus1 hangs after "Revert to Stock 1.3.3". Just the "Connecting to Shelly" screen.

With http://a.b.c.d/rpc/Shelly.FactoryReset the same as above: {"code":500,"message":"unauthorized"}

@tothbe
Copy link

tothbe commented Oct 30, 2024

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.

@lindingerm
Copy link

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.

@markirb
Copy link
Collaborator

markirb commented Oct 31, 2024

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.

Exactly

@markirb
Copy link
Collaborator

markirb commented Oct 31, 2024

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.

Yet another case.
You did try to factory reset?
Do you have any logs?

@lindingerm
Copy link

I tried a factory reset, different browsers and multiple times to update. It comes always back to the stock webUI.
As this is a critical device for my smart home, i have now switched to HomeAssistant.

@metallus42
Copy link

metallus42 commented Oct 31, 2024

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!

  1. Use reset Button (not the one under the homekit tile, the one in the System tile)
  2. Connect to AP, 192.168.33.1, reconfigure your WiFi
  3. Go to whatever IP your shelly now has in your LAN
  4. Firmware tile -> Revert (get stuck at 90% but give it like 30sec on it and then reload)
  5. Reload and the shelly is now on stock FW
  6. Update stock FW to latest
  7. http://A.B.C.D/ota?url=http://shelly.rojer.cloud/update it
  8. Reload and change the Name back to what it was before. For me Homekit was connected still.
  9. Setup your Password and the switch specific setings again (if u wish so)

This makes the process a bit tideous but possible w/o phyiscal interaction. I wonder if this could be automated?

@markirb
Copy link
Collaborator

markirb commented Oct 31, 2024

Same Problem here.

1 ShellyPlus1 worked.

The other ShellyPlus1 hangs after "Revert to Stock 1.3.3". Just the "Connecting to Shelly" screen.

With http://a.b.c.d/rpc/Shelly.FactoryReset the same as above: {"code":500,"message":"unauthorized"}

Did you have a password set?

@johannesvogel
Copy link

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.

@lindingerm
Copy link

Did you have a password set?

No password.

@markirb
Copy link
Collaborator

markirb commented Nov 1, 2024

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"}'

@tschutschi
Copy link

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!

@markirb
Copy link
Collaborator

markirb commented Nov 1, 2024

So there seems to be another case:

  1. Revert to 1.3.3 works
  2. Update to 1.4.4 works
  3. Upgrade to Shelly Homekit fails.

In this case a simple reboot was observed to help.
However this is completely different than the "Connecting to shelly" issue

@datadorf
Copy link

datadorf commented Nov 4, 2024

Bildschirmfoto 2024-11-05 um 00 04 10 Bildschirmfoto 2024-11-05 um 00 02 59 I have the same issue, after reverting I get this "Connecting to Shelly" screen with my shelly 1plus

@datadorf
Copy link

datadorf commented Nov 6, 2024

I could not revert to stock firmware, with pressing the reset button, so I installed a new shelly plus 1 now.

@markirb
Copy link
Collaborator

markirb commented Nov 6, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants