Monthly retrospective: May 2025

I’ve been struggling to post retrospectives this year – they are pretty time consuming to write. But, you may have noticed the volume of content on the blog increasing lately. That’s because I finally have a workflow with ChatGPT prompts that help me draft content quickly, in my own style. (I even subscribe to ChatGPT now, and regular readers will know how I try to keep my subscription count down.) Don’t worry – it’s still human-edited (and there are parts of the web that ChatGPT can’t read – like my LinkedIn, Instagram and even parts of this blog) so it should still be authentic. It’s just less time-consuming to write – and hopefully better for you to read.

On the blog…

Home Assistant tinkering (again)

I’ve been continuing to fiddle with my smart home setup. This month’s project was replacing the ageing (and now unsupported) Volvo On Call integration in Home Assistant with the much better maintained HA Volvo Cars HACS integration. It works brilliantly – once you’ve jumped through the hoops to register for an API key via Volvo’s developer portal.

And no, that doesn’t mean I can now summon my car like KITT in Knight Rider – but I can check I locked it up and warm it up remotely. Which is almost as good. (As an aside, I saw KITT last month at the DTX conference in Manchester.)

Software-defined vehicles

On the subject of cars, I’ve been reflecting on how much modern cars depend on software – regardless of whether they’re petrol, diesel or electric. The EV vs. ICE debate often centres on simplicity and mechanics (less moving parts in an EV), but from my experience, the real pain points lie in the digital layer.

Take my own (Volvo V60, 2019 model year). Mechanically it’s fine and it’s an absolute luxury compared with the older cars that my wife and sons drive, but I’ve seen:

  • The digital dashboard reboot mid-drive
  • Apple CarPlay refusing to connect unless I “reboot” the vehicle
  • Road sign recognition systems confidently misreading speed limits

Right now, it’s back at the body shop (at their cost, thankfully) for corrosion issues on a supposedly premium marque. My next car will likely be electric – but it won’t be the drivetrain that convinces me. It’ll be the software experience. Or, more realistically, the lack of bad software. Though, based on Jonathan Phillips’ experience, new car software contains alarming typos in the UI, which indicates a lack of testing…

Thinking about the impact of generative AI

This update isn’t meant to be about AI – but it seems it is – because it’s become such a big part of my digital life now. And, increasingly, it’s something I spend more time discussing with my clients.

AI isn’t new. We’ve had robotic process automation (RPA), machine learning, data science and advanced analytics for years. I even studied neural networks at Poly’ in the early 1990s. But it’s generative AI that’s caught everyone’s imagination – and their budgets.

In Episode 239 of the WB-40 podcast (AI Leadership), I listened to Matt Cockbill talk about how it’s prompting a useful shift in how we think about technology. Less about “use cases” and more about “value cases” – how tech can improve outcomes, streamline services, and actually help achieve what the organisation set out to do.

The rush to digitise during COVID saw huge amounts of spending – enabling remote working or entrenching what was already there (hello, VDI). But now it feels like the purse strings are tightening, and some of that “why are we doing this again?” thinking is creeping back in. Just buying licences and rolling out tools is easy. Changing the way people work and deliver value? That’s the real work.

Meal planning… with a side of AI

I’ve also been experimenting with creating an AI-powered food coach to help me figure out what to eat, plan ahead, and avoid living off chocolate Hobnobs and toasted pitta. Still early days – but the idea of using an assistant to help nudge me towards healthier, simpler food is growing on me.

Reading: The Midnight Library

I don’t read much fiction – I’m more likely to be found trawling through a magazine or scrolling on my phone – but Matt Haig’s “The Midnight Library really got me. OK, so technically, I didn’t read it – it was an impulse purchase to use some credits before cancelling my Audible account – but it was a great listen. Beautifully read by Carey Mulligan, it’s one of those rare books that manages to be both dark and uplifting. Some reviews suggest that not everyone feels the same way – and my reading it at a time of grief and loss may have had an impact – but I found it to be one of my best reads in a long time.

Without spoiling anything, the idea of a liminal space between life and death – where you can explore the infinite versions of yourself – is quietly brilliant. Highly recommended. So much so that I bought another copy (dead tree edition) for my wife.

On LinkedIn this month…

It’s been a lively month over on LinkedIn, with my posts ranging from AI hype to the quirks of Gen-Z slang (and a fair dose of Node4 promotion). These are just a few of the highlights – follow me to get the full experience:

  • Jony and Sam’s mysterious new venture
    I waded into the announcement from Jony Ive and Sam Altman with, let’s say, a healthy dose of scepticism. A $6.5bn “something” was teased with a bland video and a promo image that felt more 80s album cover than product launch. It may be big. But right now? Vapourware.
  • Is the em dash trolling us?
    I chipped in on the debate about AI-written content and the apparent overuse of em dashes (—) –often flagged as an “AI tell” – usually by people who a) don’t understand English grammar or b) where LLMs learned to write. (I am aware that I incorrectly use en dashes in these posts, because people seem to find them less “offensive”.) But what if the em dash is trolling us?
  • Skibidi-bibidi-what-now?
    One of the lighter moments came with a post about Gen-Z/Gen-Alpha slang. As a Gen-Xer with young adult kids, I found a “translator” of sorts – and it triggered a few conversations about how language evolves. No promises I’ll be dropping “rizz” into meetings just yet. Have a look.
  • Politeness and prompting
    Following a pub chat with Phil Kermeen, I shared a few thoughts on whether being polite to AI makes a difference. TL;DR: it does. Here’s the post.
  • Mid-market momentum
    Finally, there have been lots of posts around the Node4 2025 Mid-Market Report. It was a big effort from a lot of people, including me, and I’m really proud of what we’ve produced. It’s packed with insights, based on bespoke research of over 600 IT and Business leaders.

Photos

A few snaps from my Insta’ feed…

https://www.instagram.com/markwilsonuk/p/DJr5Ui8N94u

For more updates…

That’s all for now. I probably missed a few things, but it’s a decent summary of what I’ve been up to at home and at work. I no longer use X, but follow me on LinkedIn (professional), Instagram (visual) and this blog for more updates – depending on which content you like best. Maybe even all three!

Next month…

A trip to Hamburg (to the world’s largest model railway); ramping up the work on Node4’s future vision; and hopefully I’ll fill in some of the gaps between January and May’s retrospectives!

Featured image: created by ChatGPT

Sorting out my smart home

A few years ago, I bought some Philips Hue lights. Then I extended the system with some Innr bulbs, and some IKEA Trådfri lights too. It’s mostly worked OK: the Philips and Innr stuff is flawless; the IKEA kit has its foibles (but was cheap).

More recently, I started to look at Home Assistant and I installed a pre-built “Home Assistant Green” unit. One of the things I bought was a SkyConnect dongle – for Zigbee support. When I set up Home Assistant it discovered my Hue bridge and all the lights, so I didn’t use the SkyConnect at first, until I started to add some more sensors that Hue didn’t recognise.

Consolidating Zigbee networks

I couldn’t understand why my lights were not acting as Zigbee routers for the door/window sensors I had purchased – and then I realised that I actually have two Zigbee networks in the house now! So I started to move the Hue lights over to the Zigbee Home Assistant (ZHA) network that the SkyConnect had established.

The next problem was, predictably, an IKEA bulb I’d purchased. When I originally joined it to Hue, I had problems with the official app and I needed to use TouchLink via the Hue Essentials app. I’m having no such luck on ZHA – I can’t even get the bulb into pairing mode… so it’s presently just a normal (not smart) lamp…

Extending the reach

With most of the Hue and Innr lamps now migrated to ZHA, I’ve started to add other Zigbee devices to the network now. Firstly, I have some cheap (£3) temperature and humidity sensors from Tuya that I bought on AliExpress. One of these is monitoring the levels overnight in the Man Cave and turning on a radiator if necessary overnight to keep the humidity down. I’ve also put a Tuya Zigbee signal repeater in the kitchen, to help boost the signal towards the garden (at least until I put some more bulbs in that will act as routers).

I’ve since found that the SkyConnect is not necessarily the best Zigbee co-ordinator (people seem to recommend a Sonoff model instead), but it has the advantage of being supported by Nabu Casa – the creators of Home Assistant. And then there’s the choice between ZHA and some other competing approaches… let’s not go into that here.

A couple more things…

A year or so ago, I wrote about using NFC tags to automate some of the routines in my house. That’s all been moved across to Home Assistant now, with the advantage that the automations are no-longer device-specific and anyone with the Home Assistant app can scan a tag.

As for the app… after an incident last summer when the garden lights turned off (on a timer) and my wife wanted to switch them back on but didn’t know how, I gave access to the app. She is pleased that she now has “the power”. I am pleased that the system is usable by non-geeks. I do need to learn how to create Home Assistant dashboards though, because the list of connected devices and entities is getting quite extensive.

I still can’t get my family to stop turning off the lights at the switch though… so I need to find some UK-compatible Zigbee smart switches that will be acceptable for use!

Featured image by Gerd Altmann from Pixabay.

Using NFC tags to automate my home

This content is 2 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Imagine a home with a smart thermostat to control the heating, smart lights to control the lighting, and smart sockets to control other electrical devices. Well, for some people, that doesn’t require a lot of imagination – it’s just the way things are!

My home isn’t quite like that. We still have an analogue thermostat switch on the hall wall (one day we might upgrade) but there are various smart sockets around and we do have some smart lighting. The smart sockets control things like the heater in my Man Cave, the Christmas tree lights (mid December-January 6th only) or the fairy lights in the garden. And I wrote some posts about the smart lights, in this two part series in 2021:

NFC tags

Many of us are familiar with Near Field Communication (NFC), even if we don’t know it. It’s the technology used in contactless payment cards. To learn more, I thoroughly recommend watching Professor Hannah Fry‘s Secret Genius of Modern Life TV episode about the bank card, on BBC iPlayer.

And those smartphones we carry everywhere with us, well, if they are NFC-enabled, they can read NFC tags to perform other operations. It’s not just for making electronic payments!

All you need is to buy some tags and, as much as I try to avoid the big online marketplace that sells everything from A to Z, that’s where I picked mine up.

What follows is for iOS, as my family are all iPhone users (tested on 17.2.1). Android users can do similar things, but you’ll use a different app.

Shortcuts and automations

The iOS Shortcuts app has a section called Automation.

  1. Click + to create a new automation.
  2. Scroll down to NFC.
  3. Click Scan and scan your tag, then name it.
  4. Pick when to run the automation (immediately, or after confirmation) and whether to be notified.
  5. Select what the automation will do.

That’s it. Just touch the top of the iPhone to the tag and it will run your automation. Stick it to the desk, the wall, or wherever is handy to run the automation.

Things I discovered

In this experiment, I did find out a few things…

  • I should have bought tags with sticky pads. Or maybe not – a glue stick seems to work pretty well for attaching them to things.
  • They don’t seem to work on metal things (like my desk lamp, or the metal switch sockets in the Man Cave). I guess it interferes with the signal, so you’ll need to stick them nearby.
  • The iOS Shortcuts app will integrate with many applications, but not directly with Alexa, it seems. I have tested a couple of workarounds though:
    • Play a recording that issues the Alexa command.
    • More elegantly, use the scripting option to Open the Alexa app, wait a second, speak “Alexa”, speak the Alexa command.
  • You can also create quite advanced no-code scripts to launch menus and ask for input – for example scan the same tag and ask whether to turn on the device or turn it off, then take action accordingly.

There’s more in this thread on Twitter/X…

Conclusion

NFC tags are cheap (especially when bought in bulk) and an effective way to automate tasks around the home (or at work, in the car, or wherever). There’s lots more that you can do with NFC tags and YouTube is full of videos to provide inspiration. Have fun!

Featured image from the Computer Science Wiki, used under a Creative Commons Attribution-NonCommercial-ShareAlike licence.

Smart lighting: Part 2 (adding Innr and IKEA Trådfri bulbs to my Philips Hue installation)

This content is 5 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

My blog posts are like buses. You wait years for one to come along, and then two arrive at once. The only problem is that they are four years late.

In part 1 of this series, I wrote about getting started with Zigbee lighting, in the form of Philips Hue. Unfortunately, although it’s widely supported, Hue can be expensive so I quickly started to add compatible devices to my network. Here’s what I found.

Coloured bulbs

Whilst I use white lights in communal areas, I have some coloured lamps in some of the bedrooms and in the home offices. I also have one on the landing outside my office, which can be linked to my Teams presence information to show if I’m busy, using Isaac Levin (@isaacrlevin)’s PresenceLight solution).

Rather than shelling out £50 for a coloured Philips Hue bulb, I used Innr smart bulbs (both B22 and GU10 formats). These are also Zigbee-based but are not Apple HomeKit certified. That means that they work with the Hue app, but not natively in iOS. I decided that I can live without that (even more so since I switched to Android).

Innr supports connecting its smart bulbs to a Philips Hue bridge (but not for Hue Sync).

Low cost GU10s

I mentioned in my first post that I have some low-voltage MR16 bulbs in the house, for which I can’t find Zigbee replacements. Newer parts of the house (like the loft extension) have mains voltage GU10 fittings. For these, I used inexpensive IKEA Trådfri bulbs.

At the time, getting Trådfri working with Hue was a bit hit and miss but newer firmware seemed to improve this. The IKEA website even states that the Trådfri products can be used with Hue:

Do the IKEA smart lighting products work with the Philips Hue Bridge?

Yes, you can use the IKEA smart lighting products together with the Philips Hue Bridge.

How do I connect my IKEA smart lighting products to a Philips Hue Bridge?

If the software version of your IKEA smart lighting products is 1.2.x or later, you can connect them directly to a Philips Hue Bridge. Simply follow these steps: – First, make sure that the light sources that you want to connect have an updated software version (1.2.x or later).

– Keep the light sources close to the Philips Hue Bridge.

– Search for new devices with the Philips Hue app.

– Do a factory reset of the light sources by toggling the main switch six times.

[…] If the software version of your products is not 1.2.x or later, you need to update it by using a TRÅDFRI gateway and the IKEA Home smart app.”

IKEA Smart Lighting product support

A few things I found:

  1. Trådfri bulbs do seem to need to be physically close to the Hue Bridge in order to pair (as noted above).
  2. Some early firmware versions didn’t work so well with non-IKEA gateways (as noted above). I’ve had no real issues with my 2017 Week 44/46 and 2018 week 01 bulbs. You can find the version number on the packaging before purchase. According to the Hue software, these are all running software version 1.2.214.
  3. I couldn’t make IKEA Trådfri accessories (switches, etc.) work with the bulbs whilst the bulbs were paired with Hue. Your mileage may vary. I returned my Trådfri gateway to the store.
  4. Sometimes, the Trådfri bulbs will stop responding (remain on or off, regardless of control). This can usually be fixed by removing them from their fitting and then reconnecting them (basically rebooting the bulb). Later firmware may help.

Mixed messages

One side effect of the mixed system is that the Philips Hue software can only update its own equipment. It recognises the other equipment and will even tell me the software versions but updates would need the corresponding Innr or IKEA gateways and apps to be used. That’s a cost and level of complexity that I decided to manage without.

Software update in the Philips Hue app (Hue bulbs)
Software update in the Philips Hue app (Ikea Trådfri bulbs)
Software update in the Philips Hue app (Innr smart bulbs)

Smart Assistants

I mentioned that my cheaper bulbs are not compatible with Apple HomeKit, but I’ve had no problems working with Amazon Alexa via the Philips Hue skill. In truth, my home automation is a rats nest of Samsung SmartThings, TP-Link Kasa, SmartLife, Apple HomeKit and Amazon Alexa. I really need to look at sorting that out (maybe with Home Assistant). Watch out for a future blog post… hopefully it won’t be four years in the making).

Wrap-up

My experience with Zigbee smart bulbs from a variety of manufacturers has largely been positive. I still occasionally ask Alexa to turn on a light and find it doesn’t work because someone has switched off the circuit but that’s what us IT folks refer to as a “layer 8 problem” or an issue with the “wetware”. Whilst mixing manufacturers may present some challenges with updates, a Hue hub at the centre of a mixed network seems to work pretty well for me. After all, the likelihood of someone hacking my unpatched IKEA lightbulbs seems pretty minimal…

Acknowledgements

Featured image by soynanii from Pixabay.

Smart lighting: Part 1 (getting started with Philips Hue/Zigbee)

This content is 5 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Earlier today, I spotted a tweet from Karan Chadda (@kchadda) that reminded me of an unfinished blog post from 2017…

So, here’s part one of the story that never got posted…

A new Hue

Around four years ago, I began an experiment. Hot on the heels of success with a Wi-Fi activated smart socket (a TP Link HS-110), I thought I’d expand on my home’s Internet of Things (IoT) credentials with some smart lighting.

I should explain that my house is a fairly typical UK house: a 1990s-built, detached property, with some pretty uninspiring pendant lights in most rooms. The kitchen/dining room is a little different, as it has low-voltage MR16 spotlights. These were recommended by the electrician who worked on our extension in 2009.

I did some research, and decided that I wouldn’t go down the Wi-Fi route. Not only were the bulbs expensive but it’s not a great use for Wi-Fi (and at the time my home Wi-Fi performance was pretty flaky). Instead, I went for a Zigbee-based solution, with Philips Hue at its heart.

The Hue gateway is pretty easy to set up – it just needs a wired connection to the network. Most home routers have a few of these; my setup is a little more extensive, with PowerEthernet running to my office and other locations that are away from the Internet connection but have a need for wired network connections. With a gateway in place, it was just a case of strategic lightbulb swap-outs, taking out traditional bayonet-fit (B22) bulbs and replacing them with smart equivalents.

Smart lighting, not so smart users…

At this point I should explain, all the smart technology is useless if the circuits aren’t left powered on. And this has been the major flaw in my plan. Our family is divided between the geeks (myself and my eldest son), and the “normal” tech users (my wife and my youngest son). If I was being less charitable, I might put my wife into the laggards category but, to be fair, she’s happy to adopt technology when she can see its value.

For me, part of that value was the ability to set up routines so that lights turn on/off when we’re away from the home. I also have one that turns all the lights off after everyone has gone to work/school (because physical switches appear to only work in one direction for my family – they can all turn lights on, but seemingly not off – I believe this is a common complaint for Fathers up and down the land, walking around houses turning lights off in empty rooms, even during daylight hours).

The biggest drawback I found was that I’ve yet to identify suitable Zigbee switches for the UK market. That means that, when the circuit is switched off (usually when leaving the house or going to bed), the lights are no longer controllable in software. On the flip side, the less-technically-inclined family members can operate the lights as normal, with the only minor inconvenience being, if the light has been turned off in software, they need to flick the switch off and on again to turn on the light “manually”.

Those in other parts of the world may have more luck – have a listen to these podcast episodes or watch some of the videos on this channel:

Form factors and accessories

Over time, I’ve expanded the system and I now have smart bulbs in the communal areas (hall, stairs, landing, etc.) as well as in the home offices and some of the bedrooms.

Unfortunately, there are no suitable MR16 Hue-compatible bulbs, so the rooms with those lights still have traditional halogen (for dimmer-controlled rooms) or LED spotlights. I’ve also stuck with “normal” bulbs in the bathrooms.

I’ve added a Hue sensor in the garage storeroom (so the light comes on when we open the door) and a couple of Hue dimmers, one of which has moved between various rooms over the last couple of years but is currently in our loft room. For the dimmer, I bought a Samotech adapter that covers the original light switch (left switched on), whilst still allowing the Hue dimmer to attach magnetically.

Samotech adapter in use with a Philips Hue dimmer and a standard UK light switch

The verdict?

All in all, things are working well. After nearly four years I’ve only had one failed bulb (replaced under warranty after about a year). The Philips Hue system seems to be a widely supported platform, with plenty of integrations (e.g. to smart home assistants) and the use of third-party bulbs in places has helped me to keep costs down to a reasonable level (I’ll write about these in my next post).

Acknowledgements

Featured image by HeikoAL from Pixabay.