Shelly Pro 3EM

[michalk-k]

I have measured Shelly Pro 3EM, but as mentioned in previous discussions, this device has different consumption depending on what interface (or combination of interfaces) are enabled.
Here are:

• WiFi AP
• WiFi Client
• BlueTooth
• Ethernet

I measured it with different combinations of the above, and created profiles. Before I create PR, I would like to ask for a naming convention for profiles. I suppose profile names are picked directly from the subdirectory's names? Isn't it?

[michalk-k]

Unfortunately after adding it from discovery no device/entity is created

Here is the configuration

{
  "measure_description": "The measured device fw: 1.4.4, Eco Mode disabled. The result represents the average value of measurements collected from the measurement device API for the following scenarios: dumb device/baseline consumption (~4.9W) and several device configurations. See sub-profiles.",
  "measure_method": "manual",
  "measure_device": "Shelly PM Mini gen3",
  "measure_device_firmware": "20241011-114503/1.4.4-g6d2a586",
  "measure_settings": {
    "SAMPLE_COUNT": 200,
    "SLEEP_TIME": 0.5
  },
  "name": "Shelly Pro 3EM 3CT63",
  "aliases": [
    "SPEM-003CEBEU63"
  ],
  "discovery_by": "device",
  "device_type": "power_meter",
  "sensor_config": {
    "power_sensor_naming": "{} Device Power",
    "energy_sensor_naming": "{} Device Energy"
  },
  "created_at": "2024-01-03T20:07:00 CET",
  "author": "Michal Bartak <[email protected]>"
}

and one of the profiles:

{
  "measure_description": "The device measured with Ethernet port enabled. Other interfaces were disabled",
  "standby_power": 0.930,
  "created_at": "2024-01-03T20:07:00 CET",
  "author": "Michal Bartak <[email protected]>"
}

[bramstroker]

Unfortunately after adding it from discovery no device/entity is created

Strange, the logs might give clues as to why.

[michalk-k]

yea... see the last line

2025-01-11 15:37:19.496 DEBUG (MainThread) [custom_components.powercalc.discovery] 1b115cba44088d08bc74735320a1b17d: Found model information on device (manufacturer=Shelly, model=Shelly Pro 3EM 3CT63, model_id=SPEM-003CEBEU63)
2025-01-11 15:37:19.497 DEBUG (MainThread) [custom_components.powercalc.discovery] 1b115cba44088d08bc74735320a1b17d: Initiating discovery flow, unique_id=pc_1b115cba44088d08bc74735320a1b17d
2025-01-11 15:37:19.497 DEBUG (MainThread) [custom_components.powercalc.config_flow] Starting discovery flow: {'entity_id': 'sensor.dummy', 'source_entity': SourceEntity(object_id='shellypro3em63-2cbcbbb829f8', entity_id='sensor.dummy', domain='sensor', unique_id=None, name='shellypro3em63-2cbcbbb829f8', supported_color_modes=None, entity_entry=None, device_entry=DeviceEntry(area_id='powercalctest', config_entries={'01JH90EGFNE3YYA7B6C8250VFA'}, configuration_url='http://192.168.0.42:80', connections={('mac', '2c:bc:bb:b8:29:f8')}, created_at=datetime.datetime(2025, 1, 10, 21, 3, 15, 43077, tzinfo=datetime.timezone.utc), disabled_by=None, entry_type=None, hw_version='gen2', id='1b115cba44088d08bc74735320a1b17d', identifiers=set(), labels=set(), manufacturer='Shelly', model='Shelly Pro 3EM 3CT63', model_id='SPEM-003CEBEU63', modified_at=datetime.datetime(2025, 1, 10, 21, 3, 20, 359289, tzinfo=datetime.timezone.utc), name_by_user=None, name='shellypro3em63-2cbcbbb829f8', primary_config_entry='01JH90EGFNE3YYA7B6C8250VFA', serial_number=None, suggested_area=None, sw_version='20250109-090622/1.5.0-beta1-g16e0ef4', via_device_id=None, is_new=False, _cache={'json_repr': b'{"area_id":"powercalctest","configuration_url":"http://192.168.0.42:80","config_entries":["01JH90EGFNE3YYA7B6C8250VFA"],"connections":[["mac","2c:bc:bb:b8:29:f8"]],"created_at":1736542995.043077,"disabled_by":null,"entry_type":null,"hw_version":"gen2","id":"1b115cba44088d08bc74735320a1b17d","identifiers":[],"labels":[],"manufacturer":"Shelly","model":"Shelly Pro 3EM 3CT63","model_id":"SPEM-003CEBEU63","modified_at":1736543000.359289,"name_by_user":null,"name":"shellypro3em63-2cbcbbb829f8","primary_config_entry":"01JH90EGFNE3YYA7B6C8250VFA","serial_number":null,"sw_version":"20250109-090622/1.5.0-beta1-g16e0ef4","via_device_id":null}'})), 'unique_id': 'pc_1b115cba44088d08bc74735320a1b17d', 'power_profiles': [<custom_components.powercalc.power_profile.power_profile.PowerProfile object at 0x7f60ba9eb0>], 'manufacturer': 'shelly', 'model': 'Shelly Pro 3EM 3CT63'}
2025-01-11 15:37:19.498 DEBUG (MainThread) [custom_components.powercalc.discovery] Done auto discovery
--
2025-01-11 15:37:35.488 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=sensor.dummy entity_category=None, sensor_name=shellypro3em63-2cbcbbb829f8 Device Power strategy=lut manufacturer=shelly model=Shelly Pro 3EM 3CT63 unique_id=pc_1b115cba44088d08bc74735320a1b17d)
2025-01-11 15:37:35.488 ERROR (MainThread) [custom_components.powercalc.sensors.power] sensor.dummy: Skipping sensor setup: Only light entities can use the LUT mode

[bramstroker]

you forgot calculation_strategy. When not defined lut is the default.

"calculation_strategy": "fixed",

[michalk-k]

Thank you. only_self_consumption was missing too, otherwise, it complained about fixed configuration.

Now it's working as expected. Maybe I would expected an error message instead of silently swallowing the bug in config.

[bramstroker]

Currently; yes it's picked from sub directory name. Current naming scheme seems fine by me.
I think we can improve upon that by also looking at name prop from model.json which we can set differently in other sub profile.
Not sure how many places needs refactoring to incorporate that. Will have a look soon.

See: #2931

[michalk-k]

Shouldn't PC hide fixed and standby consumption GUI from the configuration in case self_consumption is set to true?
In the video above you can see fixed and basic configuration which allows to do that regardless of settings in the profile.
Is it regression?

[bramstroker]

Which video are your referring too?
Could you please create an issue report with details?