State value to set for "hm-rpc.1.xxxxxxx.1.LEVEL" has value "10" greater than max "1.01"

[DutchmanNL]

Describe the bug Error messages ar thrown to the log as the max value is set to 1.01, but the level can have a range from 0-100% Issue occurs on Homematic IP - RadiatorThermostat of type HMIP-eTRV

Expected behavior Correct min/max value to reduce error messages in log

Screenshots & Logfiles State value to set for "hm-rpc.1.xxxxxxx.1.LEVEL" has value "10" greater than max "1.01"

{
  "type": "state",
  "common": {
    "def": 0,
    "type": "number",
    "read": true,
    "write": true,
    "min": 0,
    "max": 1.01,
    "unit": "%",
    "role": "level",
    "name": "xxxxxxx.LEVEL",
    "custom": {
      "influxdb.0": {
        "enabled": true,
        "changesOnly": true,
        "debounce": "",
        "retention": 0,
        "changesRelogInterval": "1800",
        "changesMinDelta": 0,
        "storageType": "",
        "aliasId": ""
      }
    }
  },
  "native": {
    "MIN": 0,
    "OPERATIONS": 7,
    "MAX": 1.01,
    "FLAGS": 1,
    "ID": "LEVEL",
    "TYPE": "FLOAT",
    "DEFAULT": 0,
    "UNIT": "100%"
  },
  "_id": "hm-rpc. xxxxxxx.1.LEVEL",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  },
  "from": "system.adapter.admin.0",
  "user": "system.user.admin",
  "ts": 1624305131281
}

Versions:

• hm-rpc version: 1.15.5
• hm-rega version: 3.0.35
• JS-Controller version: 4.0.9
• Node version: 14.9
• Operating system: Ubuntu 20.4
• CCU model: RaspberryMatic
• CCU firmware: 3.61.7.20220115

[foxriver76]

have you tried deleting the datapoint once, unit 100% dps should be created with a max of 100

[DutchmanNL]

have you tried deleting the datapoint once, unit 100% dps should be created with a max of 100

Yes I did, the level state did only come back when I activated the object synchronize once. result of the object after that is still the same:

    "write": true,
    "min": 0,
    "max": 1.01,
    "unit": "%"

logging :

[foxriver76]

Currently not seeing how this can happen code-wise, at last we check if it is UNIT: 100% then say max = 100

[DutchmanNL]

Currently not seeing how this can happen code-wise, at last we check if it is UNIT: 100% then say max = 100

hmm than lets make this even more weird, please have a look how my current logging looks like ( checked my logging and didn't receive this error anymore sins 15-02).

but also.... the values are write now totally different :

so no everything is back to 0-1 scale... I am confused :/ wil monitor what happens anything I can add or specifically monitor/test to assist finding the RC ?

[DutchmanNL]

just to add, this is my history logging of the 15th

as far I remember only thing that happens in between was an adapter restart

Edit : reviews my complete system log.... only thing that happens in between was a adapter restart + system reboot sind than all running smoothly

[DutchmanNL]

ok no i m getting totally confused, it looks like the way of value handling has changed see my history. If I remember correctly, I also updated RaspberryMatic during that time-window so maybe here was an issue that these values were submitted incorrectly ?

[DutchmanNL]

sorry, I checked my installation twice and the update of raspberrymatic is longer ago my virtual machine with updated RaspberryMatic runs already for 15 days now so was updated on the 5th of februari and not anywhere in the time-frame of the 15th were this issue did occur so I see no relation

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

[DutchmanNL]

Still relevant

[Kev0123]

I got the same issue

[PEPITO82]

I'm facing same issue with my HMIP-WKP:

State value to set for "hm-rpc.1.002E9F299XXXX.0.CODE_ID" has value "32" greater than max "8"

Any solution for this?