LIFX Bridge issue

[Woetjes]

Hi Joe,

I've installed the LIFX bridge and setup some devices. But the Harmony Hub doesn't find any 'LIFX bulbs', I've tried both the mobile and the Mac app. I've put debugging on and the message I got was:
"LIFX Bridge Debug deviceDeleted called"

Any idea?

Thanks,
W.

[FlyingDiver]

I'm going to need to see the actual log output for the entire process. Make sure the plugin is set for debugging level messages, then restart the plugin. Make sure you have at least one Indigo device advertised through the plugin.

Then make the Harmony look for LIFX devices. Using the iOS app, press the menu image (horizontal bars in upper left of screen), then Harmony Setup, then Add/Edit Devices & Activities. Then drill down to Add Device and "Home Control" devices. Select LIFX there. If you've already done that part, "Smart Bulbs" will be on the previous screen. If so, go to that screen and touch REFRESH at the bottom of the screen. You should get a item labeled "Lights", which you can expand to get the list of items advertised by the bridge.

[FlyingDiver]

Better yet, go through that process, then attach the plugin log file to a reply in this thread. The file will be in your Indigo 7 folder -> Logs -> com.flyingdiver.indigoplugin.lifxbridge -> plugin.log

[Woetjes]

Hi Joe,

See the log file attached.
I don't know if it's something but I noticed in the logs: "Bind failed. Error Code : 48 Message Address already in use"

Thanks,
W

[FlyingDiver]

Well, that's definitely the problem. You have something else running on the port that the LIFX devices use. Quit anything else related to the Harmony or LIFX and restart the plugin.

[Woetjes]

OK stupid me - I thought I disabled the Autolog LIFX plugin but it was enabled
Now it's working Thanks for the quick reply.

[FlyingDiver]

Yeah, that's a problem I ought to talk to Autolog about. My server HAS to be on the default LIFX port, because the clients (like the Harmony Hub) need to contact it on that port. By default, LIFX clients use the same port. Which is a really bad design decision. The default client code will try a different port if the standard one is in use, but mine can't. So if the LIFX Bridge plugin is started first, you should be able to start Autolog's plugin after. If he's using the default LIFX library code.

Edit: Which he isn't. He's using the hard-coded port number. So the two plugins can't coexist on the same Indigo server.

[autolog]

That looks like a simple change to do in my LIFX plugin.

What do you suggest, allowing the user to define the port number in the plugin config?

I can incorporate the change in the V7 LIFX plugin that I am working on.

[autolog]

That looks like a simple change to do in my LIFX plugin. ...

Spoke to soon, it seems it has to be port 56700 to work

[FlyingDiver]

That looks like a simple change to do in my LIFX plugin. ...

Spoke to soon, it seems it has to be port 56700 to work

We should take this offline. Is the I7 code significantly different than the current plugin?


Sent from my iPad using Tapatalk