Cyknight

YOU START BY TURNING CAPS OFF. Then you re-read the dimmer's instruction manual which will give you every possible method of wiring an aux keypad, also telling you that an aux has no hot whatsoever. Unless of course you don't actually have auxiliary keypads but normal keypads. Obviously tech support can't help you, can't go around yelling at them.

Ah - note that the above drivers are updated and scan works. As for IR location, it's about 1/2 inch/ 1.2cm to the LEFT or the USD port (Sammy's own docs state to the right I think....)

There IS a driver, but it's to have C4 trigger IFTTT, not the other way around. Web events driver would be the way to go - have the event trigger a specific web event, and program that web event to do whatever it is you want.

I've seen it - too much surge current on initial startup. I'm going to guess both connections on the bus are in use? Try removing one output, see if the keypad bus starts up - it'll be a pretty solid indicator that there are too many devices on the powersupply. Alternativel, there may be a minor short somewhere (ie data neg to ground)

First off - I wasn't suggesting they were implemented poorly. Second - my example was heavily simplified. Third - yeah, the idea of what I intended to say is indeed that it 'holds' the individual script 'hostage' - not the system as a whole. Fourth - while delays do not cause a true 'lag' on a system overall, it's not that hard to create conflicts where delays build creating a perceived delay or other weird behavior (where in actuality it's just following script). Triggering (and re-triggering) a timer won't cause this. Example: WHEN door bell is pressed turn light on delay 1 second play announcement delay 5 minutes turn light off Now have someone push that doorbell 15 times in a row. (Durn kids) Now add a schedule to have the light on at an hour before dusk Add some motion events to that same lights. Now imagine that doorbell being pressed a few minutes before the scheduled time, and the kids playing in the front yard. I think you can see where you'll get a lot of odd behavior of the light turning on and off.

LONG delays aren't good - because they are DELAYS. See delay as a 'stop what you're doing and wait there five minutes until I say go' command. Where a timers is 'stop what you're doing and come back in 5 minutes' command Using 5 minute delay will hold up the system for 5 minutes, whereas a timer does not. Frankly personally for anything more than a second - I use a timer, but especially if you're looking at minutes.

Don't use delays in the span of minutes please - it can cause major overall system delays. Instead, create a 5 minute timer, and start the timer instead - then on the timer expiring, turn the light back off. Other than that, yes, anything dependent on the if statement needs to be 'indented'.

OK I'm going to stop posting until this multi posting is cleared up

I like messing around with the icons too https://www.dropbox.com/s/4w6ng9lz7n4j6vj/2016-07-04 16.14.12.png?dl=0

And touchscreens - this is less about OSD as it is about icons.

And touchscreens - this is less about OSD as it is about icons.

You can't.

There could be some form of short in the matrix though - then again you mention you have TWO amps, and only one shuts down? This is not something I'd ask you to troubleshoot yourself, but if I was the tech on site i'd have swapped all connections between amps and tested it - if it sticks with that same amp, it's the amp - if it moves over to the other amp, it's the matrix - well at least it isn't the amp. I'd go one step further and move the yamaha connections over to the other side of the matrix - and again see what happens - this would eliminate the matrix or the yamaha most likely - then there's wires.....

mhh - is there an audio matrix that is feeding both the yamaha and the amplifier?

And as such you keep claiming to know better than C4's board of directors, stakeholders and so on. You keep stating opinion as fact. Reminds me of a politician...

Much like the ones that think there's a problem don't have it? This is a discussion that just goes in cycles because there IS no 'right or wrong' - just opinion and want.

C4 has little to do with that particular matter directly though - which doesn't make it any less of a flaw of the dealers. Except that it isn't really - but you have to be/have someone knowledgeable enough to do it first, and be able to sell it (and properly estimate time) second. That's where the problem is, neither is all that easy to 'do'.

Sorry to hear you've been told that - it wouldn't hold true as such here though. Because I can tell you I almost never run wires (other than my own house - and boy do I find that I've done it very little lately at the moment), and am rarely involved in installing gear, and even don't do any major wiring at the rack anymore. A good programmer's time is too valuable (in the sense that it's a much more uncommon resource - not so much in monetary value) to spend it on anything but programming and troubleshooting.

No, what it shows is that that was exactly what was happening. An argument you will loose in short order quite frankly. Go tell Apple you want the ability to have access freely to the root OS on any of their products. Understand that I'm actually pretty uncaring on the whole general discussion on who should have access to what, as in don't care one way or the other, except that C4 has a hard enough time to keep tech support running smooth for a dealer only model as it is - thus my belief is that opening it up would be a disaster in that regard (as things stand now).

Understand that I'm not attacking you specifically on this - but what I truly meant is that access to being a developer was closed down upon because people were using it to try backdoor into having PRO. You may think it's not unreasonable to have/pay for PRO after doing education - but the fact is that C4 has shown no intend to have anyone other than dealers have access to PRO - trained or not. Why/reasonability/smart choice/right or wrong aside - you can discuss on here all you want, but that's there standpoint. Just because you want something, doesn't mean you have a 'right' to get it.

And that is where the problem lies...

You won't hear me recommending NEST - and the cloud is one of the reasons. I find them to be mediaocre in gerenal. Not bad, and of course easy to set up as is NEST's true 'strength' - but nothing to get excited about as such.

The driver for the HIKvision is by C4 and in the database. Just set up the cam for wifi, drop in the driver and go for basic use, selecting an alternate camera for intercom is simple too - just a checkbox and dropdown once the cam is in. PLEASE note that even with that you'd still need a touchscreen at either end for intercom (audio) etc - no the touchscreens have no night vision to speak of.

First and foremost - congratulations. Now, I'm not sure what 'monitoring' you speak of with the new touchscreens and IP camera's - the only thing that I can think of (and has been possible with the previous gen) is using a TScreen and it's intercom function AS a baby monitor - in other words, place a touchscreen (potentially a portable one) and set the intercom to a 'monitor' mode. Now as for the cameras - the current SOFTWARE allows you to use a camera OTHER than the T-screen as the intercom camera - BUT audio HAS to come from the screen. So you could get a different/nightvision camera and use that for the video, but any audio functions on it are useless as far as C4 is concerned. "Portable" camera's though are not really in existence that would work well - at least not in a battery operated sense. There's numerous wireless camera's though (as in need a powerplug but talk over WiFi) that can be made to work fine with C4 - HikVision, Dlink and more. One example that I used: http://overseas.hikvision.com/en/Products_accessries.aspx?c_kind=1&c_kind2=2&c_kind3=154&c_kind4=161&id=4919

Fair point, it may well do exactly that.