I've been messing around a little bit today and my opinion of everything but Alexa integration is migrating away from 'meh' towards 'hmm, that's cool'. The 'UI Key - Status Button' and 'Scenario' experience button drivers are downright cool.

Control4 Has your balls if you purchase one of their. Come on control-4. Please help me with some infor about how dropout this f**** system o crack them. Control4 doesn't trust the DIYer with composer pro. They will only sell it to dealers.

There are a few others that look promising in the Experience section of the driver library that I haven't been able to check out yet. I wish they publicized these more.

[Edit] One more thing: Looks like Snap has an OVRC driver for C4 in conjunction with their OVRC Pro gadget. If you go to the Snap page for that device, download the C4 driver from the support tab, then add it to a project, you can now add your processor to OVRC. You can also program notifications to be sent to OVRC. Pretty sweet. Winrar 32 Bit Ware. Experience Button - Published 3 hours ago. I guess when I looked this afternoon, it wasn't up yet. Weird though that a verbatim search for 'Experience Driver' only turned up the new RGB driver among a sea of other articles completely unrelated to the new Experience Drivers.

Searching 'Experience Button' returns the RGB article (very cool driver for DMX and Hue, BTW) and a second article on programming a sleep timer using one of the new countdown drivers. No mention of Mockupancy, any specific device countdown drivers, Snapshot, or anything else classified as an 'Experience Driver'. I get that they're posting as fast as they can, but these drivers have been in the Beta for months now.

No one was working on an article for he release? Local source driver - Not sure who asked about this, but the article you linked does helpfully explain in depth how to make a connection from a TV's audio output to a distributed audio system.

Realistic Turf Patch there. Variable programming - I should have elaborated more here. I'd like to have information available >somewhere.

I think we might roll 4Sight in with OVRC. My rationale is that our clients are paying $30-$40/mo for alarm monitoring anyway. We might also wrap both up into a service plan and hide the actual monthly cost behind a multi-year service contract. Visual Basic 6 Microsoft. The OVRC driver is awesome though. You don't need the widget or a pro account.

Just add the driver to the project, enter the MAC address in the OVRC app, type in the activation number in the driver, and it shows up in OVRC as a monitored device that can be rebooted.