-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP8266 switch_example #134
Comments
I think GPIO config went wrong. Could you check device_control.h file in switch_example? There are GPIO pint number setting like below. You can modify GPIO Pin settings according to your device kit.
|
Actually I need only one button and one LED pin. Button->5 and LED->14,15. So I have removed the extra pins. And there was a issue with GPIO pins. I settled it but now I am stuck at this point.
LED is glowing on board at GPIO 14,15. But this device is not recognized by smartthings app yet. Also the code gets stuck at this point. Please help. |
Did you enable developer mode in smartthings app? Also could you check there is wifi advertising SSID something like NAME_E4***QD5f. |
Yes I have enabled developer mode. Where to check this wifi SSID? |
Did you also change onboarding_config.json with yours? Looks like you use default empty onboarding_config.json. Your onboarding_config.json can be downloaded from your Project on DevWS. |
Yes I did change onboarding config and device info |
it's wired. Then your onboardingId is "NAME"? In below log, looks like onboardingId set as "NAME".
Could you share your onboarding_config.json? Also could you clean build and rebuild it? Json files are not included in build dependency so you might need to clean and rebuild after changing json files. |
I am using the command
which I guess builds automatically
This is my onboarding.json |
Then please clean and try to rebuild it after replacing json files.
|
My device is detected by smartthings app. But it is not fully connected. It gives an error after 34% saying
And giving this error on monitor
and this also
Errors are highlighted in bold. |
Are you using IOS or Android? And your ST app looks like old version. Could you update latest ST app and try again? |
It says,
on the latest version(1.8.01.22) downloaded from play store. |
Did you enable developer mode after reinstall? Also could you check https://github.com/SmartThingsCommunity/st-device-sdk-c-ref/blob/develop/doc/getting_started.md#add-a-product-info At above, you can add availability country in product info. You need to add your samsung account country at that. |
Yes I enabled developer mode. Atleast on the older version, the connection was starting but new versions are not allowing to connect the device @junyoun-kim |
Then how about country availability setting? |
The site is not currently supporting. But as far as I know, India and US regions are set as available there. But I will check as soon as the site opens |
Hmm.. Could you share mobile log? We need ST app log to identify issue. |
How can I share them? |
On phone number, press *#9900#. Press "Run dumpstate/logcat" and after that, "Copy to sdcard". And then you can get dumpstate file under "Log" folder. |
@junyoun-kim I have sent the logs to [email protected] . |
After unzip the log you sent, dumpstate file in it was 0 byte. Could you check your dumpstate file? |
@junyoun-kim I have shared the file now. Can you please check it? |
The connection process goes till 99% but then this error is coming.
@junyoun-kim please help... |
Please check your email |
I am working on switch_example on esp8266 using the code from this repo. Have followed all the steps mentioned in this repo and espressif website. Also I have run the example from ESP_RTOS_STDK so that my enviorment check is done. But now when I am trying with switch_example, I am stuck at this point. I couldn't figure out whats the problem and my device is not connected to wifi and smarthtings app also not recognizing the device.
also when I have connected the LED on board, the switch thing is working. Please help me...
The text was updated successfully, but these errors were encountered: