Technology meets the smoke detector

We needed a new smoke detector. I was tired of having to unplug the current one every time we fried fish 😉 so I thought I’d shop around some and see what features are there. I also wanted to see how these “connected” detectors worked so that you could get an alert if not home. Kidde has an interesting device that listens for the sound of standard detectors and then can communicate with you remotely. I then looked at the Nest Protect (2nd generation, and now $30 cheaper than before they had to disable the “Nest Wave”), and it had some nice features and was the same price as the Kidde device. One appealing feature was that in addition to remote notification, it had the “I’m going to alarm, is this really a problem?” mode (they call it the burned popcorn feature). Also sounded like “frying fish” mode!

So, I ordered a Nest Protect (wired) and set it up. Then cooked Cajun Mackerel, yummy! Sure enough, while cooking the 2nd filet (the stove is less than 10 feet from the detector), the Nest Protect says in a nice voice, “I’m going to alarm, and it will be loud. Do you want to silence?” I did, and it quieted down. It keeps a log of events, it tests itself, it interfaces with and alerts your phone, it can be a nightlight, and it’s very friendly. If there is more than one on your network, it tells you the location of the problem in clear language, with all broadcasting (so say the docs). OK, sure, it generates data and sends it to the mothership to make the magic happen. But if I want the conveniences of technology that’s a price I pay.

I like it so much I ordered a second one to replace the other detector in the house. I’ll follow up with more info as I get the next one online.

Reflections on the Apple Watch

Much ink (metaphorical and physical) has been spilled with regards to Apple’s first wearable device. I won’t attempt to write a comprehensive article, as those are best found in the various trade journals where folks are focused on such endeavors. My contribution here is just my “n=1″ sample of myself.

I ordered my Watch (the 42mm Sport model with a black band) on April 10th, so where around mid-morning. Since orders went live at 3am EDT, I knew I’d be well back in the queue, and sure enough, my ship date said “June.” That was OK, though, as I was inspecting my eyelids at 3am and didn’t want to try to get in the first tranche of shipments. I was thrilled, then, to get the notice on May 29th that my Watch was on the move! I got one of the most interesting UPS tracking displays I’d ever seen, as I watched it move from China to the US on its way to Chapel Hill.

  
It arrived around mid-day on Monday June 1st, and I was eager to give it a try. Alas I had meetings for most of the afternoon. I did carve out a few minutes to unbox the Watch and begin the setup process, so I could play when I got off my WebEx’s. The box was heavy and odd-shaped for a watch (long) but I remembered reading about this and the way they came with the band flat. I pulled out, skipped the setup documentation, and fumbled for the power button. As there are only two choices, it was a short search. Voila! An Apple, the symbol of a booting iDevice! I went thru the setup screens, told it to load all the apps matching those that I had on my iPhone, and it worked for a while while I did the same. It occurred to me that the battery charge might be low, but it wasn’t complaining and I didn’t see at first how to find the charge level.

When my calls were done, it was playtime! So I started pushing, twisting and poking. I’d read that the interface was not intuitive but it seemed logical to me. I tried apps, set watch faces, and started to make it mine. Ok, I did cheat. I couldn’t figure out how to find the battery charge. Google. Oh, doh! Glances, and a swipe thru the options. Ok, I couldn’t figure out how to change the world clock time on a clock face. Google. Oh, doh! Just select the widget and then spin the crown wheel to select. Overall, things really did work the way I expected. 

It’s now been about 30 hours since I got the Watch. What do I think? Very cool. Feels good on my arm. I’ve not worn a watch in years, but it’s light and unobtrusive. Battery life? I’ve been playing with it a lot today, and it’s been over 14 hours since I took it off the charger. Battery indicator says 52%, so that’s not an issue. What can you do with it? It does tell time very effectively! It lights up the face when you raise your arm to look. It alerts for text messages, and the voice recognition for reply is better than expected. I’ve made a phone call, ignored a call, and sent several texts. I’ve read a lot of email previews. The Gmail app works nicely with the alerts and has a lot of flexibility , and you can archive messages and remove them from your inbox. Apple’s mail app works well, too, but the way Gmail segments your mailbox lets me control which messages appear on the Watch better. The biggest shortcoming I’ve seen so far is the inability to respond to email, even with a canned phrase. I understand the design decision but I hope this gets updated to add reply functionality. I’ve not tried the exercise app yet, but will do so. MotionX GPS has a nice app that I know I’ll use. I like the timers and stopwatches. The activity monitor will encourage movement and fitness. The weather apps are handy. I’ve added my credit cards for Apple Pay but have not had a chance to use it yet. My phone is a 5S so I’d not been able to participate in Apple Pay and I’m looking forward to it. I like the news alerts from the NYTimes and others. The presentation remote control apps for Keynote and PowerPoint will be useful; I have a projector dongle for my phone, and it’s handy to have a remote to drive the presentation from the phone. 

The bottom line there is a lot you can do with the Watch. I’m eagerly looking forward to new apps and software updates as the ecosystem matures.

White Bass 2015

I practiced some defensive calendaring today (which is pretty bad for a retired dude, but the part-time job can create some schedule challenges 😉 ), marked off the afternoon, and drove about 20 miles from my house to where the Haw River runs into Jordan Lake (central NC). The spring weather was spectacular, with temperatures in the low 80’s and blue skies. It’s “yellow season” with the pine pollen every and spring busting out all over. My goal was to catch some white bass on their spring spawning run up the river.

haw_view_1_2015

Haw River View

I got to the Robeson Creek canoe landing about 1:30PM, after taking care of a few things in the “office” during the morning. I rigged up, and headed down the trail from the parking lot. I crossed Robeson Creek, and walked upstream past the end of the impoundment to the running water. There were a few fishermen around, mostly with buckets they were hoping to fill, and I walked upstream to a pool that had worked for me in the past.

The water was pleasantly cool and perfect for wet wading.  The water level was low, and the river was clear.  If the water had been high or stained, this wouldn’t work, as the Haw is like wading on greasy bowling balls.  It’s a big river, and if the water is up, it gets too deep pretty quickly. I cast a black sparkle wooly bugger a few times, but I wasn’t feeling the love with that fly. I put on a white Shenks’s streamer, and immediately hooked up with a nice little white bass. These guys can put quite a bend in the rod, especially when they leverage the current.

white_bass_2015

Haw River White Bass

 

I fished for about two hours, an hour in one place, and then moving upstream to another spot for another hour.  I caught about 15 white bass, several small largemouth bass, a few sunfish, and one nice black crappie (below). All fish were on the same white Shenk’s streamer. All the white bass were medium-sized males.  I didn’t see any of the larger females; they’ve not come up the river yet.

Nice black crappie

Nice black crappie

About 4PM, I decided I’d had a great day, the bite had slowed, and I headed for shore and the trail back. Got back home before 5PM, in time to sit on the porch with my wife and a glass of wine.  Not a bad day!

Another day at Clearwater

Two days of fishing in the last three?  Wow! Sam and I met at Camp Clearwater today to try for winter-stocked trout (too warm here in the NC piedmont for a natural population). This is such civilized fishing.  Leisurely morning at home, walk the dogs, breakfast with the wife, newspaper, coffee, and then drive less than 15 minutes to get there. Since the gate opens at 9AM and there were only 6 rods scheduled, no need to rush :-) .

I met Sam in the parking lot at ~9:20 and compared notes on flies to try. The last time we’d ben out, the key was small midges (#18 or #20) as droppers below a dry as an indicator, primarily. We decided we’d stick with that, and the telemetry from the Lake Master was that this would be effective. It worked, but was slow, technical fishing. Trout were madly jumping all over the lake, sometimes hitting the dry indicator, most times nudging the dropper, but were devilishly hard to hook, especially on long casts, and then hard to keep on the hook. I managed to land several over the course of the day, most hitting a “Sweet Thang” tied by Sam, a tiny #20 bead head with a brown wire-wrapped body. Hell, I can hardly see ’em much less tie ’em!

clearwater201503-1

Clearwater Rainbow

At one point, Sam and I were casting from a long dock, with another angler between us. We were both catching fish, and he was getting skunked.  Sam passed him a Sweet Thang and he got two in short order. Keeping with the osprey theme from my post last Friday, as we stood on the dock, we watched an osprey grab a trout from lake and head to a nearby tree. It hit the water with a giant splash and I first thought a mondo trout had jumped until I saw the osprey.

I caught a few on my dry indicator, a #16 CDC emerger, but mostly, they’d clobber it but miss the hookup.

It was a nice day, pleasantly warm, in contrast to our recent chilly weather.  Nice fellowship with our fellow fishermen and the Lake Master. A good way to spend the day.

 

Shad, ospreys, and eagles

Osprey eating a shad

Osprey eating a shad

 

St. Patrick’s Day, this past Tuesday, was beautiful with blue skies and temperatures in the upper 70’s. Was that the day that I made my annual trek to Weldon for the shad run?  Nope! Sam and I waited until Friday the 20th, with temps starting in the 30’s and topping out about 50, with some drizzle and thick clouds. However, it was the best day for the two of us to get together so we loaded up the canoe on the old red truck for the 2 hour trip.

We didn’t rush due to the cold and rain…rain which was pulling out to the northeast. We timed our drive well, and the rain was finished by the time we arrived. We paddled across the river to our usual spot, but things didn’t look too promising, as we were virtually the only folks at the landing — never a good sign with something like the shad run, where people fishing means the fish are in. However, onward! We beached the canoe and clambered over the rocks to the top of the “Little River,” where the flow splits 90/10, with the small flow being the “Little River.” The water was quite chilly (49F) as I wet-waded through crotch-deep water to our favorite fishing rocks :-) . Invigorating!

Well, to say fishing was slow was an understatement.  However, I did manage a half dozen Hickory Shad, and besides, the camaraderie made the trip worthwhile, regardless of what we caught.

Hickory Shad

Hickory Shad

All the fish I caught were on a single orange fly…orange chenille body, orange bucktail wing, with some gold crystal flash added for good measure. This particular fly had bead chain eyes rather than the weighted eyes I usually use, and that may have made a difference but I think it really was more just putting the fly in front of a fish, and I had a better day of that than Sam.

We saw a number of ospreys during the day, mostly as fishless as us :-) but one did catch a fish just a bit down the river from us, and it flew into a nearby tree to eat the shad while we fished. We also saw a bald eagle, also clutching a shad, on the far side of the river. In the past, we’ve seen wild turkeys fly by, but none today.

All in all, a great day of fishing, so-so catching, good bird watching, and great fellowship.

I still like ChromeOS but I also like my new MacBook Air

MBA

Those who happen by this blog know that I like Google’s ChromeOS. I’ve got two Chromebooks, and have written a number of posts about ChromeOS. However, there are a handful of things that I need to do that I just can’t do well on a Chromebook. One of the main things is the ability to run Cisco’s WebEx software. Support for ChromeOS has been “coming” for a long time and given that I spend a lot of my day in WebEx meetings, this has been an annoyance. My employer (N2N Services) uses this as its standard, and I found myself sitting with a Chromebook and connected to the WebEx on my iPhone. Also, while Google Docs is great, roundtrip fidelity with Microsoft Office docs is still an issue. Microsoft’s online offerings are getting much better, but are not there yet.  I use KeePass for passwords, and there’s not a version that works with ChromeOS. FTP/SFTP are possible with web-based tools like NetFTP, but kludgy. SSH works with an app, but is kludgy. The Chrome shell is OK for a few things, but want to run cURL? Nope. Can’t run Skype. But, I love the quick boot & online or SSD storage, and the small light form factor. So, I decided to get a MacBook Air.

I’ve got an iMac at home so I’m quite conversant with OS X. But which Air to buy. Yes, I know that refresh time is coming up, but you can drive yourself crazy with that. I decided to get the entry level 11.6″ 4GB RAM/128GB SSD model. I was a bit concerned about the RAM, but after 24 hours of using this, I can say that this is one sweet laptop. The screen size is like my Chromebooks, so no issue there. Boot is very fast, but then again, I don’t boot my Macs often anyway, and return from sleep is instantaneous. Very nice build quality and keyboard. Beautiful screen, even if it’s not as hires as the 13″ MBA. I wondered if I’d regret not going with the 256GB SSD, but after loading everything I want, I still have 85GB or so free. I’ve not had any issues with the RAM, and honestly, I guess swapping to SSD is going to be pretty fast. The weight at 2.38 pounds is nice. The difference between 2.38 and 2.96 on the MBA 13″ is one of the main reasons I went with the MBA 11″.  I’m going to work hard to keep most stuff in the cloud and not on the MBA, and to not try to overload it with things like Xcode 😉 . There’s a sweet spot here with the MBA!

So, yes, I still like ChromeOS and think it’s a great solution for many things…but it’s just not quite flexible enough…yet…

New platform for the Flyfish listserver archives

I spent a bit of time this weekend knocking a job off my digital “todo” list. Back last fall, the old Parallels virtual machine that ran the Flyfish listserver archives finally succumbed to old age. It was a very old instance of Red Hat Linux, but the virtual disk had become corrupt and would not stay up. I had copied all of the data, configurations and programs (WAIS/free-WAIS-sf) to my iMac, but had been procrastinating on trying to rebuild.  I wanted to change Linux distros and I figured I’d probably have to re-make all the programs, and was “looking forward” to compatibility issues when I set it up. However, cold, nasty weather is good for hacking and not much else, so, I started the process.

I decided to run a basic server installation of Debian. I didn’t want any of the GUI and it seemed that this was going to be one of the best platforms to grab a basic installation like this, plus I like Debian and the way the update and program installation work. I first played with it on the Raspberry Pi, which initially came out with a version of Debian. So, I downloaded the ‘Net install ISO (about 280MB), and created a VM.  I then installed the packages I wanted, and set about installing the archive server.

I have almost 25 years of postings to this listserver archived, so it took a few minutes to copy over all that “wisdom.” Then, the Wais configuration “source” files. Then…the binaries for the Wais programs…and they ran! Guess since I built it with gcc and the target was i386, there really weren’t any dependencies from the old platform. I did have to tweak one of my scripts that had a hard-coded path to the cgi-bin directory, which has moved out from under the var/www path under Debian to improve security.

I’ve still got a bit of cleanup to do, including collecting and indexing the postings from 7/1/14 to the present, but that’s a simple task.

The old thing took just a couple hours to set up. Check it out at archives.flyfishlist.org!

More fun with WordPress (Participants Database)

As I wrote back in December, I’ve been working on setting a WordPress instance for the Emerald Isle Parrothead Club. One of the things we wanted to do was to move the membership roster of nearly 400 club members from an Access database (that obviously only one person could use at a time) to a system that was web-enabled so that we could have distributed maintenance. Also, if we could enable web-based membership applications, produce a membership list and other such things, all the better. I decided to see what I could find.  I discovered several software packages (some open source) that worked for clubs, but most of these seemed to be focused on sports clubs with court reservations, etc. Seems that “club” was not a good keyword. Then, I said let’s just see what sorts of WordPress plugins might be available.  I quickly stumbled onto Participants Database, which we’ve now implemented on our test site.  This is a most excellent plugin! The description is:

Build and maintain a fully customizable database of participants, members or anything with signup forms, admin backend, custom lists, and CSV support.

As you can see, that pretty well covered my use case :-) So, we’ve set it up, we have our database schema defined, and have demoed to the Club administrative folks, who’ve enthusiastically endorsed it. My next task is to import existing membership info, make a few more configuration tweaks, get all to give the “thumbs up” and then implement on our production site.

The only thing that didn’t work quite like I wanted is that it’s set up to allow only users with an “administrator” role to export data extracts to a CSV file, though it allows (by default) an “editor” to update data.  I wrote the author on the support forum, and he said the next version would allow what I wanted (the editor to be able to export a CSV). However, I’d already figured out how to patch the plugin to do what I wanted.  Patched one line of code in each of two files, and it works.  I’ll regress those changes when the update comes out…

The bottom line is that if you have a club or organization that has a WordPress website and you want to set up member/participant info, you should check out this plugin.  It’s very flexible about letting you create whatever fields you need to track things, display the things you need, manage administratively, and expose the info you want to the public.  It even has the ability to allow participants to maintain their own info through a “token” rather than a password, to make administration easier…

Playin’ with WordPress

My standard volunteer niche is to be on the technology committee for the organization. Something about 35 years in IT is hard to run away from 😉 . Anyway, I’m on the tech committee for the Emerald Isle Parrothead Club. For several months, we’ve been in the process of visioning a new website that was easy to use, supported distributed editing, and lots of folks know how to use it…hmmm…sounds like WordPress! I’d previously set up a prototype site on my personal ISP space, and everybody was happy with the look and feel.  I didn’t do much but set up the shell, and others on the committee added content and structure, but I was the one in the sysadmin role. The time came to move it to its new home, and an additional complication was that the club domains were on GoDaddy, not 1and1, the ISP I’ve used for years, so I had to learn to speak GoDaddy.

We switched from a domain-only account that had pointed elsewhere to a Linux hosting account, and with that came a new “free” domain. So, I decided that we needed to do things right and have a test/validation site and a prod site, using the new domain for “test.” I use Updraftplus for backups so I transferred the backups over to the new site. I first created a new virgin site, installed the Updraftplus plugin, and then restored the backup. I knew I needed to patch some things in the wp_options table, so I did that first with PHPMyAdmin, but I wanted to do a better job, so I Googled up a really nifty tool, Search Replace DB which had some great features (like an audit mode) so I gave it a whirl. It found quite a few places to fix, albeit most in areas that would have never been a problem like spam comments. Got the prime site working, though I knew I still needed to move it again before finishing, as I’d intentionally put it in an experimental location. I then cloned the database for my validation site, patched the URL’s, copied the directory, and set up the validation site. Then moved the production site again to its final location, patched the database again, fixed the DNS entries, and all was well.

Fun stuff!

Camp Clearwater Trout

I’d been eagerly awaiting the “trout season” at Camp Clearwater lake, just a handful of miles from my house in Chapel Hill, NC. The lake is seasonally stocked with rainbow trout by the local Trout Unlimited chapter and it’s run as an annual cold-weather catch & release fishery. The trout get acclimated very quickly, getting tuned in on the mayfly and midge hatches, and can be quite challenging to catch.

I arrived just after the gates opened at 9am, having booked one of the eight angler slots. While I was rigging up, my buddy Sam pulled up, and we strategized on fly selections for a chilly, overcast day. The morning was above freezing, unlike the previous day, thankfully. I started with a Chili Pepper, having used it to great success at Clearwater in February. I caught a nice trout on my second cast!

clearwater trout 1 (1024)

I had a couple more strikes, but then things went cold for me. Some of the guys on the other side of the lake seemed to be doing better, and we figured we’d swap intel at lunch. I picked up this very nice fish in the late morning, also on the Chili Pepper, but overall it was a slow morning.

clearwater trout 2 (1024)

We saw that some folks were having success with nymphs suspended below a strike indicator, a technique we’d used at Clearwater before. I lost a really nice fish to a bad knot and then promptly landed several nice fish, including this one below, using a stimulator for an indicator with a bead-head flashback pheasant tail dropper.

clearwater trout 3 (1024)

We were casting well out into the lake, 40-50 feet, and the takes were slow and soft, but the action was steady. Then, Sam picked up 3 or 4 fish on a tiny midge dropper.  It was a size 20 bead-head that had a brown body, called a “Sweet Thang,” and it sure was. In the meantime, I’d not had a strike for a while on the pheasant tail, the air was filling with midges, and trout were jumping. I bummed a “Sweet Thang” from Sam, and  we each caught several more nice fish on that combo (again, I had the stimulator as an indicator).

We ended the day with the pleasant feeling that you have when you’ve caught plenty of fish, and when you LDR one, that’s great, since you didn’t have to net ’em. I headed home about 4:30 and lifted a beer to a great time with good friends and fine fishing.