Wednesday, 16 April 2014

Connected bulbs - a comparison of Philips Hue and LIFX

I'm making this comparison because I'm responsible for OSX apps that control Philips Hue bulbs and I hope to shortly have available two apps which will control the new LIFX bulbs.[edit]LIFXstyle for Mac is now available. I'm now using both types of bulbs in my home and don't favour one brand or the other, although there are pros and cons on both sides which I hope to list below.

The first thing to notice is that the LIFX bulb is physically larger than the Philips bulb. This means trouble fitting certain shades and lamps, but then the Philips bulb is also larger than a regular household bulb (if there is such a thing any more) and I've had trouble fitting those into certain lamps, especially with a screw/bayonet adaptor (more of that later).

Once fitted and switched on, the next noticeable thing is the brightness. The Hue bulbs go to around 600 lumens, and run up to 9W. The LIFX ones go to 17W and 1000 lumens (these are maximums, the actual power and brightness will of course depend on your colour and brightness settings).

Also worth a mention is that the Philips bulbs only come with an edison screw cap (ES). For UK users, this means either buying a fitting which takes screw-in bulbs, or buying an adaptor separately. I found these in a local electrical shop so no problem there but the adaptor does add to the overall height of the bulb. The LIFX bulb is available in bayonet (BC), so more convenient for UK users, as well as screw (ES) and 'downlight'.

LIFX bulbs are 'standalone', ie you just buy a bulb, plug it in and your app connects to it. This is interesting after using the Hue bulbs that require a 'bridge' which helps apps talk to the bulbs. The bridge comes as part of a starter kit with three bulbs, after that you buy individual bulbs. It would be wrong to list the Philips bridge as a con though because it does contain some functionality, for example any schedules that you set up sit on the bridge, so even with your computer off or your iPad away from the house, your lights will continue to operate on schedule.

In both cases there are a few steps to go through to get the lamps set up and your app controlling them. For me this was trouble-free in both cases and I can't say that one was much easier to get running than the other. If anything, the Philips bridge may make things a little more straightforward - you're only required to press the button on the bridge the first time that you run any app that wants to connect to it. and that's it. But in return for this user-friendliness you have got the extra hardware, extra leads to plug in and another power socket taken. The LIFX bulb may have taken a few more clicks to get running, It involves switching wireless networks and entering your regular wifi key to get everything talking. This was straightforward and just a case of following on-screen instructions.

With the bulbs up and running the next big noticeable difference is the colour range. I've seen criticism of the Hue bulbs for the gaps in their colour range. I've developed the app Ambisleeves which changes the colour of bulbs to reflect the album cover of the music currently playing and being displayed by Screensleeves. It's unfortunate that for apps like this, when a primary blue is required, hue bulbs are lacking and a violet-blue is the best they can do. Greens are almost non-existent. I'm not using any kind of measuring equipment, just my eyes, but the difference is obvious. I was very pleased to see the LIFX bulb show a good strong colour all the way around the spectrum. To be fair to Philips, lighting your room with a green light is generally not very conducive to any kind of mood.

Price-wise they're in the same ballpark, although with LIFX you can just buy as many or as few bulbs as you like, with Hue you need the bridge, so your first purchase will be the starter kit and you're paying for the bridge as part of that.

There are naturally some small differences in the way that they function. One that might be of interest is that if you ever use the wall switch, Hue bulbs will forget their previous setting and come on with a default bright white. LIFX bulbs do remember their colour and brightness settings which is a feature I like. In an emergency, you can override to that by using the wall switch to switch on rapidly after switching off which then gives you a bright white light.

If there's anything I've missed, anything you'd like to add or anything you'd like to ask, please use the comments below.

[Edit 27 Oct 2014] I've used both types of bulb in my own home for quite a while now and there's one more thing I'd like to note which will be of interest if you'd like to use the false dawn / false dusk feature. The step between 'off' and minimum brightness is quite a step with Hue bulbs, whereas the LIFX bulbs move much more smoothly from minimum brightness to off.

Friday, 11 April 2014

Scrutiny v5 (webmaster tools) - new features

The first of the new 'killer' features is website monitoring. It's very easy to add a url for monitoring, and with the 'enabled' checkbox checked and while Scrutiny is running, it'll check that url at the interval you set.
Options include sending GET or POST requests, and the code you expect back. You can choose what happens if the expected code isn't received - an on-screen alert, email, and/or writing to a log file.

Next, a couple of new options to make the crawl more flexible.
The support desk has received a few questions over the years about Scrutiny failing to find links on pages where the page requires javascript. If a page has 'nosscript' text then this is what Scrutiny has received, and if the page uses javascript to write content into the page Scrutiny hasn't seen it. We can debate whether this is the best way for a site to behave but Google now seems able to exectute js before parsing it and Scrutiny can now do the same.

Sites sometimes contain documents in pdf format which contain hyperlinks. Scrutiny can now scan those documents and check the links. It's an option turned off by default because pdfs can be huge and loading them in will obviously have an impact on the amount of memory Scrutiny is using.

The first thing you'll notice on starting Scrutiny 5 is the new interface. As Scrutiny has become bigger, the interface has become cluttered and bewildering to some. We hope that the new interface looks more welcoming. The list of sites shows more information than before with bigger icons.
It takes a step-by-step approach with Previous and Next buttons. When you click past the settings screen, you'll see a new list of tasks with a simple checkbox allowing you to run a new scan or use data already gathered.
Workflow is important to many, and I can tell you that setting a site to run on schedule is the best way to ensure that your site stays free of problems. With this in mind, this screen allows you to set a scheduled scan. Press 'Schedule', choose some options including the day and time, and then 'OK'.
From the task list mentioned earlier, it's possible to start a scan manually and then leave Scrutiny to take these actions when it's finished.

I hope that's sparked your interest. Scrutiny 5.0 is ready for beta testing and if you'd like to be involved in return for a free upgrade from v4 then contact

[update added 28 April 2014]
Scrutiny 5 is still in beta but is now on v5.0.3 and the following enhancements have been added:

  • Page character encoding detection is improved, and character encodings now supported include CP1251 (Cyrillic script eg Russian, Bulgarian, Serbian Cyrillic)
  • Now supports urls which include non-ascii characters. Some may argue that this is against web standards, but it's becoming more common and accepted by Google and browsers
  • New option to include <lastmod> in xml sitemap. If this is checked, the last modified date for internal pages is logged (if the server gives it) and shown in the sitemap table