Skip to main content
Blue Series 2-1 Switch • Troubleshooting

Common troubleshooting issues and solutions for the Blue Series 2-1 Switch (Zigbee)

Eric Hines avatar
Written by Eric Hines
Updated over a year ago

Please use this document as a resource to troubleshoot your Blue Series 2-1 Switch. We'll list out generic issues you may encounter during installation that are not hub specific. For hub specific issues, please click on your hub below to be taken to that troubleshooting page.

Hubitat

Home Assistant - ZHA

Home Assistant - Zigbee2MQTT

The easiest way to find your issue is to look at the Table of Contents located on the right side of the screen (on desktop) or via the drop-down at the top (on mobile).


Lights Will Not Turn Off

Oftentimes when your lights will not turn off on your Blue Series 2-1 Switch, it means that either Smart Bulb Mode or Local Protection may have been enabled.

To disable Smart Bulb Mode on your Blue Series 2-1 Switch, hold down on the bottom part of the paddle (off) while simultaneously tapping the configuration button four (4) times (do not let go of the paddle when finished tapping the config button). Wait for the LED Bar to flash solid blue (and then let go of the paddle) indicating the switch has disabled Smart Bulb Mode.

Video Demonstration

To disable Local Protection Mode (Parameter 256) on your Blue Series 2-1 Switch, hold down on the bottom part of the paddle (off) while simultaneously tapping the configuration button ten (10) times (do not let go of the paddle when finished tapping the config button). Wait for the LED Bar to flash solid red (and then let go of the paddle) indicating the switch has disabled Local Protection Mode.

Video Demonstration

If after you've disabled both Smart Bulb Mode and Local Protection your light still does not turn off, then please double check your wiring. If your wiring is correct, please reach out to us for further troubleshooting.


Flickering Lights

Flickering lights are often caused by a mismatch in the LED driver and internal electronics of your Blue Series 2-1 switch. The good news is that this is a relatively easy fix, however we need to figure out what type of flickering you're experiencing. Please scroll to the section that best describes your flickering issue.

Lights Flicker at a Low Dim Level Only

If your lights are flickering at a low dim level only, the easiest way to fix this is to set a minimum dim level just above where you notice your lights flickering.

For example, if you notice your lights start flickering when you dim your Blue Series 2-1 to around 20%, you would set a Minimum Dim Level (Parameter 9) to 21 (ie: 21%).

Once you set the minimum dim level, that level will become the switches new 1% and it will scale itself accordingly.

Lights Flicker at a High Dim Level Only

If your lights are flickering at a high dim level only, the easiest way to fix this is to set a maximum dim level just below where you notice your lights flickering.

For example, if you notice your lights start flickering when you dim your Blue Series 2-1 to around 90%, you would set a Maximum Dim Level (Parameter 10) to 89 (ie: 89%).

Once you set the maximum dim level, that level will become the switches new 100% and it will scale itself accordingly.

Lights Constantly Flicker (Strobe)

If your lights are constantly flickering or strobing (this is a strong flicker/strobe, not a subtle one), then there may be either an issue with the bulb itself (ie: it's not compatible) or you're using a dumb/existing switch in a multi-way setting and the smart switch is having an issue detecting it properly, which is causing the flickering/strobing. This often happens when there are multiple LED bulbs on the load causing interference on the traveler wire. To fix this issue, you need to set the Maximum Dim Level (Parameter 10) to 80 (ie: 80%).


Switch is Rebooting (Cyan, Blue, Yellow Sequence)

There are a few reasons why your Blue Series 2-1 switch is rebooting (the LED Bar flashes cyan, then blue, then yellow).

Switch is Constantly Rebooting

If the switch is constantly rebooting and you hear a clicking sound, typically this means that the Line and the Load are mixed up and you should check your wiring. Or in rare cases, it could mean that there is a loose wire in the back of the switch causing a bad connection.

Switch Reboots Every Time Its Touched

If the switch reboots every time you touch it there may be a problem with the physical paddle which is causing it to disconnect the air-gap (little button located at the bottom left of your switch) from the PCB. Another thing to check is the air-gap itself -- please ensure it is fully pressed in. Finally, this could also be that in a non-neutral mode, the switch may not be getting enough power and a bypass is required.

Switch is Intermittently Rebooting

If the switch is intermittently rebooting, there are a few reasons this could be happening:

  1. Connected to a Non-Supported Load: the Blue Series 2-1 switch is to be used for lighting only (except ballasts/tube lights or any lights connected to a transformer) and is not to be used for fans, outlets, ballasts (magnetic or electric), tube lights or any inductive/motorized loads. Doing so will cause not only possible damage to the switch or load, but it will cause the switch to reboot. Please purchase the Blue Series Fan Switch for inductive loads.

  2. Lack of Power to the Switch: in a non-neutral setting, the switch requires a minimum amount of power and if it's not getting enough, the switch will reboot. You'll need to purchase a bypass and install it at the light fixture.

  3. Congested Zigbee Network: in rare cases, if you have too many Zigbee devices, all the traffic routing through the Blue Series 2-1 switch can cause it to reboot. The fix to this is to make sure your firmware version is 2.15. Please reach out to us for updating instructions.

  4. Air-Gap is Loose: please ensure the air-gap (little button located at the bottom left of your switch) is fully pushed in. If it is pulled out even just a little, it can cause a disconnection with the PCB and thus create a reboot.

Did this answer your question?