Installing the app using HPM does not work for me either. I went to install the code directly from GitHub and there appears to be a syntax error in the parent app regarding Done in the instructions not being surrounded with quotes. Once I got past this, I can install the app but it does not function.
I managed to get this working by installing a previous version in a Git commit. That being said. Is there a way to be able to just turn on the bulb to the last known state without specifying the state of the bulb.
Thanks for the report of problems with HPM installation. I figured out that I accidentally uploaded a bit of v4 code, which I'm just working on "internally" at this point. I've restored the contents on the GitHub repo to v3.1, which is what I intended to be the current release (and incidentally, there was indeed a typo in one of the apps that could have caused the errors above; not sure why I didn't see this a while back).
Let me know if there are any issues!
Not that I can think of, unless anyone has found a creative in-app workaround I didn't think of. 
If there is demand for this feature, I could add something to do this. It may require some UI changes, so might wait until v4 where I plan on making a few non-backwards-compatible changes (sorry, people who get annoyed with Rule versions 
) to improve on some things and add some other features.
Thanks @bertabcd1234! I managed to turn on the last known state of the bulb by installing the button controller built in app and just handing this there. I am going through and figuring out my use cases around bulbs and controllers and I will play around with my setup and document what I come up with. Your app has greatly simplified what I was doing so thank you! I am working on a couple of drivers at the moment so it may take me a hot minute to circle back around to this! I will try this fix shortly!
Hi @bertabcd1234. Thank you for all your contributions to the Hubitat community. I recently began working with the DMC, having mostly programmed my Pico’s with ABC.
Would you consider adding Custom Presets on a future release? I have several use cases where additional Pico’s will follow the same mapping, but the current list of pre-built presets aren’t a fit.
Or, having the ability to clone a rule would be a nice workaround. After cloning, I could then change the light/switch that each clone/rule controls.
I won't consider the first since I'm actually going to remove that feature, but it's because if the second thing you mentioned. So, hopefully that will work going forward. If I can, I'm going to see if I can improve cloning so device swap works better, but even right now it should be fine if you choose the "Apply same level and color settings to all lights" option (if you don't, it won't know what setting goes with which lights if devices are swapped; everything else should be fine--but with this option selected, it's not a problem since the setting applies to all lights, and, of course, it's not a problem in the first place for things like "dim up/down" where this option isn't relevant).
1 Like
To clarify, I’m not looking to swap devices. I was asking about using additional button devices (that could be in a different room even.)
For instance, in my home regardless of the button device, button 1 on press is always used to dim a light to 100. And button 5 on press always turns the lights off. So, would there be a way to clone the rules so that configuring dozens of button devices is as easy as just changing the lights they control?
I know that the lights/loads would be different for each button device and that would complicate things, but wanted to make sure you understood my use case.
Isn't changing the lights a device swap?
That should work with cloning or importing now as long as you check the "Apply same color and level settings to all devices" box (and enable this option under Advanced on the first page of the app to make it appear even if you only have one light/device selected; it's otherwise hidden by default). What won't really work as expected is if you don't enable this option, then any per-light color OR CT settings won't carry over to the new/swapped device. Actions like on or off still should, but I haven't tested that much.
I guess the alternative is that you're creating an entirely new app instance or cloning and then swapping devices later, in which case none of this applies. I can see where the "presets" feature would make that easier (my original intent--this was before platform-level cloming), but I'm not sure I'd suggest that as a path forward. Again, I'm thinking of making a new release where app-level device replacements work as expected, which I think will help with this all around, then get rid of presets entirely (and then you could just clone a "base" you want to start from), though I think I already have a preset that does what you describe, at least for,those two buttons.
Hey @bertabcd1234, if I want to use DBC to control multiple bulbs from a single pico (e.g. first push on/up/down/off controls bulb #1, second push on/up/down/off controls bulb #2, et al), is it doable? Been playing with it and struggling to crack it.
Right now, not exactly--it's really meant to control the same light or set of lights (think of actions like "off" or "dim"), but you should still be able to make this work by using the Hubitat scene activation action (with, of course, a scene that had the light or lights configured how you want).
By "right now," I mean that I plan to rework the options a bit in the next version so any "on"-type action doesn't necessarily turn on all selected lights. Still thinking about what that looks like.
I gotcha. LMK if you want a beta tester once you get around to it.
Hello, I have a C7 with firmware 2.3.1.142 and I want control Inovelli bulb LZW42 with a Zooz button Zen34.
I can turn on/off the bulb when I press the buttom but I can't dim up/down when I hold the button. When I hold the button, the bulb go on or off instantly without dimming.
I try also with "Button Controler" app and the same things happen when I hold the button...
Thanks for your help.
Sounds like an issue with the device, then, not the app. To test:
-
Navigate to the device detail page for this device (Devices > your device).
-
Run the "Start Level Change" command by choosing either "up" or "down" (depending on which direction you want to go), then clicking the button to actually run the command.
-
Be prepared to click the "Stop Level Change" button very quickly afterwards (to stop dimming, i.e., what should be done when you release the button as you've configured it in my app).
If the light does the same thing there, then you've ruled out the app as a problem. But I'm not sure what to suggest for the bulb, then. There is a "dimming speed" parameter, but I think that only affects "Set Level," not these commands. You can still experiment with whatever options your driver offers to see if anything changes. If you're using Hubitat's built-in driver, Inovelli also has a custom driver you could try.
You re right! I try on the device (bulb) and the "start level change" is instantanous on or off. I will check with Inovelli support.
Thanks
Hey @bertabcd1234 - any chance of adding hub variable for Color Temp?
1 Like
I'm busy with some other projects at the moment of higher priority, but more variable usage, including this, is on my list.
3 Likes
Thank you for the Dimmer Button Controller. I do have a question regarding its usage. I would like the ability on my Pico remote when I hit button 1 to just turn the lights on. I don't want to set level, color, hue or saturation. Just turn on the light. In my setup, the light will default to the previous state when turned off. I do not mind submitting a PR for this but wondered if you would consider it. Thank you!
I have plans to address this in the future and change the way the UI works a bit. Right now, I'm not sure it's possible.
I think this is just a matter adding an option when you "turn on" to just treat the bulb as a switch. I am going through your code right now and If I can figure it out will submit a PR.
Sure, but I'm working on a new version where the options and UI will be totally reworked, so no guarantee the work you might do now will still be applicable then.
