home-assistant-myuplink icon indicating copy to clipboard operation
home-assistant-myuplink copied to clipboard

Missing writable values

Open matlimatli opened this issue 7 months ago • 1 comments

I noticed that some writable parameters are created as sensors instead of numbers. It seems like the API in some cases shows minValue and maxValue as null, causing find_fitting_entity() to return SENSOR instead of NUMBER.

Example of such a parameter:

{
    "category": "F1155-16",
    "parameterId": "47669",
    "parameterName": "activated",
    "parameterUnit": "",
    "writable": true,
    "timestamp": "2024-07-16T10:49:23+00:00",
    "value": 1,
    "strVal": "1",
    "smartHomeCategories": [],
    "minValue": null,
    "maxValue": null,
    "stepValue": 1,
    "enumValues": [],
    "scaleValue": "1",
    "zoneId": null
  }

I guess this is mainly a problem with the API. But as I suppose it might be hard to get that fixed; would a workaround be possible? Can a number exist without having a max or min value? The only parameters I care about with this problem are binaries (where the values 0 and 1 should be allowed). But I can see some other parameters, e.g. "Oper. time hot water", with the same issue, it is however a bit surprising that those are writable.

This might be related to #105

matlimatli avatar Jul 16 '24 23:07 matlimatli