Option to restart plugin automatically when cameras go offline #391
Comments
|
I will second this. I have a front door camera that seems to crash all the time and usually restarting the plugin fixes it. |
|
All my cameras seem to crash (in WyzeBridge - not in Wyze app). I'm not sure why exactly. |
|
Can you post any info from the logs so we can try to see if we can restart them automatically? |
|
Sure. In HomeAssistant is there a way to view the entire log? I think it's a limited section when I view the Log from the addon page. |
|
You should be able to see the full logs on http://homeassistant.local:8123/config/logs and select the bridge from the drop down in the top right. |
Thanks! I didn't know about that area of HA. However it still doesn't display the entire log, when I refresh I can see that earlier lines are gone. Anyway here's the logs I have manually concatenated by refreshing that page. I see it's just always timing out. Also having it running is absolutely hammering my network, Zoom calls dropping etc, maybe related issue?
[tee @ 0x3f0cbd0] dimensions not set 2022/06/16 08:51:06 [RTSP][BASEMENT] ✅ '/basement' stream is UP! (3/3) 2022/06/16 08:51:50 [MainProcess] ⏰ Timed out connecting to Outdoor 3 (20s). |
|
@mrlt8 hi, anything in the logs that you see that can help me get this working well? |
|
I have a similar issue I think. Here is the logs just from today. I can pull more if needed. Hoping this helps. |
* Add flask endpoints to restart connection to cams/rtsp-server #391 * Restart buttons for webui
|
The endpoints seem to crash when I use them. But something a little more automatic would be nice. I just get tons of "2022/08/12 21:12:39 [WyzeBridge] ⏰ Timed out connecting to BridgeTest (20s)." Maybe something that when it gets a few of these in a row, it would restart that camera or something. |
|
Unfortunately, I haven't been able to find a way to reboot the cameras over the TUTK protocol - I believe the wyze app reboots the cameras over their web API so that's something we might be able to use. |
I see that bug now.
And this one is a separate bug. Just ran into it myself - your camera wasn't timing out the bridge was just using the wrong timestamp! Will be pushing a fix for both of these! |
|
I may have used the wrong term. The physical cameras don't need to be rebooted, its just eh docker container needs to be restarted. So whatever happens with that would just need to happen after a certain number of timeouts. I never actually reboot or power cycle the physical camera, I just have to hit ctrl-c and restart the docker container. |
|
I have a similar issue with just one of my 4 cameras. I can barely get 15 minutes of uptime from it before it's connection drops. The Camera appears fine in the Wyze app - although does seem to take a little longer than others to connect sometimes (related??). I've reset and re-flashed the camera. If it's helpful, here are my debug logs: |
|
@kiwi-cam Same, I even moved the bridge closer to all the cameras and this still happens, I wouldn't say its as bad as 15 minutes for me but its definitely getting annoying and I've already put the RTSP firmware on one of V3s and that one has never gone down once. |
|
I had the same issue, and forced the p2p mode. It fixed the issue. It's
been running for about 12 days without dropping. Couldn't get more than 10
minutes before. Mine is VM in Digital Ocean.
…On Sat, Aug 13, 2022, 7:16 PM Cameron ***@***.***> wrote:
I have a similar issue with just one of my 4 cameras. I can barely get 15
minutes of uptime from it before it's connection drops. The Camera appears
fine in the Wyze app - although does seem to take a little longer than
others to connect sometimes (related??). I've reset and re-flashed the
camera.
If it's helpful, here are my debug logs:
WyzeBridgeLogs.txt
<https://github.com/mrlt8/docker-wyze-bridge/files/9332405/WyzeBridgeLogs.txt>
—
Reply to this email directly, view it on GitHub
<#391 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYTSV7M5GYISM4N75QFKPZDVZAUGTANCNFSM5W3RPQVQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
@serenityrox Gonna have to try this, I have it on any right now. |
|
So I have it on P2P mode only and I don't think it's working? At least for all cameras. LOGS: 2022/08/13 20:45:36 [WyzeBridge] 🚀 STARTING DOCKER-WYZE-BRIDGE v1.8.2
|
|
Ok update I gave it a minute and all the cameras say LAN mode now and camera streams seem to load instantly now.., but at the top you can see it didn't say LAN. Now to test if this fixes anything. |
* Add individual camera api endpoints #436 #494 * Use updated camera data * use name_uri instead of nickname * icon/color based on status/on-demand #498 * Fix boa_interval style #504 * Server side event for camera status * Update camera status icon color * Update compatibility table * Fix restarting connections #391 * Prevent camera from wrongly timing out #391 #484 * kill zombies? * More verbose http exceptions #505 * Update preview button for all non-HLS * Load preview on connection and message on lost connection * copy dictionary * version bump * update preview when connected to camera
|
v1.8.3 should fix the timeout and restart connection issues. |
|
Alright will update tomorrow, so far what is locking it to P2P mode its loading nice and fast so I think ill keep that too even after I update. |
|
If it is in p2p mode it will give a warning stating that it may consume
more bandwidth. It can be forced into p2p mode with docker compose using
NET_MODE=P2P. The photo attached shows the proper format.
…On Sat, Aug 13, 2022, 8:49 PM David Nestico ***@***.***> wrote:
Ok update I gave it a minute and all the cameras say LAN mode now, but at
the top you can see it didn't say LAN.
Now to test if this fixes anything.
—
Reply to this email directly, view it on GitHub
<#391 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYTSV7JDHJPEZQBFYX2MCZTVZA7DNANCNFSM5W3RPQVQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Updated to 1.8.3 about 2 hours ago, all 3 cameras are up stable and running. I switched to P2P mode as well, it seems to be working well I'll update again if I see any issues but so far so good. EDIT: 12 hours and still relatively stable. I say relative because it looks like they are crashing periodically, but they do seem to auto restart fairly quickly. |
|
I updated about 4 hours ago. Looking better here too - all cameras are still up. |
|
Latest update is much more stable. A few disconnects, but recovers on it's own. Awesome work dev! |
|
So far can confirm the exact same! |
For whatever my cameras seem to go unavailable on the bridge/addon on a daily basis when they are not even offline in the wyze app, restarting the plugin sometimes fixes this.
So an option to automatically restart the addon when certain or all cameras go offline would help because this really is annoying and I'm considering using the RTSP firmware instead on these specific cameras that go unavailable for no reason on the bridge.
The text was updated successfully, but these errors were encountered: