Snow chains for a Winnebago View

Over Christmas we drove the Navion (an Itasca Navion is another name for the Winnebago View) to the ski resort for a night. It had been dumping snow for days, and we wanted some of it, and it seemed a great chance to try the motorhome in the snow.

IMG_20151222_091114892

Because the weather had been so bad/awesome, chains were required on the road up to the mountain. So here’s what I learned:

  • With duallies, you need to be careful with chain clearance between tires. So even though there’s a ton of clearance in the wheel well for chains, low-clearance chains are still recommended because of the smaller space between the inner and outer tires.
  • Installing chains on a duallie motorhome isn’t too bad. You drive the inner tire up on a ramp (in my case my Lynx leveling blocks), so that the outer tire is suspended in the air.
  • Bring foul-weather gear. You’ll be on the ground checking the chains, and that ground is going to be slushy, cold, and filthy.

Once the chains are on, try to stay on the snow-covered portion of the roads. Driving on bare pavement drastically reduces the life of your chains – and it rattles the heck out of the occupants! I kept to 25mph with my emergency flashers on, and was quite happy.

For chains, I bought these:

Security Chain Company SZ429 Super Z6 Cable Chain (Amazon.com)

They were easy to install, remove, and store away, and cost less than $100.

301 redirects not working with WordPress (the solution)

I just moved my site over from github pages to WordPress. In doing so, my post URLs changed, and I wanted to redirect so that visitors from search results wouldn’t hit a ‘page not found’.

My webhost uses cPanel, so I followed the instructions to set up 301 redirects for my pages. But they didn’t work! A bit of googling turned up that redirects don’t always work as expected when using content management systems like WordPress, but didn’t provide the answer. So here it is!

Because WordPress rewrites URLs so that it can handle pretty permalinks, your redirect (rewrite) rules must go above the WordPress section in your .htaccess file:

RewriteCond %{HTTP_HOST} ^heycascadia\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.heycascadia\.com$
RewriteRule ^2014\/08\/08\/arduino\-wireless\-freezer\-alarm\/$ "http\:\/\/www\.heycascadia\.com\/arduino\-wireless\-freezer\-alarm\/" [R=301,L]
RewriteCond %{HTTP_HOST} ^heycascadia\.com$ [OR]
RewriteCond %{HTTP_HOST} ^www\.heycascadia\.com$
RewriteRule ^2014\/08\/19\/blackberry\-workgloves\/$ "http\:\/\/www\.heycascadia\.com\/blackberry\-proof\-workgloves\/" [R=301,L]

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

If they’re below the # BEGIN WordPress section, the URLs will be rewritten first, and then won’t match your redirect rules.

Some things I learned about Jekyll and Liquid

I’ve been working on a site recently for an open-source project, which is hosted using GitHub pages.

I struggled a fair amound with conditionals, and this is what I learned:

  • Liquid doesn’t accept double-quotes for conditionals. You need to use single quotes.
  • There needs to be a space between the comparison operator and the terms on either side. You can’t run them together without a space.
  • You can use any YAML front-matter value, even custom values. For example, I used category: docs for pages that are documentation pages. I can access this later with page.category.

An example of all of this:

{% for page in site.pages %}
{% if page.category == 'docs' %} ... do something .. {% endif %}
{% endfor %}

The above works. What wouldn’t work:

// Need a space before and after operator.
{% if page.category=='docs' %}

// Double quotes are not supported; use single quotes.
{% if page.category == "docs" %}

You have to solder Arduino shields

It’s so obvious to everyone else, that I couldn’t find any reference to it on the internet: you have to solder an Arduino shield to the headers.

I thought it was plug and play, since the little header pins seemed very snug when I put the shield over the Arduino Uno. But the shield wasn’t working, and it turns out that each pin needs to be soldered.

Luckily, soldering is very easy, and I was able to do it in less than 10 minutes, never having soldered before. It’s worth checking out some YouTube vids before you start, though.

Arduino wireless freezer alarm

The other day I opened my deep freeze to discover everything inside slowly melting. The freezer had tripped the GFCI on the circuit, and silently turned off.

I don’t keep a lot of food in there, so there’s no real reason for a freezer alarm that will ping me when the temperature rises, but it was a great excuse to buy and tinker with an Arduino.

Here’s where I’m at so far:

arduino_freezer_alarm

Continue reading “Arduino wireless freezer alarm”