Where can I debug or trace actions in Control4?

[Michael Bendtsen]

I have an issue where sometimes some drivers work and sometimes it doesn't!
for example the projector is not always switched off when closing the room. If I reset it then it works for some time and then it stops.
Another issue I have is the screen, sometimes it role down (KNX shutter driver) and sometimes it doesn't.

This is the actions from the room:

1: at start: projector turns on and  screen goes down
2: at stop: projector stay on and  screen goes up
3: at start: projector stays on and  screen does not move (manually down)
4: at stop: projector turns off and  screen stays down 
5: at start: projector turns on and  screen is down
6: at stop: projector stay on and  screen goes up
7: at start: projector turns on and  screen goes down
8: at stop: projector turns off and  screen goes up
9: at start: projector turns on and  screen goes down
10: at stop: projector turns off and screen stays down
11: at start: projector turns on and  screen is already down
12: at stop: projector turns off and screen goes up

There is a pattern to this but I don't know where to start looking and how to debug it (I'm quite new to C4).

[msgreenf]

Why are you programming things? Control4 will do this automatically with the right bindings 

[Michael Bendtsen]

@msgreenf I'm not programming! I'm only using drivers and some actions. but apparently it's not working as it should so where can I see this? E.g. I add a driver to the room, that should switch off the device when closing the room - but sometime it doesn't, so where do I start to debug it? where can I see if there was a trigger or not?

Still this opens an interested question. Can I program in C4?? can I make lua scripts that are triggered by something?