Crash on Startup

[Blakey069]

@samclane Hi, I'm getting this error when trying to launch the program:

lifx-control-panel.log

I've tried running this on my laptop as well and no luck.

[littlelerroyy]

Just got a new light today, having same issue as this

[aryn-0xide]

having same issue - crashing on startup but slightly different exception is thrown.

[DarynGit]

Same issue, only started happening when I got the newer "Lifx Color" bulbs. Worked fine on the old A19.

[samclane]

I'm looking at making the app startup more resilient, so the user can at least open the app and manually re-scan (and eventually just tie that into a regular heartbeat operation).

Nothing is wrong with your setup, I get this error too. In the meantime, try re-opening the app right away. You may need to do this 3-4 times; this simulates a manual re-scanning of the network. I'm aware this is the upmost-jank, and will be working on getting the resiliency-patch out soon.

[Mister-Curious]

While attempting to open lifx_control_panel.exe I get this error: I tried running the application consecutavely crash after crash, but its endless. Will this application be getting an update any time soon to fix this? I cant even get these lights to connect to the native app on my phone.

Thanks!

[RoboKun]

Having the same issue as others on this thread. also tried re-opening the app multiple times and getting the same error screen. Not sure if it's the issue, but I'm using the Color bulbs as well.

[samclane]

I'm sorry all, I've been terribly busy with work and life stuff. I haven't had much time to devote to this project. At a certain point, I think I want to just refactor the whole thing completely. Using threads in Python is awful, and leads to lots of issues like this. There are also problems with the networking library being used, where certain other software can interfere with startup (like WSL/Docker). I've had a few more years of professional Python experience since I first made this project, and I think that a refactor could lead to a lot of stability fixes, as well as make the code more maintainable by the community.

I'm probably going to make a Discord server for the project in the coming days, so I can begin to have a more casual correspondence with the community, and development can be done with a more Pythonic, and developer-friendly, mentality.

I realize those last 2 paragraphs probably aren't the most satisfying response, but I don't have an easy answer for this, unfortunately.

[ozgent]

I downloaded v2.2.0 yesterday and it worked fine but today I have the following issue.

[soundinsect]

I would advise everyone having this issue to guarantee that they aren't doing anything that is modifying their machine's visibility on the network. I was having the same error and suddenly remembered I was running a VPN at the time. Since the error seemed to be dealing with a network problem, I decided to disconnect from the VPN and relaunched the program. It immediately started without issue.

I closed the program, reconnected to the VPN and was able to reproduce the error when I tried launching again. Disconnected from the VPN again and it was fine once again.

[djcorvus]

Still getting this issue, and it's now July 2022. I'm not connected to a VPN, nor do I have any firewalls on my machine.

Is there a fix yet?

[samuellogan]

Had this same issue when opening the app with a VPN in the background (proton VPN), after disconnecting from the VPN it worked - this was the error before unless it was just that it magically worked the 4th time after failing the first 3 times