When I upgraded from IC3 to IC4, I noticed when clicking on the rules page it gives a notice that rules won't be supported in the future and to use scenes. So I went and converted my rules to scenes. In particular there are a couple triggers I have from sensors that turn on/off lights. There seems to be an issue with how scenes are processed.
I have two scene triggers to toggle the light, one is for light on when trigger open, another for light off when trigger closed. When the sensor is triggered to open it takes 4-10 seconds for the light to come on. When the trigger closes another 4 seconds or so to turn the light off.
I then disable the two scenes and re-enable my two rules that do the same thing. When the sensor is trigger to open it takes less than a second for the light to come on and when the trigger closes, less than a second to turn the light off.
I've tested this over a dozen times, disabling rules then enabling the scenes, testing the sensor, going back and forth between the scenes controlling the light and the rules controlling the light. It's by far 100% faster using the rules and I've had times where the scenes didn't respond at all and the light didn't turn on (zero failures with the rules). I would really like some assistance with this issue. Triggers are my #1 use for IC. Here is my exact configuration for this scenario.
Aeon Recessed Door sensor
GE Zwave switch
Scene 1 ClosetOn
Devices: Closet - Turn on
Trigger: ClosetTrigger changes to opened
Scene 2 ClosetOf
Devices: Closet - Turn off
Trigger: ClosetTrigger changes to closed
IC4 scene slowness
- 117 Views
- Last Post 05 August 2015
Could you send a screen shot of each section of your scene setup? You could use a service like www.snag.gy to include a link
Here are the screen shots.
http://snag.gy/brI2w.jpg
http://snag.gy/W1f9h.jpg
http://snag.gy/6OhoW.jpg
http://snag.gy/lI4gf.jpg
I'm making another test case. I've received my Gen5 USB controller so I'm going to be doing a full new install. Maybe there's some residual configuration from the previous IC3 install and my current controller.
Here are the screen shots.
http://snag.gy/brI2w.jpg
http://snag.gy/W1f9h.jpg
http://snag.gy/6OhoW.jpg
http://snag.gy/lI4gf.jpg
I'm making another test case. I've received my Gen5 USB controller so I'm going to be doing a full new install. Maybe there's some residual configuration from the previous IC3 install and my current controller.
I might be possible that you are having Zwave device conflicts. I was having that problem, I would have two more devices that would take up to 10 seconds to turn on (or off). Or the device would actually turn off after a few but took ICHA the 10 seconds to clear the command before any other commands could be issued.
What I did was had to isolate the devices by disconnection, unplugging, turning off power to the device via fuse box, etc. and one at a time remove each device from the Zwave network. Once I did that with all my devices, I added them back in after I cleared the USB stick.
Yea maybe it was device conflicts. After getting my Gen5 controller I've been slowly rolling out joining devices. I have the closet and sensor joined and is functioning fine with the scene conversion as I have been testing it. I'm going to keep adding a couple devices every few days and monitoring the events. So far I've only had 1 delay warning.
As an update to this test. I've been at 15 devices for a week, no delay warnings, no red alerts. Tonight I added two more switches. With in 2hrs I've had 4 different devices show red alerts. I find that an interesting data point. Not sure what it means yet, could be one of the two switches I just added is faulty causing bad zwave routes or something to that effect. I thought I'd share as the saga continues.
