Hub Firmware Release Notes - 25.32

Did you try adding a repeater close to your lock? It makes a big difference in the quality of the mesh and reliability of your lock communications. What you’re describing sounds like it can benefit from having one. Also as a temp measure try to reboot the hub and do a Z-Wave repair.

It happens when a DTH works with the classic app but not the V3 app. But then you can still control it with the classic V2 app.

1 Like

I did reboot the hub last night (I forgot the remove the batteries wooops do I need to try again?) but I am unsure how to do z-wave repair, can you describe how to do that? I am also using your multi lock smart app. I’m wondering if hub location and device smart lock have not changed location ever why are these problems starting now.

Ok I figured out where the repair button is and I did that and I could see it run and finish in live logging but the Schlage lock still shows as offline :frowning:

Also the door is near a wall and on the other side of the wall is the hub, I guess if you think a repeater would help I could get a long cat6 cable and move the hub to the other side of the wall which would put it right next to the lock almost?

Yes, need to power down or you can do it remotely from the IDE.
My Hub → List Utilities → Reboot hub

You can also do a Z-Wave repair from the same utilities page (wait for about a minute after the hub reboots before starting a repair)

Helps to have a repeater ideally, see this topic: FAQ: why would I need another beaming repeater if my zwave lock is already close to my hub?

1 Like

Ok I did the reboot hub option still shows offline. So now I have to buy something else lovely, is there anything you recommend? The smartthings door sensor directly above the lock works just fine

I still cannot add Fibaro Heat Controller device, I have to do it manually via Developer Workspace. And for good measure, now it won’t even work in new SmartThings app. So I guess after two months this issue is still not solved?

makes sure you don’t have any custom device handlers installed for the fibaro heat controller.

Why, they changed API again? Or they removed support for custom DTH?

Anyway I tried it, same result. I had to manually add device and since I deleted custom DTH, I had to use general Z-Wave thermostat, which is in new ST app, but obviously do not work at all, because it needs custom implementation.

I would recommend adding a repeater and checking the batteries.
Showing offline could be an issue with the health check features, if you can’t control it means the lock has either lock connection with the hub (it happens, exclude and re-pair the lock) or it’s having trouble with the mesh (add repeater and change batteries).

Open the thread you just linked, you’ll see my two months old comments.

There was a bug in ST firmware, which was also acknowledged by ST team – which I linked in this thread already. And it looks like it wasn’t fixed.

1 Like

I’m facing the same issues as Toka.

There’s a bug with custom handlers where they become stale. The sympton is you will pair the device, the device acts like it paired, but a device is never created in SmartThings. Deleting or re-publishing the device handler fixes the issue.

It’s true that the issue resulted from a FW change, but we don’t consider it a bug in the FW. The change we made was to report all the supported command classes to the cloud which is something we must do. The issue causing the problems with pairing certain devices is on the cloud side and unfortunately has been non-trivial to fix. We’re investigating workarounds that we can deploy cloud side to get things working again. I can’t commit to a timeline but I think we have a reasonable workaround identified.

I know in some sense it’s not important where the bug exists but I just wanted to clarify why it’s not something you see fixed in this FW release.

7 Likes

Ah, yeah. I keep forgetting about the v3 mobile app. I don’t use it, but I noticed that after last update (mobile app update) some devices show unavailable and cannot be controlled even though the show online and can be controlled with v2 app.

Thank you for clarification. Is there a way I can be notified, when the issue is resolved? It’s a showstopper for my DTH development.

Also, a bit of OT, but is there any information about the new hub-connected developer workspace? I’ve been registered in waiting list for a year now.

2 Likes

I have changed batteries already and they were fully charged when it quit working. What is the process to exclude and re-pair? Do I remove or delete it first? If I exclude and re-pair do I need to add it back to the routines and stuff where I had it before? Also what about all the codes in your multi user smartapp, will those need to be re-entered?

You can refer to your lock manual and you’ll need to the Classic app to complete the exclusion. Avoid deleting if possible. If not then delete it and reset the lock (see manual) and you may still need to exclude it manually using the exclude option in the Classic app under Hub utilities.
Unfortunately after an exclusion you’ll have to setup all your SmartApps that were using the lock again.
The good news is that if you’re using LUM, all you need to do after excluding/pairing the lock is to re-select the lock in the app and it’ll automatically program all codes into the lock (make sure you reset the lock after excluding it so it clears all the codes otherwise reprogramming may not work).

My hub went offline on the 19th and hasn’t came back online since. It could just be a coincidence with the upgrade, but what can I try? I pulled the batteries and plug and let it rest before retrying. The light flashes when first plugged in then goes solid. App says the hub is disconnected.

which hub do you have? and what color flashes when you powered it back on and what color when it changed to solid? did you try logging into IDE at https://account.smartthings.com and check the status there?

1 Like