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

[Bug]: Energy data are missing for Shelly Pro EM 50 #1070

Open
3 tasks done
mbrock70 opened this issue Oct 21, 2024 · 5 comments
Open
3 tasks done

[Bug]: Energy data are missing for Shelly Pro EM 50 #1070

mbrock70 opened this issue Oct 21, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@mbrock70
Copy link

I'm sure that

  • This issue is still present in the current beta version of this adapter
  • There is no other (open) issue with the same topic (use the search!)
  • This issue is not described in the adapter documentation / FAQ (read the docs!)

Shelly device

Pro EM50

Shelly firmware version

1.4.4

Protocol

MQTT

The problem

The Energy Data are missing as they are available in the Pro 3EM in EMData0 for both Channels.

iobroker.current.log (in debug mode!)

No response

Version of nodejs

18.20.4

Version of ioBroker js-controller

6.0.11

Version of adapter

8.2.1

@mbrock70 mbrock70 added the bug Something isn't working label Oct 21, 2024
Copy link

Thanks for reporting a new issue @mbrock70!

  1. Please make sure your topic is not covered in the documentation
  2. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue
  3. Search for the issue topic in other/closed issues to avoid duplicates!
  4. Ensure that you use the latest available beta version of this adapter (not the current stable version): 8.4.0

Otherwise this issue will be closed.

@bowmore16
Copy link

The issue is not solved with version 8.4.0

@mcm1957
Copy link
Member

mcm1957 commented Oct 26, 2024

The issue is not solved with version 8.4.0

Where did you read the info that it should be solved?

@bowmore16
Copy link

It shouldnt be solved with 8.4.0, I was just adding information, that was requested by the github-bot, as mbrock70 was using 8.2.1.:

  1. Ensure that you use the latest available beta version of this adapter (not the current stable version): 8.4.0

@tclas
Copy link

tclas commented Jan 15, 2025

Hi,
I can confirm this behavior. It seems the device-specific code calls the function addEM1 which does not parse the total_act_energy and total_ret_energy messages sent by the device.

In my case it looks like this:

shellyproem50-34987a67ee9c/status/em1data:0 {"id":0,"total_act_energy":3437.02,"total_act_ret_energy":0.08}
shellyproem50-34987a67ee9c/status/em1data:1 {"id":1,"total_act_energy":3098.19,"total_act_ret_energy":0.00}

where id represents the channels which are measured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants