I know very little about that particular device, but just on general principles, we should Ask if your phone/tablet where you are trying to add the device is using a 2.4 GHz network, not a 5.0 GHz network.
It is very common that smart appliances and smart home devices will only work on 2.4 GHz Wi-Fi, not 5.0. That’s not a problem in daily operation, but during initial set up your phone/tablet will also have to be on 2.4 gigahertz in order to make the connection.
I don’t know for sure if that applies to this model, but it never hurts to have the phone/tablet on 2.4 GHz during initial Setup, so it’s worth checking.
Which version of the Android app are you running? There’s an updated version being released currently (v1.7.81.22) which I believe addresses this issue but we’ve seen problems onboarding appliances with Pixel devices in the previous app version.
I found another post that fixed the issue be removing an underscore from the SSID. I had a hyphen in the network password. When I removed the hyphen I was able to register the range.
Next question, how do I change the network settings on the stove, so I can see if it works with the hyphen now that it’s registered?
Those instructions look like they’re for the original app. I have the newer Smartthings app. So for example the three lines for the menu bar are on the right not the left. Then there is no network settings option.
Hey there! @KenH60, Welcome to the Community! I’m glad to hear that you were able to get the Range onboarded into the SmartThings Application.
As far as updating the WiFi, it used to be an option in the New ST App, However, the option detailed in the article above has since been removed from the Smart Things Application.
So, I just changed my WiFi SSID back to the original containing the hyphen. There’s too many other things on my network that I don’t want to reconnect…
Then I went back and tried to rediscover the range in Smartthings, thinking that it might work seeing that it had already registered my device. This time it failed with a 15-300. When I clicked on help, there was a number of possibilities including this one:
Blockquote * Check that the Wi-Fi network name uses only numbers and English letters, since unsupported characters could cause an issue
@SamsungZell Thank you for the reply. I think you were posting your reply at the same time I was typing my detailed analysis above.
BTW I was looking to change the Wi-Fi settings on the Range, not my hub. Any thoughts on that? Would that also fail on the hyphen?
Thanks to all that have read so far through this thread. I know there’s a lot here, but I wanted to document everything, and maybe save someone a few headaches.
As someone who has spent a lot of time on this, there is some good/bad news that should make fixing this relatively easy. As one who is fluent in the technology and also able to look in detail at the router tables, the good news is that if the problem is indeed with a hypen in the SSID name, this problem is in the Smartthings app and not the cooktop. The cooktop is fully able to register with the router using an SSID with a hypen in it and get an IP address. I can see the cooktop appear and disappear in the router’s DHCP tables: when I reset the cookstop (pressing the smartconnect button) the stove disappears from the routers tables (loses its IP address) and after registering the cooktop in the app in the app using the hyphenated SSID and giving the correct WiFi password, it is able to re-connect to the 2.4 GHz network and get a IP address, which is fully PINGable from any other device on the network, So the problem is not between the cooktop and the WiFi network. The problem is that something in the Smartthings (at least Android) app seems to then have problems actually adding the cooktop back as a set of known devices to the app for reasons that make no sense. It had no problem talking to the cooktop as it was able to give it the correct SSID and WPA2 password since the cooktop was able to fully re-register and connect to the WiFi network using the hyphenated SSID and successfully get an functioning IP address. So please simply fix the problem in the app that seems to have problems recognizing the fully functioning cooktop that is active on the network.
I’m glad to hear that you were able to get the Range onboarded into the SmartThings Application.