Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

multiple status-parameters? #119

Open
pesmi30 opened this issue Jul 9, 2024 · 1 comment
Open

multiple status-parameters? #119

pesmi30 opened this issue Jul 9, 2024 · 1 comment

Comments

@pesmi30
Copy link

pesmi30 commented Jul 9, 2024

There seems something wrong with the 'status' parameter. (probably no error on your part)
When I look in 'Swagger datapoints ' (I hope I did it right), I see two status-es:
Both have als name "status'".
One has id 50113 and the other has id 50095.

I think (not sure) that your integration shows the value of the 50095 (with sensorname "vra16_status"; so no colon)
It gives me the value "15.003 min"
I think I should read this not as minutes (?), but as 15003 -> status 'off'

Issues (but: I am quite new in this):

  • why two parameters with the same name?
  • id 50113 is not (?) available as a sensor
  • id 50113 is in kW but the enumValues are statuses
  • id 50095 seems to give status OK (and is available as a sensor), but is is shown as a number of minutes (??)

I think the problem is not with you, but with the developers of myUplink.

Can you help or correct me (or clarify?)

Kind regards,

Peter

{
"category": "F1145-10 PC",
"parameterId": "50113",
"parameterName": "status:",
"parameterUnit": "kW",
"writable": false,
"timestamp": "2024-07-07T22:28:32+00:00",
"value": 1512,
"strVal": "1512kW",
"smartHomeCategories": [],
"minValue": null,
"maxValue": null,
"stepValue": 1,
"enumValues": [
{
"value": "15000",
"text": "starts",
"icon": ""
},

**** and many more ***

"category": "F1145-10 PC",
"parameterId": "50095",
"parameterName": "status:",
"parameterUnit": "min",
"writable": false,
"timestamp": "2024-07-09T15:43:10+00:00",
"value": 15003,
"strVal": "15003min",
"smartHomeCategories": [],
"minValue": null,
"maxValue": null,
"stepValue": 1,
"enumValues": [
  {
    "value": "15000",
    "text": "starts",
    "icon": ""
  },
  {
    "value": "15001",
    "text": "runs",
    "icon": ""
  },

*** and many more ***

@jaroschek
Copy link
Owner

Hi @pesmi30, unfortunately this is a problem in the myUplink API. It is a very bad example how badly it is managed/used by the manufacturers or whoever decides which parameter to include and how.

I don't see any way how this could or should be solved on the integration/client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants