I Just replaced my GE Fan controller with the Homeseer FC-200+. Alexa was not happy with the GE saying constantly "I don't know what went wrong" but usually did as instructed.
The GE was excluded. No issues. The new switch was included smoothly.
There are 4 lights. I would like the bottom one (I think this is #1) to be on, blue when the fan is off. I would like #2 to be on with a different color when the 3 speed fan is on low. Ditto for #3 on medium.
I cannot figure out the driver options "Indicator Never, when off, when on, set status LED" or what Normal mode is. Is there an ABNORMAL mode? Using the set status LED seems to turn them on, different colors but they stay on no matter what the fan is set to.
Where can I find help on configuration instructions. Most topics are from 2018 and 2019. I don't want to call HomeSeer for a Hubitat driver issue.
I think those 2018 and 2019 threads would help you. To be honest, it's not a 'five minute fix,' it's a relatively powerful -and complex- setup and it will require some time to learn.
That said, I'll answer your questions to the best of my knowledge and hopefully that will at least make some of the thoughts in those threads make more sense to you.
The neat feature about the HomeSeer line is the status LEDs, which were pretty much exclusive to them until the Inovelli devices were released. (There are some notable differences between the two brands.) All of the HomeSeer in-wall devices (dimmer, fan controller, and switch) have the same general logic around the LEDs, just with a different number of LEDs available, and all are controlled via Hubitat in the same general manner.
Normal mode is when the device is displaying what it's doing internal to the switch (dimmer level, fan speed, switch on/off, etc.) In your case it's displaying fan speed. The opposite of that is Status mode and that is when the switch displays what you tell it via the 'SetStatusLED' commands. The switch will go back-and-forth between the two modes on its own depending on what was last controlled, and as you note the Hubitat driver can attempt to 'influence' that behavior in a few different ways.
The indicator being referenced is the 'pilot light' that most smart in-wall devices have, generally defaulted to 'when off', but you can control the behavior as you've noted. IIRC, for the HomeSeer devices the indicator is only active in normal mode, and not in status mode.
You have to set the Status LEDs individually via the 'SetStatusLED' command. (Note that different drivers have different capitalization of the command. I think the stock HE driver is 'SetStatusled'.) And, yes, the status LEDs will stay lit as you command until you command differently.
You can set the status LEDs according to fan speed as you are wanting, but you will have to do it via Rule Machine. There's no native method to do it just on the device or the driver.
Thank you for the time spent on this detailed and explanatory reply. My last computer programming class was in Fortran. If you are not old enough to know, that was in the late 70's. I am a former "WINK" person and so happy to be with Hubitat. In my view, one cannot/should not have to rely on outside tech to deal with these issues. I equate it to not knowing that tires in a car need air monitored occasionally. HOWEVER, the driver created for the FC-200+ appears to have functions on it which do not function is inappropriate. If they do function, there is no guide for this driver from HomeSeer or Hubitat. If it's a beta driver or a work in progress, it should be so labeled. I am not about to go with a HomeSeer controller to access these functions and even with Smartthings (I have one of those too as a backup), one has to import custom drivers (I think that's what I saw).
Please do not take this note as a lack of appreciation of your response. I have spent over an hour (maybe two) trying to find an answer before I posted my question. I have only used the Rule Machine to program locks/times for door locks. That was not terrible but still took me 10-15 minutes to figure out. So now I have learned that the HS has a 'normal' operation and 'status' operation - but no way to trigger that which is obvious. How long would it take me to find that code and where to put it so I have access to it?? I just don't have the time and the driver options as listed for the FC-200+ are misleading (to me) and incomplete (as I read them) in description.
To pontificate for one moment... This is what happens with open source... It makes the end product ultimately great but no one person is responsible. BUT the end user is not bound to one company's products (with a 4 minute minimum reset time for motion sensors for example).
Apple is a 1 Trillion dollar company because they made the GUI so simple. But they are the poster child for NO OPEN SOURCE ANYTHING (almost). Misleading non-professionals with words that do not make full sense on their face, with no instructions and no help pages for the driver makes it tough (on me). - - pontification off.
Thank you kindly again for your prompt reply and thoughts provided.
Once you put the HS200+ into status mode, it will stay in that mode (which I keep it in all the time.) All lights are blue when everything is closed. (I have another Homeseer in my master bedroom, so I can check doors from my bed at night).
-Top light is white if inside door is open, and blinking white if security door is open. It will blink red if the front door lock is "unknown" (Presumably unlocked).
-2nd light is green if back door is open. It will flash red if back door lock is "unknown" (Presumably unlocked).
-3rd light is yellow if sliding glass door is open
-4th light is cyan if indoor garage entry is open, flashing cyan if garage door is open, white if garage light is on, flashing white if garage door is open and light is on.
-5th light is red if gate light is on (motion detector), and blinking red if gate light is open,
-6th light is white if attic light is on
Eventually, the 7th light will be white if any windows are open.
At some point, I intend to rewrite this piston to include device variables for each switch 1) to make swapping devices easier, and 2) so I don't have to remove "sensor" and "switch" from the device names.
