Q Light Controller+

Hi. Yesterday i started using QLC+ on RPi 4. But i have a problem with wireless network configuration. After i write down SSID, PSK and reboot RPi, it won`t connect to my network with Wi-Fi. After connecting RPi with ethernet cable i can connect and i see in configuration menu there is blank spaces in wireless configuration. I tried qlcplus_raspios_bullseye_20230519 image and it work perfectly. I can connect to Wifi and when i go into config menu there is my SSID and PSK writen down. Thanks for any reply

Connecting to a Wi-Fi network might take some time.
When setting new parameters you should wait a few seconds before rebooting.
Also, you can check if the RPi is actually connected to Wi-Fi via SSH first (e.g. via ethernet)

mcallegari wrote: ↑Mon Oct 28, 2024 7:39 am Connecting to a Wi-Fi network might take some time.
When setting new parameters you should wait a few seconds before rebooting.
Also, you can check if the RPi is actually connected to Wi-Fi via SSH first (e.g. via ethernet)

Thanks for reply. Now i wait few minutes before roboot and about 15 minutes before try to connect again via browser or SSH. In devices connected to my router i can`t see any new devices. And still after reboot in config menu there is blank spaces in SSID and PSK. I will try 4.13.0 version to check if there will be the same issue. Do you need any more important informations?

After setting connection info from the web interface, please login from a terminal and do the following and paste the output here:

pi@raspberrypi:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether d8:3a:dd:9a:10:19 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.12/24 brd 192.168.100.255 scope global dynamic noprefixroute eth0
valid_lft 86026sec preferred_lft 86026sec
inet6 fe80::4707:72f4:6fa:694b/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether d8:3a:dd:9a:10:1a brd ff:ff:ff:ff:ff:ff



pi@raspberrypi:~ $ nmcli c s
NAME UUID TYPE DEVICE
Wired connection 1 4b539feb-ee10-3636-a335-b53d1099b118 ethernet eth0
lo 5e0457bf-b6f7-4455-8787-3b9fefbc14bb loopback lo

OK, thanks.
There should be a connection named qlcplus and I see it's not there.
I will double check myself if something is not right but last time I checked it was working.

I have just uploaded a new image with networking issue fixed and also the possibility to create a Wi-Fi hotspot
Please check if it is working as expected now

Thanks Sir. New image works immediately, i can connect to my local network. Thanks for your effort and time.

This thread was starting to get dusty, I believe this is a related issue......
I am using the WiFi Hotspot option, and found that it does not retain settings after reboot.
The fix I used for now, is to get to the terminal window (either directly or with ssh) and use

sudo nmtui

Note that you have to use the cursor keys to move around, no native mouse support here.

You will see all the network connections and can edit them.
Select QLCHOTSPOT
Cursor down to [ ] Connect Automatically
Use the Spacebar to put a X in the brackets
Move down to <Ok> hit enter
then <quit> and hit enter
then reboot

The Hotspot will come back every time!

This is useful to me because I use the Pi in places where access to it is sometimes difficult, and cold this time of year. This way I can sit in my warm truck and push a new show file to QLC from my phone I had been using cheap wireless routers as part of the installation to achieve the same end, this solution eliminates a piece of hardware---- one less thing to plug in.

I hope this helps someone!

I do have a question for you Massimo, If I am mucking around in the OS settings behind QLC, such as the above, am I going to break any of the QLC functions? I'm sure it's possible, I guess I just wanted to make that question a warning to someone like me who knows enough to be dangerous

EDIT: This is with the latest image downloaded yesterday 4.13.1-3

Thanks for sharing this information.
Another way from command line is to do And edit the autoconnect line into Save and reboot (or restart networkmanager)

I'll apply this fix for the next release

IamMarkie wrote: ↑Sat Dec 07, 2024 5:50 pm I do have a question for you Massimo, If I am mucking around in the OS settings behind QLC, such as the above, am I going to break any of the QLC functions? I'm sure it's possible, I guess I just wanted to make that question a warning to someone like me who knows enough to be dangerous

Well, for the network configuration on the Pi, QLC+ uses nmcli, so every tool around it will not break QLC+ per se.
Eventually you could break the OS network settings manually but nothing that cannot be usually fixed by deleting all the profiles in /etc/NetworkManager/system-connections and rebooting.
Also, you could break QLC+ network protocols by changing OS routes or configuring the interfaces with the same IP class (this is something Linux doesn't really like unless you play with metrics so you know what you're doing)