Wyze Forcing New Firmware #786
Comments
|
What FW ver did you get forced to? |
|
V2 - 4.9.9.3006 |
|
Here is the information from the config page:
|
|
The actual setting we need is what you have in your /opt/wz_mini/wz_mini.conf file. Look for a setting:
to see if it is true or false. Fortunately, for the V2 cam, wz_mini still works with the latest FW, but you may want to check your V3 cams for this setting as a FW update could break things on those for wz_mini. So far, Wyze has only tried updates on my V2's not on my V3's. Although most of my V3's are on FW 4.36.10.3406 or higher. I think they are ok if you are on at least 4.36.9.139 or higher for the V3 and anything less they may try forced updates, possibly so they don't have to support so many different API calls and security purposes. |
|
So Wyze is forcing updated firmware in order to use the cameras in the app: |
|
I'm seeing this too when I'm trying to view the cameras in the app |
You can’t rollback on iOS. |
I am seeing the exact same thing 😭 |
|
someone on the old firmware, try: Please write the following in V2: V3: taken from mnakada/atomcam_tools#115 (comment) see if it works. |
|
On iOS you can also switch to another app real quick and switch back, and the box will be gone for the rest of the session. |
|
Had to give up and accept the inevitable upgrade. Every time I tried to view a camera in the app the forced upgrade window would pop up with no way to close it. I was able to sneak past it by powering off the camera and, when I powered it back on, quickly clicking the setup gear icon. I had to reformat the SD Cards then run the update. Of course after that, no more wyze_mini_hacks. This really sucks. |
|
@bjs-pdx you could try and downgrade, and try the fix i posted above |
|
Not sure a downgrade is going to do anything. Wyze app checks the firmware and forces the upgrade. How does your suggested fix change that? |
|
the fix physically changes the firmware version reported by the device. icamera reads from that file to tell the fw ver |
|
Okay...I see. But still don't know what breaks in the Wyze app when running older firmware. They are forcing this for some hidden reason but can't tell what that may be. This also may be the future of constant breakage. |
|
Just to be clear, I think this project is great. I’m just done with Wyze. Seems like every month or so they make a change and things break. Tired of fighting a losing battle. Going to switch to Amcrest for my camera needs. Much more reliable. |
|
You can convert the wyze devices to a standalone firmware we've been working on... www.thingino.com. just FYI. |
|
Not really something I want to do. Liked the idea of added functionality without losing the native functions. |
That file appears to be read-only. How can I write to it? Thanks! |
|
You can’t on the V3 camera, but you should be able to alter the file that is in the /configs directory. Supposedly, that is the file that I camera reads… |
|
I tried changing /configs/app.ver - it doesn't do anything, just reverts to the old app.ver (even in /configs) on reboot. |
|
@gtxaspec do you have any other ideas? The thread on atomcam-tools that you linked said that the person had to update the firmware for this trick to work. I upgraded wz-mini-hacks using the shell script, but changes to /configs/app.ver still don't stick after a reboot. I have the wyze cam v3. Thanks! |
|
i'll have to setup a wyze device ( i dont currently have any setup with stock firmware ) I'll try to restore one soon and test |
|
Note that we should try to find out WHY its updating. I asked in the discord and WyzeJason told me it was due to a bug? (what bug im not sure)? However, if it is a certificate change wyze did on their end and the newer apps potentially have newer certs where the old will expire soon, that may be the reason for the force. I did upgrade as well as I needed things functioning and now note that a change im noticing is that wyze seems to be trying to use a hardcoded dns server and trying to bypass dnsmasq. Im seeing strange behavior where the local app is pinging api.wyze every minute. My DNAT rule at my router is successfully dnating this to pihole, but it is strange behavior regardless. |
|
Figured out the dns issue. Seems like wyze took a page out of our book :) and now runs dnsmasq by default on the device. Ours fails because the address is bound by their instance, plus on the newest firmware the build of dnsmasq in firmware is newer than the one present on wz_mini. I was able to address the DNS noise issue by killing the watchdog process they run for it + dnsmasq, running the copy as in the init file for resolv.conf, then starting the Wyze copy of dnsmasq with our config file (using -C argument.) after work ill submit a PR tonight with the fix so it can be integrated into the tree. Can include an if statement easily enough to check the existence of the system dnsmasq and if not present, simply use the wyze_mini one. |
Thanks! |
|
@sideup66 hi, what FW version did you upgrade to that had all these changes? Does the newer firmware allow wz_mini functionality again? |
|
I am on 4.36.13.0416. Aside from dnsmasq, I am not sure if the way firmware is pushed may have changed. That should be investigated as well. On the newer versions, you won't have RTSP still but wz_mini still has root shell on the device. I am simply updating the Dnsmasq script in my PR to utilize the built-in dnsmasq binary from wyze if it exists, it seems more up-to-date currently than the one present in wz_mini and I included logic for both, so the script should be able to detect one way or the other and effectively let you configure dnsmasq with our configuration file. |
|
To continue view my wyze V3 on the app, I've the following quick fix: In echo -e "[VER]\nappver=4.36.13.0416" > /opt/wz_mini/tmp/patched_app.ver
mount --bind /opt/wz_mini/tmp/patched_app.ver /system/bin/app.versomewhere between After that, restart the camera. This fix is effective for immediate needs (I just want to check if my package is delivered on my phone right now), I guess it could be better to move this code to |
|
Wanted to report my final findings regarding this. As a person who "jumped the fence" and went to the newer wyze firmware.... After upgrading, I initially had a weird issue where my camera's record light would typically get stuck after recording an event. Was able to fix that by resetting the camera. I learned that well, after the firmware jump there were multiple reports of weirdness from other v3 owners who were able to fix it by performing the reset. Wyze mini still works, albeit without any of the RTSP features, but if you need root shell to run services and effectively make the experience of it not suck, it works well :). The other interesting thing of note is that in the newer firmware (my v3 is on 4.36.13.0416 at the time of this writing). I notice that wyze actually took a page from our book, and added a local dnsmasq server on the camera. That build is at 2.88 while the wz-mini build is 2.86. Not a HUGE difference but a slightly newer version. Therefore, I had the update merged to determine whether the onboard dnsmasq was present and restart it using the wz-mini config rather than its builtin config if the local dns is enabled. otherwise, use the wz-mini's build. One thing of note in that fix is that the initial 3 second setting i pushed with the commit might be too short. If needed, I can submit another PR pushing it out to 5 seconds, or even 10 if preferred. But its such a small change if Gtxaspec wants to do it im fine with that also. Or maybe we come up with a faster way to do it. Also, I would suggest makign the firmware spoof a separate feature from blocking firmware updates. In my own setup, I am using the firmware update block as given Wyze's history of messy updates, id rather not update again unless forced and/or a major breaking bug occurs to the device but rather not spoof the firmware version, just incase there is a change in the way cloud is communicating or functioning with my device and that spoofed version throws things off.... At the time of this report my camera seems stable. Few TLDR notes.
|
|
So I have few pan cam that i had firmware update disable= true. It seems to have blocked the update but I have the nag in the wyze app(which my wife uses...sigh). I have run update-run.sh and it looks as if it has updated mini hacks. Is there something I need to do so this works as I still get the nag. I guess first how do tell if I have in fact had a successful run of upgrade-run.sh? Is there a config setting for "spoofing the firmware" Thanks EDIT: |
|
I plan to make a followup PR soon. Im testing out some further changes I made to the dnsmasq script. It seems something from the wyze app side kept trying to overwrite the change from the script, I was able to block this by remounting the bind to make it read-only. Im testing due to an unrelated issue with the LED not functioning correctly on mine. I think I solved it, but im trying to be sure. Only other follow up from all of this I am going to send a PR for is to break out the firmware spoofing potentially into its own independent script that can be controlled from the conf file. Not a fan of it being enabled with fw disable as some cams may be on newer firmware, thus breaking their reporting and potential cloud communications. |
|
Made PR #801 with my aforementioned fixes. |
I had an interesting thing happen with one camera(vs2). It was fully functional but I had the blue led in the back flashing. It was doing so even with the light disabled in the app. I think I rebooted and it was fine. It was just a problem BC it's in a dark area and was bothersome to somebody |
|
I've seen that once or twice. Not super common but usually indictive of a
past or present connectivity issue. If mine was doing it with me not around
not a huge deal as cron does a nightly reboot which would have cleared it.
…On Sat, Oct 19, 2024, 1:03 PM dasb00ter ***@***.***> wrote:
I plan to make a followup PR soon. Im testing out some further changes I
made to the dnsmasq script. It seems something from the wyze app side kept
trying to overwrite the change from the script, I was able to block this by
remounting the bind to make it read-only.
Im testing due to an unrelated issue with the LED not functioning
correctly on mine. I think I solved it, but im trying to be sure.
Only other follow up from all of this I am going to send a PR for is to
break out the firmware spoofing potentially into its own independent script
that can be controlled from the conf file. Not a fan of it being enabled
with fw disable as some cams may be on newer firmware, thus breaking their
reporting and potential cloud communications.
I had an interesting thing happen with one camera(vs2). It was fully
functional but I had the blue led in the back flashing. It was doing so
even with the light disabled in the app. I think I rebooted and it was
fine. It was just a problem BC it's in a dark area and was bothersome to
somebody
—
Reply to this email directly, view it on GitHub
<#786 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALL5UVPVMHPH4K56BA2SOULZ4KGEJAVCNFSM6AAAAABMW3KSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGA4DSNRZGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I know I'm coming late to this party, but I only recently discovered how great wz_mini is for V3 cams and so I bought two of them to use for livestreaming, monitoring and generally doing public outreach for astrophotography. Originally, I flashed the beta RTSP firmware from Wyze, obtained from Wayback Machine. It worked great with my two test cams on 32GB cards. I decided to get six more cams to do a full roll-out of setting up live streams for the telescopes (both looking at the rigs and looking at the sky). I purchased 128GB cards to go in all those cams. I use RTSP to stream all that to OBS that then streams to YouTube and/or Twitch. Then I found out that I had to ugprade the firmware to solve the micro SD card corruption problem. I went to 4.36.9.131 and then .139 to make sure I didn't go past the RTSP barrier. Now I see, like everyone else, that the app is forcing me to ugprade further. Honestly, I don't care. I don't use the app, I don't need its features, and if I do, I'll use Home Assistant. But I just downloaded the latest wz_mini which seems to have the "echo -e "[VER]\nappver=4.36.13.0416" > /opt/wz_mini/tmp/patched_app.ver" line in S10firmware, and yet the Wyze app is still telling me I should update. While I don't need the app, it's faster to check on cam stats there than it is to pop up an RTSP stream (though I could use VLC for that on the Android phone). Do I need to do something else to have this fix work for convincing the app that I don't need to upgrade? wz_mini web page reports the .0416 firmware so it looks like it's working, but the app still complains. Also, the whole point of wz_mini for me was the RTSP streams. If I bite the bullet and push past the upgrade barrier, I know I lose that. Would I still be able to pull a live stream via the Go2RTC server, or does that rely on the RTSP under the hood? Sorry for the questions, I'm just trying to make sure I didn't make a $400 mistake with all these cameras and cards. |
|
Hi!
If you move past the rtsp barrier no, no custom rtsp streaming would work
unfortunately.... If you are looking to exclusively use it for that I'd
recommend dafang or thingino which fully replace wyze stock firmware, and
fully support streaming.
I personally am sticking to wz_mini because though I don't use rtsp I do
use the hack to provide some stability, security, and usability patches to
my otherwise stock v3.
At this point the logical solution is to start testing the new firmware and
look for a workaround to rtsp. It's a matter of time imo before wyze kills
the legacy firmware with some cloud change I think.... Not to discourage
anyone.
…On Thu, Oct 24, 2024, 10:33 AM Eric Loyd ***@***.***> wrote:
I know I'm coming late to this party, but I only recently discovered how
great wz_mini is for V3 cams and so I bought two of them to use for
livestreaming, monitoring and generally doing public outreach for
astrophotography. Originally, I flashed the beta RTSP firmware from Wyze,
obtained from Wayback Machine. It worked great with my two test cams on
32GB cards. I decided to get six more cams to do a full roll-out of setting
up live streams for the telescopes (both looking at the rigs and looking at
the sky). I purchased 128GB cards to go in all those cams. I use RTSP to
stream all that to OBS that then streams to YouTube and/or Twitch.
Then I found out that I had to ugprade the firmware to solve the micro SD
card corruption problem. I went to 4.36.9.131 and then .139 to make sure I
didn't go past the RTSP barrier.
Now I see, like everyone else, that the app is forcing me to ugprade
further. Honestly, I don't care. I don't use the app, I don't need its
features, and if I do, I'll use Home Assistant. But I just downloaded the
latest wz_mini which seems to have the "echo -e
"[VER]\nappver=4.36.13.0416" > /opt/wz_mini/tmp/patched_app.ver" line in
S10firmware, and yet the Wyze app is still telling me I should update.
While I don't need the app, it's faster to check on cam stats there than
it is to pop up an RTSP stream (though I could use VLC for that on the
Android phone). Do I need to do something else to have this fix work for
convincing the app that I don't need to upgrade? wz_mini web page reports
the .0416 firmware so it looks like it's working, but the app still
complains.
Also, the whole point of wz_mini for me was the RTSP streams. If I bite
the bullet and push past the upgrade barrier, I know I lose that. Would I
still be able to pull a live stream via the Go2RTC server, or does that
rely on the RTSP under the hood?
Sorry for the questions, I'm just trying to make sure I didn't make a $400
mistake with all these cameras and cards.
—
Reply to this email directly, view it on GitHub
<#786 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALL5UVNVJUUFYLJRFYNDXM3Z5EAL3AVCNFSM6AAAAABMW3KSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGQ3DQNJWGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Okay, thanks for that. I was unaware of the other firmwares. I took a quick look, but it does not seem like they do the recording that the Wyze firmware does. Which is something I like; being able to go back in time to look at a specific event/time is great for monitoring remote telescopes. Honestly, I'd be fine with just using the .139 firmware to get the RTSP and then wz_mini to get the streaming capabilities and other things that it provides, but now I have a new problem - the camera keeps crashing on me. It's like it ran fine on a 32GB test microSD card with the old beta RTSP firmware from Wyze, but now that I've got the .139 on it, on a 128GB card, it's just completely unstable. Maybe I'll return all these 128GB cards and get 32GB cards instead. They seem to work with the old RTSP firmware just fine but man, what a pain. |
|
You could possibly have them record somewhere and be able to do time lapse.
As for the firmware message, make sure the wz_mini system is actually
loading on your SD card...usually I know it's not if ssh isn't running
…On Thu, Oct 24, 2024, 11:04 AM Eric Loyd ***@***.***> wrote:
Okay, thanks for that. I was unaware of the other firmwares. I took a
quick look, but it does not seem like they do the recording that the Wyze
firmware does. Which is something I like; being able to go back in time to
look at a specific event/time is great for monitoring remote telescopes.
Honestly, I'd be fine with just using the .139 firmware to get the RTSP
and then wz_mini to get the streaming capabilities and other things that it
provides, but now I have a new problem - the camera keeps crashing on me.
It's like it ran fine on a 32GB test microSD card with the old beta RTSP
firmware from Wyze, but now that I've got the .139 on it, on a 128GB card,
it's just completely unstable.
Maybe I'll return all these 128GB cards and get 32GB cards instead. They
seem to work with the old RTSP firmware just fine but man, what a pain.
—
Reply to this email directly, view it on GitHub
<#786 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALL5UVMAIV3SIWUKKF44QKTZ5ED7XAVCNFSM6AAAAABMW3KSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGU2TCNRQGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
An alternative if you move to New firmware is to setup new firmware, still
run wz_mini and copy off the video folder, could even smb mount it I think,
then playback using whatever. Even when rtsp is not running the ssh
functions as well as file transfer capabilities of wz_mini still work fine
on newer firmware
…On Thu, Oct 24, 2024, 11:16 AM Vincent ***@***.***> wrote:
You could possibly have them record somewhere and be able to do time lapse.
As for the firmware message, make sure the wz_mini system is actually
loading on your SD card...usually I know it's not if ssh isn't running
On Thu, Oct 24, 2024, 11:04 AM Eric Loyd ***@***.***> wrote:
> Okay, thanks for that. I was unaware of the other firmwares. I took a
> quick look, but it does not seem like they do the recording that the Wyze
> firmware does. Which is something I like; being able to go back in time to
> look at a specific event/time is great for monitoring remote telescopes.
>
> Honestly, I'd be fine with just using the .139 firmware to get the RTSP
> and then wz_mini to get the streaming capabilities and other things that it
> provides, but now I have a new problem - the camera keeps crashing on me.
> It's like it ran fine on a 32GB test microSD card with the old beta RTSP
> firmware from Wyze, but now that I've got the .139 on it, on a 128GB card,
> it's just completely unstable.
>
> Maybe I'll return all these 128GB cards and get 32GB cards instead. They
> seem to work with the old RTSP firmware just fine but man, what a pain.
>
> —
> Reply to this email directly, view it on GitHub
> <#786 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ALL5UVMAIV3SIWUKKF44QKTZ5ED7XAVCNFSM6AAAAABMW3KSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGU2TCNRQGI>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
|
Yes, wz_mini is definitely loading. I have monitoring software that SSHes to the box and checks to make sure that /opt/wz_mini/log is writeable. That's how I found the corrupt microSD card problem. I'm actually going to see if I can find the 4.49.1.47 firmware, since the person on the microSD corruption thread said that solved their problem. And while I could move images around with new firmware, if I can't stream with it, then it's useless. That's the whole point - to be able to stream these things to Youtube and Twitch for real-time outreach in the field of Astrophotography. |
|
Wait. I can't go to 4.49.1.47, because that breaks the RTSP barrier. I'm going to downgrade from .139 to .131 and see if that solves my crashing problem. |
|
4.49.x is for the pan, not for the v3, FYI. |
|
Thanks. Just put .131 on and let it run for a few minutes. No crashes. Now I've got wz_mini on and just first booted. Waiting to see if it crashes or gives me an sd card corruption. |
|
So far, with just RTSP enabled (low res for now) and the web interface but no Go2RTC, the 4.36.9.131 firmware is holding steady without crashes and without sd card corruptions. If this works, I may just lock it here and call it a day. |
|
if you have no interest in using the app, you may want to switch to thingino, which provides RTSP too. There's other folks interested in astronomy which are using it. |
|
I saw that briefly, but wasn't sure if it still did the automatic recording that the Wyze app does, and I have no clue on how to figure out what my specific SoS and Wifi controller is. So I punted and came back to this. |
|
Okay. I spoke too soon. Still crashes doing nothing other than web and low-res RTSP. I guess it's time to look into thingino if I can figure out my specific hardware. |
|
I've seen the camera do weird stuff after firmware jumping around, have you
tried resetting it post migration? Also the presence of wz_mini when doing
upgrades caused weird behavior for me too. I'd flash whatever firmware you
want without wz_mini installed, then reset and reconfigure the camera
WITHOUT wz_mini (can just turn the camera off and yank the SD card out)
then reset the camera, setup, then introduce a clean copy of wz_mini from
the git tree
…On Thu, Oct 24, 2024, 12:37 PM Eric Loyd ***@***.***> wrote:
Okay. I spoke too soon. Still crashes doing nothing other than web and
low-res RTSP. I guess it's time to look into thingino if I can figure out
my specific hardware.
—
Reply to this email directly, view it on GitHub
<#786 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALL5UVPASJSQYO5BWO5LSALZ5EO3JAVCNFSM6AAAAABMW3KSJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVG42TMMRQGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hm. Did not do resets. Will try that before abandoning Wyze ship. |
|
No improvement. It seems that I can spend hours more trying to figure this out. Just finished flashing Thingino on my first cam. Seems to work. Thanks! |
|
whats the cleanest way to update to latest while keeping the config settings? |
|
Switch to thingino and never look back. |
Thought about it but does it support poe adapter UCTRONICS? |
|
Thingino is a custom firmware that turns your Wyze cam into a full-fledged Linux computer. I can't speak to a specific PoE adapter, but you can start at https://github.com/themactep/thingino-firmware/wiki/Features, which does say "USB Ethernet Adapter Support: Extend network connectivity with external USB Ethernet adapters, including PoE adapter support." So I'm guessing "yes." |
Thanks for that. The only reason I asked is because I wanted to add the 5 wyze cams I have to each corner of the house through the attic and poe is a must for me. I rather not have to deal with powering each camera with a power adapter. |
|
Watch https://www.youtube.com/watch?v=SX637mrp0R0 and install Thingino and you will never look back. |
|
How is this working out for folks? Has anything broken on their device since adding the firmware spoof? just curious as I have tried updating but continually having led status problems, despite the camera working fine. |
It looks like Wyze is forcing new firmware onto cameras. Just noticed a V2 that was changed.
What is the best way to stop this. It’s going to break things.
The text was updated successfully, but these errors were encountered: