Add fallback to connect to wifi when Wyzecam v3 debug enabled.#106
Open
BiatuAutMiahn wants to merge 7 commits intoHclX:masterfrom
Open
Add fallback to connect to wifi when Wyzecam v3 debug enabled.#106BiatuAutMiahn wants to merge 7 commits intoHclX:masterfrom
BiatuAutMiahn wants to merge 7 commits intoHclX:masterfrom
Conversation
Implemented WLAN configuration and handling when native Wyze debugging is enabled.
Forgot udhcpc
|
I have the ability to stream h264 from the cameras as part of a larger project I am getting ready to upload to GitHub. Before I do that, I’d like to find an alpha user.
It just occurred to me yesterday that just the streaming hack may be of more interest than the rest of the project.
There’s a quick demo video here:
https://www.youtube.com/watch?v=h1Xa3kCbsvI
You can read about the project here: ( I talk about the streaming way down at the bottom in the Updates: section )
http://www.sonic.net/~crb/ReadMe.html
The code is rather crufty right now and I’ve only tried it on a V2 cameras. I have a V3 and getting it to run on that is on my todo list.
… On Apr 1, 2021, at 3:47 PM, BiatuAutMiahn ***@***.***> wrote:
Background: While exploring methods of establishing an h264 stream from the camera I noticed that killing /system/bin/assis, /system/bin/hl_client, and/or /system/bin/iCamera the system would reboot a few moments after. Thus preventing any attempts to poke and prod around the system. Reviewing the init process shows that if /configs/.debug_flag exists app_init.sh will not spawn these processes. However after creating this file, I ended up soft bricking my device.
This PR resolves this matter by implementing a few configuration options to:
A, Enable/Disable the debug mode.
B, look for wlan.new in the nfs share to update wpa_supplicant.conf and restart wpa_supplicant
C, Specify WLAN SSID and KEY in the config.
You can view, comment on, or merge this pull request online at:
#106 <#106>
Commit Summary
Implement WLAN Config & fixes
Update hack_ver.inc
Update main.sh
Tests
Fixes
More Fixes
More Tests
File Changes
M installer/config.inc.TEMPLATE <https://github.com/HclX/WyzeHacks/pull/106/files#diff-44d2bbb6651f66b186453284c2213283a84025b4e4f001e02a01b556d004d166> (12)
M wyze_hack/hack_ver.inc <https://github.com/HclX/WyzeHacks/pull/106/files#diff-04d124532681cad49e11c2f9632532a342ab9a4fbe5aa61f805a2b74dfdb6be3> (2)
M wyze_hack/main.sh <https://github.com/HclX/WyzeHacks/pull/106/files#diff-2729b72c28b9ef22b4d5603e17d5f7183cecefe1631834e4a246c3a033abdda8> (71)
Patch Links:
https://github.com/HclX/WyzeHacks/pull/106.patch <https://github.com/HclX/WyzeHacks/pull/106.patch>
https://github.com/HclX/WyzeHacks/pull/106.diff <https://github.com/HclX/WyzeHacks/pull/106.diff>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#106>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBXSYFLYL6PYI2QFKBSLRDTGTZYZANCNFSM42H45WPQ>.
|
Author
|
Thx, im currently in the process of compiling the uboot to try and get the ispmem variable in the kernel cmdline then attempt to stream from the V3 again |
|
Sounds good. Good luck. There are probably many different ways to get video off the camera.
… On Apr 1, 2021, at 7:08 PM, BiatuAutMiahn ***@***.***> wrote:
Thx, im currently in the process of compiling the uboot to try and get the ispmem variable in the kernel cmdline then attempt to stream from the V3 again
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBXSYGPNAYPEJORMBEXUZLTGURJXANCNFSM42H45WPQ>.
|
Author
|
Seems i've missed something Update: |
This looks very promising on a stock camera. I like the progression you are making, especially on stock camera firmware. The local h264 streaming sounds very cool. I have something similar to your cli except I am using plain ole Korn shell and wget commands to interact with the wyze API mostly because I don't know how to program in python, hehe. It's very kludgy but so far works well, until, like you say, Wyze changes their API. |
|
@BiatuAutMiahn were you able to get a working uboot compiled? |
Author
|
Unfortunately no, I abandoned this project after Wyze pretty much made this irrelevant |
|
@BiatuAutMiahn, perhaps I can pick your brain since you were working on replacing the bootloader, is it possible to flash via serial? or just via /dev/mtd0? |
Author
No, but I was able to put the bootloader on the sdcard and managed to use the uboot serial prompt to flash it |
Author
|
At one point I managed to get the T31 toolchain in attempt to make my own binaries and hopefully get uboot compiled but life happened and I switch focus. If we can get some kind of discord or telegram thread going I can hop back on this project for a while but I'm by no means an expert. |
|
checkout t.me/wzmods @BiatuAutMiahn |
|
Hi guys, y’all seem like the ones that would have answers to some questions I’ve always pondered. |
|
the sd card update is done by the bootloader. once the bootloader loads the kernel, it takes over everything. |
|
This may be going a little sideways I just figure considering you guys build uboot images, you know about compiling. I notice the build toolchain of mips-gcc472-glibc216-32bit-r2.3.3 is on here. How would I use that to compile tcpdump for the cams. I know I would also need to compile libpcap. My linux uname comes up with 'i686 i686 i386 GNU/Linux' (if that's important) and what special CFLAGS=, LDFLAGS=, etc would I need to make sure I use the uClibc that the cams do. |
|
wz_mini includes a static build of tcpdump, cross compiling can be a pain. |
|
Didn't notice that. You been busy. Great job on that repo!! :) Thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background: While exploring methods of establishing an rtsp stream from the camera I noticed that killing
/system/bin/assis,/system/bin/hl_client, and/or/system/bin/iCamerathe system would reboot a few moments after. Thus preventing any attempts to poke and prod around the system. Reviewing the init process shows that if/configs/.debug_flagexists app_init.sh will not spawn these processes. However after creating this file, I ended up soft bricking my device because it will no longer connect to the network.This PR resolves this matter by implementing a few configuration options to:
A, Enable/Disable the debug mode.
B, look for
wlan.newin the nfs share to update wpa_supplicant.conf and restart wpa_supplicantC, Specify WLAN SSID and KEY in the config.