Categories
Technology

Smart Home, Older House, Cold House

Update:

Several publications have come out today, including one from the New York Times, about a software update being responsible for the battery drain. That’s one bad bug, and Nest is going to take a major credibility hit because of it.

We also had problems with our Nest Protects (smoke/carbon monoxide detection) a few weeks prior, with none of them being able to access the cloud. However, they work without wireless access, including the ability to connect and communicate with each other, so it was more of a nuisance than a problem. I do wonder, though, if the same bug didn’t get introduced into all Nest products.

In the meantime, adding a C wire didn’t work for us. It would have required too many holes being drilled, and damage to floor and wall. We’re going with the add-a-wire feature, instead.

Earlier:

Our home was built in 1986, which means it’s on the border between modern, new standards and the old way of doing things.

When we tried to add new GE smart light switches, we found that most of the switches don’t have a neutral wire needed to power the switches. The old, unintelligent switches didn’t need power—they’re just on or off. The new ones, need power to communicate with the controlling hub and other compatible devices.

The same applies to our thermostat: we don’t have a ‘C’ or common wire that runs from the heating/cooling system to the thermostat.

We have a second generation Nest thermostat, and not having a ‘C’ wire is supposed to not be an issue with this thermostat—at least with most HVAC systems. The device gets its power from the “red” wire (the power line) by “power stealing” a little bit of the power that comes through the line. The problem with this approach is if the system is very active, the device doesn’t have a chance to charge the battery as frequently and you can lose thermostat functionality, or even drain the battery.

The other issue is if the HVAC equipment isn’t running, at all, and the device needs power. What the Nest thermostat does is “pulse” the equipment to get a bit of juice, but supposedly very quickly, so that the equipment doesn’t come on. If this doesn’t sound like something you would want to do,  you’ll get agreement from many HVAC manufacturers.

Then there’s the situation that happened last night. It was very cold, so the system was running intermittently  through the night. In addition, I suspect from chatter in the Nest forum, the thermostat received a software update in the night. I also suspect that the software update drained what little power the battery had, to the point where I was faced with a completely black device this morning. I couldn’t even run it manually.

When the temperatures are below freezing, you don’t want a thermostat that doesn’t work. At this point, you’d settle for a dumb thermostat, as long as it turns on the heat.

I knew I could power the device using a micro-USB cord, connected to my computer. I connected it for about a half hour, charging the battery enough that I could connect it to the wall plate and turn on the heat. Of course, while the heat is running, the device isn’t charging, but it should have enough juice to take the chill edge off the house.

If we weren’t at home, I’m not sure if the device would have even been able to start charging without my assistance. Normally, the Nest thermostat shows a blinking red light when the battery is very low and charging, but it wasn’t showing this light this morning. It was completely drained.  We could have come home to frozen pipes and damaged walls.

Assurances from Nest aside, it’s time to update our wiring. We have a couple of options. One is we could attach a Venstar Add-a-Wire Adapter, which turns a 4-wire setup into the 5-wire setup needed for smart thermostats. Or we can run a ‘C’ wire from the HVAC to the thermostat. Though the latter approach is more expensive, we decided if we were going to fix the problem, we’d do so without a hack and we’d fix it once and for all.

Tomorrow morning our HVAC company is coming out to run the new ‘C’ wire to the thermostat, and hopefully we’ll never again wake up to a freezing cold house. If we do, than the Nest thermostat is being replaced by an Ecobee.

 

Categories
JavaScript Writing

My latest, and last, book for O’Reilly

I said a few years back that when Node.js released version 1.0, I’d issue an update for my book, Learning Node. Little did I know that waiting for Node.js 1.0 was like waiting for Godot, but in JavaScript.

I did try to do an update on the first edition of Learning Node earlier this year, but the changes were just too significant. So many of the modules I covered are no longer supported, Express 4.0 happened, and then there’s that Node.js/io.js thing, and skipping version 1, altogether. The first edition of Learning Node just can’t be updated, in place. The only solution was a new edition. It’s also a good time to do a new edition: there’s more stability in the development of Node.js, and less personal ownership.

I just hit the half-way mark in Learning Node, the second edition. It should be out for early release in January or so. The finished book should be in the market some time around April/May. We took a different direction with this book: smaller, learner, and staying closer to the core of Node.js. I’m very happy with the direction it’s taking. It’s the Learning Node book I probably should have written, way back in Node.js’s infancy.

Of my books, I finished JavaScript Cookbook, second edition earlier in the year, and I’m happy with it. I like the design of the book, and feel it’s nicely comprehensive. A new author has taken over for the Learning JavaScript series, beginning with Learning JavaScript, third edition. I’ve been chatting with O’Reilly about releasing Practical RDF to the public domain. With the second edition of Learning Node on its way to completion, I feel it’s a good time to ease my way out of writing books for O’Reilly, and finally take the plunge to self-publication.

My first book for O’Reilly was Developing ASP Components, published in 2001. It actually hit the Amazon top 100 bestselling books list for a brief moment. In 15 years, we’ve managed to publish 16 books, and I’m proud of all the work we’ve done together. O’Reilly has been a good publisher, and a good company to work with. They’ve always been supportive of my efforts. I’ve enjoyed working with the people, including, and especially, my long-time editor, and friend, Simon St. Laurent.

Categories
Technology

Alexa as service, Echo as interface

Today, Amazon released new versions of its tablets, as well as a new Fire TV. The latter is generating interest in part because Alexa has been added to it. This means you can use the new Fire TV in a manner similar to the Echo, and be able to play favorite TV shows, too.

The new device supports the new 4K Ultra HD in addition to 1080p, promises to eliminate buffering, supports all the popular streaming apps, and has voice search enabled on the remote. I hope Amazon has improved the remote, because I’ve found that Echo’s remote is no where near as sensitive as the Echo device is, itself.

I like the video support, but I have a Roku and I don’t have a 4K Ultra HD TV, yet. What I’m more interested in, is the Alexa integration. Watching the demo video at Amazon, Alexa will display an answer to the TV rather than verbally.  (Engadget notes this, also.) If you have it play music, it uses your TV’s speakers.

Of course, this is a double-edged sword. If you have an Echo and the new Fire TV in the same room, you’re going to have contention over which device answers when you call out, “Alexa…”. While watching the Amazon demonstration video, my Echo responded when the voice in the video asked, “Alexa, what’s the weather?” I’m rather hoping that Amazon gets away from only allowing one to use Alexa, or Amazon, as the device voice indicator.

I’m also assuming you do have to have the TV on for the device to work. Currently I use Echo’s timer functionality, as well as have it play music while I’m working. I wouldn’t want to turn my TV on for both. In this regard, Echo wins. Echo also has smart home integration, which the Fire TV currently lacks.

From a developer perspective, the Fire TV demonstrates Amazon’s new Alexa Voice Service Developer Preview. If you’re a developer, and you have a device with a microphone, a speaker, and an internet connection, you can interface with Alex as a service. First thing that comes to my mind is this opens up some interesting possibilities if you like to tinker around with microcomputers, such as Raspberry Pi. However, I’m not sure how open Amazon is to people tinkering with the service. The sign-up for the developer kit seems to assume you’re a developer for a company with a product to sell.

Like Roku.

This new developer kit joins with the existing Alexa  Skills Kit, where you can create an app that can be installed on an Echo (and possibly other Alexa devices, eventually), such as my favorite, Cat Facts.

Node.js developers, note that Node.js figures heavily with both kits. See? Your mad  programming skills just found a new outlet to explore.

Amazon made, what I feel, is a very smart move with its recent innovations. Rather than compete directly with device companies who control marketplaces, such as Roku, it’s taking the same type of functionality (video streaming), and integrating it into the smart home controller environment. It’s similar to Google’s new OnHub, which takes Wi-Fi routing into the same environment.

Exciting times. Let’s just hope security is considered first, rather than last, with all this cross-line innovation.

 

Categories
Burningbird Technology

Server is moved

Moving to a new VPN (Virtual Private Network) was as simple as signing up for a second Linode instance, and then building it to my specs. Eliminating half the cruft I had on my old system saved about 40GB of space. Now I have room for all new cruft.

I decided to stay with Drupal for this site. Frankly, I just don’t want to muck with content systems anymore. I have a couple of new sites on WordPress, this on Drupal, and that gives me a foot in two worlds. I was reading that the Drupal 8 upgrade should be button-press easy, especially if you haven’t customized your site. Sure sounds simpler than fighting to get it into WordPress.

Linode’s new billing system made the move a whole lot easier, and cheaper. I was only charged for the double VPN until I dropped the original once the move was finished. I think I’ll take this approach the next time there’s a major Ubuntu upgrade. Not only can I cleanly upgrade, this approach gives me a chance to clean my system.

Categories
Burningbird Technology

Mind the scaffolding

image of destroyed front porch

I have attempted to upgrade to Ubuntu 14.04 from 12.04.5 three times, failing each time. The points of failure are complex and seemingly many. I can ignore the necessary upgrade until 12.04.5 hits end of life in 2017, but whatever cruft is preventing a clean upgrade may be allowing all sorts of bad things. I also use my server as testing environment for all of my books, which means I’m constantly installing and uninstalling a host of software. When I ran

ubuntu-support-status

I was surprised at how many packages I have installed that are no longer supported.

No matter how much I want to avoid it, It’s time to clean up my system.

Not just clean up. I want to move my site to HTTPS/SSL. The new Let’s Encrypt Certificate Authority should be in business in September, simplifying the process for obtaining an SSL certificate, and removing a major obstacle for making this move.

I’m also looking at migrating my site(s) back to WordPress from Drupal. Drupal is a marvelous CMS when you like to tinker under the hood, or you have a business site that needs extensive customization and complexity. But it’s not a good CMS when you don’t have the time to tinker, and you just want a place to write. With the upcoming changes for Drupal 8, I realized that I could either migrate to the new version, or I could migrate to WordPress: the work would be the same.

The advantages to WordPress is it is geared more towards just having a place to write. There is also more updated support for social networking, commentary, mobile devices, and a larger pool of weblog themes. Drupal is powerful, but I’m finding many of the modules I’m interested in have erratic support, at best. The Drupal environment is set up in such a way as to channel all interest in a certain functionality into one module. This is fine, except when the module developer tires of it, and no one picks it up. WordPress fosters a more competitive environment for functional extensions, so you’re almost always going to be able to find a supported plugin for what you need.

Moving from WordPress to Drupal is a snap, but the reverse isn’t true. In fact, it’s been downright ugly in the past, requiring either a great deal of hacking, or an expensive migration service. Thankfully, this has changed with a new PHP script and associated tutorial, both of which help remove most of the pain. I hope.

I expect, though, that my site will end up even more fractured than it is now, with my many moves between domains, weblogs, and software—not to mention removing dated content, and merging and splitting weblogs. Such is life. One of the advantages of today’s web environment is it’s adaptable to change. A broken link is no longer the anathema it once was, and 404 errors are like gray hair and bad knees: a sign of increasing maturity.

All of this is my way of saying that things are going to be erratic around here for the next couple of months. Of course, I’ve been so quiet in my space for so long that folks might not even notice the erratic nature of my web site. I’m hoping to get better about this, too.