Z-Wave device repeatedly dropping after firmware 0.60.11 — Qubino Flush Shutter DC

Devices & Integrations
1

Subject / Opening line: Z-Wave device repeatedly dropping after firmware 0.60.11 — Qubino Flush Shutter DC

Hi team,

I am experiencing a Z-Wave device instability issue that started after updating to hub firmware 000.060.00011 on my Aeotec Smart Home Hub.

Hub EUI: D052A8C557160001

Issue summary:

One of my Qubino Flush Shutter DC (ZMNHOD3) devices, which had been completely stable for over 2 years alongside identical devices on the same network, suddenly disappeared from my SmartThings network. When I re-add it, it disappears again after a short time. This has happened repeatedly.

Additionally, when I run a Z-Wave network repair, the affected device (and the newly re-added replacement entry) shows “something went wrong” in the repair results. All other Z-Wave devices on the network are unaffected and working normally.

What I have tried:

• Full power cycle of the hub (unplugged for 30+ seconds)

• Z-Wave exclusion and re-inclusion of the device

• Running Z-Wave network repair multiple times

None of these have resolved the issue. The problem appears to have started with the 0.60.x firmware series.

Hub logs have been dumped on e.g. 23 March 2026, 16:00 GMT +10 I have also enabled Account Data Access on my account for your team to investigate.

Any assistance or escalation to the engineering team would be greatly appreciated.

Apologies if I’m in the wrong place here. New to posting

Thanks,

Chris

───

2

Hi, @Chris_Ryan
The engineering team looked at your hub logs and they noticed the following:

The re-onboarding attempt failed due to the device not responding to some communications over the mesh network.
You need to ensure the node is close enough to the Hub to communicate directly or add adequate routers between the Hub and the device.

3

About this, @Chris_Ryan, do you mean it didn’t appear in the SmartThings app or my.smartthings.com/advanced at all?

If you re-add it successfully and it happens again, please share a new timestamp and submit the hub logs and, it would be helpful if you let the device in that state so the team can analize the logs using the original device IDs.

Also, please provide a screenshot about this to have a better reference on what you mean.

4

Thx Nayelz. Appreciate your help on this. To confirm I have positioned it close to the hub. Perhaps too close? I will place it 5m away.

I have been able to re-add multiple times. However before doing that I have to force delete it as the normal exclusion does not work. I then re-add it successfully. After a period the device then goes “offline”.

I will do the process again in about 8 hours and submit logs. Thanks again.

5

ok, and does it come back if you trigger an event in the device directly? I ask because this means the device would have to “report” back to the hub and thus make it online, if it doesn’t come back, then there’s an issue with the communication path.
It’s also weird that the normal exclusion mode doesn’t work. When you select this option, do you follow the correct steps on the shutter to put it in exclusion mode as well?

6

Exclusion mode has never worked for this it seems. I will have to trigger the device directly manually as normally it sits close the the window it controls without a manual switch. But I can do this no problem. I will revert back. Thank you

7

Thank you for your ongoing support. Pls note

  1. I excluded the device using z wave utilities successfully.

  2. At 16:50 I re-added the device. It shows as "connected " attached screenshot. It is not operational. I called it “Stairs 2”

  3. At 16:51 I dumped the logs.

Hope you can help.

Thx

Chris

28411.jpg1080×2340 269 KB

8

In case you want the attached, this is what i see when doing z wave repair.

(attachments)

Screenshot_20260326_170014_SmartThings.jpg
Screenshot_20260326_170014_SmartThings.jpg1080×2340 171 KB

9

Hi, @Chris_Ryan
Sorry for the delay.
Did you remove the device “stairs 2”? I can only see a “stair” device and it has a status of “opened”. And it was created on 2026-03-29.
This is to check if the device ID might have changed.

10

Hi - I ended up having to remove the old device multiple times. Eventually when I excluded 1 device the hub excluded 12 devices on its own. I think these must have been ghost nodes. I then tried to re-add the original device and it failed again. So I added a replacement device and it worked. Thank you for your help. I am unsure on what has actually happened.

11

ok, thank you for letting me know.
Regarding the devices, I also think they were ghost nodes since the physical device must be in exclusion mode as well.
It might have triggered the correct step to “repair” the network. And about the device not being able to onboard, it might be a hardware issue. I’ll see if the engineering team can find the logs for such device to confirm there was a missing response from it.

Please let me know if the new device starts failing too.

12

No problems. Thx for letting me know.

I undetstand if the team do not have time to examine logs of 1 device.

I appreciate your help