Problems today? (April 2016)

[JDRoberts]

@Mbhforum

So this morning I woke up again to unresponsive zWave. I hard booted the hub, and it came back…I tried a zWave repair and it fails on other devices now. It seems to be random. Anyone else ever experience anything like this?

The following thread has some things you can try:

FAQ: Zwave repair not working (how to fix error messages)

I’m having challenges with several of my zwave devices working. When I attempt to do a network repair inside of the zwave utilities, I don’t get any action being performed on the hub. I’ve run the repair from both the android application and from the website. When I watch the log after selecting repair, no entries show up in the log. Suggestions?

But there’s also an entirely different problem that some people have after the recent update, so definitely report it to support@smartthings.com

Here’s the thread on the recently introduced problem. Note that this is apparently only affecting a small percentage of users:

No Z-Wave since firmware update to 14.38 on 4/21

Wanted to post this here since I know it’s affecting at least @denis and it’s hard to track in the other thread. Since the update, I’ve lost all control of all my z-wave devices. Cloud integrations still work fine. Most ominously, we both see some variables set to false that we’d rather not see: zwaveHomeID: C58D3EEF zwaveNodeID: 01 zwavePowerLevel: full zwaveRadioDetected: false zwaveRadioEnabled: true zwaveRadioFunctional: false zwaveRegion: US zwaveSerialVersion: 4 zwaveSucID: 01 zwaveVersion: 3.83 I’ve rebooted, power cycled, disabled+enabled the z-wave module, all to no effect. We both have tickets open with support. I’ll update the thread with any news. Feel free to chime in if you have the same problem and make any progress.