Towards the end of my recent trip to Pas de la Casa I realised that I was missing the telemetry I’d got from the Valnord App whilst skiing in Arinsal. A quick search suggested that the Ski Tracks app would be a good purchase for my iPhone and Apple Watch, so this is a reflection on the single day that I used it so far.

It worked pretty much as expected

As I got booted up before the first lift I set the app in motion from my Apple Watch (Series 2), and as I glanced at it after a few runs it seemed to be recording runs as expected.

When I got to the end of the day and looked at the phone app I was surprised to see nothing there, but then it imported the days runs presenting an overview:

a chart of speed and altitude:

and a breakdown of individual runs:

Faster earlier?

I was pleased that my day had been recorded, but a bit miffed about some inconsistency. When I looked at my watch after run 13, which had been a clear blast down Obagot III it had read 122.6km/h (76.2mph), so how did that become 64.3mph?

I now wish I’d done a screen grab of my Apple watch.

Health Tracking

One of the main things I use my Apple Watch for is health tracking, and I’d been surprised how little activity got clocked up in my first few days. The watch was barely registering the hike from the hotel to the lifts and back.

Using Ski Tracks seems to have massively over-corrected things:


It seems that every minute I had the app running counted as exercise (even when it knows I was stood standing for lifts or sat on them); and I’d clocked up a whopping 1700+ move calories – I should have felt much hungrier by the end of that day :0

Hopefully this stuff will get fixed in an update. I’d like my actual ski time to count as movement and exercise, but not all the waiting around for lifts etc.

It didn’t run down my batteries

A big promise for this app was to not run down batteries (which can happen quickly when GPS is used all the time), and it kept good to that promise. My watch battery seemed to go a little quicker than usual, but my phone was still at around 60% at the end of the day skiing.

The group that I’ve been skiing with for the past few years wasn’t coming together this year due to some health issues and other commitments, so my daughter and I chose to return to Pas de la Casa, which we last visited three years ago (on the proviso that we could return to Hotel Les Truites, which fortunately still had space).

Getting there and back

I planned flights around the Andbus transfers arranged via Unfortunately fog at Gatwick significantly delayed our departure, but thankfully the Andorra Resorts team were very responsive and rebooked us onto a later bus (though this turned out to be news to the driver, and we just made it onto the last two available seats on a packed bus). The trip back was also made fraught by protests for Catalan independence (though luckily I’d allowed stacks of time, which I’d planned on spending in the T2 lounge at Barcelona Airport – though sadly it’s been closed for months for ‘improvement works‘).

The length of time spent on transfers (which essentially becomes a whole day getting there, and another getting back) are probably the main thing that would put me off returning to Andorra.

The skiing

Without such a large group getting around the Grandvalira area was pretty easy, and we spent a lot more time over in El Tarter and Soldeu, though the ‘funnel lift’ as we came to call ‘Cubil’ remained a significant and annoying bottleneck between one side of the area and the other. They really need something with more capacity at that point in the network.

With half term holidaymakers from the UK and France the entire area was busy, and though we found a handful of quiet lifts, all the primary routes were pretty choked up. I also can’t remember being on a trip where lifts stopped quite so frequently for bozos who can’t sit down and stand up again without falling over or some other buffoonery.

All 5 days that we skied were beautifully sunny, so there was no fresh snow. The piste was good throughout at the start of each day, though things got a little piled up and soggy by the end of the day. Our last day saw some of the runs we wanted to do closed.


Having had a decent experience with Skiset last year in Austria I used them again this time and got a voucher for Surf Evasio 1. My plan to pick up gear on our day of arrival was thwarted by the delays, but when we pitched up on Saturday morning the place was busy but not too busy, and they did have stuff ready for us[1].

For boots they used a 3D scanning machine for fit, and the boots I got (Nordica brand) were the most comfortable I’ve ever had.

The ‘excellence’ skis they gave me were Head Supershape i.Magnum, and I didn’t get along with them. The bases were pretty scratched up, so they didn’t glide; and everything felt like hard work. So I took the shop up on their offer to swap, and when asked what I wanted different the answer was simply ‘faster’. They gave me some Nordica Dobermann SLC skis that were absolutely brilliant. Their target user profile of ‘groomed, expert, short turn, high speed’ suited me perfectly. I’d say it’s a close call between these and the Lecroix Mach Carbons I had on my last trip to Pas for best skis I’ve ever had.

My daughter was very happy with the Roxy Dreamcatcher 78s that she got (which were definitely faster than the Heads I wore on day one, but a little slower than the Nordicas I switched to).


Restaurant La Familia had been great last time, so we took the easy option (as it’s just downstairs from the hotel) and dined there again on our second and final nights. It’s now rated #1 restaurant in Pas, which I think is well deserved. On arrival we grabbed take away pizza from Oh Burger Lounge, which was good enough for us to return a couple of days later for the dining in experience.

A chance stop at the Hotel Nordic restaurant in El Tarter led to us returning there for three days in a row. The tapas portions are huge, tasty, and surprisingly inexpensive for a place that seems so posh. Having seen the salmon and avocado salad I had to go back to try it; and my daughter insisted on returning again the following day (it helped that she loved the run down Aliga). The hotel also has great WiFi.


A bit like returning to your old school, Pas (and Grandvalira) felt smaller, though there was still plenty of fun to be had. I left last time feeling like there was more to explore, whilst I left this time feeling like I’d exhausted the place. If I go back to Andorra I’d like to try Arcalis, though it doesn’t look like there’s enough there for a whole week.


[1] For some weird reason they’d prepared a snowboard for me rather than skiis, but as soon as the mistake was recognised they sorted things out, and the service was very friendly. I was less impressed that they somehow managed to give my daughter different sized boots (which we realised when one of them wouldn’t fit the bindings), but that mistake was also sorted quickly and efficiently.

Life with a better Outlook

People frequently send me ‘invites’ with attached Internet Calendaring and Scheduling (.ics) files. This is problematic, as I don’t use (fat client) Outlook, and web/mobile Outlook might be able to open those files (sometimes), but can’t do anything useful with them[1].

To make matters worse, it’s pretty common for the ‘invite’ to say nothing about when the event is happening. It’s a secret. Open the .ics attachment and all will be revealed.

Still using letterhead

This as a subset of a larger problem where people wrap a few lines of text that could so easily just go into an email into a PDF, Word doc, Excel spreadsheet or whatever; which completely fails the keep it simple, stupid (KISS) test. It’s also an accessibility issue, and a potential security issue – making people open other apps (that they may not have, or might have difficulty using) so that those apps can read attachments that could be carrying any manner of malware.

My kids’ school is one of the worst perpetrators. They’ll happily send a PDF that has a single line of content. Often something completely mundane like, ‘please log onto section blah of the parent portal (for the actual info we’re trying to convey)’.

I suspect that in their case (and many others) it’s a failure to adapt to ‘digital’. They may crow about kids using iPads in their classes[2], but I suspect that their approval workflow is much the same as when everything went to the headmaster’s secretary to be manually typed onto school letterhead.

Email overload is a modern disease, and much of the ‘digital’ conversation these days goes on about shinny new tools that are supposed to eliminate email (and it seems any free RAM you might have had on whatever you’re using). But attachments make overload worse rather than better, as they introduce more friction into reading email.

You can help by…

If you’re asking somebody to come along to an event, for sure add an .ics file in case it might be useful. But make sure to say (in the subject line) when it’s happening, so it’s not obligatory to open that attachment.

More generally a good rule of thumb might be that anything that fits onto a page or less shouldn’t be an attachment – just put the text into the body of the email. Hooray – you’re now a digital native.


[1] Let’s not go down the rabbit hole of incompatibility between the worlds of Microsoft, Google and Apple when it comes to invites.
[2] The iPad fad was in fact short lived, and they soon switched (back) to laptops.

‘Filter failure at the outrage factory’ is a term I’ve been using on Twitter[1], usually as part of a quote tweet for something describing the latest social media catalysed atrocity, but I thought it deserved a longer form explanation, hence this post.

I fear that I buried the lede in a note when I first published this. But the core point is that Rule 34 (if it exists there is porn for it on the Internet) is being weaponised against the general population. The people out past (what should be) the 5th standard deviation are very into their peculiar peccadilloes, and that looks like ‘engagement’ to the algorithms.

The Outrage Factory

This is a label I’m going to smear across the entire advertising funded web, but the nexus of the issue is where traditional media and its previously trusted brands intersects with social media. The old sources of funding (subscriptions and classifieds) dried up, and that drove media companies into the arms of online advertisers, which quickly became a race to the bottom for our attention. Click bait headlines, fake news, outrage – they all get attention. Facebook, and YouTube and all the rest run off algorithms that finds the stuff that grabs and holds our attention, and those algorithms have discovered that outrage == $$$. Unfortunately those algorithms don’t care whether the material they hype is based on truth or some conspiracy theory nonsense or just an outright falsehood.

Filter Failure

Clay Shirky famously said [2] “It’s not information overload. It’s filter failure.” when describing how we could deal with the fire hoses of information the Internet can throw at us. At the time (2008) we were seeing the beginning of a shift from hand selected filters such as the RSS feeds one might subscribe to in Google Reader to ‘collaborative filters’ where we started to use the links posted by friends, colleagues and trusted strangers on Facebook and Twitter. Notably those were the days before algorithmic feeds.

The problem that developed from there is that where we thought we were handing curation over to our ‘friends’ we ended up handing curation over to the attention economy[3]. JP Rangaswami laid out Seven Principles for filtering, and it seems what we have today fails on all counts – we lost control.

Why care?

We should care because our democracy is being subverted. The checks and balances that worked in the world of print, radio and TV have proven utterly ineffective, and bad actors like the Internet Research Agency (IRA) are rampantly exploiting this to undermine our society[4].

We should care because dipshit stuff like the anti-vax movement that used to be consigned to wingnuts on the fringe of society has been sucked into the mainstream to the extent that it’s ruining herd immunity and we’re having life threatening and life changing outbreaks of completely preventable diseases.

We should care because algorithmically generated garbage is polluting the minds of a whole generation of kids growing up with iPads and Kindles as their pacifiers.

We should care because our kids are finding themselves a click or two away from Nazi propaganda, the Incel subculture, and all manner of other stuff that should be found somewhere out past the 5th standard deviation in any properly functioning society rather than being pushed into the mainstream.

We should care because this is the information age equivalent of the Bhopal disaster, and the Exxon Valdez, and the Great Molasses Flood, where toxic waste is leaking out and poisoning us all.

What can we do?

We don’t have to play along and sell our attention cheaply.

A wise friend once tweeted ‘I predict that in the future, “luxury” will be defined primarily by the lack of advertisements’. So upgrade your life to a life of luxury. Leave (or at least uninstall) Facebook. Install an ad blocker. Curate you own sources of information on something like Feedly.


[1] About not amplifying outrage, listening at scale, outrage amplification as part of the system design, and recommendation engines pushing anti-vax onto new parents
[2] “It’s Not Information Overload. It’s Filter Failure.” Video, Clay Shirky at Web 2.0 Expo NY, Sept. 16–19, 2008.
[3] Aka ‘surveillance capitalism
[4] Renée DiResta‘s Information War podcast with Sam Harris is a good place to start, and then maybe move on to The Digital Maginot Line.

Skills development and training is a huge part of driving an organisation forward into the future, and so it’s something that I spend a lot of time and energy on. I’ve seen a bunch of stuff over the past year that leads me to expect a revolution in training.


I first came across Katacoda at RedMonk‘s Monkigras conference a couple of years ago when Luke Marsden showed me the Tutorials he’d been building; and I immediately fell in love with the openness and interactivity of the platform. I’d seen training before that simulated a real world environment, but nothing that provided an authentic on demand experience[1].

I spent the following months creating what became ‘DevOps Dojo White Belt’ taking the ‘Infrastructure as Code Boot Camp’ materials we’d used for in person workshops and making it into something that could scale a lot better[2].

It was much more recently that I saw the full potential of Katacoda realised. The team that created our ‘DevOps Dojo Yellow Belt’ incorporated Continuous Integration and Continuous Delivery (CI/CD) pipelines in such a way that we could test whether students were achieving specific outcomes.


After attending a Google Cloud Derby hosted by Ant Stanley under the auspices of the London Serverless Meetup I was sent an invite to some Google Cloud Platform (GCP) training on the Qwiklabs platform (that was recently acquired by Google).

Specifically I was invited to do the GCP Architecture Challenge, which turned out to be like no training I’d ever done before. As explained in the ‘quest’ intro: ‘Challenge Labs do not provide the “cookbook” steps, but require solutions to be built with minimal guidance’…’All labs have activity tracking and in order to earn this badge you must score 100% in each lab.’

I found it was like doing an escape room. Each lab would describe an outcome that needed to be achieved, and it was up to me to figure out how to do that (using the tools provided), against the clock. Perhaps I should have done some training first, but it was really fun to learn stuff on the fly, solve the puzzle, and escape from the room lab before the clock ran down.

Open book (it’s OK to use Google and Stack Overflow)

The emergent point here is that students shouldn’t expect to be spoon fed every minute detail – they’re expected to go and read the docs, dive into Stack Overflow, search for answers on Google and in GitHub, maybe even watch some YouTube primers. Real life is an open book test, so training should reflect that.


I saw this outcome oriented theme continue when a colleague pointed me towards Exercism yesterday. It provides training for a wide variety of programming (and scripting) languages with a common underpinning that it’s all based on tests. Just like with test driven development (TDD) you write code to pass the test suite. This results in a stunning variety of working results that can be seen from other people’s submissions, which are worth reviewing to discover everything from language idioms to significant performance improvements. Students can edit the tests too, adding things that might have been missed. It’s a really neat way of learning a language and at the same time getting into the discipline of TDD.

Codecademy, Microsoft Learn and The Hard Way

I can’t finish without a nod to these:

I started using Codecademy when it first launched, and put up with the early wrinkles because it was so beautifully immersive. I was lured back in the past week by their Learn Vue.js course (after seeing Sarah Drasner showing off the potential of Vue.js in her Servless Days London talk[3]), and it was great (the course and Vue.js) – though I can’t say I’m keen on the cost of their ‘Pro’ subscription model.

When I saw Microsoft launch Learn at Ignite 2018[4] my first take was ‘they’ve totally ripped off Katacoda’, but that was quickly followed by being seriously impressed at how well they’ve incorporated on demand subscriptions for the underlying Azure services it provides training for. There’s some seriously good introductory material there, and I hope over time they’ll close the gap to meet up with Azure certifications.

The Hard Way‘ isn’t so much a platform as a methodology designed to get ‘muscle memory’ into students, and show them the essential details that often gets buried under layers of abstraction (but matters when things fall apart). I first came across it with Kelsey Hightower‘s Kubernetes The Hard Way, and got pulled deeper with Ian Miell‘s Learn Git/Bash/Terraform The Hard Way, though it’s worth noting that it all started with Zed A. Shaw.


The future of IT training is interactive and outcome oriented. Rather than being spoon fed a particular way to do something we can expect to be given open platforms that allow experimentation (and provide a safe place to try things out), and open challenges that test our ability to solve problems with the entire resources of the Internet at our hands (just like when we’re putting knowledge to use at work). If we want people to use TDD and build CD pipelines, then it should be no surprise that those same tests and pipelines can form an essential part of their skills development. The good part is that this unleashes unlimited creativity, because people can figure out their own way to achieve an outcome; and approaches can be compared with peers and mentors to discover how things might be improved. It’s a long way from passively sitting in a classroom, or watching a video.


[1] For me the best demo of Katacoda is the 10 minute beginner level ‘Get Started with Istio and Kubernetes‘ – there’s just so much packed into it.
[2] At the time of writing over 10,000 DXCers have done the White Belt.
[3] I can’t find a recording of that talk, but her VueConf.US talk ‘Serverless Functions and Vue.js‘ seems pretty similar.
[4] I wasn’t actually at Ignite (I’ve never been) – it just seems to me that Learn is by far the most important thing that came out of the 2018 event.


Getting a Midas Plus squirting properly again is very easy once you learn the secret of removing and cleaning the thermostatic cartridge. A simple procedure due to some great design, but one that isn’t documented anywhere that I could find.


In just over a year since I had a new shower fitted as part of an en-suite refurb it went from ‘Oh yeah!’ to ‘meh’. I’ve had Aqualisa showers at home for over 20 years, which I guess makes me a loyal customer, but in that time I’ve needed a few replacement thermostatic cartridges – generally because the flow rate has become a bit useless.

Checking filters

The trouble shooting guide in the installation instructions suggests three possible causes for poor flow rate – twisted hose, debris in shower head, and debris in filters, with ‘check and clear as necessary’ as the action to take. I knew it wasn’t the first two, as flow was fine if I turned the thermostat to cold. So I set about checking the filters, which meant taking the mixer bar off its mount.

  • First I turned off the water supply
  • Then I taped over the fixing nuts with electrical tape (as they’re shiny stainless steel, and I didn’t want to scratch them with my dirty old adjustable spanner [they’re 29mm, and I don’t have a regular spanner that big])
  • After loosening the nuts I was able to pull the mixer bar away and remove the filters. The cold filter was clear, but the hot filter did have quite a large crystal deposit in it, which I rinsed off with a jug of water.

All of this made absolutely no difference. The shower flow rate was still poor.

The cartridge

I called the Aqualisa support team for help, and after talking through the problem they offered to send me a replacement thermostatic cartridge. This led to a follow on question from me about how to fit it once it arrived? The support person said to follow the installation guide, but I’d already been through that, and it makes no mention at all of cartridge removal and replacement. She then told me to start by taking the end cap off the control. When I went and tried that I soon discovered that isn’t how to get the cartridge out.

Picture of cartridge from Aqualisa website

I then did what I perhaps should have done in the first place. I took to YouTube, and found this video ‘Thermostatic cartridge: maintenance, replacement and calibration‘, which showed me that the cartridge is held in by a (very well hidden) grub screw on the bottom of the mixer bar. All I had to do was:

  • Turn off the water supply (IMPORTANT – the water on/off on the left hand side of the bar simply acts on the cartridge, so if you take it out without isolating the supply first the cartridge will fly out and then water will gush from the mixer bar).
  • Undo the grub screw on the bottom right hand side of the mixer bar with a 3mm hex bit
  • Pull the cartridge out
  • Rinse away any debris using a jug of water

    Other side of cartridge showing where grub screw fits

Once I popped the cartridge back in the shower was as good as new.

Crucially there was no need to remove the end cap and mess around with the thermostatic calibration.

I have questions

Once you know where the grub screw is, the simplicity of removing and refitting the cartridge stands out as a wonderful piece of design. Somebody thought very hard about how to make this as easy as possible; and then somebody else decided to exclude any mention of the grub screw and the cartridge from the instructions. Given that in the past Aqualisa have provided detailed instructions for the much more complex process for removal and refitting of earlier designs it seems really odd that they managed to make everything so much better, then chose to keep the details to themselves. This must result in a higher than needed support burden, and associated drag on profitability, which I find utterly bizarre.

Also the filters on the cartridge itself are (by my estimation) finer than the main inlet filters. So ‘check and clear’ for the filters should definitely mean both the inlet filters and the filters around the cartridge itself. Again I’m guessing that’s by (very good) design, and then somewhere else a decision has been made to withhold crucial information :/


Cloudflare recently announced two additional capabilities for their “serverless” Workers: support for WebAssembly as an alternative to JavaScript, and a key-value store called Workers KV. WebAssembly will allow Workers to be written in compiled languages such as C, C++, Rust and Go. Workers KV provides an eventually consistent state storage mechanism hosted across Cloudflare’s global network of over 150 data centres.

Continue reading the full story at InfoQ.

This is one of those posts that started life on an email thread. It comes from a discussion on the topic of multi cloud governance for large enterprises.

Why cloud?

The answer is not ‘cloud is cheaper’, because it just isn’t. We know from Amazon’s financials that it’s gushing money because cloud is a high margin and very profitable business. Any halfway competent large enterprise can run its own data centres cheaper, and the mainframe and midrange legacy isn’t going anywhere so neither are those data centres.

The answer is ‘cloud is faster’. Cloud enables quicker delivery of value in response to changing user needs. ‘Digital’ is built out of continuous delivery (CD) pipelines, and CD pipelines need cloud at the end of them, because you can’t do continuous delivery without API enabled on demand infrastructure (which is lots of words for ‘a cloud’).

What kind of cloud?

Having focused our attention on the right category – applications that deliver outcomes more quickly by constructing CD pipelines – we finally come to the vexed question of what type of services do they want to consume? Is it IaaS, CaaS, FaaS (or some combination)?

Safety First

The crucial outcome is safety[1]. The app developers need to be able to consume services without crossing lines with respect to security and compliance.

Safety costs money (but far less than unsafe practices) so we end up at a cost/benefit trade off. For every class of services that consumed how much does it cost to make them safe, and what benefit is accrued (in speed to market and revenue achieved from that)? This doesn’t just apply to which cloud will be used (AWS vs Azure vs Google); it also applies at a finer grained level to which services are consumed within those clouds.

Control vs Productivity

Most large enterprises are looking down the wrong end of the telescope. They’re thinking about control before productivity rather than productivity before control; and that pattern is borne from the traditional enterprise mindset of standardisation to reduce complexity and cost.

Many enterprises feel like they have these options:

  1. Make the complexity appear to go away by putting a unifying broker layer between the cloud and its consumer.
  2. Accept that there will be multiple data centres and cloud providers and use some sort of common technology (e.g. containers) to enable common approaches to application development and deployment.
  3. Some combination of (1) and (2) where elements of the infrastructure and operations are treated in a common way (e.g. billing, operational data, software delivery).

None of them are good, because all of them presuppose that we make an activity safe before we even know what the activity is. It’s a great way of spending time and treasure on something that never delivers any practical value[2].

Getting to the cost/benefit trade off

This means actually knowing the cost, and actually being able to figure out the benefit. A managed cloud service with safety built in (like you get from a services company rather than the raw cloud underneath it) will show a sticker price for cost – so we’re half way there. The other half naturally extends into the enterprise’s own investment appraisal processes (and there’s room for services companies to be facilitators for the extra work needed there).

In the end it doesn’t matter whether they use one cloud or five. Whether they use containers, functions or VMs. It only matters that engineers are safe, and the overhead of achieving that safety is part of the broader business case for the functionality.

The final issue is the classic ‘buy the restaurant to eat the first meal’ problem that so often comes up with large enterprises, where any given app can’t make the business case stand up on its own. That takes us to a portfolio management exercise where the investment in safety for a category of apps with common needs gets justified by the expected benefits of all those apps (and the apps that might follow them). So there’s a need for some degree of aggregation. What happens next is essentially paving the cow paths – early success becomes the path of least resistance for things that follow (so that they don’t have to make fresh cases for their own new safety demands).

What this brings us to is the ability to say to application developers ‘you can have anything you want provided that you can afford the safety’, ‘you may club together to pay for safety’. That leads to an initial cohort of apps that make something happen within the confines of a given set of safety systems. It’s easy to follow them, because the safety investment has already been paid down. Apps can choose not to follow, but that choice comes with the consequence that they need to stand up their own safety and pay the premium.

They key point is ‘they come and we build it’ rather than ‘build it and they shall come’.


[1] I’ve written about safety (first) before.
[2] For more on why brokers are considered an anitpattern take a look at Barclays’ Infrastructure CTO Keiran Broadfoot in his 2017 re:Invent presentation.

Our expectations for user experience are shaped by the huge consumer platforms such as Google, Apple, Facebook and Amazon, and also the devices that we access them with such as iPhones, iPads, Android phones and tablets, and the PCs or Macs we use at home.

When we use these consumer devices and services, there’s no help desk for issues that come up, but in general there’s also no need for a help desk because the devices “just work.” That’s the type of user experience organisations strive for on their journey to digital.

head to the full piece to continue reading


My hardware and software setup for my Raspberry Pi sous vide setup have remained the same for over 5 years, but a failed remote controlled socket forced me to update almost everything.


The Maplin remote control socket would turn on, and briefly supply power to the slow cooker, but then it would appear to trip. This wasn’t the first time, as the original socket failed after a few years, but this time there’s no chance of getting a replacement from Maplin as they’ve gone out of business.


After a bit of hunting around I tried ordering a Lloytron A1210WH socket set, as it looked identical to the Maplin one (and hence was likely to have come from the same original equipment manufacturer), but the package I received had the newer model A1211WH.


I could have returned them in the hope of getting some of the older ones from elsewhere, but I decided to bite the bullet and just make things work with the new ones.

Blind Alley

I had a go at using 433Utils, which was able to read different codes from the new remote with RFSniffer, but sending those codes using codesend just didn’t work (and didn’t even show the same code being played back on RFsniffer).


How I Automated My Home Fan with Raspberry Pi 3, RF Transmitter and HomeBridge had a similar issue with 433Utils, and used pilight to read codes from his remote then send them out from a Pi controlled transmitter.

Here began a bit of a struggle to get things working. My ancient Raspbian didn’t have dependencies needed by pilight, so I burned a new SD card with Raspbian Stretch Lite (and then enabled WiFi and SSH for headless access).

My initial attempts to use pilight-debug crashed on the rocks of missing config:

pilight no gpio-platform configured

In retrospect the error message was pretty meaningful, but Google didn’t help much with solutions, and all of the (pre version 8) example configs I’d seen didn’t have the crucial line for:

gpio-platform: "raspberrypi1b1"

That raspberry version maps to the options for the WiringX platform that sits within pilight.

With the config.json sorted for my setup (GPIO 0 to transmitter, and GPIO 7 to receiver [as a temporary replacement for the 1Wire temperature sensor]) I was able to capture button presses from the remote control. It quickly became apparent that there was no consistency between captures, and I’m guessing the timing circuits just aren’t that accurate. But the patterns of long(er) pulses to short(er) pulses were consistent, so I extracted codes that were a mixture of 1200us, 600us and a 7000us stop bit (gist with caps, my simplification, and generated commands).


With timings in hand I was able to turn the new sockets on and off with pilight-send commands in shell scripts for on and off. It was then just a question of updating my control script to invoke those rather than the previous strogonanoff scripts (having migrated my entire sousvide directory from old SD to new via a jump box with a bit of tar and scp).