Jump to content
C4 Forums | Control4

Light Scene


Recommended Posts


Sorry here are some more details:

All lights work correctly from hitting the dimmer (or keypad), or using the remote, touch screens, opad etc. The lights can also be controlled from composer as normal, no problem. I've had several light scenes that have worked, up until this latest update to 2.3

From composer when I hit the "activate ligt scene" nothing happpens. I've tried creating new light scenes and they won't activate either. A few light scenes that were activated by a double tap on a dimmer, no longer function either. Or when selecting the light scene from the ipad. Individually the lights work however.

This is odd, I'd appreciate any input.

Thanks

Link to comment
Share on other sites

I have the same issue.... so your not crazy... I have yet to investigate this further but I reprogrammed my switch to turn off all lights instead of triggering the scene, which works for now until I get further into it.

Ill try and look at this weekend and let you know.

Link to comment
Share on other sites

Glad Im not the only one!

Just noticed when I activate the light scene with the ipad, the ipad shows all the lights come on to the programmed %, however the actual lights stay off. When I adjust the individual light it immediately comes on the the correct level, but I have to actually touch the light.

Link to comment
Share on other sites

  • 2 weeks later...

Straight from C4. Take a look and see if it helps

Lighting Scenes not Working After Updating to 2.3.0

Created: Jan 07, 2013

Topic: Loss of Lighting Scene control in 2.3.0

Affects: Lighting Scenes on 2.3.0 projects

Detail: Control4 has had a handful of reports that Lighting Scenes are not working after the update to 2.3.0.

1st Scenario

Control4 has found a scenario where a Zigbee Mesh can get into a state where it doesn't have a designated ZAP configured as the Lighting Scene initiation point. This initiation point for Lighting Scenes is defined when any Zigbee node in the system sends an identification broadcast, which can be fairly common in most systems. If none of the devices send this broadcast however, Lighting Scenes will not work until that happens. For this reason, it is only possible to encounter this issue when Zserver restarts. Once scenes are working, they will continue to work.

Action: In order to get scenes working in the rare event one encounters this problem, you will need to force a zigbee lighting node on the system to send out a multicast by one of the following steps:

1. 4 tap the top button on dimmer/switch/keypad (Sends out the Identification MIB).

2. 15 tap the top button on dimmer/switch/keypad (Reboots the device. As part of the Reboot, the device will send out an "Hello! I'm Back!" broadcast.).

3. Pull the air-gap switch on a dimmer, forcing a reboot, which sends out the multicast.

Note: If zserver gets restarted the system may get into this state again and you will need to tap the top button or pull the airgap again.

Note: Please also view KB Article 337 relating to Lighting Scenes and synchronization. New scenes and Converted Advanced Lighting Scenes take some time to sync, this is not an instantaneous process, and in some cases it may take overnight. If you have migrated Lighting Scenes or have created new Lighting Scenes and they appear to not be working, Synchronize your scenes and then give them time.

Root cause has been identified and will be addressed in a future maintenance release.

2nd Scenario

Detail: The system will have a functional mesh, Zigbee nodes are controllable, dimmers and switches will respond to button-bound commands from keypads or Composer. The issue is Lighting Scenes will not trigger, OR, the Lighting Scene will call loads that are not part of the initiated scene.

Action:

Add ALL of the dimmers/switches in the project to a Lighting Scene.

Sync the Lighting Scene.

Execute the scene a couple of times.

Remove the unneeded loads from the Lighting Scene.

Link to comment
Share on other sites

I have same issue and we cannot figure out what it is. In my case I when I hit the pause button it is supposed to activate a lighting scene and isn't. We have tried several things and since the upgrade to 2.3 it has stopped working. The weird part it is only this scene. Hopefully the next update will resolve this

Link to comment
Share on other sites

Gary,

Didn't understand this - agent and set-up scene - done

programming and dragging, not sure what to drag?

My scenes work, just the scheduler is not working? I can go in and turn them on and off from Composer, but they don't work as scheduled? So my zigbee is working, just not the scheduled on/offs?

Not sure what to do, even tried setting up a new schedule on one?

Link to comment
Share on other sites

Gary,

Didn't understand this - agent and set-up scene - done

programming and dragging, not sure what to drag?

My scenes work, just the scheduler is not working? I can go in and turn them on and off from Composer, but they don't work as scheduled? So my zigbee is working, just not the scheduled on/offs?

Not sure what to do, even tried setting up a new schedule on one?

Sorry my way of talking - I go into programe, select the scene ( On the lift hand side) then go over to the right hand side and select the lights that make that scene, ensure they say on

or off or x%, then select the Green Arrow and bring into the middle - This builds the scene up.

Sorry had no problems with Scheduler - But you could try the same way of doing it.

Link to comment
Share on other sites

A reboot fixed my scheduler issue. I'm expecting issue to recur over time again. Hopefully 2.4 will address it.

I've also had some zigbee slow downs over the last few days, (unresponsive sr-250's) and some bizarre issues with unresponsive outlet dimmers/switches.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.