-
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.13.4-alpha2@2PMGen3: Calibration not working #1617
Comments
Hi, Most likely that the power measurement channels are swapped in code. Can you try to set your Shelly to normal mode. Then you see direct power readings per channel. If you switch on channel 1 you should read power on channel 1, and so on. This would help to see if things are right or wrong |
With "normal mode" you don't mean "Mode" = "Switch" or something? You likely mean shifting back to stock-firmware, don't you? Just quickly want to check before I do a re-config :) If so: you just want me check in the stock app whether channel-1-switching appears in channel-1-power-readings, did I get that right? PS: Prior to that I used beta firmware 1.5.0 and calibration went fine and the power consumption was displayed in realtime. And btw: When the shutter reached it's top position the power consumption dropped to 0 Watt |
I do mean switch mode yes. See here for similar problem on first hw revision with screenshots of what to look for: |
Ah ok. Thank you for the information. This means that the PM chip could not be initialized. I will have to double check the code.... |
Hi there,
I am new to Shelly and Github, please be patient :)
My Shelly2PMGen3 is flashed with the brand new v2.13.4-alpha2, build 20250121-122123. After updating and reseting I did the following:
I was able to re-create this issue several times.
Any idea?
Anything I can help you with?
PS: When calibrating the shutter is always driving up first, am I right? Has the shutter to be in a specific position before I start the calibration? Does it need to be at the very lower end? Or somewhere in the middle?
The text was updated successfully, but these errors were encountered: