I recently installed a bunch of Enbrighten fan speed controllers. On setup I selected the GE Smart Fan Control built-in driver. This generally seems to work but there is a mismatch in the speed controls.
There are some threads about similar issues; but mine seems to be different (and those are quite old).
From the device Commands tab if I use Set Speed or Cycle Speed it cycles through off (0) -> low (25%) -> medium (50%) -> high (75%). Whats odd is that high is notably slower than when I use the physical switch on the wall -- if I go press that and check in the Current States the speed is at 99.
The other threads I saw say that the speed is fixed in the fan speed controller -- but it seems that the speed set in the controller don't match what is set in the device driver. Unfortunately the code doesn't seem to be available so I can't confirm -- but this seems to be a bug in the "GE Smart Fan Control" driver.
Can you provide a link to these? Additional context would make this clearer. Thanks!
Additionally:
What hub platform version are you on? (Check Settings > Hub Details to see.)
What exact model of GE fan controller do you have? There are different versions, and it's possible you have a 4-speed model using the 2.4.2 driver that supports only 3 speeds and might be a bit under for at least the highest settings, for now.
Can you provide a link to these? Additional context would make this clearer. Thanks!
I will attempt to; when I included the links in the initial post the forum complained and said I couldn't include links in the post...
Unfortunately when I try now I get the same error:
An error occurred: Sorry, you can't include links in your posts.
There are a few that I found but they aren't seemingly "the same" issue; just giving me enough context that I believe the issue is due to a mismatch in percent -> speed mapping.
What hub platform version are you on? (Check Settings > Hub Details to see.)
Platform Version: 2.4.2.160
Hardware Version: C-8 Pro
What exact model of GE fan controller do you have
I have the Enbrighten 58446 (ZWA4013)
it's possible you have a 4-speed model using the 2.4.2
That seems to be the case here, which is interesting... because when I use the physical buttons it cycles through only 3 speeds as far as I can tell... So that is a bit confusing to say the least
From the context in the other threads although you can set a percent it seems that the underlying controller will "pick a speed" based on the percent; so it sounds like a mismatch here.
Have you tried 2.4.3? It was just released and fixes the one 4-speed model previously reported here (without the actual data from your device, I can't say for sure if it was one; the Device Details table on the Device Info tab of the device detail page would say more).
After the upgrade it is different -- but not what I was expecting. I still see 3 speeds (low, medium, high). But the mapping has changed high is 98, medium is 49, low is 24. So this is definitely an improvement as those are registering as 3 speeds (meaning "high" is actually faster than medium) but apparently there are supposed to be 4 speeds -- but for osme reason it only detects 3.
Yeah, I really did mean that 2.4.3 was just released, so I wanted to be extra sure.
Where are you seeing three speeds only? You'll need to run a "Configure" if you've already added the device in order for them to show up in supportedFanSpeeds, which some apps might read to let you see only appropriate options for your device. I checked, and your model is the exact one that was added to this driver for four speeds and confirmed working by a couple users during beta.
I see it under "Current states" in "supported fan speeds":
You'll need to run a "Configure" if you've already
I have run "Configure" and also "Refresh" but no change there.
confirmed working by a couple users during beta.
I wonder if its an issue because the old driver set them to 3 -- IIRC they had 4 speeds initially but after hitting "Configure" on the old driver it set it to 3 speeds.
Thanks for the details! I don't see any reason one should work and the other not, but maybe it's a browser cache issue. Try a force reload/cacheless reload in your browser if you haven't. It's really only looking for the "Device Id" as you see in the "Device Data" table, and that looks the same for both that you provided -- so I guess really compare that to the ones that are to see if they are the same, too.
For the ones that do have four speeds visible on the device detail page: do they work as expected? (I'm not clear from the above.) If so, the good news is that it should work when you do it from an app/automation, dashboard, or anything that lets you select the speed; just not sure what's going on with the device detail page for you, then.
Turns out its actually a bit more complicated. Even the ones that show 4 speeds in "current states" don't show those 4 options in the "Set Speed" section:
but if I use "Cycle Speed" it does go through all 4 speed options -- I see those 4 in the "speed" of current states as well as can confirm that the physical fan has 4 different rotational speeds.
Try a force reload/cacheless reload in your browser if you haven't.
I did try a private window, a different browser, and a different computer. So this seems to not be a caching issue
Interesting. I'll see if I can figure anything out with the device detail page (doing dynamic things like this doesn't work well, but this particular thing did in my testing).
The good news, as I mentioned above, is that this should work as expected in any apps/automations, any dashboard that reads the supported speeds, etc. I would not recommend the device detail page for day-to-day control of devices, so hopefully you are doing something else for that already -- but it's normally good for testing (except this right now!).
That's odd if the supportedFanSpeeds attribute is populated correctly. I'd again try a force reload (if you're viewing in a browser) or maybe removing and re-adding the device to the dashboard to see if anything helps.
So removing and re-adding the fan to the dashboard seems to have helped there -- I tried it for the fans showing 3 speeds; but those didn't fix.
Definitely seems like some data inconsistency with how the device is stored within hubitat. Is there some other debugging information I can provide to make the debug easier?
Sorry, I'm confused by the seemingly contradictory statements: it fixed the fans with four speeds, but are you saying there's a new problem with three-speed fans (that actually have three speeds) only? If there is any information about what that is above, I must have missed it.
Sorry if that was confusing. I decided to try removing and re-adding the fans that still showed 3 speeds -- and that didn't magically fix anything.
So as of now the 2 fans that show 4 speeds show it in the dashboard and in the status -- but not in the selector of the device details. There are 2 other fans which show 3 speeds everywhere.
I guess the next thing I could try is removing and re-adding one of the fan devices from hubitat to see if that would fix it, any problems with me trying that? (not sure if this being stuck is helpful from a debugging perspective).
Definitely not any problems from the hub side with you trying -- just make sure you remove the device from any apps first (you'll be warned on removal about this), so it might just be more of a pain for you. (The Swap Device tool can make a neat way to hold the device's place in most apps, e.g., with a virtual device, in the meantime if you need to.)
I'd mostly ignore the device detail page aside from the "supportedFanSpeeds" attribute value, which a "Configure" should fix on an existing device; it should be right, and was when I tested, but it's hard to make things dynamically change based on some characteristic of the device. Splitting the 4-speed model out into a separate driver might be the only way to really make that work, which I was hoping to avoid. But if the rest isn't, either, I suspect something else is going on.
A reboot with database rebuild can't hurt to try if you haven't (Settings > Reboot, expand the Advanced section and check the box).
I literally just installed this a couple of days ago and it updated; I didn't think to check for more updates in the last 3 days 
(
