Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AutoDiscovery only gets a subset of bulbs on the network #37

Open
tovster opened this issue Jan 6, 2024 · 0 comments
Open

AutoDiscovery only gets a subset of bulbs on the network #37

tovster opened this issue Jan 6, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@tovster
Copy link

tovster commented Jan 6, 2024

Describe The Bug:
Similar to #9, however, it seems to only discover some of the bulbs, and fails to discover others. It doesn't seem to specifically be an issue with any type of bulb, but none of my GU10s are discovered.

  • These lights are confirmed to be connected to the network
  • They were addressable with Homekit using the LIFX official connection (I have removed them as I'm trying to use homebridge instead)
  • The lights can be manually added by IP (but I'd really prefer to avoid that)
  • I have set the broadcasting address as referenced in Auto discover and manual not working #9 (in my case it was 192.168.2.255)

To Reproduce:
Install the plug-in, configure it with AutoDiscovery.

Expected behavior:
It detects all bulbs.

Logs:

DEBUG - 2400003429986e560000000000000000000000000000007b000000000000000002000000 to 192.168.2.255
DEBUG - 2400003429986e560000000000000000000000000000007b000000000000000002000000 to 192.168.2.43
DEBUG - 2900001429986e56d073d514c5aa00004c4946585632007b38a47ea8069ba71703000000017cdd0000 from 192.168.2.26
DEBUG - 2900001429986e56d073d53a74e700004c4946585632007b6896f6b5d821000003000000017cdd0000 from 192.168.2.30
DEBUG - 2900001429986e56d073d538321d00004c4946585632007bc80ee93e0bb8290003000000017cdd0000 from 192.168.2.11
DEBUG - 2900001429986e56d073d55aa56400004c4946585632007b986283ade1a22c0003000000017cdd0000 from 192.168.2.42
DEBUG - 2900001429986e56d073d5655f5500004c4946585632007b4008467c1102000003000000017cdd0000 from 192.168.2.51
DEBUG - 2900001429986e56d073d53aeb1200004c4946585632007b18c7cc14e5a7200003000000017cdd0000 from 192.168.2.44
DEBUG - 2900001429986e56d073d538321d00004c4946585632007b70577f3f0bb8290003000000057cdd0000 from 192.168.2.11
DEBUG - 2900001429986e56d073d5655f5500004c4946585632007be09eeb7c1102000003000000057cdd0000 from 192.168.2.51
DEBUG - 2900001429986e56d073d53aeb1200004c4946585632007b78986315e5a7200003000000057cdd0000 from 192.168.2.44
DEBUG - 2900001429986e56d073d55aa56400004c4946585632007b68ce19aee1a22c0003000000057cdd0000 from 192.168.2.42
DEBUG - 2900001429986e56d073d53a74e700004c4946585632007b40d78cb6d821000003000000057cdd0000 from 192.168.2.30
DEBUG - 2900001429986e56d073d514c5aa00004c4946585632007b38ec66aa069ba71703000000057cdd0000 from 192.168.2.26
DEBUG - 2900001429986e56d073d556037600004c4946585632007ba88503891102000003000000017cdd0000 from 192.168.2.43
DEBUG - 2900001429986e56d073d556037600004c4946585632007b78f798891102000003000000057cdd0000 from 192.168.2.43
DEBUG - 2400001429986e56d073d55603760000000000000000007c000000000000000065000000 to 192.168.2.43
DEBUG - 2400001429986e56d073d538321d0000000000000000007d000000000000000065000000 to 192.168.2.11
DEBUG - 2400001429986e56d073d514c5aa0000000000000000007e000000000000000065000000 to 192.168.2.26
DEBUG - 2400001429986e56d073d53aeb120000000000000000007f000000000000000065000000 to 192.168.2.44
DEBUG - 2400001429986e56d073d53a74e700000000000000000080000000000000000065000000 to 192.168.2.30
DEBUG - 2400001429986e56d073d5655f5500000000000000000081000000000000000065000000 to 192.168.2.51
DEBUG - 5800001429986e56d073d514c5aa00004c4946585632007e38cef3bd069ba7176b0000007cb2cd0cffffac0d00000000556e6465726465736b00000000000000000000000000000000000000000000000000000000000000 from 192.168.2.26
DEBUG - 5800001429986e56d073d538321d00004c4946585632007d685a49570bb829006b000000c0d60000ffffac0d0000ffff4465736b204c616d7000000000000000000000000000000000000000000000000000000000000000 from 192.168.2.11
DEBUG - 5800001429986e56d073d53aeb1200004c4946585632007ff8d13c2de5a720006b00000000000000ffff8c0a000000004d61726be2809973204c616d70000000000000000000000000000000000000000000000000000000 from 192.168.2.44
DEBUG - 5800001429986e56d073d53a74e700004c4946585632008008eb93ced82100006b00000000000000ffff8c0a00000000426c616972e2809973204c616d700000000000000000000000000000000000000000000000000000 from 192.168.2.30
DEBUG - 5800001429986e56d073d5655f5500004c4946585632008168d91095110200006b000000551551b8ffffd90c0000ffff50656e64616e742049736c616e640000000000000000000000000000000000000000000000000000 from 192.168.2.51
DEBUG - 2400001429986e56d073d55aa56400000000000000000082000000000000000065000000 to 192.168.2.42
DEBUG - 5800001429986e56d073d55aa56400004c49465856320082a017f8cbe1a22c006b0000005ad0ffff0080ac0d0000ffff4c616d70000000000000000000000000000000000000000000000000000000000000000000000000 from 192.168.2.42
DEBUG - 5800001429986e56d073d556037600004c4946585632007c58aa70a1110200006b0000002d18ead15c0fac0d0000ffff4365696c696e67203500000000000000000000000000000000000000000000000000000000000000 from 192.168.2.43

Plugin Config:

{
            "name": "Lifx Plugin",
            "duration": 200,
            "brightnessDuration": 200,
            "colorDuration": 200,
            "default": "0.0.0.0",
            "broadcast": "192.168.2.255",
            "lightOfflineTolerance": 3,
            "messageHandlerTimeout": 45000,
            "resendPacketDelay": 150,
            "resendMaxTimes": 3,
            "updates": true,
            "debug": true,
            "autoDiscover": true,
            "bulbs": [
                {
                    "name": "Ceiling",
                    "address": "192.168.2.43"
                }
            ],
            "platform": "LifxPlugin"
        }

Environment:

  • Plugin Version: v0.3.0
  • Homebridge Version: v1.7.0
  • Node.js Version: v20.10.0
  • NPM Version: 10.2.3
  • Operating System: Docker
@tovster tovster added the bug Something isn't working label Jan 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant