Wyze cam V3 stuck on solid red light

Working camera v3_init log:

+ export 'PATH=/bin:/sbin:/usr/bin:/usr/sbin:/opt/wz_mini/bin'
+ export 'PATH=/system/bin:/bin:/sbin:/usr/bin:/usr/sbin:/opt/wz_mini/bin'
+ export 'LD_LIBRARY_PATH=/system/lib:/opt/wz_mini/lib'
+ export 'LD_LIBRARY_PATH=/thirdlib:/system/lib:/opt/wz_mini/lib'
+ ifconfig lo up
+ mount -t squashfs /dev/mtdblock3 /system
mount: mounting /dev/mtdblock3 on /system failed: Resource busy
+ /opt/wz_mini/etc/init.d/wz_post.sh
+ mount -t jffs2 /dev/mtdblock6 /configs
mount: mounting /dev/mtdblock6 on /configs failed: Resource busy
+ '[' -f /system/init/app_init.sh ]
+ /system/init/app_init.sh
#############ubootddr = 540.000MHz ########
################## to wait wifi vendor id ####################
################## [vendor:0x024c] rtl8189ftv wifi #################
(O _ o) welcome to the config file repair script [start part]!
(O _ o) this is valid mac!
(O _ o) set [/configs/.product_config] to read-only!
(O _ o) to mount kback...
(^ _ ^) kback mount ok!
(O _ o) found the md5 file in kback! [/mnt/MD5.bfcccd4613f31f513d749223654e9115.config]
(O _ o)  real  md5 is [bfcccd4613f31f513d749223654e9115]
(O _ o) record md5 is [bfcccd4613f31f513d749223654e9115]
(^ _ ^) check md5 file [/mnt/MD5.bfcccd4613f31f513d749223654e9115.config] is ok!
(^ _ ^) the md5 file in kback is ok!
(- _ -) to umount kback...
(- _ -) i will exit!
Updating device time to:
Tue Oct 24 00:28:55 UTC 2023
===========welcome to ver-comp tool=========
[ver-comp]dbg: appver:  4.36.11.7095
[ver-comp]dbg: rootver: 4.36.11.7095
[ver-comp]exec cmd: cp -rf /system/bin/app.ver /configs/
checking upGradeRestFlag
#######################
#   IS USER PROCESS   #
#######################
[FC] mount tfcard finish!
[FC] Test.tar no exist
[FC] umount tfcard finish!
[FC] In [user] mode!
kernel.core_pattern = |/system/bin/ucoredmp_collector.sh --pid %p --signal %s --name %e --time %t --output-dir /media/mmc/cores
kernel.core_pipe_limit = 1
net.unix.max_dgram_qlen = 128

wz_user log:

+ true
+ '[[' -d /media/mmc/wz_mini ]]
+ '[[' -d /media/mmcblk0p1/wz_mini ]]
+ echo 'sdcard not ready yet...'
sdcard not ready yet...
+ sleep 5
+ true
+ '[[' -d /media/mmc/wz_mini ]]
+ echo 'sd card ready'
sd card ready
+ break
+ wait_wlan
+ true
+ grep 'inet addr'
+ ifconfig wlan0
+ '[[' false '==' true '||' false '==' true ]]
+ echo ' wlan0 not ready yet...'
 wlan0 not ready yet...
+ sleep 5
+ true
+ grep 'inet addr'
+ ifconfig wlan0
          inet addr:192.168.1.222  Bcast:192.168.1.255  Mask:255.255.255.0
+ store_mac
+ echo 'store original mac'
store original mac
+ tr '[:lower:]' '[:upper:]'
+ cat /sys/class/net/wlan0/address
+ break
+ grep WYZEC1-JZ
+ cat /params/config/.product_config
cat: can't open '/params/config/.product_config': No such file or directory
+ V2=false
+ KMOD_PATH=/opt/wz_mini/lib/modules/3.10.14__isvp_swan_1.0__
+ '[[' true '==' true ]]
+ grep mini
+ cat /proc/swaps
+ echo 'Swap not enabled, enabling'
Swap not enabled, enabling
+ swap_enable
+ '[[' -e /media/mmc/wz_mini/swap ]]
+ echo 'Swap exists, enable'
Swap exists, enable
+ swapon /media/mmc/wz_mini/swap
+ '[[' false '==' true ]]
+ echo 'ipv6 disabled'
ipv6 disabled
+ sysctl -w 'net.ipv6.conf.all.disable_ipv6=1'
net.ipv6.conf.all.disable_ipv6 = 1
+ '[[' false '==' true ]]
+ echo nfsv4 disabled
nfsv4 disabled
+ '[[' false '==' true ]]
+ echo 'iptables disabled'
iptables disabled
+ '[[' false '==' true ]]
+ echo 'usb ethernet disabled'
usb ethernet disabled
+ '[[' false '==' true ]]
+ echo 'usb direct disabled'
usb direct disabled
+ '[[' false '==' true ]]
+ echo 'usb direct disabled'
usb direct disabled
+ '[[' false '==' true ]]
+ echo 'wireguard disabled'
wireguard disabled
+ '[[' false '==' true ]]
+ echo 'cifs disabled'
cifs disabled
+ '[[' false '==' true ]]
+ echo 'usb_storage disabled'
usb_storage disabled
+ '[[' false '==' true ]]
+ echo 'ext4 disabled'
ext4 disabled
+ '[[' false '==' true ]]
+ mkdir /tmp/Upgrade
+ '[[' false '==' true ]]
+ echo 'remote accessory disabled'
remote accessory disabled
+ '[[' false '==' true ]]
+ echo 'mp4 write disabled'
mp4 write disabled
+ '[[' false '==' true ]]
+ echo 'rtsp disabled'
rtsp disabled
+ '[[' false '==' true ]]
+ echo 'rtsp disabled'
rtsp disabled
+ '[[' false '==' true ]]
+ '[[' false '==' true ]]
+ /opt/wz_mini/bin/busybox inotifyd /opt/wz_mini/usr/bin/watch_up.sh /tmp:n
+ '[[' false '==' true ]]
+ '[[' false '==' true ]]
+ hostname_set
+ echo 'set hostname'
set hostname
+ hostname WCV3
+ touch /opt/wz_mini/tmp/.wz_user_firstrun
+ pkill -f dumpload
+ sysctl -w 'kernel.core_pattern=|/bin/false'
kernel.core_pattern = |/bin/false
+ dmesg_log
+ DMESG_LOG=/opt/wz_mini/log/dmesg
+ '[[' -e /opt/wz_mini/log/dmesg.log '||' -L /opt/wz_mini/log/dmesg.log ]]
+ touch -- /opt/wz_mini/log/dmesg.log
+ dmesg
+ sync
+ echo 3
+ '[' -f  ]
+ echo 'custom script not found'
custom script not found
+ echo 'wz_user.sh done'
+ event=n
+ directory=/tmp
+ file=48.mp4
+ date
Thu Dec 21 11:48:00 UTC 2023
+ '[[' 48.mp4 '==' img ]]
+ event=n
+ directory=/tmp
+ file=aws_iot
+ date
Thu Dec 21 11:48:07 UTC 2023
+ '[[' aws_iot '==' img ]]
+ event=n
+ directory=/tmp
+ file=alarm_0.jpg
+ date
Thu Dec 21 11:48:17 UTC 2023
+ '[[' alarm_0.jpg '==' img ]]
+ event=n
+ directory=/tmp
+ file=alarm_0.jpg
+ date
Thu Dec 21 11:48:18 UTC 2023
+ '[[' alarm_0.jpg '==' img ]]
+ event=n
+ directory=/tmp
+ file=edgeai
+ date
Thu Dec 21 11:48:20 UTC 2023
+ '[[' edgeai '==' img ]]
+ event=n
+ directory=/tmp
+ file=49.mp4
+ date
Thu Dec 21 11:49:00 UTC 2023
+ '[[' 49.mp4 '==' img ]]
+ event=n
+ directory=/tmp
+ file=50.mp4
+ date
Thu Dec 21 11:50:00 UTC 2023
+ '[[' 50.mp4 '==' img ]]
+ event=n
+ directory=/tmp
+ file=51.mp4
+ date
Thu Dec 21 11:51:00 UTC 2023
+ '[[' 51.mp4 '==' img ]]
+ event=n
+ directory=/tmp
+ file=52.mp4
+ date
Thu Dec 21 11:52:00 UTC 2023
+ '[[' 52.mp4 '==' img ]]
+ event=n
+ directory=/tmp
+ file=53.mp4
+ date
Thu Dec 21 11:53:00 UTC 2023
+ '[[' 53.mp4 '==' img ]]
+ event=n
+ directory=/tmp
+ file=54.mp4
+ date
Thu Dec 21 11:54:00 UTC 2023
+ '[[' 54.mp4 '==' img ]]

seems like SDcard is not ready until v3_init passes from wifi vendor initialize to config file repair or whatever. But it doesn’t do it…

Could still be WiFi since it stops at

################## [vendor:0x024c] rtl8189ftv wifi #################

I had the same issue (missing the timezone_config). Haven’t figured out what’s going on (not an expert).
I feel v3 is a failed product line. After coming back from my trip yesterday, 4 of my 5 v3s (rtsp firmware) are showing offline. Haven’t got a chance to see what’s going on with them. 3 of them are mounted high. I can’t imagine climbing up to fix them every once awhile.

Depending on where it was purchased, claiming warranty could incur additional cost. Wyze only gives credit for the product. The customer has to use the credit to buy new one from Wyze site. Normally there will be a $5 shipping charge that the customer has to pay from his own pocket. If the device keeps failing, warranty shipping cost will pile up.

Quite possible. Seems like it’s really wifi problem. I appreciate your time and thank you for your help. Sorry for late reply, wyze forum allows only 3 posts for newcomers )

Support asked me if I want store credit but I asked them for replacement and they shipped me new V3 without any additional cost.

BS, It works fine when it works with 64Gb,128Gb and 256Gb. but you are right it should be in exFAT format. not NTSC.
It is a bad quality hardware issue.

I just:

  • took a 1GB microSD card and inserted into PC.
  • downloaded firmware from Wyze, (link below)
  • extracted the the bin file [ demo_wcv3.bin ] from download to the root of the formatted SD card (FAT32).
  • Safe ejected SD card from PC.
  • Insert SD card into Wyze Cam v3.
  • Held setup then applied power.

The LED changed from solid red to a slightly different color. Waited about 5 minutes and the RED / BLUE flash started.

Setup as new.

I recently discovered a red light on my V3 camera and was about to give into a loss. I unplugged one of my cameras and plugged the one with the solid red light and it connected to the app after setup immediately. I also used another standard USB cord for it and the same thing, it instantly reconnected to the wyze app. I believe that experiences are different, however, I would give this a try! Try another power cord and just see if it works for you! I hope that this helps others

No link to the firmware you used

Hey @kennethmobley ,

I just used the latest firmware at the time, but try a few if the latest doesn’t work.

Good luck and Cheers!

fwiw, I just figured out the root cause of the solid red light on my Cam v3. It turned out the power adapter was faulty. I swapped it with the adapter from my Cam Pan v3, and the problem was solved.

I also confirmed it by testing the old adapter with the Cam Pan v3, which then got stuck on a solid red light as well.

Looks like it’s time to get a new 5V/1A power adapter.

Welcome to the Forum, @cycw! :wave:

Please be aware that Cam Pan v3 has a higher power requirement and ships with a different power adapter than Cam v3:

Wyze Cam Model Supplied Power Adapter
Cam v4[1], Cam v3[2], Cam OG[3] 5V ⎓ 1A
Duo Cam Pan[4] 5V ⎓ 1.5A
Cam Pan v4[5], Cam Pan v3[6] 5V ⎓ 2A

That’s probably a good idea for your Cam v3, and please be sure that you return to using a 5V ⎓ 2A adapter for your Cam Pan v3. :+1:


  1. ↩︎

  2. ↩︎

  3. ↩︎

  4. ↩︎

  5. ↩︎

  6. ↩︎

Thanks for that info. I had forgotten about those adapters being different and had to using them interchangeably. I did find one that I needed to replace! I had inadvertently used a cell phone adapter on one of my pancams that was 1A.

You’re welcome, and thanks for the reply. That also prompted me to update my table with information for the new Indoor Cam Pan. :+1:

Keeping track of those specifications isn’t always easy, and the low contrast and small print on the adapters themselves doesn’t really help. I often keep a :magnifying_glass_tilted_right: handy for things like that. :squinting_face_with_tongue:

Same here. I didn’t have my magnifying glass nearby so I just zoomed in with my cell phone.

Is that indoor pancam the one that can look farther down? I saw a new one that I liked, as the ones I have now end up looking at the bottom box and I needed it to see the ground below.

I’m not sure what you’re asking, so I don’t know how to answer that question. Indoor Cam Pan is the new model they announced a couple of days ago, which I linked in my previous post. I think a lot of times what you want to see and what you’re able to achieve with a Cam’s view is determined by what mounting option you use.