Skip to content
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

temporary guest wifi #289

Closed
Arkady23 opened this issue Apr 15, 2021 · 10 comments
Closed

temporary guest wifi #289

Arkady23 opened this issue Apr 15, 2021 · 10 comments
Labels

Comments

@Arkady23
Copy link

In yi-hack-v3, it is possible to connect to wifi with the data that was on the SD. If the SD card is removed, the connection went with the old wifi data. There was a script on the sd that copied the wpa_supplicant.conf file to /tmp/. It was very convenient and safe, so as not to lose control of the camera. Pulled out the sd and everything went back. It doesn't work that way right now. What is offered via the bin file is somehow not elegant, suitable for changing the wifi to permanently. And I would like to have a guest temporary wifi. While I'm thinking about how to do this, I decided to write.

@Arkady23
Copy link
Author

I think I found a way. In my opinion, you need to put the wpa_supplicant.conf file on the sd in the Factory folder. Tomorrow I'll take the camera to visit and check it out.

@Arkady23
Copy link
Author

Perfectly work.
Don't forget to edit "Your_WiFi" and "Your_password"!!!
wifi_on_sd.zip

@Pulsar981
Copy link

Could you please tell me how that worked for you, 'cause for me unfortunately it doesn't, it keeps saying "waiting for connection" with yellow light blinking.
Have you put the wpa_supplicant.conf file before or after a successful hack in the Factory folder? After the hack the folder "Factory" changes to "Factory.done", in my case. Your zip-file shows a "Factory" folder.
Where have you got the wpa_supplicant.conf file from? In my case when I reset the cam and do the hack (allwinnerV2) there's no such file on SD. I can find this file just in the case when using the cam with the official yi-home-app, then a "log" folder with ...tar.gz appears, with the wpa_supplicant.conf file in it.
(my goal is to use the cam without the yi-home-app, and without internet access)
Would appreciate if you find some time for a short reply.

@Arkady23
Copy link
Author

This feature has nothing to do with the hack. Don't interfere with the hack here. This is an option of the camera manufacturer. So it is provided, if there is such a file on the sd, then it is included in the work. And another such moment. This works on Allwinner models cameras. Is this feature available for allwinnerV2 cameras.... I don't know.

@Pulsar981
Copy link

I understand, haven't considered that this might not be available in the allwinnerV2. Seems like I have to keep trying other ways. Thanks

@WalkingDot
Copy link

It's working on Allwinner-v2, too.
However, I would recommend using the app for the initial setup.

@Pulsar981
Copy link

@WalkingDot have you tried that succuessfully? If so, could you please describe your process of doing that?
I've also tried with the yi-app to initialize first, then done the allwinnerV2 hack, then copied the modified wpa_supplicant.conf (with another ssid and pw) to the "Factory.done" folder (also tried copy to the SD root folder), but it keeps using the initialized wifi data ...

@WalkingDot
Copy link

@Pulsar981
Remove all files from the "Factory.done" folder and rename it to "Factory".
Then copy the "wpa_supplicant.conf" into the "Factory" folder.

@Pulsar981
Copy link

That worked for me! Thanks @WalkingDot
I've tried two ways succesfully:
a) When initialized with the yi-app before the hack, I had also to delete the "log"-folder (since there are the old wifi-settings stored). Then proceed how you advised - worked.
b) When reset the camera and do the hack without initializing with the yi-app before, it also worked with your advise. Camera connects on startup automatically to the wifi set up in the wpa_supplicant.conf.

Copy link

github-actions bot commented Apr 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Apr 6, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants