Does the Sengled remote send "released" events? I don't have one and don't know what it supports. The app shouldn't warn you if it doesn't, though it's possible they're supposed to and it's just not working (which the app wouldn't know). The "Events" button at the top of the devices detail page will give you recent history.
It is supposed to, and I can issue them from the device page, but it doesn't look like it is sending them when buttons are actually released. I'll experiment more tomorrow.
1 Like
Tested. Apparently not. It sends "Held" over and over every second or so.
I tried using "Dim up" and "Dim down" on buttons 2 and 3, for the Pushed action AND the "Held" action, and this works, if the light is already on. But I can't press or hold the "up" button to slowly turn on the lights (like I can with a Pico). The setup screen says "Dim Up will work for any lights "...that are on when button 2 is pushed".
So if the light is not on, this won't turn it on. Is that correct? Is there any way around that? I tend to use 75W or 100W equivalent bulbs instead of 60W, and then normally run them at 50-75%. It's jarring to have to turn it on full before I can dim it back down.
Any solution? I'd definitely get more of these (just $10.99!) if I could make them work more like picos, but without "released" events, and/or a way to do something different for "pressed when off" and "pressed when already on", they're not very useful.
1 Like
Hi, found this app and now trying to use it with Ikea Styrbar and Ikea bulb.
Just wondering is there any possibility just turn lamp on in it's last stage (before it was shut down)?
This was not a use case I designed for, though I want to incorporate it into the next major version. It might work if you just choose "Set dimmers/bulbs to..." and just don't provide any values, including level, but I'm really not sure if/how that case would be handled at the moment. (You could use a variable and maybe keep that set to the last/desired level...)
1 Like
Hello,
New Hubitat user here and have this setup with my Hue bulbs (via CoCoHue) and Pico dimmers, and it works nearly flawlessly in two of the three rooms I've configured so far:
If I press and hold the dimmer (configured with the Fast Pico (5-Btn) with startLevelChange preset) in my living room or bedroom it functions as intended, i.e. continuously dimming until the button is released. If I use an identically configured Pico with my office Hue lights, as soon as I push either the up or down dimmer button it will slowly ramp to either 0 or 100 depending on which was pushed. It will not stop that process when the button is released as with the properly functioning living room and bedroom Picos.
I'm guessing that this is either a software bug somewhere in my Hubitat setup, or possibly that the Hue bulbs in the office are somehow incompatible here? I want to say that at least one of the bulbs I have in the office is one of my oldest 1st/2nd gen color Hue, since RGB isn't a big priority there.
I might try manually changing the settings for that button event to "Dim up until released" (or down) instead of relying on the presets to see if that helps; it's possible they missed something. They will likely be going away in the next major release now that app cloning is available, though existing setups will continue to work; but this will require some re-thinking of the app's internal settings.
You'd see something like this on the configuration page:
2 Likes
This was regarding adding an option to set color temp with a variable. I’m NOT raising this as a nag, but because I’m wondering, in the current version of DBC, what CT level is used when DBC turns on a bulb but CT is blank in the app parms?
I’m asking because I have separate automation that presets CT based on a specific circadian rhythm in our home, but I noticed the rhythm is interrupted by a mid-range CT every time the bulb is activated by DBC. Odd behavior I’m trying to chase down.
Any ideas? Logs available upon request.
Very honestly no idea and I'm (still) thinking about reworking all this anyway..,but if you turn on as much logging as you can and point me to where the lights actually get turned on, I should be able to dig to the right spot of the code and find the answer. 
Off the top of my head there shouldn't be any "defaults" here, so it's probably something the device is reporting and the driver might be doing, but I can't say for sure.
Robert, the logging below isn't super granular w.r.t DBC, but I'm hoping it helps narrow it down some. Thanks in advance for the help
Those are device events, not logs, though FWIW I don't see any commands sent by DBC in those. I would need output from the app in the Logs page of the UI.
@bertabcd1234, appreciate you pushing me to look deeper into the logs --> mystery solved and from a source that was the last place I looked.
In case anyone has the same kind of problem, here's what I learned. It turns out that group devices (as in, a virtual device created by the Groups and Scenes built-in app) does not inherit prestaged CTs from its member devices, even when the group device is of a bulb device type. Sure enough, there is no prestage command (legacy or current) available to a group bulb device. And if you try to add such a device to a presetColorTemperature command in RM, the action will convert to a broken action immediately. I don't know if the same problem exists with preset-level, but I suspect that's the case too.
So when DBC was activating a group (without the preset CT), it was interrupting the circadian rhythm that we otherwise manage centrally for our home across all light bulbs.
Eye-opener for me -- hopefully others can avoid the painful lesson I went through.
EDIT: And P.S. Robert, I’d still love it if you could add a CT variable to DBC. LMK if you want a beta tester for your revamp.
2 Likes
Not a big deal, since the child instances can be cloned after setup.... But all the presets are for 4- and 5-button devices, when 2-button devices (a.k.a. ordinary dimmers) are really common. Think you might consider a preset where pressing turns on/off, holding changes levels, and releasing stops level change?
1 Like
I was actually planning on getting rid of "presets" entirely since app cloning (new since that feature was introduced in this app) would let you do nearly the same with whatever "presets" you want for yourself.
Hi. I bought the hue dial scene button. It has 4 buttons and a dial. Is there support for the dial please? I noticed that in the apps there are button nr5 and nr6?
Thank you
This app does not need to "support" any particular button device; it reads the capabilities and attributes, including number of buttons, from the device (or you can override it in the app, I think?). Then you can set it up in the app however you like.
I don't know how I never saw this app before.
Something I'm doing in RM which is sort of a PITA I wonder if would be easier to do with this.
Use case:
I have a couple pico's and fan controllers. I have it set up to step the fan speeds up and down based on how many times you press the top/bottom buttons..
The fan would need to support "Set Level," which some fan drivers don't (in favor of fan-only commands), but you can certainly try it and see if it works for you.
1 Like
I don't see a toggle light as one of the button action options. Can this be added? Would be useful on single button device which I want to easily program to also dim on hold.
That option will be there when I get around to revamping the app and UI, which I've been (slowly) working on for sometime. I really didn't have that kind of automation in mind when writing this app, and it would probably be easy enough to set up with plain Butron Controller or another option in the meantime.
