no wifi Wyze Cam V2

Question

no wifi Wyze Cam V2

mon5termatt opened this issue 2 years ago · comments

random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0'
ap_scan=1
Priority group 2
   id=0 ssid='Get off my LAN'
nl80211: Could not add multicast membership for vendor events: -2 (No such file or directory)
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
netlink: Operstate: ifindex=0 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
Could not read interface wlan0 flags: No such device
nl80211: Set mode ifindex 0 iftype 2 (STATION)
nl80211: Failed to set interface 0 to mode 2: -19 (No such device)
wlan0: Failed to initialize driver interface
Failed to add interface wlan0
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout```

SSID and password is defiantly correct

Jeff Tchang · Answer 1 · Thu Jul 14 2022 11:50:24 GMT+0800 (China Standard Time)

Is key_mgmt=WPA-PSK set?

LilTrublMakr · Answer 2 · Mon Aug 01 2022 07:41:04 GMT+0800 (China Standard Time)

I am getting the same.

Logs:

wpa_supplicant v2.5
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='0'
ap_scan=1
bgscan='simple:30:-45:300'
Priority group 2
   id=0 ssid='MINE-IoT'
nl80211: Could not add multicast membership for vendor events: -2 (No such file or directory)
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
netlink: Operstate: ifindex=0 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
Could not read interface wlan0 flags: No such device
nl80211: Set mode ifindex 0 iftype 2 (STATION)
nl80211: Failed to set interface 0 to mode 2: -19 (No such device)
wlan0: Failed to initialize driver interface
Failed to add interface wlan0
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout

WPA Supplicant:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=1
bgscan="simple:30:-45:300"

network={
        ssid="MINE-IoT"
        key_mgmt=WPA-PSK
        pairwise=CCMP TKIP
        group=CCMP TKIP WEP104 WEP40
        psk="DefinitelyNotMyPassword"
        priority=2
}

This is using the latest release on a cam v2.

Matthew Clark · Answer 3 · Mon Aug 01 2022 08:19:20 GMT+0800 (China Standard Time)

I forgot to mention I was using the latest version of v2 as well

Larry Wright · Answer 4 · Fri Aug 12 2022 11:30:41 GMT+0800 (China Standard Time)

I’m getting this same issue with a Wyze Pan Cam. I tried the latest version as well as several older versions. Everything seems to flash fine, and I see logs on the SD card, but the Wifi never connects and I see the “no such device” error mentioned above.

Ed · Answer 5 · Sat Sep 03 2022 04:45:32 GMT+0800 (China Standard Time)

getting this same error

mmarbut · Answer 6 · Wed Sep 14 2022 10:56:03 GMT+0800 (China Standard Time)

same issue with my wyze cam pan


wpa_supplicant v2.5
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'wlan0' conf '/etc/wpa_supplicant.conf' driver 'nl80211' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
Priority group 2
   id=0 ssid='MrUniverse Cortex Uplink'
nl80211: Could not add multicast membership for vendor events: -2 (No such file or directory)
rfkill: Cannot open RFKILL control device
nl80211: RFKILL status not available
Could not read interface wlan0 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
nl80211: Remove monitor interface: refcount=0
netlink: Operstate: ifindex=0 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
Could not read interface wlan0 flags: No such device
nl80211: Set mode ifindex 0 iftype 2 (STATION)
nl80211: Failed to set interface 0 to mode 2: -19 (No such device)
wlan0: Failed to initialize driver interface
Failed to add interface wlan0
wlan0: Cancelling scan request
wlan0: Cancelling authentication timeout

Tukamok · Answer 7 · Tue Sep 20 2022 22:46:57 GMT+0800 (China Standard Time)

I had the same issues. Cam would get on the network using the stock firmware, so I knew it wasn't a hardware issue. I'm relatively certain one of the two below solved the issue:

Re-Flashed several times, just to be safe.
Ensured that my wpa_supplicant.conf was using unix, and not windows, line endings.

Yes, I know that the docs said that #2 shouldn't be an issue with the latest, but I was running out of things to try before I gave up.

mmarbut · Answer 8 · Tue Sep 20 2022 23:10:48 GMT+0800 (China Standard Time)

Got the answer on the slack at the bottom of this you have to change the wifi module.
https://github.com/openmiko/openmiko/blob/master/overlay_minimal/etc/openmiko.conf
then put the file in the same folder as the supplicant file.

Matthew Clark · Answer 9 · Tue Sep 20 2022 23:27:20 GMT+0800 (China Standard Time)

Got the answer on the slack at the bottom of this you have to change the wifi module. https://github.com/openmiko/openmiko/blob/master/overlay_minimal/etc/openmiko.conf then put the file in the same folder as the supplicant file.

is that for the pan or v2?

mmarbut · Answer 10 · Tue Sep 20 2022 23:29:27 GMT+0800 (China Standard Time)

the pan, but it would be worth doublechecking and making sure that you have the right module.

Matthew Clark · Answer 11 · Tue Sep 20 2022 23:34:51 GMT+0800 (China Standard Time)

the pan, but it would be worth doublechecking and making sure that you have the right module.

i can check when i get home from work but the pan (according to documentation) is the one that needs a different one.. not the V2

LilTrublMakr · Answer 12 · Wed Sep 21 2022 07:41:08 GMT+0800 (China Standard Time)

Got the answer on the slack at the bottom of this you have to change the wifi module. https://github.com/openmiko/openmiko/blob/master/overlay_minimal/etc/openmiko.conf then put the file in the same folder as the supplicant file.

Not relevant for the V2. We are having problems with the V2 specifically.
@tachang any input on this?

Larry Wright · Answer 13 · Wed Sep 21 2022 11:41:40 GMT+0800 (China Standard Time)

I can confirm that the issue I was having was related to the wifi module. Changing to the appropriate one resolved it.

Martin Butt · Answer 14 · Mon Feb 20 2023 14:36:15 GMT+0800 (China Standard Time)

I decided to merge together all of my changes from the last six months and release them for testing. I've included new config file generators that ask which camera you are using and outputs appropriate config files. Testing is appreciated, and you can file an issue in that repo if you have any problems.

Matthew Clark · Answer 15 · Mon Feb 20 2023 14:45:14 GMT+0800 (China Standard Time)

Sounds like a plan. I still have one camera out of three that's just refusing to work with it so I'll give it a try tomorrow

Martin Butt · Answer 16 · Mon Feb 20 2023 15:01:24 GMT+0800 (China Standard Time)

Great, thanks! To get the camera and SD card back to a clean slate before starting, you can:

Hold the reset button for a few seconds and it will flash blue three times to show it has deleted any residual files
Format the memory card, as it can easily become corrupted if it is writing to a log file when it is powered off.