Our Chickens are Preparing the Garden

This past weekend we put our chickens into their new mobile coop, and found them a nice space in our garden area for them to prepare.  It’s a bit of an experiment, but I think it will work.

Here in Wisconsin the weather is still pretty cold in March and April, and our average last frost date in my area is the 1st week of May.

So what are the chickens doing?  Chicken things!  Scratching, digging, pooping, and spreading anything that’s put in their reach.  Here they are on day 1.

chicken garden week 1

By the time we are ready to plant, this area will have the vegetation removed, be organically fertilized, and will have a nice layer of mulch spread out, all via chicken power.  No tillers, no backbreaking work with a shovel.  Just chickens doing what they like best anyway.

I’ll update with a photo each week as this area is transformed into a nice area for a garden to be planted.

 

 

New Mobile Chicken Coop is Ready

We tried our first chicken tractor last year and it worked out well enough but it really was only big enough for 10 birds or so.  It started out as a straight tractor, but as the season moved on and the birds got bigger we ended up just using it as a mobile coop.

You can see it below, surrounded by premier1 poultry netting.

wp-1489334857725.jpg

 

As a mobile coop it worked ok, but had some limitations:

  • Small wheels made it kind of tough to move over rough ground
  • It was easy enough to move 8′ at a time (every day), but when it was time to move it across the farm, it was tough going
  • Our bigger birds (such as pioneers/red ranger meat birds) weren’t able to get up into the roosting area very well
  • Insuffient space for nesting boxes if we wanted to have laying-aged birds in it

So this year I’m trying a new design, based on the one created by Justin Rhodes at Abundent Permaculture.  You can find his build instructions here.

This new design should fix the problems above:

  • Big wheels make it go over rough stuff no problem
  • Plenty of space for our layers and room for more
  • Open floor means manure goes where it belongs – on the pasture
  • Nesting boxes easily accessed from outside the coop
  • Plenty of easy to access roosting space

Here it is, all put together and ready for its maiden voyage!

wp-1489335704274.jpg

The birds will move in this weekend, and we’ll put them to work fertilizing and preparing the garden right away.

 

 

How to receive events from an Microsoft Azure Event Hub on a Raspberry Pi

I received a question on my “How to send events from a Raspberry Pi to Microsoft Azure Event Hub” post:

“I want to ask about do you know “how to receive events from azure event hub to raspberry pi””

After a little research I found an article outlining how to do so , via the AMQP protocol using Proton C.  However, I found myself wondering about the use case.

Typically, we are sending events from our IoT devices to some cloud application for analytics, machine learning, or the like.  Event Hubs are great for those high volume cases.

However, if you need it for a messaging scenario, queues or topics might be more appropriate, and they are directly supported by the Azure Python SDK.  In my own case, I elected to use a simple long-polling strategy to have my raspberry pi listen to my cloud app for instructions.

So, can it be done?  Yes, here’s how.  But it may not be the right tool.

“Alexa, raise my desk to 15 inches”

Last year, I built a DIY Raspberry Pi controlled electric standing desk.  It was a great project and I’ve gotten a ton of use from it.

To move the desk, I simply had to:

  1. Launch PuTTY on my computer
  2. PuTTY to the raspberry pi
  3. Log in
  4. Navigate to the directory where the program was running
  5. type sudo python3 robotdesk.py
  6. Tell it what height to move to

It works and is definitely better than sitting all day… but we can do better than that, right?

Yes, we can.  My desk is now voice-activated via Amazon Alexa!

Isn’t that better?

How does it work?

There are 3 parts to the integration:

  1. Alexa Skill
  2. Azure-hosted API
  3. Desk Controller

voicesolution

Alexa Skill

Amazon has an SDK for the Amazon Echo family devices called the “Alexa Skills Kit“.  In short, the Alexa skill contains 3 things:

  1. The things your skill can do (called intents)
  2. Sample ‘utterances’ and how they map to the intents
  3. Instructions on how to call your program

Your program can either be an Amazon Lambda program, or it can be a HTTPS API that the Alexa service will post a message to.

It’s easy to set up a simple skill to get started.  Check out the Amazon developers site for how tos, tutorials, etc.  Or if you want to learn in a bit more structured way, check out “Developing Alexa Skills for Amazon Echo” on Pluralsight.

The speech assets for my desk are on github.

API

The API is simple and does 2 things:

  1. Receives commands from the Alexa service and translates the intent and parameters to a desk command
  2. Responds to the desk controller’s requests for command.  The desk is using a long-polling mechanism to get commands.

The code is here (disclaimer: this is hack-it-together code, not production quality!)

Desk Controller

The desk controller uses the python program I had previously created to control the desk, but adds long-polling to get commands, rather than waiting for someone to type into the console.

What’s Next?

The program has lots of room for improvement, the Amazon process for certifying skills is rigorous, and the interactions with the desk will get better as I find the terms that I want to use to control it.

Have feedback?  I’d love to hear it.  Leave a comment or reach me @_brentonc on twitter.

Building a… hmm, what’s it called?

I’ve been quiet lately.  We’ve been busy with work, kids, new puppy, and building a….  not sure what to call it.

People around us, at work for example, say it’s a farm.  But don’t you have to plan to sell food if you’re a farm?

For a while, I toyed with the word ‘homestead’, but that’s not it either.  Homesteads are pretty serious.

Ultimately, I think we’re just having fun growing our some of our own food and doing something that feels incredibly wholesome.

It started last summer when we got a few chicks.  Caring for them was so easy and so satisfying, especially when that first egg arrived in January.  By February/March we were getting more eggs than we could handle, so we started giving them to neighbors and coworkers.  It’s fun to share, and worth much more as goodwill gestures than $3-$4 a dozen =  $12-$16 a week.

eggs

Then we got the itch to start a garden, and it’s amazing.

wp-1467401532520.jpg

 

We’ve made lots of mistakes, but you have to start and every mistake is an opportunity to learn.  Every meal now has something we’ve grown ourselves, especially kale and lettuce but also some peas and carrots.  And the tomatoes are coming, and the jalapenos, habaneros, onions, garlic, brussel sprouts.  And maybe even a few raspberries and blueberries.

In April we received our first batch of meat chickens – we ordered 15 birds from Murray McMurray hatchery.  We received 16 Red Rangers and one other rare chick that the hatchery throws in.  One needed to be culled after she got hurt and couldn’t walk, but the others are doing great.

birds

We’ll be processing them in late July at 12-13 weeks of age.  I’m not looking forward to it, but we feel that we should process them ourselves.

And finally, we are getting four Clun Forest sheep – 3 ewe lambs and an older ewe – at the end of the month.  Here they are with their brothers & sisters at the breeder’s place:

clun

Along the way, I’ve started to become super interested in all the plants growing out in our pasture.  At first I just saw grass and weeds, but I’m started to appreciate better what they are.  Weeds are nature’s way of repairing damaged soil, and we’ll see if we can help out with some carefully managed gazing and manure additions.

So…  what do you call that?  I think I’m just a guy that likes learning and doing things himself.

Standing Desk: Wiring 6 relays to 2 GPIO pins

A comment on a video about my desk recently asked,

I’d like to know how you wired up everything (the pi to the relayboard) using 2 GPIO pins. Could you please take a picture and upload it to your blog?

Good question, Jake.  Here’s a picture.

wiring-numbered

 

But that’s not too clear, let’s break it down.

  1. This gray band connects the RPi to the breadboard to make it easy to make multiple connections.  But you can connect directly from the pins to the breadboard; just make sure you bring power and ground as well.  And you’ll beed male/female connecting wires to make the connection.
  2. Connect the 5v power (red wire above) and ground (black wire above) to the power/gnd pins on the relay.
  3. The breadboard lets us connect multiple wires to a single pin.  When that pin is ‘on’ all three connected wires are signaled.  In the picture above, the 3 green wires on one pin; the 3 blue wires are connected to a second pin.
  4. The green and blue wires are connected to the relays in alternating pairs.  Each one turns on one relay when signaled, so each time the pin on the RPi is on it triggers 3 relays in my case (one for each actuator in my desk).
  5. For each of my actuators I use two relays.  This allows the signal to be reversed by flipping which switch is on, thereby telling the actuator to extend or contract.

So, after all this, the code to extend, retract, and stop is easy!

comments

Good luck!