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

Newly added Camera not showing up #974

Closed
kiwi-cam opened this issue Aug 26, 2023 · 5 comments
Closed

Newly added Camera not showing up #974

kiwi-cam opened this issue Aug 26, 2023 · 5 comments

Comments

@kiwi-cam
Copy link
Contributor

I've been using this for a while now and it's been solid - THANKS!

I've just had a tidy up and moved some Camera's around, specifically:

  1. I removed Back Lawn Cam WyzeCamv2 in the app
  2. I moved Driveway Cam (WyzeCamv3) to the back lawn and renamed it as Back Lawn Cam
  3. I moved the old Back Lawn Cam (WyzeCamv2) to the Garage and re-set it up as Garage Cam

These changes have all gone smoothly in the Wyze App and appear on https://view.wyze.com/live.

Now in WyzeBridge I have Back Lawn Cam and an existing, untouched WyzeCamv2 being discovered and streamed but the repurposed v2 (now known as Garage Cam) just will not show up?

[+] Running 2/2
 ✔ Network docker-wyze-bridge_default  Created                                                                     0.1s 
 ✔ Container wyze-bridge               Created                                                                     0.2s 
Attaching to wyze-bridge
wyze-bridge  | 
wyze-bridge  | 🚀 DOCKER-WYZE-BRIDGE v2.3.16 
wyze-bridge  | 
wyze-bridge  | 
wyze-bridge  | [WyzeBridge] 🔍 Could not find local cache for 'auth'
wyze-bridge  | [WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
wyze-bridge  |  * Serving Flask app 'frontend'
wyze-bridge  |  * Debug mode: off
wyze-bridge  | [WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
wyze-bridge  |  * Running on all addresses (0.0.0.0)
wyze-bridge  |  * Running on http://127.0.0.1:5000
wyze-bridge  |  * Running on http://172.18.0.2:5000
wyze-bridge  | [WyzeBridge] Press CTRL+C to quit
wyze-bridge  | [WyzeBridge] 💾 Saving 'auth' to local cache...
wyze-bridge  | [WyzeBridge] 🔍 Could not find local cache for 'user'
wyze-bridge  | [WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
wyze-bridge  | [WyzeBridge] 💾 Saving 'user' to local cache...
wyze-bridge  | [WyzeBridge] 🔍 Could not find local cache for 'cameras'
wyze-bridge  | [WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
wyze-bridge  | [WyzeBridge] 💾 Saving 'cameras' to local cache...
wyze-bridge  | [WyzeBridge] [+] Adding Back Lawn Cam [WYZE_CAKP2JFUS]
wyze-bridge  | [WyzeBridge] [+] Adding Dog Cam [WYZEC1-JZ]
wyze-bridge  | [WyzeBridge] starting MediaMTX 1.0.0
wyze-bridge  | [WyzeBridge] 🎬 4 streams enabled
wyze-bridge  | [WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Lawn Cam on 192.168.1.62
wyze-bridge  | [WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Lawn Cam on 192.168.1.62
wyze-bridge  | [WyzeBridge] 🎉 Connecting to WyzeCam V2 - Dog Cam on 192.168.1.63
wyze-bridge  | [WyzeBridge] 🎉 Connecting to WyzeCam V2 - Dog Cam on 192.168.1.63
wyze-bridge  | [Dog-cam-sub] [-90] IOTC_ER_DEVICE_OFFLINE
wyze-bridge  | [Dog-cam] [-90] IOTC_ER_DEVICE_OFFLINE
wyze-bridge  | [WyzeBridge] 👻 Dog Cam is offline.

Note that Dog Cam is regularly left off so those last lines are expected.

I've tried restarts, FRESH_DATA=True. Any other tricks to force the camera to show up - it's working in the Wyze App?
mrlt8 added a commit that referenced this issue Aug 27, 2023
@mrlt8
Log number of cams from API #974
b51994f
@mrlt8
Copy link
Owner

mrlt8 commented Aug 27, 2023

hmm, this is very strange. I see the Fetching 'cameras' from the Wyze API... so it should be getting the latest changes from the API AND it is pulling the v3 Back Lawn Cam that you renamed. Can you double check Garage Cam to see if it has any special characters that might be causing issues in the bridge?

@kiwi-cam
Copy link
Contributor Author

It doesn't seem to be that. I've tried a few different names, reset and reconfigured the camera - It's still not showing up.

@mrlt8
Copy link
Owner

mrlt8 commented Aug 28, 2023

Could you try the dev branch with LOG_LEVEL=debug? that should print out the number of cameras and the names of the cameras it is pulling from the API.

@kiwi-cam
Copy link
Contributor Author

Looks like it's still only getting the two from the API:

[+] Running 1/1
 ✔ Container wyze-bridge  Recreated                                                                                                                                            0.2s
Attaching to wyze-bridge
wyze-bridge  | 01:43:41 [WARNING][WyzeBridge] WARNING: invalid escape sequence '\d'
wyze-bridge  | 01:43:41 [WARNING][WyzeBridge] WARNING: invalid escape sequence '\w'
wyze-bridge  |
wyze-bridge  | 🚀 DOCKER-WYZE-BRIDGE v2.3.16 [DEV BUILD]
wyze-bridge  |
wyze-bridge  |
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] ♻️ Clearing local cache...
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] 🔍 Could not find local cache for 'auth'
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] ☁️ Fetching 'auth' from the Wyze API...
wyze-bridge  |  * Serving Flask app 'frontend'
wyze-bridge  |  * Debug mode: off
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
wyze-bridge  |  * Running on all addresses (0.0.0.0)
wyze-bridge  |  * Running on http://127.0.0.1:5000
wyze-bridge  |  * Running on http://172.20.0.2:5000
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] Press CTRL+C to quit
wyze-bridge  | 01:43:42 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): auth-prod.api.wyze.com:443
wyze-bridge  | 01:43:42 [DEBUG][WyzeBridge] https://auth-prod.api.wyze.com:443 "POST /v3/user/login HTTP/1.1" 200 None
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] 💾 Saving 'auth' to local cache...
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] 🔍 Could not find local cache for 'user'
wyze-bridge  | 01:43:42 [INFO][WyzeBridge] ☁️ Fetching 'user' from the Wyze API...
wyze-bridge  | 01:43:42 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): api.wyzecam.com:443
wyze-bridge  | 01:43:43 [DEBUG][WyzeBridge] https://api.wyzecam.com:443 "POST /app/user/get_user_info HTTP/1.1" 200 260
wyze-bridge  | 01:43:43 [INFO][WyzeBridge] 💾 Saving 'user' to local cache...
wyze-bridge  | 01:43:43 [INFO][WyzeBridge] 🔍 Could not find local cache for 'cameras'
wyze-bridge  | 01:43:43 [INFO][WyzeBridge] ☁️ Fetching 'cameras' from the Wyze API...
wyze-bridge  | 01:43:43 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): api.wyzecam.com:443
wyze-bridge  | 01:43:44 [DEBUG][WyzeBridge] https://api.wyzecam.com:443 "POST /app/v2/home_page/get_object_list HTTP/1.1" 200 4282
wyze-bridge  | 01:43:44 [INFO][WyzeBridge] [API] Fetched [2] cameras
wyze-bridge  | 01:43:44 [DEBUG][WyzeBridge] [API] cameras=['Back Lawn Cam', 'Dog Cam']
wyze-bridge  | 01:43:44 [INFO][WyzeBridge] 💾 Saving 'cameras' to local cache...
wyze-bridge  | 01:43:44 [INFO][WyzeBridge] [+] Adding Back Lawn Cam [WYZE_CAKP2JFUS]
wyze-bridge  | 01:43:44 [INFO][WyzeBridge] [+] Adding Dog Cam [WYZEC1-JZ]
wyze-bridge  | 01:43:44 [INFO][WyzeBridge] starting MediaMTX 1.0.0
wyze-bridge  | 01:43:44 [INFO][WyzeBridge] 🎬 4 streams enabled
wyze-bridge  | 01:43:46 [INFO][WyzeBridge] 🎉 Connecting to WyzeCam V3 - Back Lawn Cam on 192.168.1.62
wyze-bridge  | 01:43:46 [DEBUG][back-lawn-cam] Connect via IOTC_Connect_ByUIDEx
wyze-bridge  | 01:43:47 [INFO][back-lawn-cam] AV Client Start: chan_id=0 expected_chan=0
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] Now listening on channel id 0
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] SEND <K10000ConnectRequest code=10000 resp_code=10001> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10000 txt_len=0> b''
wyze-bridge  | 01:43:48 [INFO][WyzeBridge] [CONTROL] ☁️ Get Device Info for dog-cam via Wyze API
wyze-bridge  | 01:43:48 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): api.wyzecam.com:443
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10001 txt_len=17>: b'\x03xA\xb6\xf0\x0f\x07\xad\xc6\x94\x8a!n\x807\x8c\xcc'
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] Sending response: <K10008ConnectUserAuth code=10008 resp_code=10009>
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] SEND <K10008ConnectUserAuth code=10008 resp_code=10009> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10008 txt_len=30> b'\x80\xdb\xf8\xd09_Z\x01\xeb3\xc0\xf1a\x07\x08\xb97828\x01\x00\x074160192'
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10009 txt_len=733>: b'{"connectionRes":"1","cameraInfo":{"audioParm":{"sampleRate":"16000"},"videoParm":{"type":"H264","bitRate":"180","resolution":"1","fps":"20","horizontalFlip":"1","verticalFlip":"1","logo":"2","time":"1"},"settingParm":{"stateVision":"1","nightVision":"3","osd":"1","logSd":"1","logUdisk":"1", "telnet":"2","tz":"12"},"basicInfo":{"firmware":"4.36.10.4054","type":"camera","hardware":"0.0.0.0","model":"WYZE_CAKP2JFUS","mac":"7C78B221E82F","wifidb":"86"},"channelResquestResult":{"video":"1","audio":"0"},"recordType":{"type":"1"},"sdParm":{"status":"2","capacity":"0","free":"0","detail":"0"},"uDiskParm":{"status":"2","capacity":"0","free":"0"},"apartalarmParm":{"type":"1","startX":"0","longX":"100","startY":"0","heightY":"100"}}}'
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] SEND <K10056SetResolvingBit code=10056 resp_code=10057> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10056 txt_len=3> b'\x01\xb4\x00'
wyze-bridge  | 01:43:48 [DEBUG][back-lawn-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10057 txt_len=1>: b'\x01'
wyze-bridge  | 01:43:49 [DEBUG][WyzeBridge] https://api.wyzecam.com:443 "POST /app/v2/device/get_device_Info HTTP/1.1" 200 2795
wyze-bridge  | 01:43:49 [INFO][WyzeBridge] 192.168.1.50 - - [28/Aug/2023 01:43:49] "GET /api/dog-cam/power HTTP/1.1" 200 -
wyze-bridge  | 01:43:49 [DEBUG][back-lawn-cam] No longer listening on channel id 0
wyze-bridge  | 01:43:49 [DEBUG][back-lawn-cam] [videoParm] {'type': 'H264', 'bitRate': '180', 'resolution': '1', 'fps': '20', 'horizontalFlip': '1', 'verticalFlip': '1', 'logo': '2', 'time': '1'}
wyze-bridge  | 01:43:49 [INFO][back-lawn-cam] 📡 Getting 180kb/s HD stream (H264/20fps) via LAN mode (WiFi: 86%) FW: 4.36.10.4054 🔒 (DTLS) (2/3)
wyze-bridge  | 01:43:49 [WARNING][back-lawn-cam] WARNING: Skipping smaller frame at start of stream (frame_size=1)
wyze-bridge  | 01:43:49 [WARNING][back-lawn-cam] WARNING: Skipping smaller frame at start of stream (frame_size=1)
wyze-bridge  | 01:43:49 [WARNING][back-lawn-cam] WARNING: Skipping smaller frame at start of stream (frame_size=1)
wyze-bridge  | 01:43:49 [INFO][WyzeBridge] ✅ '/back-lawn-cam stream is UP! (3/3)
wyze-bridge  | 01:43:49 [INFO][WyzeBridge] 📖 New client reading from back-lawn-cam
wyze-bridge  | 01:44:04 [DEBUG][back-lawn-cam] [CONTROL] Attempting to GET: param_info
wyze-bridge  | 01:44:04 [DEBUG][back-lawn-cam] Now listening on channel id 0
wyze-bridge  | 01:44:04 [DEBUG][back-lawn-cam] SEND <K10020CheckCameraParams code=10020 resp_code=10021> <TutkWyzeProtocolHeader prefix=b'HL' protocol=5 code=10020 txt_len=10> b'\t\x01\x02\x03\x04\x05\x15\x16\x1b2'
wyze-bridge  | 01:44:04 [DEBUG][back-lawn-cam] RECV <TutkWyzeProtocolHeader prefix=b'HL' protocol=36 code=10021 txt_len=63>: b'{"1":1,"2":3,"3":180,"4":1,"5":20,"21":1,"22":12,"27":2,"50":1}'
wyze-bridge  | 01:44:05 [DEBUG][back-lawn-cam] No longer listening on channel id 0
wyze-bridge  | 01:44:05 [DEBUG][back-lawn-cam] [CONTROL] Response: {'command': 'param_info', 'payload': '1,2,3,4,5,21,22,27,50', 'value': {'1': 1, '2': 3, '3': 180, '4': 1, '5': 20, '21': 1, '22': 12, '27': 2, '50': 1}, 'status': 'success', 'response': {'1': 1, '2': 3, '3': 180, '4': 1, '5': 20, '21': 1, '22': 12, '27': 2, '50': 1}}
wyze-bridge  | 01:44:08 [INFO][WyzeBridge] [CONTROL] ☁️ Get Device Info for dog-cam via Wyze API
wyze-bridge  | 01:44:08 [DEBUG][WyzeBridge] Starting new HTTPS connection (1): api.wyzecam.com:443
wyze-bridge  | 01:44:08 [DEBUG][WyzeBridge] https://api.wyzecam.com:443 "POST /app/v2/device/get_device_Info HTTP/1.1" 200 2795
wyze-bridge  | 01:44:08 [INFO][WyzeBridge] 192.168.1.50 - - [28/Aug/2023 01:44:08] "GET /api/dog-cam/power HTTP/1.1" 200 -
wyze-bridge  | 01:44:20 [DEBUG][back-lawn-cam] [CONTROL] Attempting to GET: param_info

Interestingly, I can see the cameras on https://view.wyze.com and the get_object_list call which does include the missing Garage Cam in the results:
image

@mrlt8 mrlt8 added the bug Something isn't working label Aug 28, 2023
@kiwi-cam
Copy link
Contributor Author

This one was on me 😤

I forgot that WyzeBridge is accessing cameras shared from another Wyze account and I hadn't shared the new camera with that account.

Sorry

@mrlt8 mrlt8 removed the bug Something isn't working label Sep 1, 2023
mrlt8 added a commit that referenced this issue Oct 10, 2023
@mrlt8
Motion Events and Audio Fix (#1006)
27fd845 
* audio latency #388

* Motion Events

* Log number of cams from API #974

* Store and reuse s3 thumbnail from events #970

* better error handling

* Increase MTX_WRITEQUEUESIZE #984

* MOTION_START for HA

* limit login attempts

* pass exceptions upstream

* motion images for webhooks/ntfy in header

* REST API motion endpoint

* Additional audio codecs

* keep stream alive if livestream enabled #985

* Catch RuntimeError #994

* assert bitrate value

* refactor av_send_io_ctrl

* Refactor API client and use battery from device_info

* motion_ts endpoint

* use .pipe instead of .wav for audio pipe

* update frame size if not preferred_frame_size

* Exclude battery cams from RTSP snapshots #970

* revert changes

* buffer mtx event data #990

* Match all 11.x or newer firmware #975

* MOTION_WEBHOOKS

* clean

* revert changes

* Media MTX changes

* ffmpeg v6

* Use ffmpeg-for-homebridge in QSV build #736

* remove unneeded packages

* don't return none

* Adjust queue size and compression #388

* Adjust sleep, queue, and fifo for lag

* Catch other HTTPErrors for events

* Revert "Adjust sleep, queue, and fifo for lag"

* Update ffmpeg.py

* Update tutk.py

* adjust thread_queue_size #388

* Add build date time

* Update ffmpeg.py

* Additional queue tweaks and fifo options #388

* Catch RequestException in motion events

* Update MediaMTX version from v1.1.0 to v1.1.1 (#1007) (#1008)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: mrlt8 <[email protected]>

* Fix ETag header for MediaMTX 1.1.1

* Don't use wallclock  #388

* remove asetpts

* audio #388

* Update ffmpeg.py

* allow wallclock flag in FFMPEG_FLAGS #388

* changelog

* Update .env
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
2 participants
@kiwi-cam @mrlt8