Problem adjusting Lutron Fan Control speed via Pico w/ Button Controller

[stephack]

@ogiewon

For Hampton Bay Fan Controller the list would be “low, medium-low, medium, medium-high, high, off”

For Lutron the list would be “low, medium, medium-high, high, off”

@ogiewon, unless something has changed recently the HB controller only has 4 speeds.
Low, medium-low, medium and high....and of course off.
I just want to confirm what the Lutron device has so I can create the code properly.
@ogiewon or @clang1, please confirm the exact names for the Lutron Controllers fan speed.

Edit: I am also assuiming this driver takes the setSpeed command with numeric values like the HB controller does. Please confirm this as well.

[clang1]

Attached is the list of speeds from the Lutron Fan Control edit device page:

But:

@ogiewon

Low, Medium, Medium-High, and High. Currently Medium-Low and Auto are not implemented in the driver. In the next release, Medium-Low will be mapped to Medium, and Auto will be mapped to Low, IIRC. Also, On currently sets the Fan to High, regardless of the previous setting. This will be fixed as well, to return to previous speed.

My experience was that using the numeric values did not work. But I did not do any specific debugging/investigation. Unless someone knows the answer already, I can do some more testing later today or tomorrow.

[stephack]

@clang1

Unless someone knows the answer already, I can do some more testing later today or tomorrow.

Let's just ask the all knowing all wise instead.
@mike.maxwell, what are the compatible fan speeds for the Lutron Fan Control device (somehow I doubt they support all 5 listed) and do they support the setSpeed() command with numeric values like the HB controllers?

[stephack]

From google images so I can't say for sure if this is as it appears in the app...looks legit.

This might explain why @mike.maxwell and team have now added the MEDIUM-HIGH option. The HB used medium and medium-low for speeds 2 and 3. I assume the HE team wanted the app to match the driver so they made they added medium, medium-high for the Lutron devices. Kind of confusing to list both on the same driver though.

[clang1]

@stephack

From google images so I can't say for sure if this is as it appears in the app

I can confirm that is how it looks in the Lutron app for me.

[clang1]

It seems that trying to track multiple manufacturers' English-language level descriptions in every app that needs to set speeds will get hairy. Mapping to a numeric level (perhaps with a separate attribute indicating the number of discrete levels) seems more sustainable in the long run. Perhaps drivers could still expose a human-readable speedName attribute if desired (but if this was read-only for purposes of displaying to user, apps would not need to worry about the complexity of which speed names were supported, and how they were ordered).

In other words, knowing that levels go 0 -> 1 -> 2 -> 3 -> 4 is a lot easier than tracking that one device supports "off" -> "low" -> "medium-low" -> "medium" -> "high" while another is "off" -> "low" -> "medium" -> "medium-high" -> "high".

[stephack]

@clang1

In other words, knowing that levels go 0 -> 1 -> 2 -> 3 -> 4 is a lot easier than tracking that one device supports "off" -> "low" -> "medium-low" -> "medium" -> "high" while another is "off" -> "low" -> "medium" -> "medium-high" -> "high".

Exactly. This was why the setSpeed() allowed both string and numeric values. We could easily adapt to a different naming convention on HE. Bare in mind what I said in my previous post was just conjecture. We'll have to wait for Mike to chime in for a reality check.