Just add it to the 1st metadata line for the DH
Oic didn’t seem to make a difference if I had it in or not
ocfDeviceType
changes the icon on the main tile
i think the vid also controls the ‘value’ on the mail tile
That’s what I thought also, maybe it used to do that. But I could not get it to change the value when I tested now
@mark_cockcroft, I have received this message today,
Do you see the same? Can you set any temperature to decimal values? I have some TRVs what are registered in the new app like “generic-radiator-thermostat-1” and another which one has a DH with “generic-radiator-thermostat”.
I have tried to set it to 18.5, but it is neither not scrolling there or in the numerical entry I cannot set it.
Was it working before with decimals? I haven’t played too much with it yet.
@Philippe_Portes, I honestly don’t understand this.
NUMBER `5` , `10.6` The Number data type is a guideline indicating that a number should be expected, and not a specific type. Device Handlers contain the implementation of what kind of number object is actually returned.
And these allow decimal point.
# reviewed 2018-01-30
name: Thermostat Heating Setpoint
status: live
attributes:
heatingSetpoint:
schema:
$ref: Temperature
type: NUMBER
setter: setHeatingSetpoint
commands:
setHeatingSetpoint:
arguments:
- name: setpoint
required: true
schema:
$ref: TemperatureValue
type: NUMBER
public: true
id: thermostatHeatingSetpoint
ocfResourceType: x.com.st.temperature.heating
version: 1
And this too:
{
"id": "thermostatHeatingSetpoint",
"version": 1,
"name": "Thermostat Heating Setpoint",
"status": "live",
"attributes": {
"heatingSetpoint": {
"schema": {
"title": "Temperature",
"type": "object",
"additionalProperties": false,
"properties": {
"value": {
"title": "TemperatureValue",
"type": "number",
"minimum": -460,
"maximum": 10000
},
"unit": {
"title": "TemperatureUnit",
"type": "string",
"enum": [
"F",
"C"
]
},
"constraints": {
"title": "NumberConstraint",
"type": "object",
"additionalProperties": false,
"properties": {
"min": {
"type": "number"
},
"max": {
"type": "number"
}
}
}
},
"required": [
"value",
"unit"
]
}
}
},
"commands": {
"setHeatingSetpoint": {
"arguments": [
{
"name": "setpoint",
"schema": {
"title": "TemperatureValue",
"type": "number",
"minimum": -460,
"maximum": 10000
},
"required": true
}
]
}
}
}
And of course, both of them live…
Maybe post your issue here Get ready to make the switch! and tag Blake.Arnold and Brad_ST.
Already have a ticket with support
Oh, I see it in the DH’s control. I am unable to select half values. It might be the UX plugin.
HI was wondering if anyone had a complete list of the VID’s avaliable.
@Automated_House, @Richard_Griffiths asked for a complete list, the vid selector is incomplete. It is missing all the thermostats.
@Automated_House thanks you. This should be able to get started @GSzabados do you know where i can fine the thermostat list
@Richard_Griffiths, in the post what you have quoted. Just click on it and it will show the whole post. That is @mark_cockcroft’s research.
@GSzabados i am dumb. Do you know if it is possible to have one than one VID. I have thermostat that has a boost button or will i have to create two things one thermostat and one switch
@Richard_Griffiths, unfortunately what you are looking for is not really there yet. I would love to implement a boost up and down button, but that will be later available. Custom capabilities are on the way, but nobody knows when will be available for us.
@GSzabados i have chnaged over to vid: “generic-radiator-thermostat” but i can only adjust the set point in 1 degrees increments. Do you know of a way to change this to 0.5 degree increments.
That is a bug over there. Support told that it should be fixed soon, but haven’t been fixed yet.
Recently Smartthings device controller has changed for thermostats.
After this change, vid: “generic-radiator-thermostat” no longer displays heatingSetpoint controller.
Only vids made for both heatingSetpoint and coolingSetpoint work properly after the change.
This should be fixed.
Thank you.
Known issue: