stringandstickytape / maxlifx Goto Github PK

Hi I'm trying to use this app but it constantly is crashing. I'm on Windows 10 64bit. All the bulbs are detected but it doesn't work. Please advise.

When you open the app and i select "Yes" to discover, nothing happens.

if i select no and go to discover, i get the following error.

0.2 and 0.3 work ok

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.Sockets.SocketException (0x80004005): An attempt was made to access a socket in a way forbidden by its access permissions
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.Net.Sockets.UdpClient..ctor(Int32 port, AddressFamily family)
at MaxLifx.Controllers.MaxLifxBulbController.DiscoverBulbs(String ip) in C:\Git\MaxLifx2\MaxLifxBulbController\MaxLifxBulbController.cs:line 74
at MaxLifx.MainForm.toolStripMenuItem1_Click(Object sender, EventArgs e) in C:\Git\MaxLifx2\MaxLifx\MainForm.cs:line 863
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

MaxLifx
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/jimmy/Desktop/maxlifx%20.5/MaxLifx.exe

System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2104.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

System
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2103.2 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

MaxLifxBulbController
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/jimmy/Desktop/maxlifx%20.5/MaxLifxBulbController.DLL

System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

WindowsBase
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll

Newtonsoft.Json
Assembly Version: 7.0.0.0
Win32 Version: 7.0.1.18622
CodeBase: file:///C:/Users/jimmy/Desktop/maxlifx%20.5/Newtonsoft.Json.DLL

Microsoft.CSharp
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll

System.Numerics
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll

System.Runtime.Serialization
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll

System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0 built by: NET47REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll

System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

System.Dynamic
Assembly Version: 4.0.0.0
Win32 Version: 4.7.2046.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll

Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

LIFX strips are zoned; would it be possible to have the app treat each zone as an individual bulb?

I just started using MaxLifx with my Lifx Mini Color. I've noticed that whenever the screen is completely white or any shade of grey, it becomes a warm white instead of cool white like the screen. I am unable to test whether this occurs with non-mini bulbs.

If a scene that is very dimly lit occurs, a lamp may flash very rapidly as it tries to reproduce the scene on the display. It seems plausible that the lamp may be attempting to produce light below its minimum threshold. This may result in observed rapid switching between off and on in a dark scene. An option to reduce flicker and strobing, particularly when the fade and delay variables have been lowered considerably, would likely alleviate this issue.

Hey there! I know it's been a while since you touched this app, but I'd really like to use it and now that I've put my Bulbs on their own LAN subnet (My home LAN is x.x.10.x and now the 'IoT LAN' as I call it is on x.x.20.x), I can see when MaxLIFX tries to discover bulbs it reaches out to broadcast, it seems:

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 262144 bytes
15:44:11.816078 IP 192.168.10.50.65289 > 192.168.10.255.56700: UDP, length 36
15:44:36.793388 IP 192.168.10.50.57182 > 192.168.10.255.56700: UDP, length 36
15:46:48.609113 IP 192.168.10.50.64130 > 192.168.10.255.56700: UDP, length 36
15:48:02.345216 IP 192.168.10.50.64174 > 192.168.10.255.56700: UDP, length 36
15:48:20.358130 IP 192.168.10.50.54793 > 192.168.10.255.56700: UDP, length 36
15:48:40.004710 IP 192.168.10.50.63145 > 192.168.10.255.56700: UDP, length 36
15:49:12.999449 IP 192.168.10.50.63162 > 192.168.10.255.56700: UDP, length 36
15:49:19.851017 IP 192.168.10.50.62279 > 192.168.10.255.56700: UDP, length 36

But nothing is received on the LAN2 side. I've allowed all traffic between the two subnets on port 56700 (And I can verify that traffic does flow on LAN2 to the LIFX Cloud, it appears:

15:54:45.895369 IP 104.198.46.246.56700 > 192.168.20.118.53027: Flags [.], ack 5176, win 65392, length 0
15:54:45.902500 IP 104.198.46.246.56700 > 192.168.20.108.56509: Flags [.], ack 7282, win 65392, length 0
15:54:45.902677 IP 104.198.46.246.56700 > 192.168.20.114.64825: Flags [.], ack 6724, win 65392, length 0
15:54:45.905052 IP 192.168.20.111.21709 > 104.198.46.246.56700: Flags [P.], seq 4600:4717, ack 4134, win 1460, length 117
15:54:45.906731 IP 192.168.20.115.56700 > 192.168.20.255.56700: UDP, length 88
15:54:45.908168 IP 192.168.20.116.56700 > 192.168.20.255.56700: UDP, length 88
15:54:45.909430 IP 104.198.46.246.56700 > 192.168.20.146.60080: Flags [.], ack 6542, win 65392, length 0
15:54:45.938087 IP 192.168.20.110.31600 > 104.198.46.246.56700: Flags [P.], seq 4296:4413, ack 3817, win 1460, length 117
15:54:45.953788 IP 192.168.20.115.20937 > 104.198.46.246.56700: Flags [P.], seq 4599:4716, ack 4135, win 1460, length 117

I'm using a pfsense firewall, if that helps at all. I'm wondering how to finagle this on my side if it's not something that MaxLIFX can do. Please let me know if you have any ideas! Thank you!

Unfortunately, I switched my LIFX lamps (four) to a different network entirely, and the lamps will not show up in MaxLifx anymore. They show up and are lightning fast in the LIFX app, but not in MaxLifx. Perhaps there is a difference in how the LIFX Universal Windows app connects to the lamps?

I suppose maybe it has something to do with the LIFX Cloud, but it's really hard to say.

Another Reddit user mentioned that he encountered the same issue, where his lamps show up in the LIFX official app, but not in MaxLifx.

I have been using this program since day one. Would you please see if there is anything that can be done for those of us who are having this trouble? Unfortunately, it will be impractical for me to try to go back to the configuration I had before, and I don't want to be without MaxLifx!

Thank you!

Hey, this issue has been posted before, but cannot seem to find a fix. I'm using MaxLifx 0.6 and up until today it was working fine. I cannot discover any bulbs. I tried resetting them, resetting wifi, changed fire wall settings, etc. Any ideas how to fix?

It's been awhile, but I use this program often. I have my own script for my unique living room setup too, but one thing I can't ignore is the amazing, music-reactive feature in the desktop app. Can this be brought to UWP? Possibly via Xamarin & UWP? I see that you began work on an Android app, but this feature alone is worth paying for, because it's significantly better than the official music-reactive LIFX app feature.

Thanks, and hope all is well!

I'm on ethernet, while my bulbs are on wifi (same network though) - is that likely the cause?

lifxDynamic and the official Lifx windows app don't have any issues detecting

Tried being on same wifi instead of wired. Disabled firewall and virus protection. Ran as admin. Not sure what else to try. Thanks!

I have not been able to get this to discover my lights. However, when using the lifxlan utilities, that seems to work fine. Also, another program I found on github, called Lifx control panel, uses lifxlan and that one works fine, never has any issues discovering the lights. It seems to be hit or miss (mostly miss) though, because yet a 3rd program using lifxlan called lifxlan-gui does not work either. The official Lifx windows 10 app, and a 3rd party app from the windows app store called lifxdynamic, both work as well. At first I thought there was something about my network that lifxlan just didn't like, but seeing how lifxlan standalone utilities work, and Lifx control panel works using lifxlan. I can't wrap my head around how this could be possible. Any help would be greatly appreciated as I very much would like to use this program.

When I click "Start Sound Response Thread" On Remote Desktop session the program crash

Hi,
Works great thanks but it would be much better if we can map the lights according to their placement so when the light can display for example the left side of the screen and the right section of the strip will display the right of my screen.

Not an issue, but a question. Does Maxlifx only work with lifx bulbs or are other wifi bulbs like the Yeelight ones supported as well?

Just stumbled across this via the thread in Reddit. Want to say how awesome it is with Mechwarrior Online, in FULL SCREEN too!

Here's the demo video!

https://drive.google.com/file/d/1b3zN8-5csn3sG5zKBOsL2W9W--KJHuGF5g/view?usp=sharing

Upon opening a thread for screen colour response or sound response, a maximum of seven (byte limitation?) lights may be addressed simultaneously. However, saving the thread, which initially appears to work, is where the issue becomes problematic. After "saving" the thread, clicking on load thread kills the existing "saved" thread process, and the previously "saved" thread no longer exists.

I have added several lights to my room, and have now more than doubled the total number of lights I wish to use simultaneously (from four to ten). Why? Because I love MaxLifx! I also won an eBay auction, and got the lights at a steep discount (woo!)

My best guess is the reason there is an issue saving and/or loading threads with more than the number of lights I have been using is that the number of lights are not generally expected to exceed a byte in size. The overall number of lights in my home has gone up by 10 now, so this is a different game. Let me know if there's anything I can try out to help with the troubleshooting.

A couple of additional notes, the total number of discovered lights now also exceeds a byte, and before I clicked discover, I was able to successfully run the four lights by loading my previously working threads. Now, if I attempt to open said threads, nothing happens. On another, less important note, it appears the new Lifx Mini lamps are not supported by MaxLifx. This may require information by LIFX to fix, so that's low priority for me here.

Thanks, @stringandstickytape, for everything you do. If there is any chance you can get around to this, that'd be super cool!

Tried using the same wifi network as my bulbs and I still cannot connect to them.

After starting MaxLifx, starting the sound response thread and selecting a light to use with it, the program crashes. It's selecting the bulb I want that does it, every time.

Really keen to get some lighting tuned to my gaming, hope this project is still in development!
Thank you for your work so far :)

The application crashes without any error message when starting a sound response thread on Win 10 x64.

Hey great tool, exactly what I was looking for.

Could you add a white point correction? So we can set the Monitor/TV white point (3000k, 3500k, 4000k...)? My Monitors are not set to 6500k so whites are represented wrongly. Warm whites are displayed cold on the Lifx bulbs because of that.