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.

Sign up for GitHub

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

Jump to bottom

Wyze Cam OG not working #677

Open
mr-bobdobalina opened this issue Jan 18, 2023 · 144 comments
Open

Wyze Cam OG not working #677

mr-bobdobalina opened this issue Jan 18, 2023 · 144 comments

Comments

@mr-bobdobalina
Copy link

mr-bobdobalina commented Jan 18, 2023 •
edited
Loading

Not seeing the Wyze Cam OG showing up on the bridge. Running docker compose up (without the -d) I don't even see it listed in the initial "Connecting to..." section.

I also did FRESH_DATA=true on my yml.
@ScottySTL
Copy link

I just got my new Wyze Cam OG going as well and it's not showing up on the bridge either. I am assuming it is not yet supported?

@talormanda
Copy link

Same issue here.

@jmluxem
Copy link

jmluxem commented Jan 20, 2023

Same issue here. I have the new Pan v3 also, which worked right away. Wyze Cam OG is not working.

@mrlt8
Copy link
Owner

mrlt8 commented Jan 20, 2023

Thanks for the data points! The OG seems to be using a different P2P protocol than all the other cameras (similar to the Doorbell Pro).
Currently looking into alternate methods to access the stream.

@ScottySTL
Copy link

Do you think it will be possible to find a way to access the stream via docker at some point in the future?

@adricrist87
Copy link

Same here, hopefully something is worked out within the 30 day return window otherwise they are going back :(

@ScottySTL
Copy link

Unfortunately, this could be Wyze purposely finding ways to now allow this kind of access to streams (So they can keep pushing their Cam Plus subscriptions)

@cheme75
Copy link

cheme75 commented Jan 20, 2023

Unfortunately, this could be Wyze purposely finding ways to now allow this kind of access to streams (So they can keep pushing their Cam Plus subscriptions)

Sadly I tend to agree it may well be wyze intentionally changing for the new hardware to force the subscription. It started to become clear when the lite version was only offered for v2 and v3 cams and the new hardware omitted the lite option. I really don’t need all the extras. For next house I’m considering going with something like amcrest poe cams if I can get some cables run before they drywall it. Or I’ll breakdown and get a couple HomeKit compatible cams since we really won’t need much in new location.

@mrlt8
Copy link
Owner

mrlt8 commented Jan 21, 2023

I believe the protocol change has more to do with the fact that the OG/3X and the Doorbell Pro seem to be designed and/or produced by "gwell", whereas the other cameras were mostly Hualai cameras.

@adricrist87
Copy link

I believe the protocol change has more to do with the fact that the OG/3X and the Doorbell Pro seem to be designed and/or produced by "gwell", whereas the other cameras were mostly Hualai cameras.

Hey thanks for getting back to us. Do you anticipate we will eventually be able to bring these OG into the bridge container? Is this work in flight or out of scope at the moment? That would help me decide wether to return these or hold on to them.

Thank you.

@mrlt8
Copy link
Owner

mrlt8 commented Jan 21, 2023

Potentially, but it may be more cloud dependent than our current solution (which could also mean it gets blocked by wyze).

Can you test: http://localhost:5000/webrtc/ogcam-name

@adricrist87
Copy link

adricrist87 commented Jan 21, 2023 •
edited
Loading

Tried this link http://192.168.2.101:5000/webrtc/Driveway2 and got {"cam":"Driveway2","result":"cam not found"} but if I try a V3 Cam I can pull it up fine.

@talormanda
Copy link

Tried this link http://192.168.2.101:5000/webrtc/Driveway2 and got {"cam":"Driveway2","result":"cam not found"} but if I try a Cam V2 or V3 I can pull them up fine.

same

@adricrist87
Copy link

Here is my docker log, It only picks up the 3 V3 Cams:

2023/01/21 03:56:01 [WyzeBridge] 🚀 STARTING DOCKER-WYZE-BRIDGE v1.11.3

  • Serving Flask app 'frontend'
  • Debug mode: off
    2023/01/21 03:56:01 [WyzeBridge] 📚 Using 'user' from local cache...
    2023/01/21 03:56:01 [WyzeBridge] ♻️ Refreshing camera data for thumbnails
    2023/01/21 03:56:01 [WyzeBridge] 📚 Using 'auth' from local cache...
    2023/01/21 03:56:01 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
    2023/01/21 03:56:01 [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
  • Running on all addresses (0.0.0.0)
  • Running on http://127.0.0.1:5000
  • Running on http://172.17.0.4:5000
    2023/01/21 03:56:01 [WyzeBridge] Press CTRL+C to quit
    2023/01/21 03:56:06 [WyzeBridge] 💾 Saving 'cameras' to local cache...
    2023/01/21 03:56:06 [WyzeBridge]
    🎬 STARTING ALL 3 CAMERAS
    2023/01/21 03:56:12 [WyzeBridge] ☁️ Pulling "Front Door Cam" thumbnail
    2023/01/21 03:56:13 [WyzeBridge] 192.168.2.215 - - [21/Jan/2023 03:56:13] "GET /api/sse_status HTTP/1.1" 200 -
    2023/01/21 03:56:17 [WyzeBridge] ☁️ Pulling "Driveway Cam" thumbnail
    2023/01/21 03:56:23 [WyzeBridge] ☁️ Pulling "Back Yard Cam" thumbnail
    2023/01/21 03:56:23 [WyzeBridge] SET WB_IP to allow WEBRTC connections.
    2023/01/21 03:56:23 [WyzeBridge] Starting rtsp-simple-server v0.21.1
    2023/01/21 03:56:23 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - front-door-cam on 192.168.101.75 (1/3)
    2023/01/21 03:56:23 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - driveway-cam on 192.168.101.217 (1/3)
    2023/01/21 03:56:23 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - back-yard-cam on 192.168.101.234 (1/3)
    2023/01/21 03:56:30 [Back Yard Cam] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 73%) FW: 4.36.9.139 🔒 (DTLS) (2/3)
    2023/01/21 03:56:30 [Back Yard Cam] 🔊 Audio Enabled - ALAW/16,000Hz
    2023/01/21 03:56:30 [Driveway Cam] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 36%) FW: 4.36.9.139 🔒 (DTLS) (2/3)
    2023/01/21 03:56:30 [Driveway Cam] 🔊 Audio Enabled - ALAW/16,000Hz
    2023/01/21 03:56:30 [Back Yard Cam] WARNING: Skipping smaller frame at start of stream (frame_size=1)
    2023/01/21 03:56:30 [Driveway Cam] WARNING: Skipping smaller frame at start of stream (frame_size=1)
    2023/01/21 03:56:30 [Front Door Cam] 📡 Getting 120kb/s HD stream (H264/20fps) via LAN mode (WiFi: 36%) FW: 4.36.9.139 🔒 (DTLS) (2/3)
    2023/01/21 03:56:30 [Front Door Cam] 🔊 Audio Enabled - ALAW/16,000Hz
    2023/01/21 03:56:30 [Front Door Cam] WARNING: Waiting for keyframe
    2023/01/21 03:56:32 [RTSP][FRONT-DOOR-CAM] ✅ '/front-door-cam' stream is UP! (3/3)
    2023/01/21 03:56:32 [RTSP][DRIVEWAY-CAM] ✅ '/driveway-cam' stream is UP! (3/3)
    2023/01/21 03:56:33 [RTSP][BACK-YARD-CAM] ✅ '/back-yard-cam' stream is UP! (3/3)

mrlt8 added a commit that referenced this issue Jan 21, 2023
@mrlt8
Don't ignore cams without ENR #276 #677
7b4a111
@mrlt8
Copy link
Owner

mrlt8 commented Jan 21, 2023

I pushed a new commit to the dev branch. Could you try using that to see if it recognizes the OG in the bridge and lets you access the webrtc endpoint?

@jmluxem
Copy link

jmluxem commented Jan 21, 2023

Am I able to test the dev branch using the Home Assistant plugin? If so, I could test right now

@mrlt8
Copy link
Owner

mrlt8 commented Jan 21, 2023

You should be able to access the DEV branch using this repo https://github.com/mrlt8/edge-repo

@jmluxem
Copy link

jmluxem commented Jan 21, 2023

Thanks, got the edge-repo setup in Home Assistant. Dev branch is still only showing 6 of my 7 cameras - OG is not listed.

@jmluxem
Copy link

jmluxem commented Jan 21, 2023

and not seeing the OG listed anywhere in logs. Doesn't appear to be detecting it

@ScottySTL
Copy link

I tried the same with dev branch and not seeing my new OG camera listed

@adricrist87
Copy link

Is there a Discord or other chat room we can use to coordinate testing?

mrlt8 added a commit that referenced this issue Jan 22, 2023
@mrlt8
Don't ignore cams without p2p_id #276 #677
68047ea
mrlt8 added a commit that referenced this issue Jan 22, 2023
@mrlt8
v1.11.4 (#688)
1ba1507 
* disable autoplay for webrtc

* libopus as default for WebRTC compatibility #676

* Don't ignore cams without ENR #276 #677

* Don't ignore cams without p2p_id #276 #677

* Webrtc (#687)

* Check if webrtc_url is available

* Option to force re-encode h264 #681

* autoplay for webrtc

* version bump
@camblack
Copy link

Still not detected after these latest commits.

{"cam":"og-cam","result":"cam not found"}

2023/01/22 22:49:37 [WyzeBridge] ♻️ FORCED REFRESH - Ignoring local 'user' data
 * Serving Flask app 'frontend'
 * Debug mode: off
2023/01/22 22:49:37 [WyzeBridge] ♻️ FORCED REFRESH - Ignoring local 'auth' data
2023/01/22 22:49:37 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
2023/01/22 22:49:37 [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5000
 * Running on http://192.168.1.147:5000
2023/01/22 22:49:37 [WyzeBridge] Press CTRL+C to quit
2023/01/22 22:49:38 [WyzeBridge] 💾 Saving 'auth' to local cache...
2023/01/22 22:49:38 [WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
2023/01/22 22:49:38 [WyzeBridge] 💾 Saving 'user' to local cache...
2023/01/22 22:49:38 [WyzeBridge] ♻️ FORCED REFRESH - Ignoring local 'cameras' data
2023/01/22 22:49:38 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
2023/01/22 22:49:39 [WyzeBridge] 💾 Saving 'cameras' to local cache...
2023/01/22 22:49:39 [WyzeBridge] 
🎬 STARTING ALL 7 CAMERAS
2023/01/22 22:49:39 [WyzeBridge] SET WB_IP to allow WEBRTC connections.
2023/01/22 22:49:39 [WyzeBridge] Starting rtsp-simple-server v0.21.1
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam Pan V2 - living-room-cam on 192.168.1.45 (1/3)
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - mom-driveway on 192.168.2.2 (1/3)
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - back-yard-cam on 192.168.1.162 (1/3)
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - mom-porch on 192.168.74.4 (1/3)
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - mom-backyard on 192.168.74.7 (1/3)
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - food-cam on 192.168.1.40 (1/3)
2023/01/22 22:49:39 [WyzeBridge] 🎉 Connecting to WyzeCam V3 - bedroom on 192.168.1.43 (1/3)```

mrlt8 added a commit that referenced this issue Jan 24, 2023
@mrlt8
ignore missing IP #677
f271c96
mrlt8 added a commit that referenced this issue Jan 24, 2023
@mrlt8
v1.11.5 (#691)
20f218c 
* ignore missing IP #677

* Autoplay related changes #690

* Version bump
@camblack
Copy link

On 1.11.5 it seems that it's no longer able to fetch cameras

2023/01/24 16:51:46 [WyzeBridge] 🚀 STARTING DOCKER-WYZE-BRIDGE v1.11.5
2023/01/24 16:51:46 [WyzeBridge] 🔍 Could not find local cache for 'user'
 * Serving Flask app 'frontend'
 * Debug mode: off
2023/01/24 16:51:46 [WyzeBridge] 🔍 Could not find local cache for 'auth'
2023/01/24 16:51:46 [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5000
 * Running on http://192.168.1.147:5000
2023/01/24 16:51:46 [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
2023/01/24 16:51:46 [WyzeBridge] Press CTRL+C to quit
2023/01/24 16:51:46 [WyzeBridge] 💾 Saving 'auth' to local cache...
2023/01/24 16:51:46 [WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
2023/01/24 16:51:47 [WyzeBridge] 💾 Saving 'user' to local cache...
2023/01/24 16:51:47 [WyzeBridge] 🔍 Could not find local cache for 'cameras'
2023/01/24 16:51:47 [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
2023/01/24 16:51:48 [WyzeBridge] 1 validation error for WyzeCamera
ip
  value is not a valid integer (type=type_error.integer)

@jmluxem
Copy link

jmluxem commented Jan 24, 2023

Wyze Cam OG is being detected in 1.11.6!
It shows a recent snapshot but it isn't able to load the WebRTC stream - gives a 404 error for both WebRTC and HLS.
All other cams working normally.

@sguy311
Copy link

sguy311 commented Jan 24, 2023

So, the OG is at least showing up on the page, but here is the log entry about it
2023/01/24 21:32:40 [WyzeBridge] 🎉 Connecting to WyzeCam OG - carport on (1/3)
2023/01/24 21:32:40 [Carport ] IOTC_ER_UNLICENSE

@carTloyal123
Copy link

Also, thanks for everyone willing to test alpha features and I will update this thread with ways to test in the future as integration develops more.

@cybersholt
Copy link

I also have a OG that I can help test with if needed as well as 2 local v3's and 2 remote v3's. I'm not familiar with reverse engineering but have compiled and loaded custom firmware for the v2 cams.

It's a shame these are so different, the little spotlight is cool and the picture quality especially at night is pretty impressive for the price.

@nbetcher
Copy link

nbetcher commented Jan 14, 2024 •
edited
Loading

@carTloyal123,

I have been working on an android app bundled in a docker container that implements the native libiotvideo.so and libiotp2pav.so libraries.

What container project are/would you [be] using? docker-android, redroid?

While I realize you're just being practical (I would be doing the same, if I had time), wouldn't your proposed approach require at least 1GB (or for speed maybe even 1.5-2GB) of RAM? And the bootup speed be in the realm of at least 30 full seconds?

I guess I'm just curious what you're using to defeat the major drawbacks of using a full-blown Android solution in this context.

I will post a repo link once I get it organized.

That would be excellent. Please, the sooner the better since people often (I've done it, lol) suddenly go missing and all of their proposed work is lost, never to be heard from again. 😜

Thank you for your hard work!!!

@carTloyal123
Copy link

I have not been able to run an android emulator in a docker container on my main dev machine which is an m2 macbook pro so that is slowing me down at the moment. I have tried all readily available android emulator docker solutions. As far as I can tell there is no way to avoid using a full android emulator so take it or leave it or come up with a new solution.

I will post the new repo soon, I have it in progress but its not ready for public consumption.

@jhansche
Copy link
Contributor

As far as I can tell there is no way to avoid using a full android emulator

Keep in mind you may also be able to release it on the play store, or at least give access to an APK that can be installed manually, to allow a real device to run it. I'm sure I'm not the only one that has a handful of old Android devices lying around 😂 This bridge just needs to be able to connect to the Android bridge, whether emulator or real device. I also have an Android Things dev device.

@nbetcher
Copy link

I have not been able to run an android emulator in a docker container on my main dev machine which is an m2 macbook pro so that is slowing me down at the moment.

That's your main problem: Mac M2
If you had an x86 machine you wouldn't need an emulator at all. Redroid doesn't even emulate at all as long as you have x86_64 versions of the library. That would be ideal for most.

I hate to say it, but due to Apple's extreme proprietary nature, Mac OS isn't exactly what most users on here are going to be using, ever.

@carTloyal123
Copy link

As far as I can tell there is no way to avoid using a full android emulator

Keep in mind you may also be able to release it on the play store, or at least give access to an APK that can be installed manually, to allow a real device to run it. I'm sure I'm not the only one that has a handful of old Android devices lying around 😂 This bridge just needs to be able to connect to the Android bridge, whether emulator or real device. I also have an Android Things dev device.

I have no intention of releasing it to the play store. If you want to use it on a spare android device then you can load it manually.

I have not been able to run an android emulator in a docker container on my main dev machine which is an m2 macbook pro so that is slowing me down at the moment.

That's your main problem: Mac M2 If you had an x86 machine you wouldn't need an emulator at all. Redroid doesn't even emulate at all as long as you have x86_64 versions of the library. That would be ideal for most.

I hate to say it, but due to Apple's extreme proprietary nature, Mac OS isn't exactly what most users on here are going to be using, ever.

I know how platform architectures work and was not asking for a recitation of my problem but feel free to offer a solution if you wish to comment further. The problem is not apple silicone, but the lack of support from androids command line tools which enable you to automate an emulator on any ARM based device. We also do not have x86 versions for the libraries at all. They are also JNI libraries meaning you basically have to use a real device or emulator to get the JVM environment correct. Again, solutions are welcome but rather not more problems or issues already stated

@lflondonol92
Copy link

Are there any updates available? I have 2 OG cams and would be happy to help with the testing.

@carTloyal123
Copy link

Cryze is my project for accessing Wyze Gwell based cameras like the OG Cam, Video Doorbell Pro and I am sure there are others. I have a working prototype and am currently working on a full integration with other projects like this one. Feel free to check that repo periodically as I iron out the kinks and get things release ready.

@dinan5
Copy link

dinan5 commented Feb 21, 2024 via email

@talormanda
Copy link

Cryze is my project for accessing Wyze Gwell based cameras like the OG Cam, Video Doorbell Pro and I am sure there are others. I have a working prototype and am currently working on a full integration with other projects like this one. Feel free to check that repo periodically as I iron out the kinks and get things release ready.

Can you add some documentation on how to install this? I have docker / portainer but not super familiar on adding things on my own yet.

@quistuipater
Copy link

quistuipater commented Feb 22, 2024 via email

@carTloyal123
Copy link

carTloyal123 commented Feb 22, 2024 •
edited
Loading

@talormanda as mentioned, I am in the process of getting the project ready for full release. Once that is done, check back to the Cryze repo for install instructions.

@quistuipater do you know the model number of the OG cam? Or have the mac address of one? I think they all start with "GW_"

Edit: yes, the OG and doorbell pro both have the GW model number so it should be safe to assume they are both Gwell Based at the very least.

@jhansche
Copy link
Contributor

@quistuipater

Are the Wyze Cam Pan v3 cameras Gwell based?

No, the Pan v3 works with this bridge, it is not Gwell

@quistuipater
Copy link

quistuipater commented Feb 22, 2024 via email

@Simcha-Orenbuch
Copy link

@talormanda as mentioned, I am in the process of getting the project ready for full release. Once that is done, check back to the Cryze repo for install instructions.

@quistuipater do you know the model number of the OG cam? Or have the mac address of one? I think they all start with "GW_"

Edit: yes, the OG and doorbell pro both have the GW model number so it should be safe to assume they are both Gwell Based at the very least.

Do you still need a MAC address or you got the info you needed?

@carTloyal123
Copy link

@talormanda as mentioned, I am in the process of getting the project ready for full release. Once that is done, check back to the Cryze repo for install instructions.

@quistuipater do you know the model number of the OG cam? Or have the mac address of one? I think they all start with "GW_"

Edit: yes, the OG and doorbell pro both have the GW model number so it should be safe to assume they are both Gwell Based at the very least.

Do you still need a MAC address or you got the info you needed?

I am good, I had mis-read that and I forgot about the list of devices on the home page. Thank you!

@imbkr
Copy link

imbkr commented Apr 2, 2024

is there any update on this? is anyone working on to solve this issue?

@carTloyal123
Copy link

Cryze is my project for accessing Wyze Gwell based cameras like the OG Cam, Video Doorbell Pro and I am sure there are others. I have a working prototype and am currently working on a full integration with other projects like this one. Feel free to check that repo periodically as I iron out the kinks and get things release ready.

Please read the entire thread before posting questions. I have a project that addresses the OG cam and Video Doorbell Pro V1 reference above. @imbkr

@nbetcher
Copy link

nbetcher commented Apr 2, 2024

Cryze is my project for accessing Wyze Gwell based cameras like the OG Cam, Video Doorbell Pro and I am sure there are others. I have a working prototype and am currently working on a full integration with other projects like this one. Feel free to check that repo periodically as I iron out the kinks and get things release ready.

Please read the entire thread before posting questions. I have a project that addresses the OG cam and Video Doorbell Pro V1 reference above. @imbkr

In some fairness it doesn't appear the documentation really ties it all together. E.g. what to do after the APK is installed in the emulator. (Just to name one)

@carTloyal123
Copy link

Correct that Cryze is not fully fleshed out as it is a hobby project and is a large undertaking (feel free to clone and make pull requests if you want progress on your own watch. The question was if there was someone/something working towards a solve for this which indeed there is and has been mentioned multiple times in this thread hence my reply. @nbetcher you should not have to worry about the APK at all. If you want clarity on setup please address it to the main Cryze repo

@GuySandler
Copy link

has there been a solution in this repo yet?

@xerootg
Copy link

xerootg commented Aug 20, 2024

I've got a hard fork of cryze that is working. It's a bit CPU thirsty but it is actually streaming video to my NVR. I'm activly working on getting hardware acceleration working to try to reduce the footprint. github.com/xerootg/cryze_v2

@dinan5
Copy link

dinan5 commented Aug 20, 2024

That's great! thanks. Will try it.

@xerootg
Copy link

xerootg commented Aug 20, 2024

I'm actively working on it, expect it to both change fundamentally and for there to be issues. I'm likely going to be pulling the raw h264 frames out of android into a third container to handle the RTSP side, possibly today and likely by tomorrow. The CPU consumption of Android's MediaCodec without hardware acceleration is absolutely mind boggling and I really don't feel like recompiling android for the possibility that it might be slightly more performant. I'm using just over 1 core per camera on an i7-12650H which I find totally unacceptable. I did a spike where I rendered the raw output into a MJPEG stream and that was actually worse than double encoding like it does now.

@dinan5
Copy link

dinan5 commented Aug 20, 2024

Well, we really appreciate the effort you are putting into it, thank you again!

@xerootg
Copy link

xerootg commented Aug 23, 2024

Alright, the raw streamer in my cryze fork seems pretty solid. its been running for a couple days. I got it to stream the raw h264 packets to a tcp client, like ffmpeg, so you'll need to use an intermediary to use my fork like go2rtc (which I am using with frigate). I seriously doubt the gwell cameras will ever be supported outside of an android emulator, as tencent's library uses message queueing to a proprietary backend to get the stream contents. I'm probably going to get a different doorbell after this experience, I'm disappointed in Wyze. The whole gwell API and integration of the gwell products into the wyze platform screams outsourcing chaos.

@carTloyal123
Copy link

carTloyal123 commented Aug 25, 2024 •
edited
Loading

Alright, the raw streamer in my cryze fork seems pretty solid. its been running for a couple days. I got it to stream the raw h264 packets to a tcp client, like ffmpeg, so you'll need to use an intermediary to use my fork like go2rtc (which I am using with frigate). I seriously doubt the gwell cameras will ever be supported outside of an android emulator, as tencent's library uses message queueing to a proprietary backend to get the stream contents. I'm probably going to get a different doorbell after this experience, I'm disappointed in Wyze. The whole gwell API and integration of the gwell products into the wyze platform screams outsourcing chaos.

Yeah, this is great work. And this is as far as I ever wanted to take it either for the exact same reasons that you mentioned. My whole goal was to use my video doorbell pro in HomeKit, but now that there are cheaper HomeKit secure video enabled doorbell cameras, I would much rather get one of those instead of mess with the horrendous software stack that Wyze is using. Repo is very clean and well done, great work! @xerootg

@talormanda
Copy link

This is exactly why I started going to tapo and reolink. If I hadn't gotten my doorbell pros for free, I wouldn't be using them as the current option. As nice as wyze is as a company, I don't think their development team knows anything about what's going on.....and this is really evident because anytime you would suggest a really simple feature, it was met with strong backlash about how they can't do it. They are definitely outsourcing.

@xerootg
Copy link

xerootg commented Aug 25, 2024

Thanks @carTloyal123 !! Maybe you'll get some use out of it anyway ;)

Well, all that said, I'm almost done stripping the gwell/iotvideosdk down to the minimum needed to maintain a stream. I've still got some little nags around stalled video streams and token renewal, but it's quite obvious the stack wyze used on these cameras was not designed for long-running stream reading. I'm not going to put effort into transcoding on the container unless someone needs it, it's quite difficult to do hardware interop into a container that doesn't even share a common libc. So all that to say, if you're using my cryze fork, let me know over in my repo and I'll keep working on stabilizing it for as long as it holds my attention. I might even try running the android stack in a stripped down android container to give me a bit more control and use less memory!

@mrlt8 I don't know if you want to keep these gwell camera support issues open. There's a solution now and your solution seems to work well for the TUTK cameras. I can confidently say nobody is going to port the tencent iotvideo API to python anytime soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests