search

openipcamera / openipc-firmware

OpenIPC Firmware for Wyze Cameras
https://openip.cam
894 stars 129 forks source link

Followed instructions for v2 wize solid orange light #110

Open jerkwagon opened 5 years ago

jerkwagon commented 5 years ago

here is what i did,
Open box, remove camera, download IPC zip file extract v2. folder/config renamed wpa_supplicant.conf.dist to .conf and made it .conf extentsion edited wpa_supplicant removed SSID to "Xiaomi" which is proper spelling of my SSID, same with PW copied over all files from v2 folder put sd card in camera plugged in one end, held the button down, plugged in the other end , waited for light to go blue let go. light went solid orange after a while, no audio, but you can hear the speaker kick in at one point tried different cards, 16/32 gb the disk is FAT formatted. does how show up in router device list (my xiaomi cams are showing up) angry ip scanner does not find it either.

some help said, "what does the log file say"

where is the log? i can not find anything.

proff321 commented 5 years ago

I'm experiencing the exact same issue with a Wyze Cam v2 camera (Model: WYZEC2) which arrived today.

I was able to purchase more than one and can confirm that the cameras are not running the latest version of the factory firmware. Performing a standard "factory" setup requests that I update the camera firmware once the wifi connection is complete.

chilliplow commented 5 years ago

here is what i did, Open box, remove camera, download IPC zip file extract v2. folder/config renamed wpa_supplicant.conf.dist to .conf and made it .conf extentsion edited wpa_supplicant removed SSID to "Xiaomi" which is proper spelling of my SSID, same with PW copied over all files from v2 folder put sd card in camera plugged in one end, held the button down, plugged in the other end , waited for light to go blue let go. light went solid orange after a while, no audio, but you can hear the speaker kick in at one point tried different cards, 16/32 gb the disk is FAT formatted. does how show up in router device list (my xiaomi cams are showing up) angry ip scanner does not find it either.

some help said, "what does the log file say"

where is the log? i can not find anything.

similar situation happened to me. I was able to get the camera to work again by going here: https://support.wyzecam.com/hc/en-us/articles/360010068231 and downloading "Wyze Cam v2 Firmware V4.9.2.42 (Release date: September 17, 2018)" put it on a microsd and do the normal hod down button while you plug in the power. You should be back to normal settings. Hopefully these folks will figure out a fix.

jerkwagon commented 5 years ago

did you get IPC working though or just standard? was i supposed to setup the wyze cam before putting on modded firmaware?

res88 commented 5 years ago

I'm experiencing the exact same issue with a Wyze Cam v2 camera (Model: WYZEC2) which arrived today.

Same here. Flashing back to stock was initially an issue until i realised that the Wyze firmware (demo.bin) needed to go inside /Main in the root.

res88 commented 5 years ago

Got it to work - i believe the cause was failing to delete the "wpa_supplicant.conf.dist" after renaming a copy to "wpa_supplicant.conf".

jerkwagon commented 5 years ago

i didnt delete wpa_supplicant.conf.dist, i just renamed it to the proper extension.

On Fri, Nov 23, 2018 at 4:12 AM res88 notifications@github.com wrote:

Got it to work - i believe the cause was failing to delete the "wpa_supplicant.conf.dist" after renaming a copy to "wpa_supplicant.conf".

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openipcamera/openipc-firmware/issues/110#issuecomment-441226059, or mute the thread https://github.com/notifications/unsubscribe-auth/ArFdTDdGrDaZ-g7k3Tz39Cgzye_YlunQks5ux-YZgaJpZM4YpnPv .

--

Jamie Drummond 23-2325 ranger lane port coquitlam, bc V3B 0K7 604-441-9497

aram535 commented 5 years ago

Hi, just got 2 new v2s and tried to flash them. After booting with the card, after ~6 seconds I do get 1 blue led flash then it goes back to orange. I did delete the wpa_supplicant.conf.dist file (I had copied it to the proper name w/changes earlier). I tried this with a unit that was initialized with the wyze app AND with one that is still virgin. [ I am using a 64gb, the only micros I have ]

jerkwagon commented 5 years ago

Got it to work - i believe the cause was failing to delete the "wpa_supplicant.conf.dist" after renaming a copy to "wpa_supplicant.conf".

why do you need to make a copy instead of just renaming it? can you confirm you have it all working? if so can you please provide clear steps so can get on board?

TheCloudlessSky commented 5 years ago

Are any of you on Windows? Make sure you download the project using "Download as ZIP" on GitHub:

image

Also make sure that when you edit wpa_supplicant.conf, you save it using Unix line endings. Windows line endings will not work.

jerkwagon commented 5 years ago

Are any of you on Windows? Make sure you download the project using "Download as ZIP" on GitHub:

image

Also make sure that when you edit wpa_supplicant.conf, you save it using Unix line endings. Windows line endings will not work.

i tried it both on mac and PC, still no luck, i downloaded teh zip file and extracted..

it blows my mind that no one else is able to help..

I also tried putting on newer or at least stock firmware, it boots up but no voice or anything.. i get flashing yellow light, there are recordings on the SD car as well.

TheCloudlessSky commented 5 years ago

@jerkwagon have you tried using Xiaomi DaFang Hacks?

jerkwagon commented 5 years ago

@jerkwagon have you tried using Xiaomi DaFang Hacks?

no i will do a search to enquire about it.. thanks

jerkwagon commented 5 years ago

@jerkwagon have you tried using Xiaomi DaFang Hacks?

tried it, im still getting a solid orange light.

avatar42 commented 5 years ago

Seeing same here other than I have not tried going back to stock yet.

josheaton commented 5 years ago

Same issue here. Originally I was having trouble because the card was not formatted properly, but the device is reading the card now properly. It is a 64GB card FWIW. Waiting for a solution.

avatar42 commented 5 years ago

Try removing the line priority=2 That seems to have done the trick for me. From wpa_supplicant docs I found online it should only be there if you have more than one interface. Take note too my MAC changed once I finally got it to connect and could see it.

BTW it seems you only need to do the hold down the button bit once as that replaces the boot loader with one tha looks to the SD card and loads the stuff there. It is a lot clearer with the Dafang hacks as the log a lot of status messages to a log while it is coming up that have been stripped out in this version. Might be a good idea to add the logging back into run.sh.

josheaton commented 5 years ago

Is it worth it? Far more functionality and better interface?

salman2learn commented 5 years ago

I tried many tips on this thread and other issues and here is what worked for me.

  1. Install the vendor app and connect the camera. Do not update firmware, but use the app to format the sd card. In my case, I tried formatting in linux earlier but that didnt work, while the formatted one by the camera itself worked the first time!

  2. If web server on step 8 is not accessible, make sure your camera and your pc are on the same network.

  3. Sample wpa supplicant.conf which worked for me on a 2.4 GHz WPA2 PSK network.

    
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1

network={ ssid="MyGuests"

Uncomment to connect to Hidden SSIDs

    #scan_ssid=1 
    key_mgmt=WPA-PSK
    pairwise=CCMP TKIP
    group=CCMP TKIP WEP104 WEP40
    psk="**********"
    priority=2

}

avatar42 commented 5 years ago

Is it worth it? Far more functionality and better interface?

Depends on what you want to do.

If your goal is to stream to a NVR then yeah it seems a lot more stable than the Tinycam hack, I have one of each streaming to Blue Iris. The one using the Tinycam hack loses connection all the time though it does seem to recover fairly soon most of the time. That might explain why some people seem to think the Tinycam hack works flawlessly. The other cam I have not recorded a single drop out.

In about every other way not so much.

josheaton commented 5 years ago

Interesting. I've had the device connected on version 4.9.1.60 and have had (knock on wood) zero connection issues to date

avatar42 commented 5 years ago

Interesting. I've had the device connected on version 4.9.1.60 and have had (knock on wood) zero connection issues to date

Via Tinycam or OpenIPC?

josheaton commented 5 years ago

I'm using the firmware that I got from the Wyze support site.

avatar42 commented 5 years ago

I'm using the firmware that I got from the Wyze support site.

So not streaming local then. Just looking at the Wyze app you probably would not notice other than sometimes you have to try a couple times to start watching a live stream.

Streaming to a recorder 24/7 via the Tinycam app then checking the footage recorded you will.

josheaton commented 5 years ago

Now I understand, thanks

ajm1635 commented 5 years ago

My recently purchased (within the past week) Wyze V2 cameras do not work correctly with 0.2.6.1. The same sd cards (i.e. the same software version and same configuration) work correctly in two older V2 cameras.

Details posted here: https://github.com/openipcamera/openipc-firmware/issues/112#issuecomment-446837165

jerkwagon commented 5 years ago

so my ssid is Google Wifi Now

i have a feeling its the ssid and the conf file that is the issue.. any suggestions on this since my ssid has spaces????

ajm1635 commented 5 years ago

so my ssid is Google Wifi Now

i have a feeling its the ssid and the conf file that is the issue.. any suggestions on this since my ssid has spaces????

Spaces should be ok. Is the SSID not quoted in the wpa_supplicant.conf file? for example: ssid="Google Wifi Now" (disclaimer: I did not test this on this camera, but spaces work in other Linux variants.)

JMTK commented 5 years ago

Try removing the line priority=2 That seems to have done the trick for me. From wpa_supplicant docs I found online it should only be there if you have more than one interface. Take note too my MAC changed once I finally got it to connect and could see it.

Yep this fixed it for me.