text
stringlengths
9
408
[417.70 --> 419.20] There was a bunch of other stuff as well.
[419.36 --> 420.82] You know, you can go and listen to episode 33
[420.82 --> 421.84] if you want the full review.
[422.52 --> 424.74] Well, I worry now this means that some of this stuff's
[424.74 --> 425.84] never going to get fixed.
[426.48 --> 427.32] Do you think you killed them?
[427.46 --> 429.24] Do you think that bad review killed them, Alex?
[430.36 --> 431.26] You murdered them.
[431.74 --> 432.76] Oh, don't say that.
[432.82 --> 433.82] I mean, I didn't mean to.
[433.88 --> 434.94] I was just trying to be honest.
[434.94 --> 438.26] It was presented in a way that I felt was constructive
[438.26 --> 439.44] to say that there are these,
[439.92 --> 441.52] it's a very promising piece of hardware.
[441.64 --> 444.26] I mean, the aluminium chassis was really lovely.
[444.90 --> 446.78] There was just a couple of key things that let it down,
[446.84 --> 448.52] you know, in terms of manufacturing tolerances
[448.52 --> 449.88] and a couple of firmware things.
[450.04 --> 452.28] But overall, they did a really great job.
[452.32 --> 455.70] And I wish there was some way we could tell them that,
[455.74 --> 458.00] you know, even though we weren't 100% positive,
[458.00 --> 459.82] it was just because we loved the idea,
[459.92 --> 462.06] not because we didn't want them to carry on and succeed.
[462.64 --> 463.26] I agree completely.
[463.26 --> 466.52] And they don't completely close the door in their blog post.
[466.60 --> 468.10] We'll have that linked in the show notes if you want.
[468.16 --> 469.78] They do kind of leave it cracked a little bit,
[469.82 --> 470.76] like maybe it'll come back.
[471.14 --> 474.10] But I wanted to shift gears and talk about something
[474.10 --> 476.12] that could solve a big problem for me.
[476.20 --> 478.30] I actually went out and I pre-ordered
[478.30 --> 481.14] a bunch of Wyze 3 cameras a long time ago.
[481.18 --> 483.74] And I have a box of Wyze 3 cameras
[483.74 --> 485.36] that I haven't installed
[485.36 --> 489.30] because they do not yet have an RTMP firmware
[489.30 --> 491.72] or an RTSP firmware for Wyze 3.
[492.06 --> 493.92] But Alex, I think you've solved that this week.
[494.14 --> 495.86] Yeah, I don't know where I came across this,
[495.98 --> 497.76] but I found a Docker container
[497.76 --> 500.62] that is called Docker Wyze Bridge.
[500.84 --> 502.12] Link in the show notes, of course.
[502.48 --> 504.08] And essentially what this does
[504.08 --> 507.62] is you give it your Wyze username and password
[507.62 --> 509.86] and it goes and sort of acts as an intermediary
[509.86 --> 512.18] between the Wyze API and the cameras.
[512.18 --> 514.80] And somehow it hooks into the local feed
[514.80 --> 516.00] on the cameras on your LAN
[516.00 --> 520.22] and then presents you with a normal RTSP stream.
[520.44 --> 522.26] So I've just got that feeding into Blue Iris
[522.26 --> 524.28] and it just works.
[524.78 --> 525.52] That's fascinating.
[525.78 --> 528.18] And yeah, it can actually do both.
[528.26 --> 530.52] It can pull from the Wyze servers
[530.52 --> 531.68] using your credentials.
[532.24 --> 534.00] Or with your credentials, it can use that.
[534.10 --> 535.88] There's a library that the app uses
[535.88 --> 538.50] and it essentially does a discovery on your network.
[539.22 --> 541.04] And the Wyze app does this as well.
[541.04 --> 544.24] And if it detects the camera, it uses LAN mode
[544.24 --> 546.10] and it just does that locally
[546.10 --> 548.20] and avoids the cloud relay.
[548.92 --> 551.02] And you can also in your Docker Compose,
[551.10 --> 553.30] there is an environment variable you can pass through
[553.30 --> 555.82] that says LAN underscore only that says,
[556.00 --> 557.84] don't even try the remote thing.
[558.30 --> 560.66] Only stream if you can locally detect them.
[561.06 --> 562.72] And that was the piece I was curious about.
[562.78 --> 563.84] That's why I dug into this.
[563.92 --> 566.04] And that means I could absolutely do this here in the RV,
[566.22 --> 567.94] which means I could replace these Wyze cams
[567.94 --> 568.88] that have been giving me trouble.
[568.88 --> 570.20] The version two was good,
[570.20 --> 572.20] but just didn't have enough horsepower,
[572.44 --> 574.26] didn't really work so great at night.
[574.58 --> 576.14] And the Wyze 3 solves those.
[576.60 --> 578.54] And with this Docker Wyze bridge,
[578.58 --> 581.32] which seems to have a decent community around it as well
[581.32 --> 582.50] and some active development,
[583.10 --> 585.54] I think my problems have been solved.
[585.82 --> 587.46] And I'll give this a go, I think,
[587.48 --> 589.28] once we get back into our home base.
[589.28 --> 591.14] So far as I can tell,
[591.24 --> 593.56] it only works on the V3 cameras.
[593.80 --> 596.92] So I've got a couple of V2s flashed with the RTSP firmware
[596.92 --> 599.02] and a couple of V3s.
[599.12 --> 601.24] And the app will, in its logs,
[601.36 --> 603.58] show me a bunch of errors for the two V2 cameras.
[604.04 --> 605.68] I don't know if that's because I'm running the,
[605.74 --> 608.60] you know, custom firmware or whatever it is.
[609.30 --> 612.56] But the performance with the V3s is great.
[612.66 --> 614.74] We've been using it as a baby monitor for my daughter.
[614.74 --> 617.16] And the night vision on there is just,
[617.50 --> 618.66] it's like daytime.
[618.94 --> 619.86] It's wonderful.
[620.44 --> 621.78] They blew it out of the park with the night vision.
[622.00 --> 623.48] It's tricky with the firmwares.
[623.62 --> 625.22] So this is an issue.
[625.34 --> 626.30] And I'm glad you brought it up
[626.30 --> 627.68] because we need to mention this on the show.
[628.28 --> 630.06] And they have it on their GitHub page.