We are using Jenkins to run our Ember builds.

Recently I wanted to publish the results of running ember test to Jenkins, luckily for us, most of the required functionality at the Ember side was available in ember-cli.

Ember CLI

CI=1 ember test ci --silent --r xunit | tee logs/xunit.xml

A little breakdown of what is in this command:

CI=1: This sets the environment variable CI=1, this is then later picked up by the testem test suite to make certain decisions. This can be seen in the testem.js pasted below. You can see this in the process.env.CI .

module.exports = {
  test_page: 'tests/index.html?hidepassed',
  disable_watching: true,
  launch_in_ci: [
    'Chrome'
  ],
  launch_in_dev: [
    'Chrome'
  ],
  browser_args: {
    Chrome: {
      ci: [
        // --no-sandbox is needed when running Chrome inside a container
        process.env.CI ? '--no-sandbox' : null,
        '--headless',
        '--disable-gpu',
        '--disable-dev-shm-usage',
        '--disable-software-rasterizer',
        '--mute-audio',
        '--remote-debugging-port=0',
        '--window-size=1440,900'
      ].filter(Boolean)
    }
  }
};

ember test ci, this runs ember-cli test suite, but triggers the browser_arg ci, in the testem.js above, this is the part in the Chrome key of the json.

--silent tells ember-cli to not output any warnings or other unrelated information.

--r xunit tells ember to output the test results in the xunit format.

| tee logs/xunit.xml pipes the output of ember-cli, to the file xunit.xml  in the logs directory.

Jenkins

For jenkins to understand the xml output of ember-cli, we must install a plugin. Go to manage jenkins > manage plugins and look for JUnit Plugin, enable the plugin, and restart jenkins.

Create or edit a project in Jenkins, and in your project, after changing the execute shell command to the ember test command above.

add a Post-build Action and choose for Publish JUnit test result report, and configure what is needed:

Make sure that the Test report XMLs is set to logs/*xml, this is the same path we told ember-cli above to output the results.

Now you should see the test results graph appearing in the project, and per build the Test Result with a breakdown of all the tests and the details.

Today I will show you how to expose your Home Assistant through an SSH tunnel, and keep it active with autossh. Then use an Nginx reverse proxy on your remote server combined with your own custom domain to use Home Assistant over the internet.

This can be used as an alternative for Port Forwarding on your router, and in case of a dynamic IP address, a Dynamic DNS provider like DuckDNS, DynDNS, ... And can even be used from inside a VM. Everything is self hosted and doesnt require any 3rd party services.

You can use all of Nginx' features on your remote machine in an industry standard way without affecting or having to configure anything on your Home Assistant. For example you can configure SSL certificates on your Nginx, and only need to encrypt that endpoint, as an SSH tunnel is encrypted by default.

Requirements

• Raspberry Pi with Hass.io installed (version used in this blog post is 0.78.3)
  In case you are using Hassbian, you can do it manually. In any other case, im not sure what is possible.
• A remote linux machine.
• A custom domain

1. Install autoSSH Hass.io addon

For starters you will have to install an addon, which will install all the necessary dependencies for you. This addon is a fork of the excellent addon by odinuge. The only difference being that the host network has been exposed to the autossh container.

1. In Home assistant go to Hass.io -> Add-on Store
2. In the repositories at the top add my repository: https://github.com/pjcarly/hassio-addons
3. Install the add-on HASS Tunnel
4. Start the add-on

At this point, we start the add-on for the first time, so we can extract the public key which will be generated by the container on the first run. We need that key, to authorize our access on our remote server in the next step.

Because the add-on itself hasn't been configured yet, nothing else will happen.

Refresh your addon log (on the bottom), until you see something similar like this:

starting version 3.2.4
[INFO] Setup private key
Generating public/private rsa key pair.
Your identification has been saved in /data/ssh_keys/autossh_rsa_key.
Your public key has been saved in /data/ssh_keys/autossh_rsa_key.pub.
The key fingerprint is:
SHA256:FhxM+7e2fmQt1Qgyz6TEqoHoxcFTZytYOfnjCsMpVgU root@03351470-autossh
The key's randomart image is:
+---[RSA 4096]----+
|   .Eoo==.       |
|    +o=+.+= o    |
|   o.=.o=o B . ..|
|  . = ..+o. o . o|
| . + . +S.. .  o |
|  + = ...  . .+ .|
| . . o .    oo . |
|      .    . ..  |
|           .o.   |
+----[SHA256]-----+
[INFO] public key is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDZZ9V6nb+on+nuaAU1MLPPEGm+tv6RP6if3oUQx9bFNBjMuPpytjNUjhX/CZXcIf6IB+K52SYZzNL18ADBTr0oJb4Aog70QU/+LDzX3ljxGTnZBKLBgM+CsOhUgBYw5tpiSTWlBhedKd48xXvhmJ959+2md/x1qNVWXwecNrHUHquWz3CJYcUtY9A4V4PaWz7nFpcGxyWRJaMU+iHexb3Jyf7Cly/EvPxITJ9KE2CbQoRlONF3JYXkgwrjYCa91EXTYOV/S5UR2j9y8FjlYAzmGZqDMQ0G/PzIiYSC7nprl96OdzEVNXHo6NYusRfypDWhkOQi1OEnX0MusVb4Ax34UD/Yt92Kt5zBTFJ+IZJxw5izDbdBSHfngH2orwxFgF+iFAxWmLi6d71B8JdXj/72lTtUmyu4qJBOlN8RMEZOWxmrrnJZutCHZzYqeAYnN6C6rpVpGmUZKyD/FhP1YJB2gcqg87TdH0abjgbRO59g7u7zzFEG4JZeHqzSiDeh6SwWK1VWWn/9iBE3mWvZNpQUIo8Z5F3BvnQJW16OwaHJGCoW0BEoIDrb79gsLzXwg+VYLTxAZRti6pxAPW4QVEhiwXLf6JNGHPDniJ64KnxADhI1ci4PvAQnCOXfWrB1ApdJZ+gLolcDReKyC69CMIi4oUYoWuH3QKtLfVSZRQXbSQ== root@03351470-autossh
[INFO] testing ssh connection
[INFO] listing host keys
usage: ssh-keyscan [-46cHv] [-f file] [-p port] [-T timeout] [-t type]
[INFO] command args: -M 0 -N -q -o ServerAliveInterval=20 -o ServerAliveCountMax=3 autossh@ -p 22 -i /data/ssh_keys/autossh_rsa_key -R 127.0.0.1:8123:172.17.0.1:8123 -v
		   [host | addrlist namelist] ...
OpenSSH_7.5p1-hpn14v4, LibreSSL 2.6.3
debug1: Reading configuration data /etc/ssh/ssh_config
ssh: Could not resolve hostname : Name does not resolve

From the log, copy the public key displayed below [INFO] public key is:

In this example this is:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDZZ9V6nb+on+nuaAU1MLPPEGm+tv6RP6if3oUQx9bFNBjMuPpytjNUjhX/CZXcIf6IB+K52SYZzNL18ADBTr0oJb4Aog70QU/+LDzX3ljxGTnZBKLBgM+CsOhUgBYw5tpiSTWlBhedKd48xXvhmJ959+2md/x1qNVWXwecNrHUHquWz3CJYcUtY9A4V4PaWz7nFpcGxyWRJaMU+iHexb3Jyf7Cly/EvPxITJ9KE2CbQoRlONF3JYXkgwrjYCa91EXTYOV/S5UR2j9y8FjlYAzmGZqDMQ0G/PzIiYSC7nprl96OdzEVNXHo6NYusRfypDWhkOQi1OEnX0MusVb4Ax34UD/Yt92Kt5zBTFJ+IZJxw5izDbdBSHfngH2orwxFgF+iFAxWmLi6d71B8JdXj/72lTtUmyu4qJBOlN8RMEZOWxmrrnJZutCHZzYqeAYnN6C6rpVpGmUZKyD/FhP1YJB2gcqg87TdH0abjgbRO59g7u7zzFEG4JZeHqzSiDeh6SwWK1VWWn/9iBE3mWvZNpQUIo8Z5F3BvnQJW16OwaHJGCoW0BEoIDrb79gsLzXwg+VYLTxAZRti6pxAPW4QVEhiwXLf6JNGHPDniJ64KnxADhI1ci4PvAQnCOXfWrB1ApdJZ+gLolcDReKyC69CMIi4oUYoWuH3QKtLfVSZRQXbSQ== root@03351470-autossh

5. Stop the add-on.

2. Configure your server

You will need a remote server (which should be accessible from the internet for our purpose).

In this step, we configure our your server to accept the earlier generated public-key for passwordless access.

I strongly recommend creating a new user on your remote server, without any rights or permissions, so in case the access is somehow compromised, this user cant do anything wrong on your server.

1. $ sudo useradd homeassistant
2. $ sudo su homeassistant
3. Check if the file ~/.ssh/authorized_keys exists, create it if not.
4. Add your earlier generated public key to this file

This step will make sure that your Hass.io add-on can connect through SSH to your server by authenticating via the Key instead of having to provide a password.

3. Configure Nginx

Installing Nginx and configuring your DNS to point to your server is beyond the scope of this blogpost, luckily there are plenty of great tutorials online to get you started.

In the examples below, I will use the example domain: home-assistant-tunnel.example.com make sure to replace it with your domain.

1. Navigate to /etc/nginx/sites-available
2. Create a new file touch home-assistant-tunnel.example.com
3. Enter the configuration below

server {
  listen 80;
  server_name home-assistant-tunnel.example.com;
  return 301 https://home-assistant-tunnel.example.com$request_uri;
}

server {
    # Secure HTTP (HTTPS)
    listen 443 ssl;
    server_name home-assistant-tunnel.example.com;

    # Certificate Information
    ssl_certificate /etc/letsencrypt/live/home-assistant-tunnel.example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/home-assistant-tunnel.example.com/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/home-assistant-tunnel.example.com/fullchain.pem;

    include /etc/nginx/snippets/ssl.conf;
    include /etc/nginx/snippets/letsencrypt.conf;

    location / {
        proxy_pass http://localhost:44400;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

The example above uses an SSL certificate provided by Let's Encrypt. To properly configure your server with Let's Encrypt, you can follow this tutorial

Please note in the above configuration, I used the port 44400 this can be any unused port on your Nginx server, just make sure to use the same port in the next step (your hassio addon configuration)

Make sure to symlink your new file in the folder /etc/nginx/sites-enabled, and restart the nginx service.

4. Configure the Hass.io add-on

1. Go back to your home assistant, Hass.io -> Dashboard -> HASS Tunnel
2. In the config paste the following configuration:

{
  "hostname": "home-assistant-tunnel.example.com",
  "ssh_port": 22,
  "username": "homeassistant",
  "remote_forwarding": [
    "44400:localhost:8123"
  ],
  "local_forwarding": [
    ""
  ],
  "other_ssh_options": "-v",
  "monitor_port": "44401"
}

A few notes here:

• hostname: your domain
• username: the username of the user you created on your server in step 2
• "44400:localhost:8123" 44400 must be the same port you used in the Nginx configuration in step 3, 8123 is port on your raspberry pi that is running the homeassistant (default: 8123)
• monitor_port: This must be the the remote forwarding port +1 (in our case, 44400 + 1 = 44401). This is the port that autossh will use to check if the connection is still active. Every few seconds autossh will send a small message over that port and if the message wouldn't arrive, autossh will restart the SSH tunnel. Making sure the connection stays active.

3. Start your add-on
4. Make sure start-on boot is on if you want to have this addon start on every reboot

In your log, you should see something like this:

...
debug1: Connecting to home-assistant-tunnel.example.com [IP] port 22.
debug1: Connection established.
...
debug1: Authenticating to home-assistant-tunnel.example.com:22 as 'homeassistant'
...
debug1: Authentication succeeded (publickey).
...
debug1: Remote connections from LOCALHOST:44400 forwarded to local address localhost:8123
...

If you now navigate to https://home-assistant-tunnel.example.com you should see your own home assistant instance running. And you can now access your Home Assistant without being connected to your home network.

In case you reboot your Raspberry Pi, the autossh addon will automatically boot, and connect to your remote server.
In case the tunnel connection is disconnected somehow (because of a temporary network drop or whatever) the autossh application will automatically try to restore the connection.

My last post about our trip to the USA was well-received, and with the risk of starting a new tradition, here is a little write-up of our trip to India in April/May of 2018.

Normally April through September is low season in India, the main reason being the heat and/or the monsoon, during our trip temperatures averaged around 40°C when the sun was out, and 30°C at night. However the low season did have some perks, almost no wait times at popular sights and lower entrance fees at some destinations.

The area we visited (Rajasthan mainly) typically has the monsoon starting in July and lasting until the end of August.

The Route

Due to some time constraints we only had 12 days for this trip. It was doable, but probably more relaxing if you add a few more (14 would have been perfect). If you have more time you should also consider adding Jaisalmer and Bikaner to your itinerary.

Highlights

We arrived in India, in Delhi in the middle of the night (2:30 AM), and took a domestic flight to Udaipur a few hours later. Where we started our journey.

1. Udaipur

While India can be a quite a shock for first timers, Udaipur, the city of lakes, seems to be a perfect entry to ease your way into the Indian way of life.

It is an easy going city, with lots of helpful people, especially if you compare it to Agra and Delhi.

Definitely visit the City Palace, Jag Mandir and the Jagdish Temple. Take a stroll through the Sindhi Bazar and go look at the Taj Lake Palace

The Taj Lake Palace is a very expensive high-end hotel that you cant visit unless you stay there. However, when you take the boat to Jag Mandir, or dine on top of a rooftop restaurant overseeing the lake, you get an nice view of this beautiful palace.

For us personally, the biggest highlight of Udaipur was witnessing the awakening and flight of the mega-bats who spend their day hanging from the trees around the lakes. And when the sun goes down, they start coming out by the thousands and flying in huge amounts around the lakes. The best place to enjoy this, is on a rooftop restaurant overseeing the lake during sunset while enjoying a tasty meal.

Recommended stay: at least 2 days.

2. Ranakpur

On your way to Jodhpur this beautiful Jain temple is a must visit place. It is located in a small and peaceful village which doesn't have a lot more to offer than the temple itself.

The temple has a strict dress code, legs and shoulders should be covered, no shoes allowed and leather items are also forbidden inside (think of belts, wallets, ...).

No food and drinks allowed either.

Around the temple there are plenty of fun and playful monkeys. Keep an eye out for them.

3. Narlai

While Narlai isn't very well known, this small village halfway to Jodhpur is well worth the stop and an excellent place to spend the night.

Normally I don't mention hotels as they aren't very important to me, but an honorable mention to the Rawla, it is easily one of the most beautiful hotels I have ever stayed, located in a renovated fort in the center of town. With excellent food, great amenities and friendly staff. Although the place isn't cheap, it is still arguably worth the money, considering you get a lot for what you pay, and the hotel supposedly does community support programs in the village.

One thing you should absolutely do here is get up early in the morning and hike up Hathi narlai mountain to the white elephant on top, so you can witness the sunrise and enjoy the stunning views over the valley and town. You can perfectly do this by yourself, but if you prefer, the Rawla also provides a complementary guide which will carry tea and biscuits. In total this should take about 1h 30m.

Recommended stay: 1 day (in case you want to relax some extra time, extend your stay at the hotel, it is worth it).

4. Jodhpur

The first large city along this route, Jodhpur is known as the Blue city, this because in the old town most of the houses are painted blue. You can see this beautifully from Mehrangarh Fort which oversees the old town.

You should also definitely visit Jaswant Thada, and go to the Ghanta Ghar which has the busy Sadar Market surrounding it. If you want you can also visit to the Umaid Bhawan Palace where the current Maharadja of Jodhpur still lives.

Recommended stay: at least 2 days.

5. Pushkar

The drive to Jaipur is long, and halfway you can visit the only temple dedicated to Brahma the Hindu creator god in Pushkar, the Brahmani Temple.

Check the calendar because every year there is also a popular Camel Fair in Pushkar in November which should be quite the event.

Be warned: the priests and the "free" guides and students in the temple are master manipulators that can easily trick you in "donating" thousands of Rupees, they will try to separate you from your travel companions. The temple can be visited free of charge, just say no to all proposals, or get up and walk away if you're not feeling comfortable.

6. Jaipur

The next big city along this route is Jaipur, and has some beautiful places to visit. A little north of the city you should visit Amber Fort (aka Amer Fort), while driving to the fort, take a quick stop at Jal Mahal.

Inside the city definitely go visit Jantar Mantar this place has a collection of peculiar structures built to study astronomy. Not far from this place, Hawa Mahal is also worth the stop and if you cant get enough of palaces the City Palace is just around the corner.

Recommended stay: at least 2 days.

7. Chand Baori

The drive to Agra is long, but fortunately there are quite a few stops along the route. Starting with the Chand Baori Step Well in Abhaneri. This step well is one of the largest of its kind in India, and can be visited free of charge.

8. Keoladeo National Park

This national park was the first National Park of India, and known for the large and diverse population of birds. Keep in mind that your ticket is only valid for the entry in the park, and if you want enjoy the full experience, you should calculate the cost of a guide (₹250 per hour) and a Rickshaw driver (₹100 per hour). The very minimum time you can visit is 1h 30m because of the distance and the slow moving rickshaws. But I recommend 2 hours.

9. Fatehpur Sikri

The last stop on your way to Agra is Fatehpur Sikri this Fort is large but very impressive. It is devided in a free part (the Mosque) and a paying part (the fort). Both are worth the visit. You will notice that the fort has influences from all different religions.

10. Agra

Once you arrive in Agra, you will immediately notice this city is not so laid back as the last few cities you have visited. Even for Indian standards the traffic is crazy, the city is loud and very crowded.

The obvious world famous Taj Mahal is arguably the most important sight in India, but other sights include Agra Fort, and Itmad-ud-Daula (aka Baby Taj)

Try to visit the Taj Mahal early in the morning for Sunrise, the sun rises beautifully along the monument, and the crowds are still manageable.

Recommended stay: at least 1 day (consider an extra day for a more relaxed visit).

11. Delhi

Delhi is the largest city of the country, and the 3rd largest city in the world. And you will notice. There are people everywhere any time of the day.

Notable sights in the city are: Jama Masjid a beautiful mosque where you can climb to the top of one of the minarets and enjoy a stunning sight of the city, Gurudwara Bangla Sahib and/or Gurdwara Sis Ganj Sahib, 2 beautiful Sikh temples, where you can enjoy the hospitality of the Sikh both free of charge (although donations are accepted), India Gate, Humayun's Tomb, Raj Ghat (the grave of Ghandi) and a lot more, go through your travel guide for more inspiration.

Delhi is huge, and getting around can be challenging, the traffic is crazy, many streets do not have names or aren't even on the maps. However the metro is very good, it is modern, clean, safe and not expensive.

Recommended stay: at least 3 days, but honestly you can stay as long as you want and never get tired of things to do and see.

Tips

Here I will try to go over a few tips to hopefully make your India visit more enjoyable.

1. Visum

Most nationalities require a visum to enter India. You can request this yourself on https://indianvisaonline.gov.in, and will cost you about 40 EUR per person. This procedure is rather quick and should normally take 4 working days.

Make sure to print out your approved visum and bring it with you to the airport, as you can be denied boarding if you can't provide proof of visum.

2. SIM

This is more a personal preference, as I enjoy the ease of looking up information myself online, and in India it is the perfect medium to request taxis on (more on that later). Airtel is the carrier in India which provides the best general coverage.

And at the time of writing it cost me about 5 EUR for 28 days unlimited calls and texts, and 1 GB per day.

The SIM card will normally take 24 hours to activate once you have requested it. When you go to an Airtel store to request a SIM card, make sure you carry a copy of your passport (or your passport), a passport photo, and the address of your hotel.

3. Hotels

One of the best tips I can give you for India, is try to find a hotel that is quite luxurious, the price is often many times lower than the same room you would have in another country. While you can find very cheap places to stay, it is very enjoyable to have a little oasis in the busy and hectic India every night.

4. Traffic

Even though nothing in the law is stopping you to rent a car and drive yourself in India, I would strongly advise against it. The traffic is nothing short of pure chaos in the cities and arguably one of the more challenging places to drive in the world. Roads often dont even have a name, or arent anywhere on the map.

Besides you can easily find taxi companies who will rent out a car plus driver with everything included (gasoline, taxes, tolls, parking, overnight stay and meals for the driver, ...) for a few days. To give you an idea, it cost us a little under 300 EUR for 6 days all included.

5. Culture Shock

India can be quite the shock, there is a lot of poverty, noise, crowds., ... But don't get scared, at the same time it is beautiful, very colorful, tasty food, rich culture, ...

Buy yourself a good travel guide and read through it before going. I am a big fan of the Lonely Planet travel guides, and swear by them for every destination.

6. Hassling

In shops you will often not find any price tags, with good reason, locals will debate prices and are natural born deal makers. Keep in mind that as a foreigner if you ask for the price of something, the initial price will be at least 3 times the price you should actually pay.

7. Taxis

Similar to hassling, the price of taxis is often 3 times (or more) the price you should pay. Finding a taxi driver that is willing to drive with a meter is equally challenging.

To make this easy and enjoyable, use the app Ola Cabs on your smartphone, which is the Indian version of Uber (although Uber is available in India, Ola is more widely used and cheaper). You must set a pickup and destination, you will get a price, and a driver will come and pick you up. You can just pay in cash to the driver. During our stay not once did a driver make a fuss or be difficult when using Ola, all went very smoothly.

8. Selfies and Pictures with locals

For some reason (I have heard multiple explanations) locals enjoy selfies and pictures with foreigners, and you will be asked multiple times a day for pictures. Nothing bad is meant by this, and they will be quick and easy. However, sometimes if you agree to one picture, all of a sudden 10 other people will be lined up for a picture with you.

Sometimes this can be a little annoying, but just enjoy and experience how celebrities go through life all the time. I had one rule regarding the pictures, every time someone wanted a picture with me, I in turn wanted a picture with them. These pictures turned out to be fantastic, and a beautiful souvenir of our trip.

9. Food and drinks

Be very careful with food and drinks in India. Only drink bottled water, even brush your teeth with bottled water, and avoid ice cubes in your drinks.

If you go out to eat, I would advise against eating meat. India is very well known for the rich veggie culture, just enjoy it as it will limit the risk of unsafe food. Try to only eat cooked vegetables and avoid raw ingredients.

Use your travel guide, trip advisor, read reviews, ask for advice in your hotels and only eat in upstanding clean places. But if you decide to try street food, only eat in places where a lot of locals are eating, and there are fast moving dishes.

Even if you are very careful, sometimes you can get a bacterial infection often from something small, this can understandably ruin your trip, as you can be tied to a toilet. Bring diarrhea medication, activated charcoal (in case of food poisoning) and antibiotics (go and see a doctor for advice).

10. Pollution

I'll just come out and say it, India is dirty. Trash everywhere, polluted rivers (never, ever swim in a river!), smog and lots of dirty traffic.

If you are walking through a city you will often switch between delicious and foul smells in a matter of seconds.

11. Airports

The airports in India are busy, very busy, come well in advance because you will loose a lot of time just queuing. I would say 3 to 4 hours before departure for international flights, and 2 to 3 hours for domestic flights.

In Delhi and Banagalore (possibly others) you have to show your ticket and passport before you can enter the airport (this can be done on your smartphone), and on busy days, you will spend a considerable amount of time queuing here before you even enter the airport. Keep in mind that you still have to check-in (or drop your baggage) and go through the security check.

12. Language

Although a lot of languages are spoken in India, you can get around very easily with English. All important street signs and information is mostly displayed in both Hindi and English. Everywhere in hotels and decent restaurants English will be the main language spoken.

This is a copy and paste blogpost, originally posted at Mapzen, because the service is shutting down and I wasn't sure how long the blogpost was going to be online for, I wanted to preserve the valuable information and republish it myself. Apart from this intro, not a single word was written by myself

Get driving, biking, walking and transit navigation in your app

Mapzen will cease operations at the end of January 2018, and its hosted APIs and all related support and services will turn off on February 1, 2018.

Your two options are to switch to another hosted API that offers similar functionality, or to run your own servers with the open-source projects that powered Mapzen services. We list several options below to make this as easy as possible.

Alternate services and hosted APIs

Mapzen Vector Tiles and Cartography

For basemaps and vector tiles, you may want to consider:

• Nextzen (A long-term support version of own own Tilezen):
• Mapbox
• OpenMapTiles
• Thunderforest
• MAPCAT

Long-term support for Vector Tiles is available via Nextzen through 2018 supported by Amazon Web Services, thanks to an award from the Earth on AWS Cloud Credits for Research Program. This includes hosted versions of Tangram JS and the map styles. The vector tile data is an archived December 2017 global build available in a requestor pays S3 bucket with associated serverless software.

Terrain Tiles will continue to be available as an Amazon Public Dataset.

Mapzen Vector Tiles and Cartography are based on the Tangram and Tilezen open-source projects. Read below for information on how to run these services locally.

Tangram scene files saved in a Tangram Play account can be saved to a GitHub Gist or downloaded locally, while Mapzen services are still running.

Mapzen Turn-by-Turn routing

For routing and navigation, you may want to consider these services:

• GraphHopper
• Mapbox Directions API
• Project OSRM

Mapzen’s routing and navigation projects were backed by Valhalla, an open-source project. Read below for how to run Valhalla locally.

Mapzen Search

For search and geocoding, you may want to consider these services:

• geocode.earth (A new hosted version of our very own Pelias)
• Nominatim
• OpenCage Data
• OSMNames
• Mapbox Search API

Mapzen Search was backed by Pelias, an open source project. Read below for how to run this service locally.

Mobile

For Android and iOS, you may want to consider these third party SDKs:

• Mapbox

In the event you decide to host a version of Valhalla and Pelias locally, you can continue to use our mobile SDKs we’ve built to interact with that service.

Mapzen iOS and Android SDKs, along with On The Road SDKs for Valhalla will be available at https://github.com/nextzen.

Our LOST project for Android will be available at https://github.com/lostzen/.

Pelias and tangram-es SDKs will continue to be available from their respective repositories.

Transitland

Transitland will continue as an open-data project at https://transit.land

Transitland’s server and data operations through 2018 will be supported by Amazon Web Services, thanks to an award from the Earth on AWS Cloud Credits for Research Program.

Continue to follow @transitland on Twitter for updates.

Who’s On First / Mapzen Places

Data (individual records) and source code for Who’s On First will continue to be hosted at https://github.com/whosonfirst, but whosonfirst.mapzen.com and the Mapzen Places API will go offline.

Who’s On First will continue (in a scaled back version, for now) at https://whosonfirst.org.

• Data (individual records) and source code are at https://github.com/whosonfirst.
• All of the data and code and blog posts have also been cloned to the Internet Archive.
• The Spelunker will go offline, in the short term.
• Batch processing and cascading edits will stop in the short term.
• A limited version of the API that returns individual records will be at https://whosonfirst.org, with additional functionality growing over time (spatial queries, point-in-polygon, editorial tool, cascading updates).

Follow along at https://www.whosonfirst.org for updates.

Metro Extracts

Metro Extracts will no longer be updated, and the custom extract service will no longer be available. We are working on making a copy of the existing extracts available.

The Humanitarian Open Streetmap Team has created the HOT Export Tool that creates customized extracts of up-to-date OSM data in various file formats, including PBFs. Please consider donating to HOT, whether or not you use this service.

For non planet-sized PBF extracts, you may want to consider Geofabrik or the Overpass API.

Also, OSMaxx can be used for downloading OSM data.

Documentation and blog posts
Blog posts will be archived on https://medium.com/postzen.

Documentation will be available in each open-source GitHub repo:

Documentation section Source location
Overview https://github.com/mapzen/mapzen-docs-generator/tree/master/docs
mapzen.js https://github.com/mapzen/mapzen.js/tree/master/docs
Tangram https://github.com/tangrams/tangram-docs
Vector tiles https://github.com/tilezen/vector-datasource/tree/master/docs
Search https://github.com/pelias/pelias-doc
Mobility https://github.com/valhalla/valhalla-docs
Metro Extracts https://github.com/mapzen/metro-extracts/tree/master/docs
Terrain tiles https://github.com/tilezen/joerd
Elevation https://github.com/valhalla/valhalla-docs
Android SDK https://github.com/mapzen/android/tree/master/docs
iOS SDK https://github.com/mapzen/ios/blob/master/docs
Address parsing/libpostal https://github.com/whosonfirst/go-whosonfirst-libpostal/blob/master/docs
Who’s On First https://github.com/whosonfirst/whosonfirst-www-api/tree/master/docs
Cartography https://github.com/tangrams/cartography-docs/

Run open-source versions of Mapzen services

Mapzen services are backed by open-source software projects, and use open data. Even with limited technical knowledge, you can run these yourself for metro-sized areas using a local web server or Docker containers.

Tangram and Tilezen (Cartography and Vector Tiles)

Documentation for Tangram is available at https://github.com/tangrams/tangram-docs.

tangram.js, tangram.es, Mapzen.js, Tangram Play are all open-source projects that can be run locally.

Basemap styles

Refill, Walkabout, Bubble-wrap, Tron and Cinnabar basemap styles will continue to be available in their repositories in https://github.com/tangrams and served via tangrams.github.io and via Nextzen.org.

Map data

While Tangram can import non-tiled GeoJSON and TopoJSON, vector tiles are what makes it interesting.

The Docker version of Tilezen can dynamically serve tiles from a Metro Extract or reasonably-sized PBF.

Tilezen in Docker https://github.com/tilezen/tileserver/blob/master/DOCKER.md
To run a map for a city or a region with no network dependencies:

• Save mapzen.js / tangram.js, index.html and scene.yaml file in a directory
• Extract a pyramid of tiles for area of interest using tilepack and save them in that same directory. (Note you don’t need to go beyond z15 tiles as they contain all the data in higher (>= 16) tiles, and Tangram overzooms.)

To download tiles from our hosted services before shutdown:

https://github.com/tilezen/tilepacks MAPZEN_API_KEY=mapzen-xxxxxx tilepack -122.51489 37.70808 -122.35698 37.83239 10 15 sf_mvt_10_15 --tile-size 512

Size and download speeds makes this viable for a city and perhaps a region. The example above generates a 30MB pyramid of MVT tiles, or 138MB of topojson, for San Francisco. For GeoJSON, SF is 67MB at z14, and 130MB at z15.

• Serve tiles via a web server (localhost or hosted).
• Create a scene file for Tangram. Note you will need to override the mapzen source in the scene file if you are importing a basemap.

sources:
    mapzen:
        type: MVT
        url:  localhost:8000/sf_mvt_10_15/all/{z}/{x}/{y}.mvt
        tile_size: 512
        max_zoom: 15

Valhalla (routing)

Documentation for Valhalla is available at https://github.com/valhalla/valhalla-docs.

Instructions on running Valhalla in Docker using data from a Metro Extract or PBF are at https://github.com/valhalla/docker.

Pelias (search)

Documentation for Pelias is available at http://pelias.io and https://github.com/pelias/pelias-doc.

Instructions on how to run Pelias in Docker with data from a Metro Extract or PBF and OpenAddresses data are at https://github.com/pelias/dockerfiles/blob/master/how_to_guide.pdf.

General instructions on running and installing Pelias and Elasticsearch: http://pelias.io/install.html

Mobile
Android and iOS SDK source code and LOST will available at https://github.com/lostzen

Preview image: World Emigration Map by Charles Minard from the David Rumsey Map Collection

After my brother-in-law spoke to me about a full solar eclipse he was lucky enough to witness in Longyearbyen, Svalbard in 2015. I made up my mind to go see one for myself. Turns out that 2 years later there was one in a very accessible location. The entire continental USA.

Only going to the USA for an Eclipse seemed a waste, so I built a trip around it.

Ever since, friends and family have been asking us about our route, and because I got tired explaining it every time, here is my route and highlights.

The Route

Firstly, you'll notice some obvious classics are missing from this route. This is because we had limited time for this part of the journey (there was a second part on the east-coast which I wont get into), and we had been to the west-coast before, where we did the classics (like LA, San Francisco, Yosemite, Kings Canyon, Sequoia, Death Valley, ...), your typical 'lets-go-to-the-USA-for-the-first-time-trip'. If people are interested in that, send me a message and I might find the time to share it.

Secondly, we did this in 2 weeks, which is quite a fast pace, and definitely not relaxing for the average traveler. Because of this, we didn't do any long hikes and didn't stay in one location for more than 2 days.

Lastly, the last part of our route I wouldn't recommend, it was a long boring drive back to Las Vegas. Consider alterations if you don't want to spend 4 hours driving through next to nothing.

Highlights

Below I'll go over the different highlights in the order we visited them. You'll probably notice the absence of Las Vegas, it is because for me, its far from a highlight, it was a convenient located international airport in a city full of madness.

1. Grand Canyon

It was our second time visiting the Grand Canyon, the first time we took a helicopter tour over the canyon. And this time, we just visited it by car, and did a small hike. Arguably I liked the last time better, you get a far better idea about the size of the canyon, and it doesn't cost as much.

We visited the grand canyon in the afternoon to witness the sunset, and it was well worth it.

I would recommend driving into Grand Canyon Village, and driving your car all the way up to Bright Angel Trailhead where the road will be closed for regular vehicles but accessible for busses, park your car somewhere. Go to the bus stop, and take the bus all the way up to Hermit's Rest, then hike back to the bus stop you started at.

This is a very beautiful hike along the rim and especially memorable if you can catch the sunset during your hike. In case you get tired, there are plenty of bus stops along the road where you can take the bus back.

2. Marble Canyon

This is not really a place to visit, more than it is a beautiful drive to a nice little town, Kanab, a good place to spend a few nights to visit the next 2 highlights.

3. Bryce Canyon

Bryce canyon is beautiful, its not very big and perfectly doable in a few hours. I recommend getting up early and visiting Bryce Canyon for the sunrise, as the sun is on the best side of the canyon in the morning.

4. Zion National Park

Zion is quite large, and the hike to weeping rock is worth it. You can drive through it if you decide to take a different route. Keep your eyes open for wildlife as there are Mountain Lions, Big Horn Sheep, Condors, ...

5. Horseshoe Bend

This is an easy spot to visit, it is along the route and walking distance from the designated parking. But keep in mind, things you often don't see on pictures of Horseshoe Bend, is the 20000 other people doing the exact same thing. It is beautiful, and you should definitely stop and go take a look, but you won't be the only one.

6. Antelope Canyon

Antelope was one of my personal favorites of the trip. The canyon is managed by the Navajo, and thus not part of the National Parks Service, because of that you'll pay a separate entrance fee.

You have 2 parts of the canyon, Upper, and Lower Antelope Canyon. We did the lower part with the company Dixie Ellis' Lower Antelope Canyon tours. You can only enter it guided, but it is well managed. You go in little groups of about 10 - 15 people at once, together with a native guide who will point out all the remarkable parts of the canyon.

Make a reservation in advance, its a very popular destination and is often fully booked. You will get an expected hour when your tour will leave, so you don't have to wait hours for your turn, and you can perfectly plan ahead. The canyon is especially beautiful with a clear blue sky. The cost of the tour is about $35 per person, but well worth it! You'll regret it if you decide not to go.

7. Monument Valley

Another absolute stunner. This park is also managed by Navajo and requires a separate entrance fee, in 2017 this was $15 per car.

You have a driving tour in the valley which is absolutely beautiful, it is on sandy roads, but very doable with a normal car under dry conditions. Take your time as you will be in awe half of the time.

Keep in mind that the drive from Page takes some time, and the drive to the next village also takes some time. If you want, there is a hotel in the park

8. Arches National Park

Unfortunately for us, the park was under maintenance when we were there, and half of the park was inaccessible to the public. Even though we didn't see all we wanted, it was well worth the stop. The sunrise should be stunning, but for us we couldn't do it because of the maintenance.

Moab is a nice town to stay in while visiting both Arches and Canyonlands, it has everything you want, and just a few minutes drive from both of the national parks entrances.

9. Canyonlands National Park

Again an absolute highlight, This is the largest park of Utah, but often forgotten. We were there during high season, but it was very calm. Take your time, hike up to Mesa arch, Buck Canyon overlook, White Rim overlook and Upheaval Dome and fall in love with the stunning views.

10. Goblin Valley State Park

This park is not big, but very unique, it is a state park, which you cant enter with your national parks pass, but the entrance fee is very small as the park isn't very well known.

Supposedly this park is also a great spot for nighttime star gazing, check the calendar online for events.

11. Capitol Reef National Park

This national park is very large, mostly accessible by car and a beautiful park to drive through up to your next destination. It is more green than the last couple of parks, and a great place to picnic. Not a lot of amenities, so take your picnic with you.

The drive up to the next point is long, in between you have Salt Lake City, but apart from the Mormon culture (if you're into that), there isn't a lot that meets the eye, it can however be a nice change of scenery from nature to a city

12. Grand Teton National Park

This park is mostly along the Teton mountain range, and absolutely beautiful to drive through up to Yellowstone, there are Bison and other wildlife to spot. So binoculars can be a great add-on to your gear.

13. Yellowstone National Park

The first and thus oldest National Park in the world. This is a breathtaking and diverse park to visit. You have Geysers, Hot Springs, Limestone Terraces, wildlife, ...

One thing we underestimated was the size of the park, it is gigantic! Take your time, I would recommend at least 3 days as the highlights in the park are quite far away from each other, and due to the popularity and wildlife crossing the streets the traffic can be slow. You can spend the night in the park, or just outside in West Yellowstone.

Bring binoculars!

14. Craters of the Moon National Monument

Another very different change of scenery from the rest, this national monument (which can be entered with the NPS pass) is a park filled with Solidified Lava from an eruption many thousands of years ago. This is a rather calm park, and not very touristy but well worth the visit.

15. Evel Knievel Snake River Canyon Jump Site

Because you are driving through Twin Falls (or possibly spending the night), you can quickly go visit the jump site where Evel Knievel jumped over the Snake River.

It is a beautiful park where you can calmly picnic and enjoy the 2 falls right in front of you.

16. Bonneville Salt Flats

If you thought you had seen the diversity of Midwest USA, you haven't visited Bonneville Salt Flats, another completely different scenery, but again absolutely beautiful.

This is the place where a lot of land based speed records have been driven. A definite must-visit place.

17. Great Basin National Park

Halfway between Twin Falls and Las vegas lays Great Basin National Park, I wouldn't say you should absolutely visit this, but if you decide to take this route, the drive to Vegas is long and boring, and this place is a nice oasis in the middle of nowhere.

Other tips

National Parks

You will be visiting a lot of national parks, to save yourself some money, and make a swift entrance, buy yourself a national park year pass. As it will be a lot cheaper than separate entrance fees.

Up-selling

Keep in mind you're traveling to the USA, the most capitalist country in the world, where everybody will be trying to sell you something, half of the country lives on commission and will want to recommend something bigger or better.

For example you will rent a car, and when you go and pick it up, the very friendly clerk will be recommending you an upgrade, a larger car, a better engine, whatever. You don't need it, stick to your original plan, because it can end up costing you a few 100 dollars extra.

This, and a lot of other small extra costs can total to quite a lot of money if you don't watch out.

Sleeping arrangements

You don't necessarily have to book very long beforehand, the entire country is filled with Hotels, Motels, Inns, Bed & Breakfasts, ... You can even get along with finding places to sleep while already traveling.

Inns

Inns are mostly great value for money, they are relatively cheap, and come with clean rooms and a breakfast most of the time. This is especially interesting if you are traveling with 4 people, as a standard room is often 2 Queen size beds for the average price of $120 per room. I found both Best Western and Holiday Inn to be the best.

Casinos

Everywhere in Nevada, you will find Casinos, while it is often horrid and depressing to see people gambling away their money, or seeing the poverty of people who lost everything, mostly you can spend the night dirt cheap in Casino hotels, this will likely be without breakfast.

Just keep in mind that some casino hotels charge a Resort Fee on top of the regular room rate, which is often not advertised and a complete surprise when you go and check-in, this can be as much or even higher than the room rate, and isn't calculated in the price when booking online, do your homework and check the resort fees per hotels before making reservations.

Food

Although you will find places to eat everywhere, eating healthy will require some extra leg work, and can often be a lot more expensive than you're used to, all the while unhealthy food can be dirt cheap ($5 for 10 donuts anyone?).

Mobile cellphone and data coverage

I do recommend buying a SIM card, as it is worth the money (say around $40 for a few gigabytes) to have data connectivity while traveling. Navigating, up-to-date traffic information; easily find (cheapest) gas stations nearby, places to eat, supermarkets, your hotels. And can call for hotel reservations without having to pay exuberant roaming charges or finding public wifi hotspots.

While the USA generally has good coverage, keep in mind that outside of cities in the mid-west it is often difficult to get cellphone coverage (let alone data coverage) because the national parks and surrounding areas are very sparsely populated and don't have the infrastructure in place for good coverage.

This is the second part of a 2-part blogpost about using the Nest thermostat with a modulating Junkers boiler. In this part I will guide you step by step through the setup and installation process of hooking up a Nest thermostat to my Junkers CerapurComfort boiler.

Read Part 1

Disclaimer: If you decide to do an installation yourself, be careful, there are risks involved, you might break your boiler, your Nest, or both, if you don't hook up everything correctly. I take no responsibility, consult a professional if you're not comfortable doing the installation yourself.

OpenTherm protocol

The Nest generation 3 thermostat uses the OpenTherm protocol to talk with modulating boilers. This protocol is used by many boilers, but unfortunately not by Junkers.

The Nest documentation was really helpful, clear and concise. It is where (in Dutch) I discovered OpenTherm adapters, these are little devices that convert the OpenTherm protocol to a protocol supported by the boiler.

To my delight, on the above linked webpage as an example, a Nefit card is shown, and from my earlier discoveries I thought this could be compatible with my Junkers boiler.

Apparently the modulating protocol from Nefit is called EMS, however nowhere in the manuals of my boiler or online I find anything about EMS and Junkers.

I learn from the OpenTherm spec, that a maximum of 42V is used to communicate.

EMS to OpenTherm adapter

Discovering the adapter was a breakthrough, but I still had no idea if it would work with my boiler.

There was 1 webshop selling an EMS to OpenTherm adapter for Junkers in Belgium. No pictures, and not a lot of documentation though. But 1 magical sentence

Enkel voor Junkers ketel met Heatronic 3, Heatronic ‘ en EMS protocol.

(Only for Junkers boiler with Heatronic 3, Heatronic and EMS protocol)

From my manuals I found that my boiler used the Heatronic 3 system inside, but nothing about EMS.

I googled the product number mentioned on the webshop's product page, and to my delight I find the exact same adapter from Nefit, with the same product number.

At this point i'm getting more convinced that this will work. I decide to open up my boiler, and see what's inside. Perhaps I find a connector resembling the one on the adapter, then I would be convinced.

Opening the boiler

Let's open up the boiler, on the bottom there are 2 screws near the front of the panel, unscrew them, and on the top there is a locking mechanism which you can lift to unlock the entire cover.

On the bottom, the panel with the buttons, that is your Heatronic 3 system. You will need to get to the back. Above the Heatronic there is a sliding lock, slide it down, and you will be able to rotate the heatronic towards you to reveal the back.

On the back there are 3 screws you need to unscrew to reveal the connectors inside. 2 screws are directly adjacent to the cable holders. and one is on the bottom right.

Once you unscrew these, you can lift the panel up, be careful, it slides directly up, dont try to pull 1 side, lift it all together.

Then you should see something like this:

Unfortunately, no luck here, no connectors resembling the one on the adapter. But lets not give up.

I decide to measure the voltage outputs on the connections where the thermostat should be connected (which I found in my manual)

This matches the voltage i'm getting at the thermostat. So the thermostat is most likely connected here.

At this point i'm fairly convinced I won't break anything by connecting a Nest. I'm still not sure it will work, but at least I can try.

Lets try connecting the nest

Time for some Famous Last Words:
Fuck it, what's the worst that could happen?

I order a Nest, and the adapter (I decided to order the Nefit adapter, as compared to the Belgian counterpart it's almost half the price and I'm fairly convinced it's the same anyway)

With the Nest came this schema:

I unplug the thermostats wiring from the Heatronic, connect the black cable of the Adapter on the same ports I just unplugged the original thermostat from (the BB ports), and connect the Nest Heatlink on the OT1 and OT2 port to the green ports on the adapter.

Edit 2021-04-05:
I received a question about other ports by someone who found this blogpost over at Tweakers.net, where he asked what was connected on the Lr and Ls ports, as his old thermostat was connected there. On my end, my old thermostat was also connected to the BB ports, so I was interested what was going on with my Lr and Ls ports, I decided to open up the boiler again, and found that a jumper was present that connected Lr with Ls.

There is no real slot to put the adapter, but it comes with a little strap, I use it to hang it on the inside of the boiler in the same hole where on the other side there is a cord that holds the Heatronic in place.

I connect power to the N and the L on the Heat Link.

Lastly I used the existing wiring to connect the Nest Thermostat to the Heat Link, by connecting ports T1 and T2 on the Heat Link, with the T1 and T2 on the thermostat

I attach the thermostat, and what do you know? It works, all my suspicions turned out to be true. After going through the initial set-up (Tip voorlooptemperatuur = 55°), this is how it looks:

Conclusion

I hope someone will find this helpful, and can enjoy the wonderful Nest thermostat, the awesome app, extensive integrations and beautiful design!

In a completely unrelated note: I'm selling a Junkers FR-120 and MB-Lan Module 2 if someone is interested

If you want to say thanks, buy me a beer:

In this blogpost I will tell you my story of how I wanted to integrate my central heating, with a smart home solution. It's a 2 part story, where I first go into detail about my setup before the nest. And the second part will be about installing the Nest.

Disclaimer: If you decide to do an installation yourself, be careful, there are risks involved, you might break your boiler, your Nest, or both, if you don't hook up everything correctly. I take no responsibility, consult a professional if you're not comfortable doing the installation yourself.

The Boiler

History

In 2014 we were in the need for a new boiler, as the one broke that came with the house we bought. I contacted our plumber and he got to work. I asked him about the Nest thermostat I learned about, but he told me that the Nest wasn't suited, because (at the time) Nest didn't support modulating boilers and using a Nest would mean my boiler would be energy inefficient.
He recommended an Junkers CerapurComfort ZWBR 30-3 boiler. For reasons he knew best, and I trusted him.

At the time there was a promotion, and with the purchase of a boiler we got a Junkers MB-LAN 2 Module for free (normal price was €300). Which would give us the ability to control our thermostat from an app.

The boiler came with the Junkers FR-120 modulating thermostat, which worked together with the Lan Module

Review of Junkers material

We used this setup for nearly 3 years. And this is what I concluded.

The Boiler, and the thermostat worked fine, they did their job and were reliable.

Lan-module

For a device that would normally cost around €300, it is not worth it at all. The module requires a cabled connection to the internet, I managed to do that, but I can imagine others having their boiler in an unreachable place from the internet router.

If the internet went down, even if it was for a few seconds, the module would stop working, the only thing that you could to was unplug the power, and plug it back in, for it to completely reboot.
This was very frustrating for when you wanted to remotely turn on the heating before getting home, only to find out the module stopped working.

And it's not like I have a shoddy internet connection at home. With a coax cabled 100mbps down/10mbps up, very reliable network, I almost never have any complaints. (and I run multiple other devices reliably for my smart home, a Philips Hue bridge, a Rasberry Pi with Home-Assistant, and a Google Home).

Another frustrating thing was, that the regular thermostat gave a warning that there was a lan module connected, and every time I wanted to do something manual from the thermostat, I had to dismiss the warning ... every ... time ... I ... did .. something 😤.

The JunkersHome-App

If you want to use the Lan-module, you have to do it via the JunkersHome app. Which (at the time) costs €7 to install from Google Play

The app is just plain bad, not intuitive, slow as hell, and of course, stopped working when the Lan Module was unresponsive.

Trying to configure a schedule for the boiler via the app, is to date, the worst app experience I have had. The app would overwrite days I had already configured. Not save things I had put in, and sometimes take minutes to save.

External integrations

Lol what?

Of course nothing officially about this, only a handful obscure German forum posts from people trying to reverse engineer the Junkers/Bosch protocol, to read out values with their raspberry pi.

I also tried sniffing my local network to intercept the TCP/IP packages with Wireshark, so I could potentially write an application that simulated the JunkersHome app.
The packages, and URL endpoints led me to the tweakers.net forums, where some dutchies seamed to have did something similar with Nefit boilers. (this was my first indication that Nefit and Junkers arent all that different)

Nest Thermostat generation 3

The third generation of the Nest thermostat was released, and after reading the specs, I was delighted to find out that Nest was able to support Modulating boilers. However my euphoria was short lived, because even though Nest supported the OpenTherm protocol, of course my boiler didn't.

Junkers solutions

I talked to my plumber, and Junkers support about possible solutions. And I was recommended the new Junkers CT-100 smart-thermostat.

€300 for a new thermostat, where I don't find that much about online, no integrations, no reviews, and my experience with their software from the Lan Module... no sir, I wasn't buying it (literally)

It was when I was researching this thermostat, I found the Nefit Easy, the Worcester Wave, the TC100 from Buderus and the Bosch Smart Room Thermostat. Fuelling my suspicion that these brands aren't all that different, all Bosch companies, with another name in different countries.

To give Bosch credit, the Nefit Easy seemed to have an IFTTT integration, but did that work with the CT-100? Nobody knows, no documentation about that anywhere.

In the next part I will go into detail of how I got the Nest thermostat working with my modulating boiler.

Next

Read my follow up blogpost, on how to connect the Nest

Read Part 2