All Z-wave devices just stopped working

Same issues here. Most zwave devices have just stopped working. I did manage to change a few of my GE Zwave switches to the philh30 drivers which fixed some of the issues, but not all.

I have the same problem.

All devices stopped responding today.

They show connected, but no longer functioning.

Im having the same issue. I noticed that on 1/3 at about 6am..all of my smart lights automagically turned on. After that..nothing else worked..smart lock and all went offline…I tried to reset the devices but they were no longer recognized by the Hub as being new adds. I will buy a new light and attempt to add to try to narrow down the cause. If hub doesnt recognize as new..then that narrow it down a bit. HELP!

Let’s hope @nayelyz can help us on monday

I’m having the exact same issue.

Tried all the usual to no avail…

  • Rebooted
  • Reconnected device
  • Tried new drivers
  • Tried new devices

It appears any zwave just does’t work but cloud devices do.

I’m brand new with the CLI - How do I tell if the hub processes and emits the events? How do I issue a refresh command from the AWA (is this my.smartthings.com?)

To see what the hub is sending/receiving from devices, you need to do driver logging. Use the command “smartthings edge:drivers:logcat” and select the driver for a particular device.

The AWA is the Advanced Web App found at SmartThings. Add a little smartness to your things.. Select a device and scroll down the page to the Commands section.

Hi everyone,
Our engineering team is already aware of your reports, but they’ve asked for some additional information in order to begin the investigation.

  1. Date and approximate time on when this happened
  2. Submit the hub logs as soon as you notice the issue.
  1. In the Advanced Users app, enter the “Hubs” section
  2. Enter the corresponding Hub and click on “Dump Hub logs”
  3. Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
  4. You’ll get a green box at the top confirming the Hub logs were requested.
  1. If you have more than one Hub, the name of the one involved in the issue.
  2. Finally, open support access so we can get the corresponding Device’s IDs and see other properties of the hub:
  3. Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
  4. Enable support access to your account:
  1. Go to the SmartThings Web (my.smartthings.com)
  2. Log in to your Samsung Account
  3. Select Menu (⋮) and choose Settings
  4. Toggle on Account Data Access
  5. Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.

See more information about this access here: https://support.smartthings.com/hc/en-us/articles/36170233944852-Enabling-Account-Data-Access-for-Support

Thanks @Itati ! My issue started around 10 am -ish central time on 1/3/26. I had activated a few of the affected switches around 9:30am central that I could no longer turn off at 10am ish. I did submit a support ticket (i dont see any identifying case number or anything to share) but I do use the same email as I do here on the community. I also dumped the logs from my Hub that day or the following day so hopefully that helps. I believe when I opened a case it auto enabled account data access as it was enabled on the 3rd when I opened the case.

Please let us know if there is anything else we can provide to help resolve :slight_smile:
Thanks again for your help!

Hi, I’ve enabled access and dumped the log.

Approximate time: midnight january 4

I’ve enabled access and requested dump.

4th Jan 2026 approx 17:50 GMT

Hello @Itati, my devices last reported on January 1st 2026 at 7:00pm EST which was just a matter of minutes or less after a mains restoration.

I have only one hub and hub logs were dumped a day or two ago after I learned how to do it.

Support access already opened but I will extend.

Email is the same.

Same issue, started 8:00 pm January 4th. I thought it was something I did when I replaced a battery and it would not connect, so I did a hard reset on my system. Doh!

Hi, I’ve enabled access and dumped the log.

Approximate time: 18:00 january 4

@jrs185p
Please follow the steps below so we can continue tracking and investigating your issue.

@Itati - Done

Same issue here with v2 hub on 000.058.00010 firmware.

All Z-wave and zigbee devices stopped working on12/29. I tried the same things everyone else in this thread have then reported it through the Samsung Members app, but haven’t gotten any solution yet (takes them like 24 hrs to respond to each question). I figured it was a larger problem since I did not make any changes to my setup in a while and everything stopped working. Couldn’t find any other reports when it happened though, but somewhat relieved that it’s not just me, and hoping we get a solution here.

Here is some additional information based on the testing I’ve done.

  • Zigbee

    • I only have 3 zigbee devices and I have deleted all 3 from the app trying to remove/re-add to see if that helped. It did not and I cannot add them back.
    • I later installed the CLI and can see the deleted zigbee devices sending events to the hub when manually activated. 1 is a motion sensor and I see events when motion is detected, the other 2 are outlets and I see the on/off events being sent when I manually click the button on the device. Updates are not reflected in the app though.
  • Z-Wave

    • I have 8 z-wave switches/dimmers in my house and 1 door lock
    • I am unable to exclude or re-add any of them
    • There are no events being sent to the hub for these when manually operated
    • I installed the ‘Z Wave Explorer’ driver to see if I could get any more details. I don’t get any details from that driver, but I found that for each switch, if I go change the driver to ‘Z Wave Explorer’, I see that event in the CLI log. Then if I switch the driver back to ‘Z Wave Switch’, that even also appears and a I can control the switch from the app one time. I also see that control event in the CLI log, but then it is immediately unresponsive again. Can’t control it anymore and no events being sent to the hub when I manually operate the switches/locks
    • The Lock will work after performing this driver swap longer than the switches, but within an hour or less it becomes unresponsive again.
    • I also found that if I perform the above driver swap, my automations that use these devices will only work if I go in and re-save them. But the same issue that the device can only be operated 1 time before going back to being unresponsive happens here.

Everything else I have connected through the partner services still works (Ring devices, wifi plugs, etc.).

When the problem initially started, I checked my app version on 12/30 and it had not been updated yet so I don’t think it was the recent app update that broke it.

same to me. All show online. but not able to command. Zigbee or Zwave.

As I am not on the location there is nothing I can do.

My devices stopped info on 5 januari from 11 a clock eastern europe time.

the person who takes care of the location only could switch the hub off and on

Lucky temperature is above zero celcius. I cannot command the central heating

firmware 000.058.00010

my aeotec cameras via Wifi work.

what can I do? Help!

I prepared the hub and granted data acces for 1 day

Pls take also my hub. I prepared the hub and granted data acces for 1 day

hub D052A81713E60001

5d355ff1-ef95-4fab-8d18-2aad4efcfe80

What makes me nervous is that your problem started on 31-12. mine today 5-1.

till that moment everything worked perfect..

Is your problem solved?