RGB Genie causes hub to "pause"

I recently installed a new z-wave RGB Genie device, but every time a command is sent to it, it causes a 30-60 second pause to the hub, in that no other things work. For example, I have two motion sensors in a room, the RGB Genie will trigger first, but the second motion sensor and separate LED will not trigger/activate if the RGB Genie triggers first. Also, If I just send multiple color changes to the RGB Genie (from the device page) the first one will go instantly, the second one will queue up and execute many seconds later.

I haven't seen this issue with the many other devices on my network. Thoughts on where I can go to troubleshoot this?

Kind of hard to troubleshoot from the limited information provided. Could you expand on your observations, including:

  1. C5 or C7 hub?
  2. What kind of RGBGenie device?
  3. Which driver is it using?
  4. If you have C7, post a screenshot z-wave logs captured while triggering the RGBGenie device.
  5. Does the pause also affect zigbee, LAN, and virtual devices?
  1. In the scenario described above, can you capture logs for this automation (events, triggers, actions). It would be useful to determine whether the issue lies in the motion trigger not being received by the hub, versus the z-wave command for the action of turning on the LED not being sent.
1 Like
  1. C5 Hub
  2. ZV-1008
  3. RGBGenie LED Controller ZW (custom driver)
  4. N/A - C5
  5. It's hard to tell, when I see issues with other devices its a combination zigbee/zwave. zigbee motion sensor controlling a zwave switch.
  6. See below. It looks like thehub received the zigbee motion alert right away, but it didn't send the "turn light" command for 37 seconds.

Is there a way on the C5 to identify the zwave path to the end device?

Only using a secondary controller. Like PC Controller or Zwave Toolbox.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.