I have a Philips Hue bridge connected via Matter to my NSPanel Pro. A while ago, some of the Hue bulbs wouldn’t work when controlled from the ewelink app (“Failed” message) but worked from the NSPanel. I also noticed that the switches and sensors connected to my Hue bridge appeared in the ewelink app and the panel, whereas previously just the bulbs appeared. I tried re-linking the Hue bridge to the NSPanel via Matter, but only a few bulbs appear, and the rest show up as “Offline” or “device0XXXX”. I can’t do anything with these devices in the ewelink app or the NSPanel. As a result of this, most of the automations/scenes I’ve set up no longer work.
It’s not clear what exactly is connected to what in your setup.
Hue Bridge doesn’t act as a full Matter bridge for all Hue devices, and NSPanel Pro/eWeLink only support a limited subset of Matter features. Because of that, the behaviour you’re seeing (offline devices, “device0XXXX”, missing bulbs, broken automations) can happen when the integration chain isn’t fully supported.
To understand what’s going on, could you describe your setup step‑by‑step?
Specifically:
What devices are paired to the Hue Bridge?
How is the Hue Bridge linked to NSPanel Pro (Matter, Wi‑Fi, or something else)?
Which devices appear in eWeLink, and which ones show “Offline”?
What changed right before the issue started?
With that information, it will be much easier to see what’s actually happening.
I have a number of bulbs (both Hue and third-party), three switches and a motion sensor (all Hue) paired to my Hue bridge. I initially synced my Hue bridge with the NSPanel via Matter, and only the bulbs appeared in the ewelink app, not the switches or sensor. This was fine, as I only need to control the bulbs, and everything worked well (Zigbee buttons and sensors paired to the NSPanel would operate the Hue bulbs) until the NSPanel started to have issues with Zigbee devices after an update, which was fixed. Recently, the Hue buttons and sensor also briefly appeared in the ewelink app under names that made sense (switch/sensor, etc.), but then the devices connected to the Hue bridge often either showed as “offline” or “device0XXX” or showed a “failed” message when clicked in the ewelink app, but would sometimes work when clicked on the NSPanel.
So, it used to work OK, but now it doesn’t. I don’t know why this is. Bulbs that are connected to the Hue bridge are sometimes operable on the ewelink app, but not on the panel and vice versa. When I started typing this, all but one bulb appeared in the ewelink app with some of them showing as offline, but none of the switches or the sensor. Now all bulbs, switches and the sensor are showing in the app, but I’ve no idea how long this will last. It’s all become very flaky and inconsistent, having worked well previously.
Hue Bridge only exposes basic lights over Matter. Switches, buttons and sensors are not supported, so when they briefly appeared in eWeLink, those were not real Matter devices but mis‑detected endpoints.
NSPanel Pro and eWeLink have only partial Matter support, and the Hue Bridge has a very limited Matter implementation. When you combine them, the result is unstable behaviour: devices showing as “offline”, “device0XXX”, working in the app but not on the panel, or disappearing and reappearing.
The setup may work temporarily, but it’s not reliable by design. To understand your situation better, could you describe exactly how your Hue Bridge is linked to the NSPanel (Matter, Wi‑Fi, or something else) and which devices appear or disappear?
BTW - NSPanel or NSPanel Pro? The’re not the same thing.
I have the same problem.
I migrated my Hue devices (bulbs and motion sensors) to the NS Panel Pro Zigbee 3.0 hub.
But since 4.7 firmware bulbs randomly become unavailable (offline). Motion sensors and smart plugs stay online but bulbs go to offline.
I have an NSPanel Pro 120. My Hue bridge is connected to the NSPanel Pro via Matter (which I presumed was wi-fi). Initially just the bulbs were synced (and worked well for months) until quite recently, when the buttons and sensors also synced and everything started to regularly fail. I have a Hue-branded motion sensor in my bathroom, which is currently reporting an accurate lux value in the ewelink app and the bulbs are all working, but I don’t expect it to continue for long.
It didn’t continue for long. Now bulbs are operable via the NSPanel Pro, but the ewelink app shows them as offline, so the smart scenes I’ve set up don’t work.
I was considering that, but with how unreliable the sonoff/ewelink system has become, I won’t risk it.
Hue devices cannot be migrated to the NSPanel Pro Zigbee hub. They stay paired to the Hue Bridge, and NSPanel only sees whatever the Hue Bridge exposes through Matter — which is lights only.
If your bulbs go offline after 4.7, that’s a Matter integration issue between Hue Bridge and NSPanel Pro, not a Zigbee migration problem.
Really?
Hue devices cannot be migrated to the NSPanel Pro. They stay paired to the Hue Bridge forever, and NSPanel only sees whatever the Hue Bridge exposes through Matter - which is lights only.
If your bulbs show as offline in eWeLink but work on the panel (or the opposite), that’s not Zigbee, not Hue, not “migration”. It’s simply eWeLink being unreliable with Matter, which has been a recurring issue lately. Nothing you do with pairing, re‑pairing or “migration” will fix this. This combination is unstable by design when you try to mix Hue Bridge + Matter + NSPanel Pro + eWeLink.
They can if you unpair them from the Hue bridge and pair them to the NSPanel’s zigbee receiver, which is what I thought true-energy meant by migration. They are just zigbee devices after all.
Apparently not.
This seems likely. Now my smart home has become stupid until this is fixed.
Hue devices cannot be migrated to the NSPanel Pro - not partially, not “kind of”, not with tricks. Technically it cannot happen.
Unpairing Hue bulbs or sensors from the Hue Bridge and pairing them directly to NSPanel Pro does not migrate anything. It simply removes them from Hue entirely and pairs them as generic Zigbee devices. You lose: Hue scenes, Hue groups, Hue routing, Hue firmware updates, Hue power‑on behavior, Hue transitions - everything. And no, Hue sensors and switches are not fully compatible with third‑party Zigbee coordinators. If they pair at all, they behave unpredictably. That is not migration. That is unsupported operation. Hue Bridge exposes lights only over Matter. If you see sensors or switches in eWeLink, those are mis‑parsed endpoints - ghost devices. They are not real Matter accessories and will never behave like real ones.
The instability you’re seeing (offline bulbs, device0XXX, panel works but app doesn’t, app works but panel doesn’t) is caused by eWeLink/NSPanel Pro’s unreliable Matter implementation. This has been a recurring issue since recent updates. This setup does not work and will not work, because technically it cannot work.
You ask for advice and/or opinions, and then you argue with them. Why? Forgive me for putting it this bluntly, but what you’re doing is spreading technical misinformation with a lot of confidence.
I noticed a problem and reported it on the forum, as I’ve noticed the staff are quicker to respond here. What is your goal here? You’ve added nothing to this thread except condescension and misinformation.
But it did, very well and for months. I’m not arguing with you. I’m telling you that you’re wrong. Your previous statements contain falsehoods (hue devices cannot be migrated to the NSPanel Pro and the hue bridge only exposes lights - both of which are demonstrably false), as does this one.
Yes. And I still haven’t learnt anything useful.
If you’re wrong, which you are, I’ll continue to argue with you.
To clarify.
I unpaired all my hue light bulbs (24), motion sensors (11), hue go (2), remotes (2) from the hue bridge.
The hue bridge is no longer used.
I paired everything to the NS Panel Pro directly with the zigbee auto discovery mode.
Everything is recognized and setup including smart scenes. Every time a hue sensor detects movement it will trigger one of the hue bulbs in that room.
But unfortunately the hue lights become offline.
They are dropped out of the Zigbee network. Hue motion sensors, smartplugs and remotes stay connected and online. It are the lights that randomly dropp off (offline)
I use the NS Panel Pro Home assistant integration to push the Zigbee devices connected to MQTT in Home assistant
Hi, I’ve located the relevant logs using the ID you provided. Please give me some time to investigate the exact cause. I’ll keep you updated as soon as there is any progress or if I need any additional information from you.
Thank you very much for your kind help. It has given us a much clearer understanding of the issue and its specific behavior. I’ll review the logs first and see whether I can find anything useful.
Hi, I’m reviewing your logs and noticed something unusual. Could you please confirm whether you added the same Matter Bridge to the NSPanel Pro more than once?
Could you try removing the Matter Bridge and adding it again to see if the issue persists? If it does, please submit the NSPanel Pro logs as soon as possible so I can investigate further.
Hello. Yes, when the lights started to misbehave, I removed and re-added the Matter bridge a few times. It’s working well from the panel now, and all devices attached to the Hue bridge appear and are correctly named in the app, but the app often gives a “failed” message if I try to control the lights from there. I’ve removed and added the Hue bridge, which has sent everything haywire again, and submitted feedback.
Hi, we have identified the cause of the issue you reported earlier, and it will be fixed in the August release.
Regarding this issue, I couldn’t find any related logs from your previous submissions. Could you please submit the NSPanel Pro logs and eWeLink app logs again? I’ll check and confirm whether it is a known issue.
