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

[shelly] Incorrect values reported for Shelly Pro EM-50 #18128

Open
embeh opened this issue Jan 19, 2025 · 1 comment
Open

[shelly] Incorrect values reported for Shelly Pro EM-50 #18128

embeh opened this issue Jan 19, 2025 · 1 comment
Labels
bug An unexpected problem or unintended behavior of an add-on

Comments

@embeh
Copy link

embeh commented Jan 19, 2025

(Caveat: My Shelly Pro EM-50 is two weeks old, and I am fresh to openHAB, so apologies if I am missing something obvious)

Expected Behavior

openHAB should report the same electricity values as shown by the Shelly Web UI or the Shelly RPC endpoints.

Current Behavior

(Note 1: There are multiple channels affected. For simplicity, I am describing this with "Current")
(Note 2: This Shelly device has two power meters; this description focuses on the first one but both are affected the same)

These are the Channel details for the Current 1 channel:

Current 1 
Shelly Pro EM-50
shelly:shellyproem50:019b5XXXXX:meter1#current (Number:ElectricCurrent)

At the time of writing, openHAB reports its value as "0.725 A"

But the Shelly Web UI under http://192.168.XXX,YYY/#/em1/0/overview reports its value as "1.006 A" for the first power meter (and "0.44 A" for the second - NB: I am also reporting the second value here to address the possible question that maybe the two power meters got mixed up)

Likewise the RPC endpoint http://192.168.XXX,YYY/rpc/em1.getstatus?id=0 returns this JSON dataset:
{"id":0,"current":1.006,"voltage":234.9,"act_power":-158.7,"aprt_power":236.6,"pf":0.77,"freq":50.0,"calibration":"factory"}

And for the second power meter the RPC endpoint http://192.168.XXX,YYY/rpc/em1.getstatus?id=1 returns this JSON dataset:
{"id":1,"current":0.44,"voltage":235.1,"act_power":36.1,"aprt_power":108.2,"pf":0.60,"freq":50.0,"calibration":"factory"}

--> the value of openHAB shold be identical to those directly reported by the device, i.e. the correct value would have been "1.006 A".

Possible Solution

Maybe the Shelly binding is not using the correct endpoints for the Shelly Pro EM-50?

Steps to Reproduce (for Bugs)

  1. Add Shelly Pro EM-50 as a new thing
  2. Go to Things > Channels and select "Current 1"
  3. Click "Link to item" and select "Create a new item"
  4. Confirm all defaults for the new item
  5. Observe the collected values for that item and compare with values directly reported by the device --> major differences in values are observed

Context

Right now, I cannot get correct measurements in openHAB, I have to rely on those directly reported by the device.

Your Environment

Shelly Pro EM-50
openHAB 4.3.1 running on Windows 10, with the Shelly Binding v 4.3.1

@embeh embeh added the bug An unexpected problem or unintended behavior of an add-on label Jan 19, 2025
@proggprod
Copy link

I also have issues with this device not showing lifetime energy consumption (kwh) on the individual channels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug An unexpected problem or unintended behavior of an add-on
Projects
None yet
Development

No branches or pull requests

2 participants