RAV

Sync scenes - the device is told to store and pay attention that when Director broadcasts Scene 128 for example (which corresponds to Downstairs All) - then Kitchen Island you go to 25% over 2 seconds, Counter 38 etc...

This avoids popcorn affect, where lights get the command at varying times, and Director doesn't have to send a command to each lighting device, but sends 1 broadcast command.
(I looked it up, each lighting device can be part of 32 scenes, and systems can have 1000 scenes.)

24 minutes ago, South Africa C4 user said:

I am experiencing a very weird and annoying bug on OS3.4.2.  It seems to be a bug with native C4 lighting (and maybe just the Advanced Lighting Agent).  I am regularly finding that when programming executes an Advanced Lighting Scene (eg All Downstairs Lights Off). It turns some lights off immediately and then the rest a couple of minutes (yes, minutes) later.  It does. It appear to be a Zigbee issue as the lights that are not off immediately show as “on” in the Navigators.  One can in fact speed things up by turning them off manually.

I have tried the IT101 trick (rebooting absolutely everything) and I have tried adding delays (which shouldn’t be necessary) before and after the offending commands… very weird.  As no one else has complained about this, I assume this issue is restricted to really large projects (or something else unique to my system)…

Have you since edited done the 'sync all scenes' action on the lighting page?
Any chance the delay lights are in more than, is it 25?? inclusive scenes?

Looking to confirm abilities of Yales Assure 2 locks in Control4.

if control4 Yale zigbee card added, local communication, user creation in Control4 UI and programming off of user code. (Must setup lock in Yale app)

if WiFi, cloud communication, Yale app manage codes, but control4 can still program off user code.

correct?

Do it reliable. Go along the top of the existing cabinets then cut a channel across over the doorway, patch and paint.

We also would not replace a KA with a KC when stairs, or other safety necessary locations, are involved.

4 minutes ago, RAV said:

In theory there is a resale value to dead accounts.

And that explains the email from December 2023 about the purging of Inactive accounts.
https://www.snapone.com/privacy/inactive-customer-account-policy

Inactive accounts = short answer, hasn't called home in 2 years, details follow the link.
 

I just called tech support for clarification.

An old account upgrading to a Core DOES NOT have to pay for Connect and may fully update to the latest OS!!

Connect ONLY triggers at creation of a new account, and does so for ALL new accounts regardless of processor or OS!
Home sold systems need to either have the previous owner do a change of email to the new owners, or new owners will HAVE to pay Connect for a new account, even for an HC running 2.10.6.

In theory there is a resale value to dead accounts.

Primarily Bug Fixes and Connect Requirement.

https://www.control4.com/docs/product/control4-software/dealer-release-notes/english/latest//control4-software-release-notes-rev-as.pdf

You could bypass the fan output of the Control4 Fan Speed Controller essentially turning it into a KC120 and run the hot direct to the new fan.
Then reprogram the buttons as you'd like. But I don't think you'll be able to 'add' an up/down to the fan controller driver in composer.

But no the KCB is not a choice as it's 48v power and RS485 for panelized lighting. KC120 would be the choice.

Much of it comes down to the cost of entry, exclusives and job security.
If you have the related Certification, than you're going to spec their hardware, in part to lock out those that don't have Certification.
It's a Union thing.

How often do you loose power?
For how long?
You may want to invest in a UPS for your processor and matrix (and other related non amplifier components)

Trying to make a pizza from a picture you saw. It’s just bread, cheese and tomatoe sauce.

15 hours ago, WhistleProjects said:

I think I now understand what you are trying to achieve - Basically, you are suggest you would duplicate Variables within the Agents, so that whenever the driver variable changes, it updates the Agent Variable to the same value. Then, you would like the driver to show all these values all in the one WebUI, and potentially separated by 'Headings', eg. "HVAC", "Lock Status" etc. So the user could just scroll up/down and see everything?

This is certainly achievable, using the same UI design, but would need to be a different driver. 

Correct on what I was thinking. Whether it's one driver with subheadings or using multiple instances of the driver, would depend on what's possible within the driver architecture itself.
It was thinking multiple instances to keep from long scrolls to find the info you want.

and there's also Presence Sensors rather than just motion:
https://chowmain.software/drivers/control4-athom-human-presence-sensor

1 hour ago, Monopoly said:

Thanks RAV.

I'm not overly concerned about the cost of running lights. More of a principle. Or even more so, the ability is already there due to C4 has programming available.

To your point, I could just delete the timer. Because why worry about a cup of coffee. In fact, I could just hardwire all the lights on and get rid of the dimmers...lol. 

I understand your point. I'm just saying, make the timer longer and you'll likely have a better experience without adding more programming and complications.

Make the timer much longer.

You've added a pain point that's not resulting in significant savings.
If you're using LED the cost savings between a 5 minute occupancy off and a 30 minute is going to be less than a latte a year.

Average kitchen LED lighting, it's about $6 a month if left on 24 hours a day!
Which is about a penny per hour.

On 4/14/2024 at 1:03 AM, WhistleProjects said:

I think you have misunderstood the intent of this driver, or I am misunderstanding what you are trying to say.

This driver is for controlling Variables that have been configured in the 'Variables Agent' within Composer. Not variables that have been set within drivers.

But I can create a user variable to match a driver variable. So was wondering if the driver allows multiple lists in one system for displaying that information to end user in one place, not so much manipulating the variable. Show all lock status, HVAC values, alarm window contacts etc.

Then there should be a Garage Door driver in your project which you'll program against, it's not a variable.

You need a timer - for however long you want the delay to be. GarageTimer

Then in programming tab
When Garage Door opens, reset timer GarageTimer
When Garage Door closes, stop timer GarageTimer
When GarageTimer expires - close door

Do you have a garage door icon that's currently reflecting the state?

I display list per project?

For example.

Cool Setpoint list - shows all the tstat cool points in the house
Heat Setpoint list - shows all the tstat heat points
Current Temperature list - etc

Fixed

1 hour ago, Darin, PM C4 CX Platform said:

Our developers have finished their testing of our app running on Apple Vision Pro, so here is a TestFlight link for early access to a version of the Control4 mobile app that includes support for Apple Vision Pro. Please give it a try and let me know if you are experiencing any bugs. 

https://testflight.apple.com/join/8TASGss5

Nice !

https://status.snapone.com/

Probably not you.
Post in the dealer forum about slow loading this morning, reproduced by and service ticket thus created by a Control4 employee.

Remote buttons get their function from the source device driver, ie cable box.
To change what a button does to a source you have to edit that driver, most drivers are not easy to edit.

You can program at the room level additional commands to any remote button, which are based on the sr series remotes nomenclature.

If no source device uses the page up down, you’re good. If any do, you get both the device and the room level commands. Adding if source is xyz type commands at the room level for a button you can send those additional commands for only devices that don’t have device commands. (You can not prohibit a device level command through programming, only through editing the device driver)