Closed cdupont closed 3 years ago
I see this in the logs right after you clicked on the connect
button which looks suspicious:
2020-12-11T10:14:19.776291620Z [BTN ] GPIO6 held long enough. Triggering the action!
GPIO6 is responsible for WIFI/AP push button which forces the WiFi to go to Access point mode. Maybe there is a short circuit on your WaziHAT or the push button is broken and always pushed.
It's probably because I use a USB LoRa concentrator at the moment (HT-M01). So I don't have any GPIO hat. The GPIO 6 default state seems to be a "pull up": https://raspberrypi.stackexchange.com/questions/32639/why-are-some-gpio-pins-high-when-the-raspberry-pi-boots-up/32643
A quick workaround is:
sudo echo "out" > /sys/class/gpio/gpio6/direction
sudo echo "0" > /sys/class/gpio/gpio6/value
This allows my Wifi to connect.
The wazigate-system
already does it. and on my pi without a HAT, the default value is already set. This is strange that on your pi it behaves like that. Are you sure there is no other process that uses this GPIO on your pi? can you see which processes are using GPIO6?
Not reproduced with the ISO 2.1.2. I started with the USB concentrator. Maybe it was due to my frequent changing of hats, that left a bad state.
Good news :)
On Fri, Dec 11, 2020 at 4:45 PM Corentin Dupont notifications@github.com wrote:
Not reproduced with the ISO 2.1.2.
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/131#issuecomment-743269824, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHECTNGW25Q4LAH7VI3SUI5CRANCNFSM4UWM75JA .
-- Mojtaba Eskandari
Nope, still have it after reboot:
2020-12-11T17:16:42.515233217Z [BTN ] GPIO6 held long enough. Triggering the action!
I'm using RPI4 and HT-M01.
Strange, what sort of Raspberry pi do you have?
On Fri, Dec 11, 2020 at 6:19 PM Corentin Dupont notifications@github.com wrote:
Nope, still have it after reboot:
2020-12-11T17:16:42.515233217Z [BTN ] GPIO6 held long enough. Triggering the action!
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/131#issuecomment-743320503, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHGUCQOAGBK5HNSLS3LSUJICPANCNFSM4UWM75JA .
-- Mojtaba Eskandari
It's RPI4 B
I tested it on pi4B and I confirm this issue.
On Fri, Dec 11, 2020 at 6:37 PM Corentin Dupont notifications@github.com wrote:
It's RPI4 B
— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/Waziup/WaziGate/issues/131#issuecomment-743329125, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJAXHDSVDV36QCXMNEPBT3SUJKE5ANCNFSM4UWM75JA .
-- Mojtaba Eskandari
It's probably because I use a USB LoRa concentrator at the moment (HT-M01). So I don't have any GPIO hat. The GPIO 6 default state seems to be a "pull up": https://raspberrypi.stackexchange.com/questions/32639/why-are-some-gpio-pins-high-when-the-raspberry-pi-boots-up/32643
A quick workaround is:
sudo echo "out" > /sys/class/gpio/gpio6/direction sudo echo "0" > /sys/class/gpio/gpio6/value
This allows my Wifi to connect.
This will not work as the button GPIOs are input and configuring pull-up/-down on Pi4 works differently than on the Pi3. I am going to find out how to make it work and it seems like a known issue.
I found the solution, now fixing the production pi to re-create the ISO
# Setting the default state for GPIO6 and 26 which are used for push buttons: WiFi/AP and PWR if ! grep -qFx "gpio=6,26=ip,pd" /boot/config.txt; then echo -e '\n\ngpio=6,26=ip,pd' | sudo tee -a /boot/config.txt fi
https://github.com/Waziup/WaziGate/blob/master/setup/install.sh#L118
Fixed in ISO 2.1.3 Thanks!
I enter my password but the Wifi never connects:
Here are some logs: