Hi guys!
Would be great is the thermostat driver had the "wind" capability.
Is there some hope it be implemented?
Thank you!
1 Like
What is that you're trying to use this for? My guess is that 'Wind' would be an attribute in some drivers but that there isn't a standard capability for it.
Can you explain what you actually mean?
2 Likes
Blower speed?
I suppose we'll have to see. 
But in that case, supportedThermostatFanModes already does this -- part of the Thermostat capability, with nothing new necessary (except maybe a driver update if this doesn't match what the device does -- and the data is actually available over whatever protocol it uses).
My Samsung splits have the capability "wind", in which the AC works just as a fan. To use the supported thermostat fan modes I must turn on the AC, which takes it directly to one of the available modes, "auto" or "cool". The wind mode turns on the AC but don't activate the compressor, it simply renew and circulate the air in the room.
This mode is available on SmartThings.
This is what the "Fan On" command should do. Do you have such a command, and does it work? Also, what device is this (manufacturer and model), and what driver are you using?
The driver exposes the "Fan On" command, but it doesn't work...
I'm using two Samsung WindFree splits, with the Replica Samsung OFC AirCon driver, and as workaround I'm using the custom capability of the thermostats.
Seems like this could be a problem with your custom driver. This command sounds like what you are describing.
What do you mean with this?
Just looking at that driver...
Isn't windFree the mode you are looking for, under the Optional Modes?
Have you tried using that command? It won't be available on the dashboard tile, as that is locked to Hubitat Thermostat Capability commands, and Optional mode is not part of that capability.
If windFree Optional Mode sets "wind", the driver could be modified fairly easily to add it to thermostat modes list of commands
WindFree really is the cool mode with the air diffuser closed. The air diffuser in this model has small holes, which prevents direct ventilation while cooling the room, it is different of the wind mode. The WindFree command just closes the diffuser.
Funny, that driver looks for "wind" as a thermostat mode when setting the supported modes:
Though it didn't make the map for some reason when that was set.
You could maybe force that mode by adding in "wind" as an always add mode:
Add a line after 260 to force wind into supported modes:
And then press configure.
It may be something @Bloodtick_Jones can look at to fix in the driver, if it really is not detecting wind mode is available when setting supported thermostat modes.
1 Like
Ooooops! @chrisbvt, your suggestion really shows the option "Wind" between the thermostat options in the tile, but it seems to break the use of it.
I see now that setThermostatMode(), which is called from the tile with the menu item selected, has no case for "wind". So the command never gets out of the driver.
You can add in wind, like below at 817, if you are seeing it in the tile menu now. That will call setAirConditioinerMode("wind"), and that will call sendCommand("setAirConditionerMode", "wind"). sendCommand will actually send the command to the parent at that point.
The parent probably calls back to setAirConditionerModeValue("wind")... which has no case for wind. So you add a case for wind to set tMode, and also an else if for "wind", to set operating state.
Lines 213-214 and 231-232 below:
I have no idea what will happen in the parent or on the smartThings side, I'm just throwing you things I would mess around with myself.
Edit: There is probably a very good reason why "wind" was not implemented in the driver, given there were already references to it in the code... but it can't hurt to try. 
I'm sure it will make a difference if you use "wind" or "Wind", if lowercase doesn't work, you could try uppercase.
Thank you for all your effort! I'm out now, but I'll try your suggestion.
As you said, it won't hurt! 
1 Like
