Moes zigbee 3.0 cct rgb led controller refusing color change on all devices same time

I have tested a MOES New ZigBee 3.0 Smart Dimmer Module Swtich RGB CCT for LED Strip for a bit over a year and it worked great connect to a Nspanel pro.

A few months ago I installed 8 of them in total to replace old controllers that are not compatible with eWeLink and Nspanel pro. They were working fine and I was able to control them in the eWeLink app and on the Nspanel pro.

Yesterday i noticed that I couldn’t change the color of the led strip activating a scene on the Nspanel pro. Trying to change the color in the eWeLink app didn’t work either. First i thought there was something wrong with the moes zigbee controller but to my surprise all 8 of the controllers had the same issue.

  • All devices are online and connected.
  • I am able to turn all the controllers on and off both on the app and Nspanel pro and automations.
  • I can change from cold white to warm white and dim the light on the white settings in the app and on the Nspanel pro.

But when I go to the color settings I can choose any color but the led strip won’t change color. I can turn the light on and off on the color page. I can dim the light without a problem. But when changing colors it doesn’t change the led strip color and if I change the second slider to change the color intensity I get an error and the slider goes back to previous position.

This happens with all 8 controllers they are in different rooms and use separate power supplies. Everything have been working perfectly before and all have same issues now so i suspect the problem would be on the Nspanel pro I use for the zigbee connection or eWeLink as i update both of them recently.

my setup has 1 Nspanel pro in hub mode and 2 Nspanel pro 120 in router mode. And I have a Ihost running but all devices are connected to the Nspanel pro using eWeLink.

App version Nspanel pro V 4.3 - 433 - 413 - 1151

EWeLink version iOS V5.22.2

Hi, I’m sorry you’re experiencing this issue. Do you mean that the device was added through the NSPanel Pro but you’re unable to control the color mode parameters in the eWeLink app? You can try controlling a few devices, and after it fails, please submit the app logs (Profile → Feedback & Help → Feedback → Submit) along with the NSPanel Pro logs ( Top drop-down menu → Settings → About → Feedback → Submit), and let me know the time of the control attempts and the device IDs. Thank you in advance for your help, and I’ll check the logs as soon as possible.

Yes all devices are added on the Zigbee gateway of the Nspanel pro (device ID 1001e37ad2 )

All the connected devices worked fine before but all of them refuse color changing at the same time. Both on the EWeLink app as on all 3 Nspanel pro’s the color settings refuse to work but all the other settings work: on off dimming and cold white and warm white settings.

Affected devices:

Device ID a480120049

Device ID a480120074

Device ID a4800cf356

Device ID a48011fde9

Device ID a48011d7d8

Device ID a48011fd11

I did try to delete 1 and reinstall it and then it works fine again also a new added device works fine.

Device ID a480120057 deleted and re added works now

Device ID a48012a399 new added device and working

Very weird that all installed devices have the same issue while re added and new added devices work fine. All devices have different locations and different power supplies. So I can solve the problem by deleting and re adding the affected devices but would be interesting to know the cause of the malfunction.

Both eWeLink and Nspanel pro logs have been sent . The test was around 8:30 and the last thing I did before sending the logs

Thanks for the fast response and keep up the good work

Hi, thank you for the logs. We’ve identified the cause: in the December version, we modified the control protocol for this device, which caused your light to be unable to control color properly. After re-adding the device, the new protocol is used, so the control works normally. Thank you again for your feedback, as it helped us discover this issue. We will fix it in an upcoming version.

1 Like