turls

I added commands for the new sharpening that was exposed in November or December. It's my daily driver scaler so I do keep it up to date when they add new features. They have also added features for me. Two bug fix releases in the last year were thanks to issues I discovered (The Nvidia shield issue and the one after it). I also got them to allow you to change the color of on screen messages. The new remote adds test patterns, saving config, HDR setup, auto aspect enable/disable, and input aspects for some additional formats. Of them the following are supported via serial:
Test patterns, Save config, Enable+reset auto aspect detection.
I refrained from exposing save config as it seems like something you would use infrequently. Same thing for test patterns. The Enable/reset auto aspect detection would be trivial to implement. The following are not exposed via serial at this time:
Auto aspect disable, HDR setup, NEW aspect ratios.
If there is need/demand of those things I can add them pretty quickly. I have a driver I'm trying to get substantially finished this week but will free up a little after that. 
I have no relationship with Lumagen other than being a customer and developing the driver (and calling support perhaps a few too many times) so I can't really comment on the PIP situation. 
 

Here is a writeup of features. I've been using it for two years, I've had customers for a full year. Since I wrote this I've added the new sharpening commands from the fall firmware release and increased the number of inputs to 10 to account for the additional virtual inputs and the new hardware with 10 inputs.
 
The preferred setup for Lumagen is to have all sources connected directly to the lumagen and then connect the lumagen to your preamp/processor/reciever. This creates an issue that you don't get any volume or mute feedback on your screen because the preamp/receiver is out of path. The driver has property enabled features called  "Auto Volume" and "Auto Mute" that will grab the volume level and mute state from the room the lumagen is located in and use them to trigger a message on the display. No programming required. If that doesn't work in your configuration, there is a mute on/off command available in programming and a message can be written to the display to indicate the volume or mute state via MESSAGE1 and MESSAGE2 variables.

Supports IR power on, set the power method to "IR" and bind an emitter to the driver, this is only needed in some rare condition.

The driver supports all remote commands fired from programming and also exposes almost all of the lumagen video attributes as variables. This allows you to alter Lumagen configuration based on something in your environment such as moving an anamorphic lens in and out or selecting a video game source that needs certain latency (game mode) or video configuration. You can also automate any aspect ratio, zoom etc changes. The state of video being displayed by the lumagen can also be used to trigger outside events. Every time the video changes aspect ratio, resolution, refresh rate, color space etc, the variables are updated and via standard C4 programming any type of automation can be triggered. We have some customers that change color space settings on their Sony projector based on the input color space. I believe they are using the Lumagen for DTM and they are putting the Sony in the proper HDR color space without triggering high lamp or something like that. We have other customers that use the aspect ratio to trigger automatic masking systems and anamorphic lenses. Care must be taken that sources that change aspect ratio frequently do not cause mechanical malfunctions. I prefer to select when my anamorphic lens is in or out of path so I automatically change output aspect ratio via a memory setting when I move the lens in and out.

An arbitrary message can be written to the display to indicate the volume via the QUICK_MESSAGE or MESSAGE1 and MESSAGE2 variables. Message persist is the amount of time any of the onscreen messages from the driver will be displayed, 1-8 seconds. With more recent firmwares, the lumagen supports setting the colors of the messages. This is configured with RGB hex codes similar to HTML. The entire set of "standard" computer colors and hex codes are added as well as the ability to define up to five custom colors. Alpha channel or transparency is also supported. We have a customer whose preamp has a feedback driver but no on screen display and they write a display message when their audio format changes as they like to know what mode it's in.

Commands

The following commands are supported via programming.

Mute On - Display Mute
Mute Off - Clear display of Mute
Select Input 1-8
Select Input Aspect Ratio NLS, 4:3, 4:3NZ, LBOX, LBOXNZ, 16:9, 16:9NZ, 1.85, 1.85NZ, 2.35, 2.35NZ
Select Output Aspect Ratio O16:9, O2.35, O1.33
Select Memory MEMA, MEMB, MEMC, MEMD
Select Resolution 480P, 540P, 600P, 720P, 768P, 840P, 1080P, 1080I
Send Generic Command - Commands not covered by above features
Send Darbee Enable/Disable, Mode, and adjust value up and down in increments of 1,5, and 10.


VARIABLES

All feedback is handled through the device variables. The "Debug Action" will display the state of these variables at any time regardless of the setting of debug on/off in the driver.

Note: These variables are all read-only, and changing the variables' values does not cause the Lumagen to change state I.E. setting the INPUT_PHYSICAL variable to 03 does not cause the Lumagen to change inputs. You must use a command (above) to do this. If you want one variable to change another, for example when a source with two way is powered on manually you want the lumagen to auto switch you can fire the input command from the power state variable on the source.

Variable Value
------------------- -------------------
INPUT_PHYSICAL Selected Physical input 1-8
INPUT_LOGICAL Selected Logical input 1-8
INPUT_CONFIG_NUMBER Selected Input configuration
INPUT_ASPECT Input aspect ratio I.E. 178 is 1.78:1 or 16:9
INPUT_RATE I.E. 23 = 23.9 FPS, 24 = 24FPS, 60 = 60FPS
INPUT_RESOLUTION I.E. 1080 for 1080P HD, 2160 for 4K
INPUT_MODE P/I/n Progressive, interlaced, or no input
INPUT_3D_MODE 2D / Frame-Seq / Frame-Packed / Top-Bottom / Side-by-Side
INPUT_DYNAMIC_RANGE SDR/HDR
HDR_MIN Minimum Luminance of HDR signal
HDR_MAX Maximum Luminance of HDR signal
HDR_CLL Maximum Coherent Light Level of HDR signal
INPUT_STATUS No Source/Active Video/Internal Pattern
NLS Normal or NLS for Non Linear Stretch enabled
MEM A / B / C / D
OUTPUT_STATUS 000e - Binary field, needs better decoding
OUTPUT_3D_MODE 2D / Frame-Seq / Frame-Packed / Top-Bottom / Side-by-Side
OUTPUT_MODE P/I Progressive or interlaced
OUTPUT_CMS_NUMBER 0-7
OUTPUT_STYLE_NUMBER Selected output style 0-8
OUTPUT_COLOR_SPACE REC601 / REC709 / REC2020 / REC2100
OUTPUT_RATE I.E. 23 = 23.9 FPS, 24 = 24FPS, 60 = 60FPS
OUTPUT_RESOLUTION I.E. 1080 for 1080P HD, 2160 for 4K
OUTPUT_ASPECT Input aspect ratio I.E. 178 is 1.78:1 or 16:9
OUTPUT_ADJUSTED_ASPECT Aspect ratio from AR detection I.E. 178 is 1.78:1 or 16:9, Can be overriden by user forcing aspect ratio with sticky.


These variables should be writable. The specified action will occur immediately after updating the variable. The message feature could be used for several things. For example, if the customer has a soundproofed theater you may want to write a message when their doorbell rings or security alarm goes off. You can safely write to the variables at any time, if the lumagen is in an off state the commands are silently discarded (so you can be lazy programming and fire the dorbell message without regard for if the theater is in use for example).

Variable Value
------------------- -------------------
VOLUME_DISPLAY integer will be immediately displayed as volume
QUICK_MESSAGE string will be immediately displayed as a 1 line message
DARBEE_ENHANCE integer value of 0 - 120 for darbee enhancement
MESSAGE1 string will be stored for displayed as line 1 of a 2 line message
MESSAGE2 string will be displayed as line 2 of a message. Writing to this will trigger display of line 1 and line 2

I've developed drivers for so many media players and have tested so many in the past 20 years.
Kaleidescape is still my go to if you can afford it as it provides you with a true cinema experience.  The quality of the videos, the feedback you get allows you to programatically adjust screen masking, projection modes, lighting (eg when the credits roll).
If you can't afford it (or justify it) then Zappiti is my low end choice.  Bang for buck.  Plays every codec you throw at it.

hi TundraSonic,
Sorry we did not get an inquiry from you, but are glad to respond to your question.
Axxess has several devices that could be used for controlling and dimming Christmas Lights, particularly in the context of a Control4 project.
The Axxess Lamp Dimmer (LD) https://www.axxind.com/smarthome/lamp-dimmer/ you mentioned can certainly be used to dim a load that is driven by line voltage (as opposed to low voltage). No pigtails required. In fact you would simply install it inline in the cord that feeds your Christmas lights with a unique crimp connection. See video on the page link above. Stated load limit is 250W for incandescent, 100W for LED.
If you are driving LED Christmas Lights that are fed from a low voltage power supply, the Axxess Lamp Dimmer would not be the obvious choice to dim those lights (unless there is a power supply already inline that accepts phase cut dimming inputs, some of which are referred to as Triac.)
You would be better served by the Axxess DCM1 Single Channel dimmer which can dim up to 100W at 12V or 200W at 24V.  https://www.axxind.com/smarthome/dimming-control-module-1/
If you have more than 1 channel to control, you could use the Axxess DCM4, a 4-channel dimming controller. Each channel can be dimmed to its own level, and the 4 channels can be fed from a single power supply, or from a separate power supply per channel. https://www.axxind.com/smarthome/dimming-control-module-4/
If you are visually ambitious, you can use the Axxess DCM5 dimming control to dim RGB, RGBW or even RGB WWCW CCT LED strips.
https://www.axxind.com/smarthome/dcm5-led-controller/
Control4 drivers are available for all these Axxess devices.
All of the mentioned Axxess dimming controls respond to ZigBee Pro wireless commands.
Axxess devices for integration into Control4 products are sold through Control4 dealers. You find the closest one through the Control4 website.
For technical questions feel free to email support@axxind.com

Just a note for those who didn't know, with the new M1 Computers you can run iOS Apps.
Just DL'd the iOS app to my MacBook Pro, and I must say it's very snappy! It runs like a native app.

We are not doing any sales this year.

Normally numerous drivers are on sale for Black Friday or Cyber Monday.  I haven't seen any this year.  Anybody seen anything?

The basic layout for programming I was playing with to test them, is to essentially have a "follow me" toggle experience button, each room having an "occupancy" variable to act as a container for the roomme variables as they come in. When toggle is active when roomme sends entry events, I use that to set the room variable true, but also use the entry to set the others (only other roomme interior rooms) as false (other than the garage for example) so as not to rely on roomme's sometimes inconsistent exit events. The exit isn't as well defined as the entry even if you calibrate it multiple times. 
I have noticed though once in a while even if you're sitting in one spot under the sensor it will still show that you left the room and re-entered. 
 
Then you just tie light loads to the variables with the conditional being the experience button is on. You could just tie that to a keypad button or something if you wanted a physical button somewhere to toggle. 

From a dealer standpoint I would definitely pass. This would only be for clients that are already technically inclined and understand the difference between experimental and stable, third party vs certified etc. I'm enjoying playing around with them as well as a couple of my co-workers. For a programmer or anyone on this board I would say I probably recommend them for a personal system in conjunction with other sensors. I have three in my house at the moment but I feel like it really works best as a percentage of overall sensors. They would really add to security and motion sensors, and actually probably best used as a fallback for motion lighting so that the room knows that someone is still there (motionless/sleeping for example). For room entry it doesn't seem to be super consistent (sometimes 20ms, and sometimes like 2s) and seems like it depends on if your phone has a wake lock or not. So it shouldn't be relied on for lighting or anything that requires consistent instant feedback. 

The only constraints limiting the DS2 or any other 3rd party door station from taking advantage of all the new features are from a hardware perspective, but we are working with the DS2 supplier to help them get their firmware and driver updated to utilize these some of these new features.

ps...the latest CarPlay will show the garage door.  and it only shows when close your home. 

Best bet might be to use Varietas' Homebridge app.  You can then add devices to the Home app, and they will show up in your dashboard...I even have the garage showing in CarPlay when I come home.
 
 

Vacuum mode is nice. Press - takes a snapshot of current lighting state, then turns on all lights.  When done double tap to return to last state. 
 
 

Chowmain - Internet Rebooter Driver for Control4!
As integrators there are times where we cannot replace ISP provided hardware (eg Cable modem or NBN modem). As such we are reliant on the uptime of these devices and when they go down they take down many of the devices in the home. The Chowmain internet rebooter driver allows reboot of modems, routers, switches, access points and other networking equipment directly from Control4's built in relays.
The idea is that the driver will monitor a specific website periodically and if it fails to retrieve the content from that website multiple times it will execute the reboot sequence. Note that this driver requires wiring of Control4's relays upto the power supplies of the networking equipment.
Note Chowmain takes no responsibility for damaged hardware as a result of poor wiring.
Features
Monitor any website for internet uptime (default is google) Power cycle up to 4 devices with different orders, delays and timing. Online and offline events means that you have the ability to power cycle via other means should you choose to. Experience button will allow a user to monitor their internet connection (online / offline) as well as initiate a manual reboot if required (They will need to confirm reboot with a secondary press)
FAQ

What is the point of this driver?

As integrators there are times where we cannot replace ISP provided hardware (eg Cable modem or NBN modem). As such we are reliant on the uptime of these devices and when they go down they take down many of the devices in the home. This driver is designed

Is there anything we need to be made aware of?
 
The experience button on navigator requires a double press to reboot. This is to provide a confirmation to ensure that you don't accidentally initiate a reboot sequence. This driver only monitors connectivity to an internet website and performs the reboot sequence based on connectivity to the website. It does not cater for other network related issues such as DHCP server failures. You can however manually initate the reboot sequence through double pressing the experience button on navigator.
How do i wire up the relay?
 
The driver allows upto 4 devices to be connected and power cycled (eg a modem, a router, a switch and an access point) If you are using a Control4 relay (eg on a controller, Z2IO or IO Extender) then split one of the wires (eg positive) and connect one side to COM and the other side to NC for each device
Does this driver have a safety net?
 
This driver will only initiate the reboot sequence after the 'Number of failed tries before automatic reboot'. Basically it will poll once every 'Website Poll Interval'. If it fails it will retry x number of times every 10 seconds and if it fails it will then perform the reboot sequence. The 'Automatic Reboot Interval (minutes)' limits the amount of reboots to ensure that you don't get into a reboot loop due to something like an internet outage at the exchange or ISP.
How do I find out more information about the driver?
Please see the links below for more information about the driver.

Chowmain Website

How do I buy the driver?
This driver can be purchased from our distributor driverCentral.

Download Driver / Purchase Licence

Do you provide trial licences?
All Chowmain drivers for Control4 come with a 90 day trial.

Who do i contact for technical support?
We have two support desks. One in Australia and one in the US. Click on the link below for details.

Support

New update to the C4 app today seems to load faster (with better startup feedback), but shortcuts still don’t work. Even with the app already loaded and connected they don’t work. Hoping this is resolved and the shortcuts become functional.

And...still no HBO Max on Amazon or Roku.  And now add Peacock TV to the list of stuff that doesn't show up at launch on either of those.  So with streaming, you still get the platform / provider wars where the users are pawns, and you can't even skip commercials.  And in the Control4 ecosystem you give up a lot of control as you always have compared to, for example, DirecTV.  Can we go back to linear TV and DVRs now?

I just wanted to point out to everyone that @alanchow has made an addition to this driver to allow you to send info to Control4 by hitting a web URL.  This is revolutionary as it allows you to send information to Control4 from other systems or other APIs.  In the past this was not easy to do other than using @RyanE's WebEvents driver.  There are endless applications for this.  Thanks Alan!

We worked on fixing the other bug and ended up creating another I guess. We tested this for a full weeks without this issue coming up. Not sure what you are seeing here. Maybe a reboot is in order for you too. 
 
In theory you shouldn't have to mess with your API key or reselect the system if everything was working before the driver updated. Emphasis added... If the driver was in a non-functioning state where the system wasn't selected it probably didn't update correctly. I'm still not sure why it was getting in that state before but there are a lot of factors. It seems a reboot of the controller fixes most issues if the update process doesn't work. 
There is a UI bug I'm trying to track down in composer where the drop downs are not showing what was selected. You can click off the driver (on to another driver) and back and it will be set. Weird. 

For anyone who lost their bindings add and remove a space from the API key. If you only have 1 controller on your system there is no need to even select the system. it will work whether your system is selected or the box is blank. The only time you need to use that system drop down box is if you have more than 1 Rachio controller on your account. 
If after that you are having issues post up debugging logs and we will reivew them. 

Exactly, security motion sensors will not do it, especially not ones powered by battery.  However, battery powered sensors can work if they are ZigBee.  The Nyce Ceiling Motion Sensor has been almost flawless for me for years.

Personally I think motion with the advanced lighting timer driver is the best. I have about seven rooms in my house that all function off motion and have time of day and different scenes triggered and even different things occur on the weekends vs weekdays. It's very cool. for example during the week when you walk through the living room midday the lights don't turn on but on the weekends when you walk through the living room midday the lights turn on. That was a wife request. So I really like that one. Next step for me on light and motion is tying in holidays. So I can run alternate AKA weekend schedules on holidays when we are home.

and I think I only have about two more rooms left where I actually want motion to occur.

If I open the app and its already on the SXM favorites it will usually load a blank list. Then I just switch to channels and back to favorites and they are all there.
Is this what your seeing?

They are working on an update

The beeping noise is the audio calibration for the mics in the touch screen. 
 
go to intercom - settings and turn off echo calibration. 

This and if you have lots of Windows, doors or whatever, use the relatively new Domosapiens Security Enhancements Driver which allows you to create Zone Groups so that one sensor can be set to tell you if any window is open, one can tell you if any door is open etc.  if you have any other Domosapiens security driver anyway, you don’t need the Enhancements driver as they have Zone groups built in.