Thanks for pointer. Took a few hours to read all the info on virtual switch & CoRE to set up correctly with webCoRE so mine is working now to control Fan turn on/off via Alexa. I only did one virtual switch for fantwo speed as I’ll wait for ranga to finish his smartapp for all functions.
hi. it’s my first time messing around with the smartthings platform. I created a smart app the sort of bi-directionally controls a virtual dimmer to allow google home have an indirect way of controlling the fan. (0% = off, 1-25% is fanOne, etc)
Anyway, it’s working well, but i’m wondering if it’s possible to expose this fan as two dimmer switches (light and fan) rather than a single device? Feel like that would be a more elegant solution.
Any pointers would be great.
Welcome to SmartThings! This device is based on the manufacturer choices which currently is a combination of both light (which is dimmer level) AND fan speed which is multi switch on-off control. You may be interested however in testing your app with another fan only speed device which is dimmer level type control such as the one I use by @ChadCK Z-Wave Smart Fan Control Custom Device Handler on a GE 12730 Z-Wave Smart Fan Control or Leviton VRF01-1LX designed specifically for motor control via dimmer style control.
It is the latest available but there are exciting changes coming. Unfortunately due to GitHub issues right now with device handlers it is a little challenging collaborating the code but I’m sure SmartThings will get that worked out soon.
@stephack is coding out the new parent/child functions that recently got announced and it will really make this handler easier to use with smartapps as well as the mobile app because it makes the fan speeds available for independent control by all built-in smartapps without the need for a custom app like CoRE. Right now the light is the only directly available control item for built-in smartapps.
It’s coming soon
I got all 3 of my fans switched over to these receivers this weekend, and I just wanted to say a big “THANK YOU!” to @ranga and @dalec both for discovering the parts ordering process and for the almost perfect device handler!
I say almost perfect though because I’ve observed a couple of odd behaviors in the device handler;
Firstly, the light dimming seems to bottom out at 20%, with setting the slider from 1%-19% showing in the recent activity as “…set to 20%” regardless of what setting below 20% you slide to. Didn’t know if this is a low-end hardware limitation of the receiver or of the code? Thoughts?
Secondly, and this is just a personal preference/request, but I just installed these in three bedrooms where the canopy lights of the ceiling fans are the main light sources for the rooms, and so I’m probably going to tweak the code to make the light the main on/off tile and also have the light show its on/off status in the “Things” list view along with a toggle there. But it would be awesome if there were (and I don’t even know if this is possible with custom device type code) a way to choose between having the light or the fan as the main tile in the device’s options…?
This is alpha code right now. I am getting ready to release beta later today with all the Stephan modifications. It is certainly a good feature to request to be able to choose which preference you want to have as the main tile but with the new composite feature of the device handler you might have a different request. I think what might be better to have is the ability to choose which child devices show up in the Things view. Play around with the new handler and see what I mean.
I believe this is a hardware limitation. When setting the light level (using either the remote control or the app) the controller reports back to the ST hub using the zigbee protocol…either way it bottoms out at 20%.
As @dalec stated, you would need to get a feel for the new component setup. If you need to show them on the main Thing page, there is only one line of code you would need to edit. Easy change you can do to customize.
OK I got the latest just posted. I am starting a new thread just to make it easier to keep the development changes updated at hopefully a faster pace and to take some of the pressure off @Ranga as he is getting busier. This is going into BETA and it has taken on a new look using the composite (child) device feature that just got released.
We incorporated your advice in the beta release @dalec just posted. It now shows both the fan and light as 2 separate controllable options on the Thing list. We left the light control options in the fan thing as well. That way you can control everything from the Fan Thing but still have separate light control available from the Thing list. Hope you like it and thanks for the great suggestion.
Sorry to hear that. Unfortunately we are going to need a lot more info from you to help. Was it paired to another controller before or is it brand new out tof the box? What else have you tried and what errors if any are you getting?
Please provide as much detail as possible and I’m sure someone here will have some advice for you.
My device is new I just bought.
My device work very well with remote TR227A.
Was my bad, I tun ON/OFF by remote but the correct way is by switch.
Now is perfect.
Great. Let us know how you like it, if there are any bugs or if you recommend any features/changes. It might take a while to get implemented but we will do our best to make this better as needed.
Either way should trigger a pairing in SmartThings but the sequence of steps is very important to make sure you start with mobile app “+ Add a Thing” THEN cycle power, not the other way around. And if you use the remote use the large button at the top of the remote not the Fan toggle button. However for sure if you remove power to the the device with the switch or the circuit breaker will also allow for SmartThings to discover the device for pairing.
QUESTIONS/COMMENTS should no longer be posted here in this DEPRECATED Alpha thread but over in the current BETA version for support
[BETA v0515] Hampton Bay Zigbee Ceiling Fan/Light Controller Please click the link to transfer over to obtain the latest device handlers and support.