[Bug]: Shelly Pro Dimmer 2PM no Consuption Data (Energy) for Output

[libertyx82]

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

Shelly Pro Dimmer 2PM (shellyprodm2pm)

Shelly firmware version

1.4.2

Protocol

MQTT

The problem

For Output Light0 and Light1 are no Energy Data (Total and Current Consumption) will be shown, but they are included in the MQTT Massage.

{"ble":{},"bthome":{"errors":["bluetooth_disabled"]},"cloud":{"connected":false},"eth":{"ip":null},"input:0":{"id":0,"state":null},"input:1":{"id":1,"state":null},"input:2":{"id":2,"state":null},"input:3":{"id":3,"state":null},"knx":{},"light:0":{"id":0,"source":"WS_in","output":false,"brightness":100,"temperature":{"tC":36.0, "tF":96.8},"aenergy":{"total":0.677,"by_minute":[139.934,140.719,51.116],"minute_ts":1729086180},"apower":0.0,"current":0.000,"voltage":234.2},"light:1":{"id":1,"source":"","output":false,"brightness":1,"temperature":{"tC":34.6, "tF":94.2},"aenergy":{"total":0.000,"by_minute":[0.000,0.000,0.000],"minute_ts":1729086180},"apower":0.0,"current":0.000,"voltage":234.1,"flags":["uncalibrated"]},"mqtt":{"connected":true},"sys":{"mac":"","restart_required":false,"time":"15:43","unixtime":1729086239,"uptime":62976,"ram_size":250924,"ram_free":112416,"fs_size":524288,"fs_free":184320,"cfg_rev":15,"kvs_rev":0,"schedule_rev":0,"webhook_rev":0,"available_updates":{},"reset_reason":1},"wifi":{"sta_ip":"192.168.2.47","status":"got ip","ssid":"web-hacker-br-k","rssi":-67},"ws":{"connected":false}}

iobroker.current.log (in debug mode!)

iobroker.current.log

Version of nodejs

20.18.0

Version of ioBroker js-controller

6.0.11

Version of adapter

8.3.0

[github-actions]

Thanks for reporting a new issue @libertyx82!

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!

---

Otherwise this issue will be closed.