The light kit on my fans work as you described and the community integration created a child light device as follows with a Start Dimming and Stop Dimming buttons that worked similar to the way my fan light control shows up in the Bond App itself. The Dim button with a number does not function for my light kit, but the start and stop dimming buttons work. I have them mapped to a pico remote which is mounted of the original light switch that powered the fan and it works fine.
As @matt1097 mentioned, Bond does not expose all 9 speeds. We had a few 9-speeds at our old house and all showed up as 6-speed via the Bond app. Not doubting the HE crew, but not sure if anything short of dark magic is accessing the additional speeds through a Bond integration.
thanks for all the fixes @bcopeland. Have you been able to look at how to allow stop/preset? It's the only gap my use cases have when compared to the community version.
@Hatallica was correct. You do not need to support 9-speeds as Bond doesn't**.
Sorry for the offhand confusing comment. There's even a 31speed fan out there that they still map to just 6 speeds in bond.
**Clarification: They only automatically support 6 speeds, but there are buttons for 9 and ways to do more via the API
@bcopeland but i have an interesting tidbit... I added a 6-speed fan to bond (for the purpose of testing it wasnt an issue specifically with 9-speed fans), hit configure on the bond device in hubitat and that worked. But also now so do all my other fans that were previously not working.
I have not touched anything else.
but with that is a new issue i think: I removed that newly added 6-speed fan from Bond. Hit configure on the parent device in Hubitat, and the child device was not removed.
Hitting refresh I see the 404 error.
@bcopeland is this something you are considering are should I just plan to keep using the community integration? Just curious, as the community integration generates an error about the hub being offline two or three times a day. I have your integration operating my fan and It works great and it hasn't generated any errors since I started using it. So I would like to switch totally to the HE integration. Without the CloseNext and OpenNExt commands, however, I will need to stick to what I have.
I lost all control of my fans I believe after the last update. I removed the app and started from scratch. Added the bond IP and token and now when I go into configuration I get no devices. Log below
This is the main thing preventing me from switching over.
Also missing is dimming stop/start for those of us who can't set a level, but I must admit that I've rarely used that in the bond app (and never in Hubitat) and can't necessarily think of a real use case for Hubitat, but nonetheless, it is a feature in the community driver that didn't make it into the built-in driver.
I use the Start/Stop dimming in the community Bond integration to control light dimming of my fans from Picos, using RM. Works nicely, so it would be great if those commands were supported. Button 2 and 4 on the pico are set to start dim up and dim down, respectively when held, and stop dim when released.
@!bcopeland I lost all control of my fans I believe after the last update. I removed the app and started from scratch. Added the bond IP and token and now when I go into configuration I get no devices. Look at logs below
@bcopeland any chance we can look forward to this in an upcoming release? It’s the one thing I’m missing and while I’d like to stick with the native app since it removes polling, I also need this feature…. Thanks!
I have the same problem. I have one fan that has up/down lights. Bond app shows separate controls for both lights. It also support the auto dimming of those lights individually. But the Bond integration on HE does not support the method of dimming and only has on/off for the up light.
I second the request for working stop function for the blinds.
The Bond app has a stop button. It works.
The HE rule machine dropdown in the shades offers stop, but if selected, nothing happens. (spent a good 45 minutes trying to figure out what I was doing wrong until I searched and found this thread...)
Presets and support for TDBU and all that would be nice, but with a stop button and a stopwatch, we can work around that given all the options Hubitat has. Without a stop button I think I'm SOL because all the other functions Hubitat offers are not supported by the Bond hub...(and I barely got the bond hub paired to my shades - had to use a different remote than bond recognized to get a press and hold function)
