3 of 3 people found this helpful
First of all, you need to have in mind that when you run the "sk_chek.bat" it reboots the Sphere Kit. I've had a similar problem as even I've had everything properly configured when I tried to run the script it was trying to take the wifi configuration just at the end of the restart and the wifi configuration was not initialized yet. (As it needs more time)
Try one thing, I suppose that you've had configured the wifi via azsphere device wifi add --ssid <yourSSID> --key <yourNetworkKey>, right? So, go to your "sk_check.bat", edit it and just below the lines which make the sphere to restart, insert this line mentioned before (obviously with your ssid and password of the wifi), and you will see that when you try to read the information again, maybe the first time it gives you an error, but if you let the script running it tries to do it again automatically and you will see that on the second time the console will turn the font to green and the wifi will be properly configured and everything will work!
Hope it helped!
3 of 3 people found this helpful
Thanks for the answer. I had the same problem, wi-fi appeared configured in command prompt, but the sdk application showed Device IP: wi-fi not configured.
I added a TIMEOUT /T5 in the bat file. That didn't work, Device IP field became empty.
I then added azsphere device wifi add --ssid --key line you mentioned.
Now Device IP shows my IP
After such a lengthy register process, I was about to loose it with this last error. I'm glad I went to bed, this little thing survived.
2 of 2 people found this helpful
Adding TIMEOUT /T 5 didn't worked for me too, just add few more delay to it. IP Field appeared blank for me too.
i did TIMEOUT /T 10 and Success.
Thank you, this helped me fix the issue where the IP was not picked up. Still I was having an issue in the message box that pops up after the script runs - "ERROR: Invalid Wi-Fi MAC Address for an Avnet Starter Kit". This was fixed by replacing the "find" command in the :validateMAC section with "findstr".
5 of 5 people found this helpful
I had the same issue as you.
The solution is mentioned on another thread. In a nutshell, a delay in the script will allow it to populate the device IP field.
To do that, open the sk_check.bat file in a text editor, and after line 25, insert a line with this text:
TIMEOUT /T 5
Now when you use the registration program, it will pause for a while, and the end result is that the field will be correctly populated.
Thanks for the answers!
The timeout solution works fine.
Thank you. This helped me.
i used to wait for 30 seconds once i connect the board , but that script wait seems a better trick , will try it once i have the chance
The TIMEOUT /T 5 solution works for me.
Thanks @shabaz mudz and netshadow ! I was having the same problem.
I added a timeout for 10 seconds after line 25 of the sk_check.bat file like you guys suggested and it worked.
Previously, before I used this solution, I had to restart a few times to get it to work. I have used the Azure Sphere with different WiFi access points and I noticed that it was easier with some. I'm guessing how quickly your WiFi configures depends on the access point it's connecting too?
Anyway, thanks for the help guys and good luck with the contest if you're entering!
Have you read it? Give it a look
It's not an error, It's telling you what data your device has sent to azure cloud, you probably had gotten an email and sms regarding your ping to server.
See the last line error': '0' there is no error. you are good to go !!
if i execute "azsphere device wifi show-status" in Azure sphere command.....
Configuration state : enabled
Connection state : connected
Security state : psk
Frequency : 2422
Mode : station
Key management : WPA2-PSK
WPA State : COMPLETED
IP Address : 192.168.100.33
But in Azure sphere starter kit sync connect server
Result is, Device IP: Not configured
Not sense, waching "sk_chek.bat" seems right.