Trouble with registering a device

I’m using the RPI version of st-device-sdk-c, but don’t let that confuse things here. The phone app is what seems to be giving me the trouble.

I’m working on my “Pool Controller” in the developer workspace. Below is the onboarding_conf.json. When I use the phone app to add the device, it doesn’t get far before the error message (see below).

I’m able to connect to the pool controller’s wifi without any problem and I confirmed from the RPI side that the phone did not try to connect to the RPI’s wifi. This is why I don’t think it’s an issue with the RPI code. Without log files on the phone app, I’m not sure how to debug this issue.

onboarding_config.json
{
“onboardingConfig”: {
“deviceOnboardingId”: “Pool_Controll”,
“mnId”: “0A4b”,
“setupId”: “001”,
“vid”: “ST_255a6219-9cf1-47bb-89f9-7a26aa86c941”,
“deviceTypeId”: “Others”,
“ownershipValidationTypes”: [
“QR”
],
“identityType”: “ED25519”,
“deviceIntegrationProfileKey”: {
“id”: “803dab36-1405-48ac-8fc8-b6fd6f0ebd61”,
“majorVersion”: 0,
“minorVersion”: 1
},
“productId”: “60b679ec-81ff-4300-8209-05cbd5e7659f”
}
}

Hi, @dcabot25. Let me check with the team if they can see the logs of that error code.

Wait, I just re-read the issue and I’m not sure why you’re still connected to the device’s local Wi-Fi when you’re in the process to install it.
As mentioned in the error, the connection to that local Wi-Fi doesn’t allow access to SmartThings because it is not an internet connection…

Hi @nayelyz I see your confusion. No, I’m using a laptop that’s connected to the RPI via eth0 to monitor the /var/log/daemon.log file. Manually connecting my phone I would see this:

May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPDISCOVER(wlan0) 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPOFFER(wlan0) 192.168.2.7 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPDISCOVER(wlan0) 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPOFFER(wlan0) 192.168.2.7 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPDISCOVER(wlan0) 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPOFFER(wlan0) 192.168.2.7 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPREQUEST(wlan0) 192.168.2.7 92:d3:58:1f:3f:e5
May 5 19:31:00 pool-controller dnsmasq-dhcp[8416]: DHCPACK(wlan0) 192.168.2.7 92:d3:58:1f:3f:e5 David-s-S10

and I don’t see that when using the app to discover the device.

It’s as if when the phone app sees the SSID “Pool_Controll_E40A4b0016lWmmiim5” it decides something is wrong and quits.

Make sense?

Pool_Controll_E40A4b0016lWmmiim5

I know where “Pool_Controll”, “0A4b”, “001”, and “iim5” are coming from. I don’t know where the “E4” nor “6lWmm” are coming from and why having those in the SSID is causing the phone app to quit.

Hi @nayelyz . I rebuilt my RPI and I’m still stuck at the same place. I really need help with what’s going on the phone APP side of this.

Yes, sorry for the delay, I was checking some details with the internal team.
SmartThings doesn’t have an official release that supports RPi, so, we’re not sure from where you got the version you mentioned:

Regarding the error, are you (by any chance) using an old direct-connected project and registering new test devices?
The team checked your onboarding config and suggested you download the onboarding_config.json file again:

  1. You would get a new SSD like Pool Controll_E40A4b0016lWmmiim5 instead of Pool_Controll_E40A4b0016lWmmiim5 (underscore in the middle of the name)
  2. Use that new onboarding file in your device.

@nayelyz you nailed it! I updated the onboarding config like you said and it worked. Thanks!

Anytime! Thank you for letting us know your results