brucecampbell

They serve no security purpose, they are only used to turn on lighting from programming in C4. However my slave controller died and already using all contacts on my 800, so looking for 'free' options rather then spending on more hardware.

Thanks - will do.

Just my luck - installer code provided by the alarm guy is not working, neither is 5555. So will go ahead and try physical installation and hope this new zone does not interfere with the way the alarm currently works. This guy was not overly familiar with external integrations such as the IT-100 module, but did say he believed you could log in and view the installer code somehow using the code 006 or 007 - I could not work out what he was talking about... Anyone know if this is possible? and how? Cheers.

Thanks for the info. Moving the cables is no problem for me - rack is not far from alarm panel. Alarm has never been used with these two unused zones, so hoping they are not defaulting or programmed to be an armed zone...Though I have since been provided the installer code by my alarm installer - installed over ten years ago and never monitored, so glad they could provide this to me with no hassle. So I should be able to add it to the alarm panel and C4 now.

Any DSC experts out there? I have the Power Series PC1832 I think. I have two unused zones, so am looking to move my outdoor sensor onto one of these zones instead of directly into my HC800 contact. Question - will the IT100 just work? I do already have these two unused zones included in my project. or will I need to program this zone with my alarm panel? The reason I ask is I don't have the installer code for the panel - so not sure I will be able to do the alarm programming, and not sure yet if the original installer will give me this info....

HC300 please. Will PM you

Hi, Are these still available? Looks like my 300 power supply has quit today.

I'm assuming you will also need a trigger built in to your project either by adding a relay to the room and programming it to open/close based on room selections. or there may be drivers which do this already??

I think you might want to use NO as opposed to the NC NC is normally closed - therefore the circuit is connected by default - providing you with your 12 volts until something opens the circuit.

probably an IR driver. And probably the commands in the driver are set to pulse more than once. You most likely just need your dealer to edit the driver to reduce the value to 1 for each of the arrow commands. A pretty quick and easy job for anyone with access to your system - you might find some dealers on here that can log in and help you out.

I don't use HDMI - but do have an old Leaf Component Matrix - but YES - a major purpose of a matrix is to allow same source to multiple zones. I'm no expert on HDCP - but I would expect if the zones playing the source do the handshake, then no problems.

You should not really need delays in code. To add a delay so a line is not skipped is not really understanding how it works. Lines of code are queued and executed in order. A code should not be 'skipped' over as such, if the result is not achieved, it is generally because of other factors. Of course there will be exceptions - but if you need to use a delay - think carefully about what you are trying to achieve - can this be done another way? If you are programming an action and then relying on that action being complete prior to further programming - then you are probably putting some of your coding in the wrong place... ie: When room motionsensor senses motion: Turn on Light ABC If Light ABC is ON Set TOP LED on Light ABC to RED Should be extracted out to two commands: When room motionsensor senses motion: Turn on Light ABC When Light ABC State Changes: If Light ABC is ON Set TOP LED on Light ABC to RED

I had my driver installed 10 years ago - and am pretty sure I have never changed it - I have a DSC with the IT100 module. Never bothered trying to get additional info from the alarm panel. I set a string variable to the name of the area/zone every time a sensor has motion detected. I then include that variable as output in notifications. (ie: "*** Alarm Triggered *** Motion sensed in <Zone>") works a treat, and (so far) never found a need to have the panel provide me further detail.

I find it best to use a single variable for this - much easier to track what you are doing (providing you can remember what each value means ) I have a integer variable to hold alarm state - but I go to another degree. I use variable 'Alarm_Status' with values from 0 to 7 I then have a macro which runs functions based on what the value of this variable is. I then set the value of the variable from different points in the project. ie: 0 = nothing 1 = away pending (two min timer where house turns off and if dark, certain lights come on for 5 mins) 2 = press away on the alarm 3 = alarm is in armed state (send notification) (if garage door open send notification) 4 = motion sensed while armed (send notification if outdoor sensors motion) 5 = disarmed (send notification, change all LED from red to normal colours) 6 = alarm triggered (send notification) 7 = smoke alarm triggered (send notification)

Any electrician can install the switches or dimmers, so yes you can buy and have a remote dealer add them to your project. The switches are identified via button clicks, so you will need to be on site to help a remote dealer. Talk to a dealer first - he/she may give more competitive pricing if buying both hardware and time.

This programming is working for me. It relies on a scene being 'Active' as soon as it is invoked. If the scene was not active until the 3 second ramp up/down completed, then it would not work. The idea is, the motion sensor (along with a timer) turn the lights on and off. If any interface is used to control these two lights, the sensor and timer are deactivated until the lights are manually turned off again.

This is perfect. This will mean my programming will work how I need it to. I will be able to accurately check if the change in state/level of a light is due to a scene being activated or some other form such as a button click or other interface used. Gives me a very smooth approach to turning lights on and off using motion sensors and allowing 'overrides'.

Can do when I'm home later tonight. Cheers.

Great info, thanks for the detail. I'm running 2.5.2, so some of these advanced lighting features aren't available to me. however, if I'm reading this right; I have my tracking set to 'At Scene Final Level' my scene takes 3 seconds to ramp to the final level. Why is my scene showing as active immediately? Is it because invoking a scene will set it active immediately?

Thanks, with what I have programmed so far, it does appear to be immediately seen as 'active'. I'm not at home now, but did think running some tests as you suggest will be useful. Hoping to find some documentation or advice on what the other tracking options might be used for?

I need some help understanding how to best use the advanced lighting scenes. Hopefully some of those in the know can lend some advice please. When is a scene 'Active'? - is the scene immediately active if it is invoked? - how does the tracking options influence when the scene is active? example: scene 1 = ramp lights to 90% over 3 seconds. scene 1 (toggle) = ramp lights to 0% over 3 seconds I currently have all my scenes use tracking 'at final %' Practical use: motion sensed in the room Option 1 -> motion sensed: activate scene 1 (is scene 1 active immediately, or after the 3 seconds it take to reach the setting of the scene?) timer expires: deactivate scene 1(is scene 1 inactive immediately or after 3 seconds?; is scene 1(toggle) active immediately or only after 3 seconds?) Option 2 -> motion sensed: activate scene 1 timer expires: activate scene 1(toggle) (is scene 1 inactive immediately or after 3 seconds?; is scene 1(toggle) active immediately or only after 3 seconds?) Cheers.

Try putting 'WORKGROUP' in the Workgroup box and try again.

I use the same interface. I had issues too when first installed 6 or 7 years ago. From memory, my motion sensors were all comunicating and I could program lights based on these, but the interface on the ipad and iphones was not great. I changed the driver and it resolved all the problems. - I'm not at home right now so I can't let you know which driver is in use, but I recall the UI changed when I changed the driver too - here is what mine looks like now:

Updated and tested with my pool lights - Thanks for the update - the customer colour palette is great. I can now keep the pool looping through blues, greens and purples (only the colours that I feel look good in water), while the waterfall loops through the rainbow colour option. Great work!

Forget about Enttec, buy the Engineering Solutions DMX engine and driver. Works a treat!