-
Notifications
You must be signed in to change notification settings - Fork 132
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.12.1 Adding Input2 to Shelly 1PM #1417
Comments
Is this the same device? The second input comes from addon detection. Something goes wrong here or do you have an addon? I think it is shaky and then primary/non primary switchingleads to what you see. |
I don’t have any add on on this ones. I have around 20 1PM and all except one is showing the input2. The only one that doesn’t shows the input2 actually doesn’t have anything connected to the sw. Sorry for the screenshot. Indeed in the images they are not the same. But same behaviour on both. |
Mhh it seems that addon detection does not work on 1pm the way it does on others. Seems like the pin is tied down in the device. We will have to skip the second check then for 1pm. |
First: Can you flash this please: this should make the problem go away. Secondly, can you please tell me the output of: curl [ip of device]/rpc/GPIO.Read -d '{"pin":3}' |
Yes. That version solve the problem. The output of the curl command is the following. { |
Ok thanks for your input. |
If you need that I do some tests let me know. |
I am experiencing this exact issue on a shelly plus1 and could use some assistance removing the rogue input #2. I am a novice user and will need complete steps to fix this. Thanks Joe |
I tried to flash the above version on my Shelly Plus 1i4 and I get a message that says: Host: http://192.168.1.10 Please advise if I am using the correct file for my Shelly device. |
When you're on Mac the zip file auto extracts. To avoid this use secondary click / right click download file as. |
Also this file is for 1PM. Which devices is it that fails for you? |
Markus,I have the Shelly plus 1 i4. I found a different file through the forum that wanted to upload, but it would stop saying the file was too large. If you could email the correct file id greatly appreciate it.
![Screen Shot 2025-01-07 at 9 30 24 AM]
![image](https://github.com/user-attachments/assets/25d88e85-9249-4a6c-bd6b-82d4ef2adf31)
Markus Kirberg ***@***.***> wrote:
Also this file is for 1PM. Which devices is it that fails for you?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Yes I did this but my Shelly doesn’t like that file. Believe it is incorrect for the Plus1 i4 model I have.
Markus Kirberg ***@***.***> wrote:
When you're on Mac the zip file auto extracts. To avoid this use secondary click / right click download file as.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Markus, |
More info. I eventually was able to load newer versions of the Plus1 firmware. I uploaded 2.13.2 and 2.13.0. In both cases the input #2 was gone but reappeared. Once it stayed gone for awhile until i opened up home assistant, which i use for other devices. I'm wondering if it is triggering something in this Shelly. |
Ok so again: which device is this? You one time wrote Plus1? one time i4? what is it now? Then I can try to work around this bug... |
It’s a plus1. Sorry for the confusion. Found the right file on your repository but it fail to up load because it’s too big. 2.13.0, 2.13.1 etc will upload and flash but seem to be much smaller files. Unfortunately they don’t fix my problem. Sent from my iPhoneOn Jan 7, 2025, at 2:49 PM, Markus Kirberg ***@***.***> wrote:
Ok so again: which device is this? You one time wrote Plus1? one time i4? what is it now?
Then I can try to work around this bug...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
ok, then please read the upgrade notes here: |
Ok so if I read this correct. I have to revert to 1.3.1 stock, then update stock to like 1.4.0, or whatever is current, then I can upload the 2.12.1 update? And what does this mean? “Please still only do this if you accept the risk to loose your config in case you need to reset”Whatever I do I don’t want to brick it or have to pull it out of the wall. Anything else I can handle On Jan 7, 2025, at 3:56 PM, Markus Kirberg ***@***.***> wrote:
ok, then please read the upgrade notes here:
https://github.com/mongoose-os-apps/shelly-homekit/releases/tag/2.13.3
this will explain it.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
Could someone please provide instructions to update my Shelly Plus1 to 2.12.1? I have reverted my relay to stock, but have not figured out how to flash anything other than the latest OTA update. |
Just follow the linked guide for OTA to latest 2.13. When this is done you can use webinterface to upload any zip file. |
Markus,
The problem is that it the web interface won’t allow a file older than 2.13.0. I can upload 2.13.0, 2.13.1 etc. I’m trying to fix the input#2 error mentioned in #1417 and according to your earlier work i need to use version 2.12.1.
Look i can tell you are very busy, but i’m trying to go backwards to 2.12.1 and I suppose because the upgrade path has been broken what you are saying below doesn’t work.
This release deliberately breaks the upgrade path from Shelly HomeKit 2.12.X for any Plus Devices (those are: +1, +1PM, +i4, +2PM, +RGBWPM, +PlugS). The reason for this is to support direct upgrade from newest stock firmware (1.4.X), that uses a changed partition layout.
Thank you,
Joe
… On Jan 13, 2025, at 12:46 PM, Markus Kirberg ***@***.***> wrote:
Just follow the linked guide for OTA to latest 2.13. When this is done you can use webinterface to upload any zip file.
—
Reply to this email directly, view it on GitHub <#1417 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BCO4RRDQVVHLZHT4LHKXPQ32KP3YFAVCNFSM6AAAAABK2TR2J2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBXG43TSMBUHE>.
You are receiving this because you commented.
|
Hi,
I just updated all my Shellies to this new version, and some of the Shelly 1PM, created an additional input. Is this as intended?
The text was updated successfully, but these errors were encountered: