Can no longer pair devices with V3 Hub

I’m in the process of moving to a V3 hub from a V1 hub and am reconnecting all my sensors. I’ve successfully connected 40+ items, but now I’m unable to pair any sensors. I’ll go through the pairing process, the lights on the open/close sensor will flash like they’ve been paired, I’ll see something in the events on the hub on the IDE, but the app just hangs and doesn’t pair with anything, and no new device shows up in either the app or the IDE.

Here’s an example of the events I can see after trying to pair a sensor (nothing ever pairs in the app, no device shows up after the process):

zbjoin: {“dni”:“A365”,“d”:“24FD5B0001043DA3”,“capabilities”:“80”,“endpoints”:[{“simple”:“01 0104 0402 00 08 0000 0001 0003 000F 0020 0402 0500 FC02 01 0019”,“application”:“1B”,“manufacturer”:“SmartThings”,“model”:“multiv4”}],“parent”:“00D1”,“joinType”:1,“joinDurationMs”:2225,“joinAttempts”:1}

Name Value
archivable true
commandId 0
date 2021-08-04 1:25:52.000 AM PDT (2021-08-04T08:25:52.000Z)
description zbjoin: {“dni”:“A365”,“d”:“24FD5B0001043DA3”,“capabilities”:“80”,“endpoints”:[{“simple”:“01 0104 0402 00 08 0000 0001 0003 000F 0020 0402 0500 FC02 01 0019”,“application”:“1B”,“manufacturer”:“SmartThings”,“model”:“multiv4”}],“parent”:“00D1”,“joinType”:1,“joinDurationMs”:2225,“joinAttempts”:1}
displayed false
eventSource HUB
hubId 8345087d-1237-4552-8e5b-630de46883e9
id 9f2da35a-f123-4842-b2ac-7c21783a874d
isStateChange false
isVirtualHub false
linkText ST Hub 2
locationId 9dfa4d1d-5d3f-4c40-a7ac-722e779ee36c
name zbjoin: {“dni”:“A365”,“d”:“24FD5B0001043DA3”,“capabilities”:“80”,“endpoints”:[{“simple”:"01 0104 040
rawDescription
translatable false
unixTime 1628065552000
value zbjoin: {“dni”:“A365”,“d”:“24FD5B0001043DA3”,“capabilities”:“80”,“endpoints”:[{“simple”:“01 0104 0402 00 08 0000 0001 0003 000F 0020 0402 0500 FC02 01 0019”,“application”:“1B”,“manufacturer”:“SmartThings”,“model”:“multiv4”}],“parent”:“00D1”,“joinType”:1,“joinDurationMs”:2225,“joinAttempts”:1}
viewed false

I’ve tried pairing several different devices with the same results. I’ve even tried to set up a new device in the IDE, but when I click the “+ New Device” button, I get this error

Oh No! Something Went Wrong!

Error: 500: Internal Server Error

URI: /device/create

Reference Id: 3f13f05f-78c2-4371-9324-4e9202828102

Date: Wed Aug 04 08:46:00 UTC 2021

I’m having the same issue. Can’t add devices using the app or web. Reported the issue with Aeotec and tell me that the Samsung Cloud part is having issues.
Bought the ST yesterday so this is not a good start…

Same for me. Cannot add two GE Zwave dimmer switches. Have been trying since yesterday afternoon. Looking at the event log, it looks like they are getting added to the network but the devices themselves are not getting created. They get assigned a network ID, so I was going to try and manually add one via IDE but also was getting the 500 error.

Oh No! Something Went Wrong!

Error 500: Internal Server Error
URI /device/create
Reference Id 6f16cb38-b877-44a7-9f0a-435dbaa9ba17
Date Wed Aug 04 15:49:09 UTC 2021

Here is my zwjoin event - but it never actually gets added as a device.

Name Value
archivable true
commandId 0
date 2021-08-04 10:21:27.000 AM CDT (2021-08-04T15:21:27.000Z)
description zw:Ls2a type:1101 mfr:0063 prod:4944 model:3237 ver:5.54 zwv:6.04 lib:03 cc:5E,55,6C,9F,22 sec:26,85,59,86,72,5A,73,5B,70,7A
displayed false
eventSource HUB
hubId 510fc60e-3066-4cf2-97db-1f7bbf67cdc8
id 149e23a3-058b-4cc6-bad8-b0912f359947
isStateChange true
isVirtualHub false
linkText Home Hub
locationId 0406d8cf-5d37-4723-925e-4b054e5f669d
name zwjoin
rawDescription
translatable false
unixTime 1628090487000
value 20
viewed false

Maybe @Brad_ST can help

Are you using the iOS app? it’s buggy as hell right now. The pairing workflow never completes even if the device successfully pairs. The only way I can can tell right now that a new device has been successfully added is i’ll get a notification from Alexa that a new device has been added (via the SmartThings skill). Give it a while to pair, back out of the pairing process and go to the Devices tab. Tap the room drop down in the upper right and look for a “no room assigned” room. That’s where devices end up right now when I pair them using the iOS app.

That is very odd. I’ve had crash issues with the latest iOS build but haven’t had devices pair in the background like that.

As for users who aren’t seeing their devices pair at all, we are looking into the issue. It is limited to users with a location in NA01 and EU01. I’ll update when I hear the issue is resolved.

3 Likes

i’ve had two in a row do it. A Sonoff temp/humidity sensor and Third reality water sensor. I’ve stopped sending tickets in for the iOS app due to the quantity I would have to send. Hopefully the next update is well tested and fixes a lot.

Just received word that the issue should be resolved. I see that the errors have dropped off in our logs so if you were having trouble pairing please give it another go. Thank you for your patience!

3 Likes

I have the same issue with not being able to add new devices. Starting the process from my android app just leads to a timeout with no findings, and starting by pressing Add device in the web admin interface gives me the same mentioned 500 ISE message. I did add some new devices on Sunday 1st or Monday 2nd before the FW update without problems, but the FW update happened Monday night, and today I have these problems. I have a hub v3 and am situated in Norway.

Edit: And just as I posted the above, the issue is resolved… :slight_smile:

1 Like

All resolved for me (both issues). Thanks @Brad_ST and thanks all!

1 Like

@Brad_ST everything is pairing as expected again; thanks for your help!

@Automated_House yes on the iOS app, and I get the Alexa notification ~10-15 seconds before the ST app confirms a device has been added, but the app does confirm that the device has been added and allows me to rename it.

1 Like

Whatever was fixed yesterday must have fixed the app pairing confirmation issue. re-paired a device last night and and it made it all the way through the onboarding flow this time.

1 Like