<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Brian Dorton on Medium]]></title>
        <description><![CDATA[Stories by Brian Dorton on Medium]]></description>
        <link>https://medium.com/@badorton?source=rss-ea75cf989066------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*lCWJ37x-hyaJ2LNK.jpg</url>
            <title>Stories by Brian Dorton on Medium</title>
            <link>https://medium.com/@badorton?source=rss-ea75cf989066------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:17:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@badorton/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Build A Better Jukebox]]></title>
            <link>https://medium.com/@badorton/build-a-better-jukebox-892a8e440025?source=rss-ea75cf989066------2</link>
            <guid isPermaLink="false">https://medium.com/p/892a8e440025</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[iot]]></category>
            <dc:creator><![CDATA[Brian Dorton]]></dc:creator>
            <pubDate>Thu, 29 Sep 2016 21:25:01 GMT</pubDate>
            <atom:updated>2016-09-29T21:25:08.571Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TLDve6bzzJsHaw0G.jpg" /></figure><p>As with most projects that are taken on, the conversation starts with a “wouldn’t it be cool if . . .” or “it’s pretty ridiculous that . . . “, or some sort of combination of those two statements. That’s what started my current project. In the office, we have a single speaker that is connected via bluetooth to a device usually streaming a shared Spotify playlist. Many times, this is my computer. And inevitably, I go into an office and jump on a conference call or google hangout, am not able to hear audio, and will be in the middle of trouble shooting before someone comes running in to let me know that the call is being broadcast through the speaker in the main room. Awesome. The other issue could not be more first world. We have been using my Spotify account to create and add to as a community shared playlists. This is such an awesome Spotify feature. Spotify also does an amazing job of suggesting songs you may like based on your listening habits. Since this algorithm is being influenced by the collective, and many times eclectic music in the shared playlists, my suggestions when listening at home are heavily skewed towards ’80s hair metal and ’90s HipPop™.</p><p>So the conversation started. “Isn’t it ridiculous that only one person can connect to the speaker at a time? What year is this?” And then, “Wouldn’t it be cool if we could just have a Spotify server running that anyone on the local network could hit and control the musical selection?” That is literally music to my ears! Pun intended. So, now we know the first world problem we need to tackle. Let’s figure out what tools we need to be successful.</p><h4>The Raspberry pi</h4><p>This one’s a no-brainer. I have been looking for an excuse to pick up a Raspberry Pi 3. Really excited about the built in wifi and bluetooth. All previous pis I have gotten have the Achilles heel that is the wifi dongle. I’m looking forward to seeing if having these built directly onto the board will help improve connectivity. I have typically opted to spend the extra $10ish or so for some sort of pi package on Amazon that includes a power cord, a case and a heat sink. This is the one I got for this project — <a href="https://www.amazon.com/gp/product/B01F2O2ZHO">https://www.amazon.com/gp/product/B01F2O2ZHO</a>. I have enough mini-sd cards laying around, but there are also packs that include one of those. The only thing I caution is, if you’re not careful you could end up spending about $40 extra on an HDMI cable and SD card. It may be a better idea to get the minimum for the project you need and buying the cables and cards separately.</p><figure><img alt="img_1246" src="https://cdn-images-1.medium.com/max/1024/0*mI6EU6UZ1Tzz6aCF.jpg" /></figure><h4>The Software</h4><p>This is where all the magic happens. So first thought was, let’s really take this project on and build a Python server that integrates with Spotify’s API from the ground up. It’s worth mentioning here that in order to make use of the Spotify API, you have to have a paid Spotify account, aka, Spotify First Class. It won’t work on the Economy class plans. While building my own would include designing a user interface, which is not my strong point, it would be a terrific learning opportunity. And this is still something I want to take on someday, there are just too many resources out there that already do a great job. Most roads lead back to <a href="https://www.mopidy.com/">Mopidy</a>, a python server that handles all the business on the backend. This is what we are going to use on this project. We will use <a href="https://github.com/jaedb/spotmop">SpotMop</a> as the front end. More on these later.</p><h4>Time to Build</h4><p>Ok, now that we have the game plan together, let’s gather the materials, prepared the software and get everything installed.</p><ul><li>First we prepare the pi which is by far and away the easiest step. This is just unpacking things, put the hardware into the case, and if you already have a raspbian image on an Sd card laying around, pop it in and see hook it up to a monitor (gonna need an HDMI cable for this one if you do it) and make sure all boots up and the hardware is working.</li><li>Second, let’s download the latest Raspbian for Raspberry image. In this case, we are using <a href="https://www.raspberrypi.org/downloads/raspbian/">Raspbian Jessie Lite</a> as the OS. This is what needs to get written to the SD card. Once this takes place, we can connect the pi to the network via ethernet cable and everything else we need to do can be done in the terminal.</li><li>Now it’s time to prep the SD card. Again, many tools out there to help do this. Basically, you need to format the SD card and then write the image onto the card. Mac, Windows and Linux all have tools for this baked into the operating system, but many times that is the intimidating part for people. Again, there are plenty of tools that make life so much easier. I have used <a href="http://ivanx.com/raspberrypi/">Pi Filler</a> a few times and it works terrifically on Mac OS. A couple of clicks will format and write the image. Done and done.</li><li>At this point, we have a full linux OS on the pi, but there is no interface to the system. So we need to connect the pi to our local network and access the system via SSH. Remember that we have not setup the wifi on the pi yet, so you will need to first plug in an ethernet cable connected to your router.</li><li>First we find the IP address of the pi. I am sure there are a few ways of doing this, but the easiest for me was to log into the router and find the device (raspberry) which will list its IP.</li><li>Then we open up our terminal and simply type:</li><li>ssh pi@yourIPaddress</li><li>You will be prompted for a password which is raspberry by default.</li><li>Once logged in, you can type sudo raspi-config to run the setup for the machine. <a href="https://docs.mopidy.com/en/latest/installation/raspberrypi/#how-to-for-raspbian-jessie">This</a> is a good guide as to what needs to be changed at a minimum.</li><li>Next we follow the steps to install Mopidy. Basically, typing the following will get you most of the way there.</li><li>wget -q -O — <a href="https://apt.mopidy.com/mopidy.gpg">https://apt.mopidy.com/mopidy.gpg</a> | sudo apt-key add -</li><li>sudo wget -q -O /etc/apt/sources.list.d/mopidy.list <a href="https://apt.mopidy.com/jessie.list">https://apt.mopidy.com/jessie.list</a></li><li>sudo apt-get install mopidy</li><li>The extension that we care about the most is the Spotify one, so let’s install that next by typing</li><li>sudo apt-get install mopidy-spotify</li><li>Then there are a few config settings that need to happen that are throughly covered here — <a href="https://docs.mopidy.com/en/latest/config/">https://docs.mopidy.com/en/latest/config/</a></li><li>While this step seems simple, it is likely where most people will get hung up on. Following the instructions linked above should get you where you need to be. It may be a good idea to read a bit about <a href="https://www.nano-editor.org/dist/v2.2/nano.html">Nano</a>, the default text editor for Linux systems, as you will be editing files within the terminal.</li><li>Now that about covers the server/back end of the system. Now we need a UI for folks. <a href="https://github.com/jaedb/spotmop">SpotMop</a> is going to be the choice for this. Very easy to install by typing</li><li>sudo pip install Mopidy-Spotmop</li><li>This is a terrific UI. Has the ability to create and edit playlists and looks really good. If you run into a problem because the system does not know what pip is, run</li><li>sudo apt-get install python-pip</li><li>and you should be good to try again.</li></ul><figure><img alt="The UI" src="https://cdn-images-1.medium.com/max/1024/0*qHvxXk5Dq3d8EmKE.jpg" /></figure><ul><li>One last thing. Now we need to setup the pi to work as a “service”, meaning that every time it boots up, it will automatically start the server and begin listening on <a href="http://raspberry.local:6800/spotmop">http://raspberry.local:6800/spotmop</a> (or whatever you have configured as your hostname.local). Follow the steps <a href="https://docs.mopidy.com/en/latest/service/">HERE</a> to get the service setup.</li></ul><h4>Things to consider</h4><ul><li>Setting up the pi to <a href="https://thepihut.com/blogs/raspberry-pi-tutorials/83502916-how-to-setup-wifi-on-raspbian-jessie-lite">automatically connect to wifi</a> is really easy to do and should be done.</li><li>You should also assign the pi a <a href="http://www.howtogeek.com/184310/ask-htg-should-i-be-setting-static-ip-addresses-on-my-router/">static IP</a>. This can be done on your router.</li></ul><h4>Let there be sound</h4><p>The audio out on a pi is pretty simple. An aux cable out is super easy. Our speaker, however only has RCA inputs. But that’s why god invented Aux to RCA cable adapters! Once it looks as though the pi is up and going, the build’s default address will be <a href="http://raspberry.local:6800/spotmop.">http://raspberry.local:6800/spotmop.</a> Of course, we should certainly go in and change the hostname of the device to make the url something a bit more, uhmmmm, memorable. Once connected, we are able to link up the Spotify First Class account and before we know it, all of the playlists are accessible and we are able to remotely control the music without needing to be connected directly to the speaker. More importantly, I don’t have to continue on with the knowledge that Spotify’s algorithm thinks I’m the world’s number one fan of both Ratt AND Mariah Carrey. (Spoiler, I’m a big fan of exactly half of those). Nooice!</p><figure><img alt="img_1249" src="https://cdn-images-1.medium.com/max/225/0*bLIvwa1u2xLr6Cp9.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*d0uV4528P2WxQcWr.gif" /></figure><h4>Next Steps</h4><ul><li>It would be nice to look into using the onboard bluetooth to connect to the speakers instead of the wired connection we have now.</li><li>Track users additions to keep that person who added Stained to the current playlist accountable for their actions!</li></ul><p><em>Originally published at </em><a href="http://blog.dorton.co/build-a-better-jukebox/"><em>Brian Dorton</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=892a8e440025" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automate all the things!]]></title>
            <link>https://medium.com/@badorton/automate-all-the-things-ca204c82fcd1?source=rss-ea75cf989066------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca204c82fcd1</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Brian Dorton]]></dc:creator>
            <pubDate>Fri, 23 Sep 2016 19:55:01 GMT</pubDate>
            <atom:updated>2016-09-24T17:24:02.347Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4IrBvKCV67QPyF7H.jpg" /></figure><p>I am often asked by our students how I got into programming. I have several instances that I can think of where I saw the lightbulb turn on, but I think my favorite moment came when I saw the power of what writing an automated task can have on productivity.</p><p>Working in a school district, you quickly realize how careful technology departments are when it comes to syncing student data between local student information systems and 3rd parties. And rightfully so! In a district position I once had, I was given the weekly task of updating the format of a couple hundred thousand row spreadsheet for a third party vendor. Our SIS export could not exclude special characters, and records with special characters could not get imported into the third party vendor’s system after it was sent via FTP server. In addition to the characters, there was a 2 page list of step by step instructions on what items needed to be updated. These directions read like “Line 3452 — Remove ` “, or “Change Peterson Elementary to Robert Peterson Elementary”, etc.</p><p>The first time I completed the task, it took me about 2 hours. And every second of the task, I was certain there was a better, more efficient way of completing it. So that weekend, I began doing research how to automate things in Excel. A quick google search later and I found something called VBScript. So I started small, like searching for “VBScript go to row”. I replicated what I found and saw that it worked. Score! Then found a specific character, then updated that character, and so on and so forth. And before I knew it, I had basically reproduced the entire 2 page instruction sheet, only telling excel to do the work this time. I ran the script for the first time, and of course it blew up, but after some debugging, I got the script to run successfully. And it turned a 2 hour task into about 20 seconds. I had a moment that I would only describe as pure excitement. And the best part, other than the amount of time it saved, it also proved to be much more accurate! Shocker.</p><p>Recently I have been playing around a ton with Zapier to build automated workflows. I just love digging in and finding ways to cut out repetitious tasks. Need to scrape data from pdfs and populate google spreadsheets? No prob, use DocParser. Need to tap into web hooks from payment sites and send out custom alerts? Super easy in Zapier. Things get super powerful when you can inject your own Python or Javascript and coax the tool into doing exactly what you want it to do.</p><p>All in all, I’m a huge advocate of automating all the things. It is what excited me to get into programming and continue to improve my skillset. And as my buddy Jwo says, “You know what does repetitive really well? Computers.” It’s true!</p><p><em>Originally published at </em><a href="http://blog.dorton.co/automate-all-the-things/"><em>Brian Dorton</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca204c82fcd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Self-aware machines may eventually rule the world, but at least the BBQ will be good]]></title>
            <link>https://medium.com/@badorton/self-aware-machines-may-eventually-rule-the-world-but-at-least-the-bbq-will-be-good-85cc4ea0d308?source=rss-ea75cf989066------2</link>
            <guid isPermaLink="false">https://medium.com/p/85cc4ea0d308</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[raspberry-pi]]></category>
            <category><![CDATA[bbq]]></category>
            <dc:creator><![CDATA[Brian Dorton]]></dc:creator>
            <pubDate>Tue, 20 Sep 2016 01:01:27 GMT</pubDate>
            <atom:updated>2016-09-30T12:19:28.443Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ofSVr2WNqXv_3eJ0.jpg" /></figure><p>Real talk. So, BBQ is not that intimidating a thing to take on as it seems. I think the reason that more people don’t cook their food with smoke as a flavor enhancer, is because they see cooking food when there is an open fire really close turning into a disaster. When in reality, putting the flames to some lump coal actually isn’t all the difficult to mange with, and this is the key, the right equipment. Because let’s face it, the secret sauce™ to cooking any delicious food is keeping a steady temperature until that food’s optimal temperature is reached. So if you have a way to monitor two temperatures, you come off as a hero to your friends and family.</p><p>Now, I won’t downplay the amount of time you have to invest in this process. It is typically a couple of hours of just getting the cooking temperature correct, before the food even goes on. It’s not unheard of for a large brisket taking 24 hours to complete, from first lighting the coals, to removing the meat. This is a huge commitment. There is a ton of hurry up and waiting during that time. This is where beer helps. Beers with multiple friends also helps. But where things get super difficult is adding kids into that equation. Specifically, babies and even more specifically, my two beautiful daughters. These girls are talented and wonderful in so many ways, but patience one thing they are still working on. So when daddy is coming in and out for the majority of the day and not giving them his full attention, things get dicey.</p><p>So, there had to be a solution for this. And the best solution would be one of automation, per usual. If there were a way to create a “set it and forget it” for the bbq, that would be terrific! A goolge search later shows that there are a ton of devices that help you get there. And for the most part, they are super expensive. My goal was to combine my love for tinkering around with gadgets and bbq. I was going to build my own bbq controller! Even more importantly, I was going to finally learn how to solder!</p><p>After some extensive research in different bbq forums (there are a ton of those, btw), I kept coming across the same term, HeaterMeter. Going down the wormhole, I found that this is a <a href="https://github.com/CapnBry/HeaterMeter">project on GitHub</a> that is documented really well and is perfect for someone who is just getting into hardware to jump into.</p><p>So what was needed to make this happen:</p><ul><li>A Raspberry Pi, to give the pit an ip address and run a webserver.</li><li>Custom PCB board that is labeled well enough that idiots like me can still follow along.</li><li>ATmega Microcontroller that will control/process the inputs.</li><li>About 100 resisters, capacitors, led lights, lcd screen, etc.</li><li>A 3D printed case so all of these electronics aren’t just out in the elements.</li><li>A computer fan to actually control the amount of oxygen the fire gets, thus the temperature.</li><li>And a few temperature probes, obvs.</li></ul><p>To be sure, I’m still not 100% sure what all of the things that I purchased and assembled do, but I am certainly more educated on hardware now than I was before. But I am pretty clear about what happens once all of the parts are put together. As simple as possible, there is a pit probe that is constantly reading the temperature inside the pit. There is a food probe that is constantly reading the temperature of the food. And just for the heck of it, there is an ambient temperature probe, so we can show others exactly how freaking hot summers are in Texas. The ATmega microcontroller is taking in all of this data and comparing against a user inputed target pit temp and target food temp. If the pit temp is dropping lower than the target pit temp, the controller tells the computer fan that is hooked up to the pit’s firebox, to either kick on or speed up. More oxygen. More fire. It’s science! Where things really get cool, it is using a predictive PID algorithm based on past snaps of temps, current temp and predicting where the temp is going to go next, and adjusts the speed of the fan accordingly to hit the target temp.</p><p>So that takes care of the outside part. Awesome! But if there where only a user interface that allowed you to both receive data and set targets. Well, that is where the raspberry pi comes in! Also included in the project linked above is a user interface running off of a super light weight server on the pi. And along with that come alerts and notifications that let you know if your pit is too hot/cold, or your food is ready to come off. This is great!</p><p>The next step was for <a href="http://jessewolgamott.com/">JWo</a> to obviously integrate this into the <a href="https://github.com/jwo/slack-score">Slack-Bot</a> that is already created to troll a friend so that anyone on your team can get BBQ updates by asking for a “bbqbot” to “bbq me”.</p><p>All in all, this was a really great project. I learned a ton about hardware. Delicious, delicious hardware.</p><p>Side note, <a href="https://mkeas.org/">Matt Keas</a> and I recently went on the <a href="https://macrofab.com/blog/">MacroFab Engineering Podcast</a> and talked all about it. It was a lot of fun. This is the episode — <a href="https://macrofab.com/blog/mep-ep20-i-will-never-know-you-viper/">https://macrofab.com/blog/mep-ep20-i-will-never-know-you-viper/</a></p><h4>All the pics:</h4><figure><img alt="IMAGE_1.jpg" src="https://cdn-images-1.medium.com/max/150/0*GdjoNQ9MwZLaPkea.jpg" /></figure><figure><img alt="IMAGE_2.jpg" src="https://cdn-images-1.medium.com/max/150/0*JuIz-mCTve0focR5.jpg" /></figure><figure><img alt="IMAGE_3.jpg" src="https://cdn-images-1.medium.com/max/150/0*sreWiRr9JxF3MI6j.jpg" /></figure><figure><img alt="IMAGE_4.jpg" src="https://cdn-images-1.medium.com/max/150/0*8UWWSzX6oZwzbpYy.jpg" /></figure><figure><img alt="IMAGE_5.jpg" src="https://cdn-images-1.medium.com/max/150/0*yi_mJ-9JhPE3oJob.jpg" /></figure><figure><img alt="IMAGE_6.jpg" src="https://cdn-images-1.medium.com/max/150/0*QCorQoj6SG35vLbX.jpg" /></figure><figure><img alt="IMAGE_7.jpg" src="https://cdn-images-1.medium.com/max/150/0*21JP9fBGFawFbZdC.jpg" /></figure><figure><img alt="IMAGE_8.jpg" src="https://cdn-images-1.medium.com/max/150/0*P6fAbOTD4qIcUQvt.jpg" /></figure><figure><img alt="IMAGE_9.jpg" src="https://cdn-images-1.medium.com/max/150/0*GXjk858JeVZUiTpN.jpg" /></figure><figure><img alt="IMAGE_10.jpg" src="https://cdn-images-1.medium.com/max/150/0*ZJwlXArWemDQaU6Y.jpg" /></figure><figure><img alt="IMAGE_11.jpg" src="https://cdn-images-1.medium.com/max/150/0*kwu5FnuG5FSlJ4im.jpg" /></figure><figure><img alt="IMAGE_12.jpg" src="https://cdn-images-1.medium.com/max/150/0*pv_i99C63vY9HQGh.jpg" /></figure><figure><img alt="IMAGE_13.jpg" src="https://cdn-images-1.medium.com/max/150/0*_ODiUMF85pRnul3p.jpg" /></figure><figure><img alt="IMAGE_14.jpg" src="https://cdn-images-1.medium.com/max/150/0*D_ak9hlf54xgV_EF.jpg" /></figure><figure><img alt="image_2014-04-06_18:54.jpg" src="https://cdn-images-1.medium.com/max/150/0*gIQk_fTvqR1GKtE9.jpg" /></figure><figure><img alt="IMAGE_4.png" src="https://cdn-images-1.medium.com/max/150/0*o-AHoxe9-WADkSm6.png" /></figure><figure><img alt="image_2014-04-08_19:22.jpg" src="https://cdn-images-1.medium.com/max/150/0*d4k_3202j242fq0V.jpg" /></figure><figure><img alt="IMAGE_5.png" src="https://cdn-images-1.medium.com/max/150/0*Hs8Vn1m1KRJKufr-.png" /></figure><figure><img alt="IMAGE_6.png" src="https://cdn-images-1.medium.com/max/150/0*7yAPs-4zAY7Su34x.png" /></figure><figure><img alt="image_2014-04-08_20:58.jpg" src="https://cdn-images-1.medium.com/max/150/0*Syjy79DgtZmDiXDj.jpg" /></figure><figure><img alt="IMG_8567.JPG" src="https://cdn-images-1.medium.com/max/150/0*KG9NJvwKaZpEsEv1.JPG" /></figure><figure><img alt="IMG_8568.JPG" src="https://cdn-images-1.medium.com/max/150/0*ndaG8PdP1dB-Eski.JPG" /></figure><figure><img alt="IMG_8569.JPG" src="https://cdn-images-1.medium.com/max/150/0*VqGcpKvVBVIXfRE8.JPG" /></figure><figure><img alt="IMG_8571.JPG" src="https://cdn-images-1.medium.com/max/150/0*bV9AssDvzhIX_p5u.JPG" /></figure><figure><img alt="IMG_8572.JPG" src="https://cdn-images-1.medium.com/max/150/0*9DNn916x5BlGPuHg.JPG" /></figure><figure><img alt="IMG_8573.JPG" src="https://cdn-images-1.medium.com/max/150/0*fQr0iKBEvdFwTynk.JPG" /></figure><figure><img alt="IMG_8576.JPG" src="https://cdn-images-1.medium.com/max/150/0*T_MPza67alfv4m0V.JPG" /></figure><figure><img alt="download.png" src="https://cdn-images-1.medium.com/max/150/0*UmsPsLYwllFzRB32.png" /></figure><figure><img alt="download_png__700×350_.png" src="https://cdn-images-1.medium.com/max/150/0*9LOJ4hRhSS4StvDm.png" /></figure><p><em>Originally published at </em><a href="http://blog.dorton.co/self-aware-machines-will-eventually-rule-the-world-but-at-least-the-bbq-will-be-good/"><em>Brian Dorton</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85cc4ea0d308" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>