Dr. Venkman

Did you try rebooting the dimmer/keypad?
15 taps on the top button. Hopefully a reboot does it, and they aren’t damaged.
Edit: Ha…you’re faster than me. 

@Denis, connections in the driver for a garage door proxy would be very cool. Though obviously not completely necessary, it might allow people to slot a Garadget into their project without disturbing any existing programming.
FWIW, I submitted an inquiry on Garadget’s website while I was installing mine, and Denis emailed me back and answered my question very quickly. (Denis, if you’re curious, I was the dummy that asked about getting the terminal to bite on the wire).

Sure. It's the Garadget for Control4. It's a new product of theirs - just started shipping in January. I've only had it a few days, so I can't vouch for it as a long-time user, but it seems really promising so far. My dealer was at my house in December and mentioned that he had heard it was coming out, so I pre-ordered (I had never heard of them, but he seemed confident enough in their products that I went ahead and gave it a try).
A little background on my setup: I've got three Chamberlain Security 2.0+ openers - I liked the MyQ integration just fine. The controls worked great until it broke. I didn't love the infrequent polling (I had thought I wanted to be able to program off the opening of a door). I added NYCE tilt sensors to try to improve the polling, but I never got them to work reliably.
The Garadget appears to solve both problems, with the only issue I've found so far being the lack of a door proxy described above (though, again, it's early).
A little about the Garadget:
It's a little round disc, about the size of a hockey puck - it seems really well made. It mounts (with an adhesive pad) to your opener and points a laser at the garage door. A reflective sticker is included for the door. It's powered by a micro USB cable that needs to be plugged into an outlet (the power supply is included), so hopefully you already have an outlet on the ceiling right above your opener. In my case (and yours, I would guess) a Security 2.0+ adapter is needed. I bought the one Garadget sells, but you could make your own if you like to solder. Wires run from the terminal on the back of the Garadget, to the push-button adapter, then to the opener, and the Garadget simulates a press on the opener. It connects to your network on WiFi (all local, no cloud), and C4 speaks directly to the Garadget device. It took me just a few minutes to configure and install the device, and it took my dealer about 5 minutes to add the driver to C4 (the driver is a free download from Garadget's website). The reporting of the door's state seems pretty much instant, and (so far as I can tell) has been accurate and reliable. As mentioned above, the driver creates an experience button that shows the state (open, closed, opening, closing), and you tap on the experience button to open/close. Once I sort out the programming I had in place on the pre-existing garage door proxy, I think I'm going to be really happy with it.
If you want pictures or have any questions, let me know.

I recently added a Garadget to control our garage door (after not doing anything for a while after MyQ broke).
I like it a lot - it’s quick and smart, has good variables and programming options, lives only on the local network, but I’ve got one problem I’m trying to solve. 
It appears to be an experience button that it uses for control (and to convey the state), rather than a more traditional garage door proxy that would be connected to a contact sensor. It works very well, and I like it for the most part, but this means it doesn’t show up as a door for things like the security light driver or the garage door monitor.
Per my dealer, it doesn’t have contact sensor connections available to report the state to a garage door proxy.
Anybody have what they think is the best way to get back the functionality of those other two drivers that monitor the state of the pre-existing garage door proxy? I could blow away everything tied to my existing garage doors and do it all in programming off the new one, but that seems like a lot of work. 
Would it make sense to leave the garage door proxies I already have and program the Garadget to set the state of those proxies every time it opens or closes?
Apologies if I’m off on my terminology.
Thanks. 

I just tried it - it works!  Powered off my phone and turned lights on and off.

Yes, so long as you've configured the LED to "Follow Connection" in the keypad's properties (the LED Behavior drop down).
You mean if the scene is not bound to the button, but there is programming on the button to activate/deactivate the scene?  Yes, you'll need to set the LED to programmed and then create the programming to have the LED do what you want.
I would vote strongly for binding the scenes to the buttons (and having the LED's follow the connection).
You don't have to do any programming on the button at all. Press and hold functionality is automatic for dimming The ramp rates for your scenes stay intact (though this may be the case if programmed to turn on/off, I'm not sure). I believe that you can also press the button once to begin the ramp up/down, and then press it again to stop it (similar to the functionality on a dimmer). You don't have to do any LED programming. It probably gives a bit quicker response, and it's probably a little more reliable. The downside is that you need your dealer to add it (also, you can't see it in composer, so keeping the keypad buttons named properly or documenting the connections is important).  I've made my peace with that, and there are a few workarounds to let you do a few things without bothering your dealer just for a couple of connections:
If you just want to move buttons around from within a single keypad, you can reconfigure the keypad in composer and it will move the connections from one button to another. If you want to remove a connection, you can do the same, but just not map the connection you want to remove over to the new configuration When I added some keypads and didn't know exactly how I wanted them set up, I created a few empty scenes and had my dealer bind them to the keypad buttons.  That let me tinker with the underlying scenes over time, and the binding was already there. I have also programmed a couple temporarily, and just waited until the next time my dealer was in the system to have him make the connection.