Adding trailer hitch and wiring on the 2017 Volkswagen E-Golf


After getting my new E-Golf, I’ve been searching far and wide for suggestions on a good trailer hitch. Initially I wanted it for mounting a bike/ski rack, but after some more thinking and research I wanted the wiring too, just in case.

I have to say information was scarce at best, most likely because the manual states clearly that no towing should be attempted with the E-Golf for whatever reason. So, in true Canadian fashion, I went ahead and started doing some research.

In terms of hitch I found that Curt hitches seem to be very popular, among MK7 owners anyway. I was not entirely sure which one would fit perfectly so I proceeded to lift the car and take a look underneath to see what mounting options I have. Here is a picture of what the undercarriage looks like behind the rear bumper.

E-Golf under body - Rear

I confirmed this way that what I was looking for was Curt 11412 Class 1 Trailer Hitch. The mounting points seemed to align and some suggestions pointed to the same part number. Notice the orange high voltage conduits. I heard that in some situations with other E-Golf owners these cables were too close for comfort to the mounting points, but in my case it turned out that they are quite far away.

Curt Hitch 11412 Golf MK7

In terms of pricing, the best deal I could find was on Amazon for $122. The hitch itself is very well build and appears to be quite good quality. Initially I thought that it may not clear the lower part of the rear bumper but it turned out to be perfectly sized to come out exactly near the edge of the bumper. The package arrived in a matter of days and here’s what’s included:

Curt 11412 package contents

Basically all necessary components to mount it, including the vital fish wires for the four bolts. There are a few very good videos on YouTube that show how to install it, but all in all, it’s quite easy and straightforward. Having somebody holding the bar up while securing it would help but it’s easily done by one person too, if in a comfortable position under the car. The basic steps are:

  1. Attach fishing wire to all four bolts
  2. Add each square hole spacer on the bolt
  3. Fish two of the bolts into the smaller opening in the frame by inserting them first through the larger opening (See fist picture above). Use the smaller holes closer to the rear of the car not the ones towards the front of the car.
  4. Insert remaining two bolts in the larger holes and use the square hole spacers to hold the bolts in place
  5. Mount the hitch bar
  6. Screw in and torque to specifications (110 ft/lbs)

Here are some shots during the install:


Package contents
« 1 of 13 »


It took about 30 minutes in total out of which I probably spent half of that fishing the wires. I had some trouble convincing the bolts through the large opening but with a little bit of patience and a large hammer they submitted to my will. (Just kidding about the hammer)

And here is the finished product. Apologies for the cleanliness (or lack of) of the car. That day rained hard and I was looking forward to installing the hitch. No time and frankly pointless to take the car to the wash.

Curt 11412 HitchCurt 11412 Hitch
Curt 11412 HitchCurt 11412 Hitch









Trailer wiring

As I mentioned before information on the E-Golf tail lights wiring was quite scarce at the time of writing. I had a vague idea of what type of wiring I was dealing with but not with 100% certainty. Since Curt had a somewhat universal kit for tapping into the existing wiring, I went for it, and decided to figure out the connections later. The kit that I got is the CURT 59236 Multi-Function Taillight Converter Kit. I believe the also sell the non-powered kit, but in my case, I wanted to make sure that I don’t draw power from the main lights circuit. This means that the converter works on a completely separate power source directly from the 12V battery.

This is the kit:


It also comes with several zip ties, a fuse, snap locks, butt connectors and ring connectors for the power wire. In a nutshell, all you need to install this comes in the package. It even comes with two-sided adhesive pads to ensure that the unit will not rattle on the mounting point which is by a self tapping screw, also included.

The hardest part by far was to take off the panels in the trunk in order to run the wires and mount the unit. If you’re planning to tackle this yourself, be prepared with a lot of patience and fine motor skills. The tabs of the panels used to hold them in place are very fragile and can break easily, not to mention that the metal clips can fall off in the deepest crevices of the car never to be found again and forever rattling while you drive.

This is the standard connector for the outer tail lights on the E-Golf.


A good old multi-meter told me what I couldn’t find anywhere. The three wires from the bottom:

  • Brown – Ground
  • Purple/Black – Running lights
  • Red/Black – Turn signal/ Brakes

This is on the driver side. If I remember correctly, the wires for running lights and turn signals have slightly different colors, but the are in the same positions. There is a fourth wire (white/black) to the left of the running lights wire in the middle, which has apparently the same functionality as the running lights. My guess is that one of them is for the regular lights while the other is for the side red positional lights.

I mounted the converter unit on the driver side because the longer turn signal wire they provided was for the passenger side. The location was pretty good also as there was enough room to comfortably mount the unit.


The final step was to run the power wire from the unit all the way to the battery in front. Little did I know that this turned out to be the most time-consuming and not because I wasn’t sure how to do it, but because of the time I took removing the threshold panels and fishing the wire all the way to the front driver foot well. From there I knew there was a grommet in the firewall that would put the wire right behind the 12V battery under the hood. Unfortunately I didn’t get a picture of this but thanks to Paul Barrett from DAP I knew exactly where to find it. You can see his very informative video here.

Once all was connected and cleaned up, ran a quick test with the multi-meter on the trailer connector and everything works perfectly.

Hopefully this will help other E-Golf owners a little bit in their quest to install a trailer hitch and figure out the wiring.


Home Improvement DIY: WiFi Gas Detector with Text Alerts

Hey guys, back with another little project that I’ve been fiddling with for the past week. With kids around, every parent is thinking how to make their home safer for the little ones and for everybody in general. One of the most dangerous thing in the house can be the stove and since we have a gas-powered one, I always wondered why there are no simple gas detectors that can be used around the stove, just to alert instantly that gas may be leaking.

sparkWell, that was the moment when I decided to build one of my own. Having a Particle (Spark) Photon lying around, I decided to use that as a foundation for the project. I like the fact that they are very small and cheap, and also can be flashed over the Wi-Fi. Having that settled, I needed the gas sensor and some kind of alerting system.

For the gas sensor I went for an
MQ-4 gas sensor because it can detect methane (CH4) as well as natural gas (CNG).
I found out later that it’s quite sensitive to CO2 as well, which turned out to be very useful while testing the setup. If you’re planning to use one in your projects and never used one before, remember that the gas sensogassensorrs have a burn-in time when they are powered. That is to say that the sensor needs time to warm up (anywhere between 2 and 10 minutes). This is because the actual sensor has a heating element that helps detect these gases and while that is cold, it will give erroneous readings.

Now on to the alerts. Half of the alerting system was simple, add a beeper next to the sensor which would work perfectly when somebody is around. However I still had to sort out the second half, for the cases when somebody was not in the immediate vicinity. For that I wanted to have text/SMS alerts to my phone and possibly to a buzzer_secondary phone, for example my wife’s phone. Now I realized that I should probably get one of our neighborhood FD guys phone number in there too. :)

Knowing that the Photon is not the most robust controller in terms of notifications (I know there’s the IFTTT or other alerting systems) but I wanted something small, reliable and really not depending on various 3rd parties in the cloud. So I made a small web app on my local web server that would send me specific text message when a URL is hit. Many cell carriers offer now the possibility to send somebody an email to a specific email address, and that email will be turned into an SMS and sent to the phone, so that turned out to be a good enough solution for me.

So the final sequence would be the following: gas sensor detects gas, starts beeping and at the same time triggers a URL which in turn sends an email that gets transformed by the carrier into a text message on my phone. The code that runs this will actually send an alert every 30 seconds while the gas sensor is being triggered. This way I know when the gas has dispersed. Here’s the photon firmware code:

#include “HttpClient/HttpClient.h”

TCPClient client;
//add your server address here. In my case it was a LAN address similar to
char server[] = “”;
//add your server port, usually if it’s a standard http request the port is probably 80
int port = 80;
//Initialize timer to 0
int AlertSentSecsAgo = 0;
//This is used to publish Spark events
char strTxt[40];
//Define the PIN for the gas sensor
int GasSensor = A0;
//Define the PIN for the buzzer
int Beeper = D0;
//Define how often to send text alerts
int AlertFrequency = 30;

void setup()
pinMode(Beeper, OUTPUT);
pinMode(GasSensor, INPUT);

void loop()
//I had to fine tune this value at which the alert is triggered based on some trial tests
if (analogRead(GasSensor) > 750)
//If we sent an alert more than 30 seconds ago, send another one
if (AlertSentSecsAgo >= AlertFrequency)
//Send alert every 30 seconds
AlertSentSecsAgo = 0;
sprintf(strTxt, “%u”, analogRead(GasSensor));
//Publish an event to the spark dashboard with the current value of the sensor
Spark.publish(“Gas Sensor Triggered”, strTxt);
digitalWrite(Beeper, HIGH); //Sound the buzzer
digitalWrite(Beeper, LOW); //Silence the buzzer
sprintf(strTxt, “%u”, analogRead(GasSensor));
Spark.publish(“Gas Sensor:”, strTxt);
//Make sure that the alert will be sent next time the sensor is triggered
AlertSentSecsAgo = AlertFrequency + 1;
delay(5000); //Wait 5 seconds before checking the sensor again

void sendAlert()
if (client.connect(server, port))
client.println(“GET /<your address to the text web app or service here> HTTP/1.0”);
client.print(“Host: “);
client.println(“Accept: text/html, text/plain”);

Finally, for the case I chose a wall surface-mount phone jack box. The size perfectly matched the components that I had.IMG_3404a

List of parts used in this project:

  • Particle Photon ($19 on Particle Store)
  • MQ4 Gas Sensor ($5.50 on Amazon)
  • 5V Buzzer ($3.99 on Amazon)
  • Wall mounted phone jack box ($3.00 at Home Depot)
  • Right-angle USB Mini B cable ($3.99 on Amazon)
  • Jumper wires

Here are a few pictures of the finished project.

[flagallery gid=4]



Home improvement DIY: WiFi Internet radio for your home using in-ceiling speakers

For a while now I’ve been planning to start on this little project but didn’t have either time or parts to actually see it through. Finally last week I decided to prioritize it and I can happily say that it turned out to be a very fun and engaging.

So, in short, this is about having access to thousands of free radio stations online and streaming seamlessly to a home audio system. Since this was more of a trial for me, the audio system consisted of in-ceiling speakers for the kitchen.

To start off, I planned where I would place the speakers. Not knowing yet how big they will be, all I could do was more of getting an idea how the kitchen is laid out and where most of the activities will take place. Being a new house, I did not have all the furniture in place yet. Finally I decided on having two speakers, one over the fridge/stove/sink area and
the second closer to the formal dining area. The plan for the setup was to have a device capable of streaming online audio content, speakers and possibly an amplifier in between (depending on whether the speakers had it built-in or not). With that decided, I started shopping for speakers.

The Speakers:

InCeilingAudio3I knew from the beginning that I will not use this for party style loud music but mostly ambient music or newscasts so after comparing models, specifications and prices I settled on the Polk TC80i. These are 8-inchers so they do pack a punch but my hopes were that the punch would actually go towards sound quality rather than quantity.
When they arrived I was again impressed by the Polk packaging and product quality. Very nicely packed with very much attention to protect all scratch-able surfaces. Well done Polk. The speaker specs can be found here in detail.



Another piece of the puzzle that was decided pretty early on, was the streaming device. Being quite familiar with micro-controllers and having tinkered on other projects containing bare-bone PCs and other miniaturized systems, I decided that the Raspberry PI Model B would be a perfect fit for this one. Model A would work too, but in this case I wanted to invest a bit more, in case I will re-purpose the PI in the future. At the time of writing the Model A was retailing for about $20 on whereas Model B was around $45. Still very cheap for a credit card sized computer. While at it, I also got a wireless adapter for it (it does not have wireless capabilities built-in) and a nice clear case for it. The wireless dongle was one of the most popular ones used by the PI community: the Edimax EW-7811Un 150Mbps 11n Wi-Fi USB Adapter.

When it comes to streaming software it was quite easy. A while ago I came across a DIY Internet radio forum that mentioned PI MusicBox as a good streaming source. I gave it a try and found out that it was exactly what I needed for this project. It’s extremely easy to install on the Raspberry PI on a micro SD card. Basically you need to format a micro SD, install the MusicBox image and plug it into the Raspberry PI. That’s it. The official PI MusicBox website has the detailed steps for that, so I won’t list them here.

The Amplifier:

Having the speakers and streaming device sortedInCeilingAudio10 out it was time to shop for the final piece that would tie these together. That is the amplifier. The main criteria for the amplifier was that it needs to be very small, low profile and just enough to drive the two speakers. The place where this would spend it’s amplifying days was on top of a kitchen cupboard, so a remote control was also not in the plan. I initially started looking for one that would be smart enough to detect when the audio-in connection becomes active and turn on by itself, but then I was advised that even if it’s on all the time, it makes a very small difference since the
consumption on most recent amplifiers is close to zero when not in use.
InCeilingAudio1That being said I went for the SMSL SA50 50Wx2 TDA7492 Class D Amplifier which retailed for about $65. This is a 50W continuous average power little powerhouse that has received outstanding reviews since it was released.  In my case the speakers are 8 Ohms 125W max so I realistically expect about 30W per channel to be delivered at peak levels to the speakers at a reasonable ambient volume.





InCeilingAudio17Here is a connection diagram for the entire layout


Time to start the installation. I knew from the beginning that the speakers InCeilingAudio16would be the most challenging. Not only because I had to cut these big 8-inch holes in the brand new ceiling but also because wires and studs usually don’t go well together, especially when they don’t come up at the same time. Using a good stud finder I mapped all joists inside the kitchen ceiling and based on the orientation, I chose a cupboard where I would place the amplifier and the Raspberry PI so that the wires to the speakers would run along the joists and not perpendicular. These two components are small enough to go inside the cupboard but since I have a small gap between the cupboard and the ceiling, I placed them on top, well hidden from the view. Armed with the templates that came with the speakers and the having the joists outlined, I marked the two placements for the speakers exactly in between joists.
InCeilingAudio14Making the holes was fairly easy using a drywall saw and I had them made in a matter of a minutes. After these were done, I made small holes in the ceiling on top of the cupboard very close to the wall where they would not be visible. These small holes were in line between the same set of joists between which the speakers were placed.
With a wire fishing line I ran the speaker wires from each small opening to the speaker location, connected and mounted the InCeilingAudio13speakers.

Once the speakers were connected to the amplifier, it was time to find a power source location from where to power the PI and the amplifier. The PI requires a 5V power supply and it only needs about 750mA at peak usage so I simply used an iPhone charger since it’s very small and rated for more than enough amps. The amplifier came with its own power supply, which was a bit big for my taste, but since it was hidden, I decided to keep it.


Initially I was planning to run a low profile extension cord from the counter top-level outlets through the cupboard, however, I realized that the hood fan was very close to the location so I simply added a three-way power splitter inside the hood fan and ran a cord to the top of the cupboard from there. This was hidden in a white wire conduit. Another good location is the microwave power outlet which is usually behind the microwave if you have one located at cupboard level.

After running some calibration tests, in order to set the correct volume on the amplifier, I turned the software volume in MusicBox up as much as I could where no distortion would be noticeable and considered that as the loudest volume I want to have. To my surprise the amplifier had to be turned to only about 1/3 of its full range. Why is that good? Because that means the amplifier does not need to do a lot of work to have a reasonable sound level, which in turns means less power consumption and less heating.
All in all a good and fun little project. Now I am looking to expand this setup to multiple rooms in the house.

Here are a few more pics during the installation:

[flagallery gid=3 name=”Gallery”]