raspberry-wifi-conf: pi 3 error after ap mode
I successfully installed raspberry-wifi-conf on RPi 3 with raspbian-jessie according to manual, AP is started, I connected to AP, typed 192.168.44.1:88 to browser. I choose my ssid from list, typed my wifi password to dialog. When i press submit button, i got error from node side. Rpi3 didnt connect my network. Also after that i cant access to 192.168.44.1:88. AP mode is open. When i try to sudo npm start, i am getting this error everytime. Any help?
sudo npm start
raspberry-wifi-conf@0.0.1 start /home/pi/Desktop/raspberry-wifi-conf node server.js
/home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:136 info[“hw_addr”].toLowerCase() == info[“ap_addr”].toLowerCase() && ^
TypeError: Cannot read property ‘toLowerCase’ of undefined at _is_ap_enabled_sync (/home/pi/Desktop/raspberry-wifi-conf/app/wifi_manage r.js:136:61) at _is_wifi_enabled_sync (/home/pi/Desktop/raspberry-wifi-conf/app/wifi_mana ger.js:115:28) at /home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:126:35 at /home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:90:20 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:251: 17 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:154: 25 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:248: 21 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:612: 34 at /home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:76:17 at ChildProcess.exithandler (child_process.js:204:7)
raspberry-wifi-conf@0.0.1 start /home/pi/Desktop/raspberry-wifi-conf node server.js
/home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:136 info[“hw_addr”].toLowerCase() == info[“ap_addr”].toLowerCase() && ^
TypeError: Cannot read property ‘toLowerCase’ of undefined at _is_ap_enabled_sync (/home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:136:61) at _is_wifi_enabled_sync (/home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:115:28) at /home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:126:35 at /home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:90:20 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:251:17 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:154:25 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:248:21 at /home/pi/Desktop/raspberry-wifi-conf/node_modules/async/lib/async.js:612:34 at /home/pi/Desktop/raspberry-wifi-conf/app/wifi_manager.js:76:17 at ChildProcess.exithandler (child_process.js:204:7)
npm ERR! Linux 4.1.18-v7+
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “start”
npm ERR! node v4.3.1
npm ERR! npm v2.14.12
npm ERR! code ELIFECYCLE
npm ERR! raspberry-wifi-conf@0.0.1 start: node server.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the raspberry-wifi-conf@0.0.1 start script ‘node server.js’.
npm ERR! This is most likely a problem with the raspberry-wifi-conf package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node server.js
npm ERR! You can get their info via:
npm ERR! npm owner ls raspberry-wifi-conf
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request: npm ERR! /home/pi/Desktop/raspberry-wifi-conf/npm-debug.log
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 16 (3 by maintainers)
Try to install darland’s fork. Maybe it works better due to some recent bug fixes…
In AP mode I have to wait a couple of minutes to see the ssid.
But I think that there is still a bug in Darlands fork regarding the reconnection. If a previous known wifi network is turned off and then turned on again (e.g. night mode), then the pi will not reconnect to the previous known network. I am not able to fix this issue. Maybe this commit might help to fix it, please see lilianharris fork:
https://github.com/lillianharris/raspberry-wifi-conf/commit/57c9830a5cd122be6de2502a2d65802ee6d9d4b9
I had the same problem first. I guess it has something to do with the boot sequence. It helped to add some sleeptime in rc.local:
sudo nano /etc/rc.localsleep 1mcd /home/pi/raspberry-wifi-confsudo /usr/bin/node server.js < /dev/null &Maybe it helps to add sudo in iwlist.js:
exec("sudo iwlist scan", function(error, stdout, stderr)After adding “sudo” the ap´s were listed and I could enter the wifi credentials. I entered the credentials successfully and my pi was able to connect to my wifi network at home. But then the next bugs turned up. After the next reboot it seemed that the pi had forgotten the wifi credentials. It started in ap-mode and didn’t connect properly to my wifi network. 😦
It would be great, if these issues were supported anyhow …