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.

Sign up for GitHub

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

Jump to bottom

Shelly +2PM (HW v1) Powermeasurement not working #1424

Open
DanielZornhagen opened this issue Jul 23, 2024 · 22 comments
Open

Shelly +2PM (HW v1) Powermeasurement not working #1424

DanielZornhagen opened this issue Jul 23, 2024 · 22 comments
Labels
confirmed-bug confirmed bug

Comments

@DanielZornhagen
Copy link

The Shelly Plus 2PM has been updated to the HomeKit version and defined as a Roller Shutter. During calibration, it only runs for a maximum of 5.09 seconds before ending the calibration. The maximum distance the shutter can move is about 30% of the total travel distance. New calibrations slightly change the maximum runtime. The same error occurs even after resetting and updating again. Turning off the power for several minutes does not affect the calibration time either. The input mode was set to separate - momentary, as it involves two push buttons. Version 2.12.1.
@markirb
Copy link
Collaborator

markirb commented Jul 23, 2024

Can you post logs please?

@DanielZornhagen
Copy link
Author

Where can I get the logs from?

@santigvz
Copy link

Exactly the same error here and also ir afecta to the wall switch which now can not move more than the 30%…

Also there is a reported error that does not allow to come back to the custom FW. Help appreciated!

@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 1, 2024

This issue is stale because it has been open 3 weeks with no activity. Comment or this will be closed in 1 week.

@github-actions github-actions bot added the stale OP has not replied, gone stale, ready to close. label Sep 1, 2024
@DanielZornhagen
Copy link
Author

the problem still exists. Here is the log file:

80260214 shelly_debug.cpp:231 No log file, sending new entries
80267279 mgos_http_server.c:180 0x3ffce4d4 HTTP connection from 192.168.189.14:51103
82014535 shelly_main.cpp:483 Up 82.00, HAP 0/1/16 ns 1, RAM: 209300/196404; st 56; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
90014553 shelly_main.cpp:483 Up 90.00, HAP 0/1/16 ns 1, RAM: 209300/196404; st 55; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
96527903 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
96834580 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
98014520 shelly_main.cpp:483 Up 98.00, HAP 0/1/16 ns 1, RAM: 209300/196404; st 55; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
101751706 W (102397) wifi:idx:1 (ifx:0, 52:e6:36:4f:8e:51), tid:6, ssn:2, winSize:64
104616618 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
105742524 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
106014800 shelly_main.cpp:483 Up 106.00, HAP 0/1/16 ns 1, RAM: 209048/196404; st 55; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
106473904 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
107490622 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
108514786 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
109536180 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
110560754 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
111683082 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
112516311 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
113535389 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
114014606 shelly_main.cpp:483 Up 114.00, HAP 0/1/16 ns 1, RAM: 209048/196404; st 56; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
114558354 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
115489630 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
116494826 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
117518404 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
118557664 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
119772962 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
120488634 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
121718412 mg_rpc.c:315 Shelly.SetState via WS_in 192.168.189.14:51101
121726757 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
121796384 shelly_hap_window_c:330 WC 1: State: idle -> precal0 (0 -> 10)
121895992 shelly_hap_window_c:450 Begin calibration
122038667 mgos_sys_config.c:323 Saved to conf9.json
122044209 shelly_output.cpp:64 Output 1: off -> on (precal0)
122050106 shelly_hap_window_c:330 WC 1: State: precal0 -> cal0 (10 -> 11)
122069935 shelly_main.cpp:483 Up 122.06, HAP 0/1/16 ns 1, RAM: 207500/196404; st 56; 4.1: c:0 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
122395456 shelly_hap_window_c:466 WC 1: P0 = 0.000
123195393 shelly_hap_window_c:466 WC 1: P0 = 0.000
123408920 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
123995472 shelly_hap_window_c:466 WC 1: P0 = 0.000
124758312 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
124795554 shelly_hap_window_c:466 WC 1: P0 = 0.000
125507385 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
125595587 shelly_hap_window_c:466 WC 1: P0 = 0.000
126395512 shelly_hap_window_c:466 WC 1: P0 = 0.000
126448952 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
127096320 shelly_output.cpp:64 Output 1: on -> off (cal0)
127102330 shelly_hap_window_c:330 WC 1: State: cal0 -> postcal0 (11 -> 12)
127196948 shelly_hap_window_c:330 WC 1: State: postcal0 -> precal1 (12 -> 13)
127295660 shelly_output.cpp:64 Output 2: off -> on (precal1)
127301567 shelly_hap_window_c:330 WC 1: State: precal1 -> cal1 (13 -> 14)
127566613 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
127895503 shelly_hap_window_c:497 WC 1: P1 = 0.000
128476554 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
128695396 shelly_hap_window_c:497 WC 1: P1 = 0.000
129495447 shelly_hap_window_c:497 WC 1: P1 = 0.000
129508063 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
130014481 shelly_main.cpp:483 Up 130.00, HAP 0/1/16 ns 1, RAM: 209436/196404; st 56; 4.1: c:0 mp:0.00 ip:5.00 mt_ms:5090 cp:49.27 tp:49.27 md:0 lmd:2
130295424 shelly_hap_window_c:497 WC 1: P1 = 0.000
130524755 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
131095454 shelly_hap_window_c:497 WC 1: P1 = 0.000
131548498 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
131896754 shelly_hap_window_c:497 WC 1: P1 = 0.000
132396145 shelly_output.cpp:64 Output 2: on -> off (cal1)
132403662 shelly_hap_window_c:503 WC 1: calibration done, move_time 5089, move_power 0.000
132409572 shelly_hap_window_c:330 WC 1: State: cal1 -> postcal1 (14 -> 15)
132451212 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
132628663 mgos_sys_config.c:323 Saved to conf9.json
132635307 shelly_hap_window_c:350 WC 1: Tgt pos 49.27 -> 50.00 (postcal1)
132641263 shelly_hap_window_c:330 WC 1: State: postcal1 -> idle (15 -> 0)
132649850 shelly_hap_window_c:330 WC 1: State: idle -> move (0 -> 20)
132695299 shelly_output.cpp:64 Output 1: off -> on (move)
132701220 shelly_hap_window_c:330 WC 1: State: move -> rampup (20 -> 22)
132795489 shelly_hap_window_c:552 P = 0.00 -> 0.00
132801551 shelly_hap_window_c:330 WC 1: State: rampup -> moving (22 -> 23)
133297494 shelly_hap_window_c:340 WC 1: Cur pos 7.62 -> 9.59, P = 0.00
133493925 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
134097575 shelly_hap_window_c:340 WC 1: Cur pos 23.34 -> 25.31, P = 0.00
134518189 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
134897577 shelly_hap_window_c:340 WC 1: Cur pos 39.06 -> 41.03, P = 0.00
135397367 shelly_hap_window_c:350 WC 1: Tgt pos 50.00 -> 50.85 (fixup)
135402381 shelly_output.cpp:64 Output 1: on -> off (moving)
135408170 shelly_hap_window_c:330 WC 1: State: moving -> stop (23 -> 24)
135456301 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
135736823 mgos_sys_config.c:323 Saved to conf9.json
135743464 shelly_hap_window_c:330 WC 1: State: stop -> stopping (24 -> 25)
135754559 shelly_hap_window_c:330 WC 1: State: stopping -> idle (25 -> 0)
136873635 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
137592795 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
138014434 shelly_main.cpp:483 Up 138.00, HAP 0/1/16 ns 1, RAM: 209436/196404; st 56; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5089 cp:50.85 tp:50.85 md:0 lmd:1
138826204 mg_rpc.c:315 Shelly.GetInfoExt via WS_in 192.168.189.14:51101
146014719 shelly_main.cpp:483 Up 146.00, HAP 0/1/16 ns 1, RAM: 209436/196404; st 56; 4.1: c:1 mp:0.00 ip:5.00 mt_ms:5089 cp:50.85 tp:50.85 md:0 lmd:1

@github-actions github-actions bot removed the stale OP has not replied, gone stale, ready to close. label Sep 6, 2024
@markirb
Copy link
Collaborator

markirb commented Sep 13, 2024

The logs show that the measured power is always 0... :(

@DanielZornhagen
Copy link
Author

Is there a solution, how the problem can be solved?

@markirb
Copy link
Collaborator

markirb commented Sep 16, 2024

I am under the impression that you have the first Hardware Version of the device. Maybe Powermetering does not work there yet?
Can you show me the output of
http://A.B.C.D/rpc/Config.Get

@zuklior
Copy link

zuklior commented Sep 21, 2024

Hi
Same problem here.. is there a walk around??

@markirb
Copy link
Collaborator

markirb commented Sep 21, 2024

Can you give me the output I was asking for? You might need to reboot the device also?

@DanielZornhagen
Copy link
Author

DanielZornhagen commented Sep 21, 2024 •
edited by markirb
Loading

Redacted

@markirb
Copy link
Collaborator

markirb commented Sep 22, 2024

Thank you I reduced your info as it maybe contained too private information. But I have what I needed:

It looks indeed like you have Version 1 of the hardware SNSW-002P16EU.

There is no proper reset for the Power IC (or it's unknown?) in this version. Also that's the only known difference between version 1 and 2.

You could try if a reboot/power cut helps for now.
Otherwise I have to look on another way to reset...

@DanielZornhagen
Copy link
Author

Sadly a power cut doesn't help. Even a reset to facorysettings doesn't help. If you find a solution, ist would be great.

Within the Shelly-App the Calibration works fine.

@markirb
Copy link
Collaborator

markirb commented Sep 24, 2024

Hi,

ok that would have been an easy fix. :(

Sadly it is hard to Pinpoint this issue. The Chip itself is reset via software. And I think it is found otherwise your device should not be able to perform any firmware Update.

So far I have no idea why this should not work. When you switch to "normal mode" i.e. non window cover you see the power showing, right? Maybe channels are switched somehow? Can you try to play around in this "normal mode"?

Bildschirmfoto 2024-09-24 um 19 53 13

@markirb
Copy link
Collaborator

markirb commented Sep 28, 2024

One more thing: did you have the device on anything other than stock or this fw? It might also be that your calibration partition is wrong.

Can you downgrade to stock? And if so does it show power measuerements?

@markirb markirb added stale OP has not replied, gone stale, ready to close. and removed needs deeper look labels Oct 20, 2024
@DanielZornhagen
Copy link
Author

I’ve only used the Shelly with the stock firmware and this custom firmware. In the Shelly app, the power measurement works perfectly and is displayed correctly on the dashboard. The only place it doesn’t work is with this custom firmware.

@github-actions github-actions bot removed the stale OP has not replied, gone stale, ready to close. label Oct 21, 2024
@markirb
Copy link
Collaborator

markirb commented Oct 21, 2024

I see.
Then it seems indeed that the previous hardware version of 2pm (v1) does not yet work with the code. I do not know how to fix this without the hardware unfortunately.

@markirb markirb changed the title 2.12.1. Shelly plus 2pm calibration doesn’t work 2.12.1. Shelly plus 2pm (he v1) calibration doesn’t work Oct 21, 2024
@markirb markirb changed the title 2.12.1. Shelly plus 2pm (he v1) calibration doesn’t work Shelly +2PM (HW v1) Powermeasurment not working Oct 21, 2024
@markirb markirb changed the title Shelly +2PM (HW v1) Powermeasurment not working Shelly +2PM (HW v1) Powermeasurement not working Oct 21, 2024
@markirb markirb added the confirmed-bug confirmed bug label Oct 21, 2024
@DanielZornhagen
Copy link
Author

So the only solution I can choose is to buy the Shelly +2PM in a new version and replace all 15 Shellys?

@markirb
Copy link
Collaborator

markirb commented Oct 22, 2024 •
edited
Loading

That is not the solution 🙃

I can say that I cannot fix this as long as I do not know the exact problem.

Can you please remove the plastic casing to confirm that the assumption is valid that we have a v1 board (0.1.5). This should be easy and is reversible.

I can only look at the problem when I have the same hardware. Which cannot be bought anymore.

@markirb
Copy link
Collaborator

markirb commented Oct 24, 2024 •
edited
Loading

Maybe you can try this: This avoids IRQ pin conflict.
Note that 2.13 can only be flashed from 1.4.X stock

fw.zip

@DanielZornhagen
Copy link
Author

I tried the firmware. Unfortunately it doesn't solve the Problem.

@markirb
Copy link
Collaborator

markirb commented Nov 7, 2024

Ok thanks for testing. I guess this leaves the only option to send me the hardware if you want it running

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
confirmed-bug confirmed bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@markirb @zuklior @DanielZornhagen @santigvz