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

Setting Decimal/Raw ValueIDs - Need to create a new ValueDelegate #39

Open
mew1033 opened this issue Jun 4, 2020 · 5 comments
Open
Assignees

Comments

@mew1033
Copy link

mew1033 commented Jun 4, 2020

It's possible I'm just not doing this right, but I can't update User Values that aren't dropdowns. This is what I'm talking about:
Can't change value
I double click on the value, type in my new value, hit enter, and nothing happens. I don't get anything in the log either. But if I change a value that is a dropdown, the change works.

Am I just doing it wrong, or is that not working?
Thanks!

@kpine
Copy link

kpine commented Jun 5, 2020

I can confirm the same with my thermostat. My light switch does not have this behavior though. I notice there is a difference between the controls. The light switch Level shows up and down buttons to increment/decrement the value, and the value applies correct. The setpoint Values have Min and Max values of 0, while the light level is 0-255. According to this comment, ozwadmin respects the range, so maybe this is the problem?

@kpine
Copy link

kpine commented Jun 5, 2020

Light level value which works fine:

{
    "Label": "Level",
    "Value": 0,
    "Units": "",
    "ValueSet": false,
    "ValuePolled": false,
    "ChangeVerified": false,
    "Min": 0,
    "Max": 255,
    "Type": "Byte",
    "Instance": 1,
    "CommandClass": "COMMAND_CLASS_SWITCH_MULTILEVEL",
    "Index": 0,
    "Node": 15,
    "Genre": "User",
    "Help": "The Current Level of the Device",
    "ValueIDKey": 256475153,
    "ReadOnly": false,
    "WriteOnly": false,
    "Event": "valueChanged",
    "TimeStamp": 1591380548
}

Setpoint value which does not work:

{
    "Label": "Cooling 1",
    "Value": 78.0,
    "Units": "F",
    "ValueSet": false,
    "ValuePolled": false,
    "ChangeVerified": false,
    "Min": 0,
    "Max": 0,
    "Type": "Decimal",
    "Instance": 1,
    "CommandClass": "COMMAND_CLASS_THERMOSTAT_SETPOINT",
    "Index": 2,
    "Node": 20,
    "Genre": "User",
    "Help": "Set the Thermostat Setpoint Cooling 1",
    "ValueIDKey": 562950294257682,
    "ReadOnly": false,
    "WriteOnly": false,
    "Event": "valueAdded",
    "TimeStamp": 1591372977
}

@Fishwaldo
Copy link
Member

Ahhh - Decimal Values are not supported in the GUI yet.

@Fishwaldo Fishwaldo changed the title Can't update User Value that isn't a dropdown Setting Decimal ValueIDs - Need to create a new ValueDelegate Jun 5, 2020
@Fishwaldo Fishwaldo self-assigned this Jun 5, 2020
@Fishwaldo Fishwaldo changed the title Setting Decimal ValueIDs - Need to create a new ValueDelegate Setting Decimal/Raw ValueIDs - Need to create a new ValueDelegate Jul 24, 2020
@matejdro
Copy link

Is there a workaround for that (maybe setting the config value manually somehow)?

@kpine
Copy link

kpine commented Sep 24, 2020

@matejdro You can use MQTT to set the value.

Publish OpenZWave/1/command/setvalue/
Data:

{
  "ValueIDKey": key,
  "Value": value,
}

But as I mentioned in #68 your problem is that the config value you are trying to set has the type Decimal, which is not valid. So your fix is to update the device XML instead.

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

No branches or pull requests

4 participants