Fan Control Speed ENUM dropdown in Dashboard

[kevin]

The Fan Control capability has a supportedFanSpeeds attribute JSON_OBJECT for supportedFanSpeeds - I have modified this to create some different entries. However when I use the 'Fan' template in Dashboard it displays just the original values. Are these ENUM values hardcoded in the template perhaps ?

Is there no way to display a dropdown of enumerated values in Dashboard yet? Yoiu can sort of abuse the virtual thermostat to achieve this but having a more generally useful template would be so useful..

[sburke781]

I've been able to do this in my drivers, let me check...

[sburke781]

This is the code I have used, may need to double-check the effect in the dashboard, but I am sure I have seen it work there.... This is from my Unified Thermostat Child driver

def adjustFanModes(pNumberOfFanSpeeds, pHasAutomaticFanSpeed) {
    def fanModes = []
    
    fanModes.add('Off')
    
    //Text or Numbers?
    if (FansTextOrNumbers == true || FansTextOrNumbers == "1") {
        parent.debugLog("adjustFanModes:Text-based Fan Modes")
        if(pNumberOfFanSpeeds.toInteger() == 3) {
            fanModes.add('Low')
            fanModes.add('Medium')
            fanModes.add('High')
        }
        else if(pNumberOfFanSpeeds.toInteger() == 2) {
            fanModes.add('Low')
            fanModes.add('High')
        }
        else
        {
        //if(pNumberOfFanSpeeds.toInteger() == 5) {
            fanModes.add('Low')
            fanModes.add('Medium Low')
            fanModes.add('Medium')
            fanModes.add('Medium High')
            fanModes.add('High')
        }

    }
    else {
        parent.debugLog("adjustFanModes:Number-based Fan Modes")
        if(pNumberOfFanSpeeds.toInteger() == 3) {
            fanModes.add('1')
            fanModes.add('2')
            fanModes.add('3')
        }
        else if(pNumberOfFanSpeeds.toInteger() == 2) {
            fanModes.add('1')
            fanModes.add('2')
        }
        else
        {
        //if(pNumberOfFanSpeeds.toInteger() == 5) {
            fanModes.add('1')
            fanModes.add('2')
            fanModes.add('3')
            fanModes.add('4')
            fanModes.add('5')
        }
    }
    
    if(pHasAutomaticFanSpeed == "true" || pHasAutomaticFanSpeed == "1") {
        fanModes.add('Auto')
    }
    
    fanModes.add('On')
    
    parent.debugLog("adjustFanModes: fanModes detected are ${fanModes}")
    //Apply settings
    sendEvent(name: 'supportedThermostatFanModes', value: fanModes)
}

[sburke781]

Ah, thermostat fan modes....Hmmm...

[kevin]

I can sort of get it to work in the thermostat template but that is a little cluttered and has two mode dropdowns. I wanted to use Fan Control because that presents just a single dropdown with the list values in it. I think it is behaving differently to the thermostat template though.

^ from the thermostat template

[sburke781]

I had people wanting to use the fan control as well, I thought I had that working....

[sburke781]

Actually, you could be right, it may have been that the systems I was working with had 5 speeds already...

[kevin]

It would seem to be a huge UI omission in Dashboard to not be able to create an enumerated list dropdown tile. I'm sure it should work even if I am (ab)using the fan control template. Or have an attribute template that you could select containing an ENUM

[sburke781]

This might be what you are after:

supportedFanSpeeds in 2.2.6

If you want the enum list in the device setSpeed command to reflect the values in your custom supportedFanSpeeds you will need to override the capability setSpeed command in the driver via something like: command "setSpeed", [[name: "Fan speed*",type:"ENUM", description:"Fan speed to set", constraints: getFanLevel.collect {k,v -> k}]] where getFanLevel in this case is: import groovy.transform.Field @Field Map getFanLevel = [ "low": 25 ,"medium": 50 ,"medium-high": 75 ,"high": 100 ,"on" :…

[kevin]

That's a spot on topic thanks - I missed it but it just reveals the same shortcoming of the fan template.

@bertabcd1234

One issue is that this value doesn't seem to get used anywhere useful--notably, Dashboard still displays all the standard possibilities (or did last time I checked).

@bertabcd1234

More likely, I suspect you have a "Fan" tile and are expecting the popup to show only the speeds indicated by this attribute. I asked about this above, and that is (currently?) not something Dashboard does,

Shame... it would be seem so useful (dare I venture ..fundamental)

[sburke781]

At the end of the topic it appears they were able to get it working.... Or am I missing something still....

[kevin]

I think that 'everything is working now' related to other problems - I don't think a matching displayed fanControl dropdown in Dashboard was ever achievable..

I have implemented the HA MQTT Discovery protocol inside HE meaning that HE can discover devices that advertise their availability using this 'pseudo' standard and (auto) create them in HE. However I have no easy way to add devices that require enumerated control values with dashboard.

[bertabcd1234]

@kevin

I think that 'everything is working now' related to other problems

Yeah, I believe that was just getting the attribute to report correctly on the child device. I still don't think this is really used anywhere useful by default in the UI; an app could certainly read this and do what it wants with the information, but the device page UI doesn't the last time I checked, and Dashboard (an app that certainly could "see" this information and modify things as needed) doesn't, either. They did mention that they are hoping to improve Dashboard in a future release (not necessarily regarding this feature or anything similar), so there is some hope...

(EDIT: I should add that you can manually "override" the command in your driver to make the device page show whatever you want, but this still won't change Dashboard and has no effect on the attribute unless you also modify it as specified, not that any stock app I'm aware of does anything with either of these pieces of information.)

[kevin]

We need to be able to create/code our own templates...

@bertabcd1234

I should add that you can manually "override" the command in your driver

Yes - indeed but not what is needed here

[sburke781]

Thanks for clarifying @bertabcd1234