PowerMeter capability - negative values will be displayed as "Out of range" in detailView

Devices & Integrations
1

Hi,

I’ve noticed that the powerMeter capability reports “Out of Range” except for negative values in the detail view.
On the dashboard view, they were correctly shown as a negative value.

Screenshot_20230510-143040_SmartThings
Screenshot_20230510-143040_SmartThings720×1280 31.9 KB

Screenshot_2023-05-10-14-42-37-144_com.samsung.android.oneconnect (1)
Screenshot_2023-05-10-14-42-37-144_com.samsung.android.oneconnect (1)1080×2340 88.5 KB

Is this a bug or do I need to set a range somehow? The ActivePower attribute has the data type " Int16", so it should work out of the box.

Thank you in advance.

2

you may want to include the version of the app :slight_smile:

3

Sure :slight_smile:

On both devices 1.8.00.22

4

Hello @nayelyz

Is this something that your team can reproduce?
I’m playing around with the Aeotec HEM Gen5 right now and when I change the clamping direction, the HEM reports negative values. It would be great to fix this somehow - maybe it’s just a presentation configuration that can be done in the driver?

5

Yes, there’s already a request to change the range in the presentation by default, but there’s no ETA for that.

However, if you’re developing an integration, you can create a custom device configuration to overwrite the range of the capability presentation. For example, this is a part of the configuration for the thermostatCoolingSetpoint capability, the properties that make the trick are key and range. In key, you need to put the attributeName.value, otherwise, it won’t work:

{
    "component": "main",
    "capability": "thermostatCoolingSetpoint",
    "version": 1,
    "values": [
      {
        "key": "coolingSetpoint.value",
        "range": [
          -4,
          80
        ],
        "step": 1
      }
    ],
    "patch": [],
    "exclusion": []
}

Once you create this custom device presentation, you’ll get a VID which you can put in your Edge driver’s profile:

name: dummyThermostat.v1
components:
- id: main
  capabilities:
  - id: thermostatMode
    version: 1
  - id: thermostatHeatingSetpoint
    version: 1
  - id: thermostatCoolingSetpoint
    version: 1
  categories:
    - name: Thermostat
metadata:
  vid: xxxx-xxxx-xxxx
  mnmn: SmartThingsCommunity
6

@nayelyz
sorry to bump an old thread, but I was wondering if the request to fix the default range limitation for powerMeters is still pending and if not can it be resurrected? It has not been implemented as far as I can tell.

7

Hi, @georgeh
Let me check the case of the detail view. What I see is that we can create routines using negative numbers and they work correctly, in case it helps while we check the “out of range” message.

8

For me it is only a minor annoyance when using the app to view current readings, since I can find the negative value on the “devices” page or in the history. But I think you’d want to clean it up eventually.

1 Like
9

Ok, I created a ticket for this. Thank you for bringing it up!

1 Like
10

Hi, @georgeh
Following up on the “out of range” message, the team mentioned this was discussed in the past and you can override the default range in the device presentation to avoid getting that message.
In the case of Edge drivers, remember you can add embedded device-configurations in the device profile, for example:

11

Thanks, I used the range values in the profile and that worked.

Was wondering - does that have any other side effect, such as not recording “out of range” values in the history/platform itself, or does it only affect what is shown on the app’s detail page?

12

No, this configuration only affects the UI, as the capability doesn’t have a range set on its definition, it can accept any numeric value and that will be shown in the history unless you define the event’s visibility=false.
When you have a range set in the capability’s definition, commands with “out of range” values to that capability will be rejected.