Do LB200 bulbs work?

[mark-hahn]

I just bought two LB200 bulbs. I can't discover them. Are they too new?

[konsumer]

No one has tested with them, but I could probably add LB200 & LB230, if you can share some network traffic (recorded with tcpdump) of discovering & talking to them. I followed the instructions here and then connected to the fake wifi AP and recorded traffic, then later analyzed it with the wireshark addon I modified.

[mark-hahn]

Thx. I will do this.

Does controlling the bulb work when it is also set up for the kasa cloud control or do I need to somehow reset it? I don't need kasa in the long run but I have set it up now to make sure the bulbs work, which they do. Kasa will also provide the tcpdump net traffic.

On Thu, Jan 4, 2018 at 3:19 PM, David Konsumer notifications@github.com wrote:

No one has tested with them, but I could probably add LB200 & LB230, if you can share some network traffic (recorded with tcpdump) of discovering & talking to them. I followed the instructions here https://learn.adafruit.com/setting-up-a-raspberry-pi-as-a-wifi-access-point?view=all and then connected to the fake wifi AP and recorded traffic, then later analyzed it with the wireshark addon I modified https://github.com/konsumer/tplink-lightbulb/blob/master/tplink-smarthome.lua .

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355427509, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv29EgbHD9iuIN4IdN4U6Vjhpfe9mks5tHVydgaJpZM4RTyRq .

[konsumer]

if you cycle power manually 3 times, it will reset the bulb. Then, with your phone on the fake wifi network, make sure tcpdump is running and setup the bulb in kasa app to use that network and do stuff like on/off/etc in kasa.

[mark-hahn]

will do

On Thu, Jan 4, 2018 at 3:39 PM, David Konsumer notifications@github.com wrote:

if you cycle power manually 3 times, it will reset the bulb. Then, with your phone on the fake wifi network, make sure tcpdump is running and setup the bulb in kasa app to use that network and do stuff like on/off/etc in kasa.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355430865, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv6bqZDfPr7fMCSWobou9PhD4nu9Kks5tHWEygaJpZM4RTyRq .

[konsumer]

I have a feeling it's a minor thing in the initial scan-broadcast, so hopefully it won't be too hard to work out.

[balvant813]

I have tested LB230 with tplight/tplink-lightbulb on Raspberry PI 3b. It recognizes LB230 and I can use hsb etc and tplight sets it correctly. Sometime I get socket conn time outs.

[konsumer]

@balvant813 That's great. I assumed they used a similar protocol, but I'll add it to the support matrix.

[mark-hahn]

I removed a bulb from kasa, started tcpdump, reset the bulb to get the three flashes, and kasa can't connect. I've done this many times. Before trying tcpdump i've gotten it to connect twice so I'm sure the bulb is good. I'll try a different bulb.

Is there a way to reset the configuration in the bulb? A fresh start might help.

On Thu, Jan 4, 2018 at 10:07 PM, David Konsumer notifications@github.com wrote:

@balvant813 https://github.com/balvant813 That's great. I assumed they used a similar protocol, but I'll add it to the support matrix.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355480244, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv2f1ceRXwSKeFhvgxDZt0RQuf2x0ks5tHbwvgaJpZM4RTyRq .

[konsumer]

The only way I have seen is to quickly turn the power off for the light (like at the switch, not the app) 3-5 times. It will flash when you reset it.

[mark-hahn]

I finally got a capture. Unfortunately the file is big, 2200 packets, because my wifi has a lot on it. I paired the bulb, named it, turned the light off then on, and finally faded to zero.

An nmap scan says there is a Tp-link Technologies node with an IP of 192.168.1.164. I unscrewed the bulb and that IP went away. So I'm pretty sure it is right.

I looked for that IP in wireshark and found nothing. But I'm not good at wireshark filtering so it could be wrong.

On Fri, Jan 5, 2018 at 2:22 PM, David Konsumer notifications@github.com wrote:

The only way I have seen is to quickly turn the power off for the light (like at the switch) 3-5 times. It will flash when you reset it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355681602, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv_NrcjzDDoYXJD_hMhl4RGWtZ9TSks5tHqCJgaJpZM4RTyRq .

[mark-hahn]

BTW, I'm using a TP-link wifi AP so don't be confused about that at 192.168.1.2.

On Fri, Jan 5, 2018 at 3:19 PM, Mark Hahn mark@hahnca.com wrote:

I finally got a capture. Unfortunately the file is big, 2200 packets, because my wifi has a lot on it. I paired the bulb, named it, turned the light off then on, and finally faded to zero.

An nmap scan says there is a Tp-link Technologies node with an IP of 192.168.1.164. I unscrewed the bulb and that IP went away. So I'm pretty sure it is right.

I looked for that IP in wireshark and found nothing. But I'm not good at wireshark filtering so it could be wrong.

On Fri, Jan 5, 2018 at 2:22 PM, David Konsumer notifications@github.com wrote:

The only way I have seen is to quickly turn the power off for the light (like at the switch) 3-5 times. It will flash when you reset it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355681602, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv_NrcjzDDoYXJD_hMhl4RGWtZ9TSks5tHqCJgaJpZM4RTyRq .

[mark-hahn]

Mac is 50:C7:BF:F8:46:CA.

On Fri, Jan 5, 2018 at 3:23 PM, Mark Hahn mark@hahnca.com wrote:

BTW, I'm using a TP-link wifi AP so don't be confused about that at 192.168.1.2.

On Fri, Jan 5, 2018 at 3:19 PM, Mark Hahn mark@hahnca.com wrote:

I finally got a capture. Unfortunately the file is big, 2200 packets, because my wifi has a lot on it. I paired the bulb, named it, turned the light off then on, and finally faded to zero.

An nmap scan says there is a Tp-link Technologies node with an IP of 192.168.1.164. I unscrewed the bulb and that IP went away. So I'm pretty sure it is right.

I looked for that IP in wireshark and found nothing. But I'm not good at wireshark filtering so it could be wrong.

On Fri, Jan 5, 2018 at 2:22 PM, David Konsumer notifications@github.com wrote:

The only way I have seen is to quickly turn the power off for the light (like at the switch) 3-5 times. It will flash when you reset it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355681602, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv_NrcjzDDoYXJD_hMhl4RGWtZ9TSks5tHqCJgaJpZM4RTyRq .

[mark-hahn]

eth.addr == 50:C7:BF:F8:46:CA got some packets

On Fri, Jan 5, 2018 at 3:38 PM, Mark Hahn mark@hahnca.com wrote:

Mac is 50:C7:BF:F8:46:CA.

On Fri, Jan 5, 2018 at 3:23 PM, Mark Hahn mark@hahnca.com wrote:

BTW, I'm using a TP-link wifi AP so don't be confused about that at 192.168.1.2.

On Fri, Jan 5, 2018 at 3:19 PM, Mark Hahn mark@hahnca.com wrote:

I finally got a capture. Unfortunately the file is big, 2200 packets, because my wifi has a lot on it. I paired the bulb, named it, turned the light off then on, and finally faded to zero.

An nmap scan says there is a Tp-link Technologies node with an IP of 192.168.1.164. I unscrewed the bulb and that IP went away. So I'm pretty sure it is right.

I looked for that IP in wireshark and found nothing. But I'm not good at wireshark filtering so it could be wrong.

On Fri, Jan 5, 2018 at 2:22 PM, David Konsumer <notifications@github.com

wrote:

The only way I have seen is to quickly turn the power off for the light (like at the switch) 3-5 times. It will flash when you reset it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355681602, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv_NrcjzDDoYXJD_hMhl4RGWtZ9TSks5tHqCJgaJpZM4RTyRq .

[mark-hahn]

I got a scan to work.

$ tplight scan
Press Ctrl-C to stop
192.168.1.164 - My Smart Bulb - LB200(E26)

I might have tried scanning before Kasa configured them.

I'll try controlling it now.

[mark-hahn]

Everything seems to work now, so don't waste your time on the dump.

Thanks and I'm sorry for your trouble.

[konsumer]

That's awesome! If ya'll want to test the full list of commands (the table on the front page) I'd be grateful, so I can ensure everything works for others.

[mark-hahn]

I've tested scan, info, power, and details and they all work.

One question; how do I dim? I've tried power with brightness but I can't get it to work. The command always returns brightness:100.

On Fri, Jan 5, 2018 at 4:35 PM, David Konsumer notifications@github.com wrote:

That's awesome! If ya'll want to test the full list of commands (the table on the front page) I'd be grateful, so I can ensure everything works for others.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355704680, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhvxgHTlASb4b8Ejn6a8-STe-OW83pks5tHr_ggaJpZM4RTyRq .

[konsumer]

The on command can do it with the brightness flag. Do tplight on --help

[mark-hahn]

I'm using the node api. If I do light.power(false) the light goes off. If I do light.power({brightness:100}) it comes on. But numbers in between just turn it on.

On Fri, Jan 5, 2018 at 6:34 PM, David Konsumer notifications@github.com wrote:

The on command can do it with the brightness flag. Do tplight on --help

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355716920, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv8ef66A6kVp8HXmzWoFymsmY5sr_ks5tHtvRgaJpZM4RTyRq .

[mark-hahn]

BTW, tplight on -b 10 192.168.1.163 works.

On Fri, Jan 5, 2018 at 6:44 PM, Mark Hahn mark@hahnca.com wrote:

I'm using the node api. If I do light.power(false) the light goes off. If I do light.power({brightness:100}) it comes on. But numbers in between just turn it on.

On Fri, Jan 5, 2018 at 6:34 PM, David Konsumer notifications@github.com wrote:

The on command can do it with the brightness flag. Do tplight on --help

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-355716920, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv8ef66A6kVp8HXmzWoFymsmY5sr_ks5tHtvRgaJpZM4RTyRq .

[konsumer]

The params are powerState, transition, options, so the command is this:

light.power(true, 0, {brightness: WHATEVER})
  .then(status => {
    // command completed. look at status to see how it went
  })

because brightness is an option.

[mark-hahn]

Thanks. It is working now. I was sending a string instead of an integer. This is one of the few times that a typed language would have helped. :-)

So add the LB200 to your list.

On Mon, Jan 8, 2018 at 3:32 PM, David Konsumer notifications@github.com wrote:

The params are powerState, transition, options, so the command is this:

light.power(true, 0, {brightness: WHATEVER}) .then(status => { // command completed. look at status to see how it went })

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/konsumer/tplink-lightbulb/issues/22#issuecomment-356130428, or mute the thread https://github.com/notifications/unsubscribe-auth/AAxhv4cfZmT3n5mJJ6Mc_EOu4aYxB4KCks5tIqWJgaJpZM4RTyRq .