expired TP-Link LB120 E27 Tunable White Smart Bulb $20 (+ Delivery/Free if over $55 or C&C) @ Officeworks


Spotted in Officeworks Richmond this morning - good price for a tunable white smart bulb (would be "white ambiance" from Philips Hue or Day+Night from LIFX). Plenty in stock here, but also available online for deliver or click and collect.

Down from $69.

The plain white bulb (LB110) is the same price but until the tunable white one sells out, why would you? Colour still full price for now.

Works with Google Home / Alexa. Wi-fi, doesn’t require a hub. Supports IFTTT.

Related Stores




    Unavailable online. What's the difference with Lb100?


    Just checked Richmond store.. stock on shelf was display - they had two left stashed which I purchased. Cheers for the post!


    Great deal but out of stock everywhere I checked.


    Ordered once with C&C. Thanks OP

  • +2 votes

    LB110 still available at 20 bucks if anyone interested. https://www.officeworks.com.au/shop/officeworks/p/tp-link-sm...


    Good deal if you can find stock. Really hoping they bring the color LB130 globes on sale, even at around $35 i only need one.


    Does this need some sort of smart socket? Or it can work in normal one?


      Normal bulb socket but you need some sort of device to control it and most likely a network wifi or bluetooth


    Just to point out that KMart do a similar Tunable white Wifi bulb for $20


    Similar but just dimable is $15, whereas full colour is $30

  • +1 vote

    And although not officially supported by Apple HomeKit can be easily made to work via Homebridge (https://www.npmjs.com/package/homebridge-tplink-smarthome)

    • +1 vote

      If I had known that I would have cleared out Officeworks instead of posting the deal… :(


      I've had some hit & miss results with the LB100's & homekit.
      Sometimes takes a couple of goes to turn the light on.
      And it seems their IP stack is a bit iffy:

      ping -t x.x.x.x & I'll see the time ramp up from ~20ms to ~200ms over about a minute, then drop back down and repeat

      Everything else on the network responds wtih <1ms

      Reply from bytes=32 time=156ms TTL=64
      Reply from bytes=32 time=161ms TTL=64
      Reply from bytes=32 time=167ms TTL=64
      Reply from bytes=32 time=165ms TTL=64
      Reply from bytes=32 time=173ms TTL=64
      Reply from bytes=32 time=176ms TTL=64
      Reply from bytes=32 time=181ms TTL=64
      Reply from bytes=32 time=186ms TTL=64
      Reply from bytes=32 time=195ms TTL=64
      Reply from bytes=32 time=189ms TTL=64
      Reply from bytes=32 time=198ms TTL=64
      Reply from bytes=32 time=201ms TTL=64
      Reply from bytes=32 time=226ms TTL=64
      Reply from bytes=32 time=216ms TTL=64
      Reply from bytes=32 time=13ms TTL=64
      Reply from bytes=32 time=216ms TTL=64
      Reply from bytes=32 time=16ms TTL=64
      Reply from bytes=32 time=23ms TTL=64


        Interesting. I'm running a couple of LB120's and some HS100/110 Smart switches. As well as a bunch of Xiaomi Yeelight bulbs and lightstrips. And one Xiaomi Philips bulb. All running through Homebridge. Everything has been rock solid except for the Philips bulb which keeps dropping off the network. But it is the furthest from the router.
        Are you running the homebtidge-tplink-smarthome package or the older homebridge-hs100 package?


          Running the homebridge-tplink-smarthome

          Just took a bit more of a look at the error…

          [2019-3-24 14:54:24] [TplinkSmarthome.API] UDP Timeout
          [2019-3-24 14:54:24] [TplinkSmarthome.API] [Light] device.send() Error: UDP Timeout
          [2019-3-24 14:54:24] [TplinkSmarthome] [Light]
          [2019-3-24 14:54:24] [TplinkSmarthome] Error: UDP Timeout
          at Timeout.setTimeout [as _onTimeout] (C:\Users\xxxxx\AppData\Roaming\npm\node_modules\homebridge-tplink-smarthome\node_modules\tplink-smarthome-api\lib\client.js:144:22)
          at ontimeout (timers.js:475:11)
          at tryOnTimeout (timers.js:310:5)
          at Timer.listOnTimeout (timers.js:270:5)

          & added "timeout: 300" to the config.
          See how it goes.

  • Top