Back in 2013 I moved from using a very good Windows program called mControl for home automation control over to Indigo for Mac OS. mControl worked great for my needs then but I didn’t want to dedicate an additional computer to the home automation and video recording tasks since I usually left my iMac running anyway.
Indigo looked like an excellent choice and over the years and it has indeed proven to be a great software package for home automation control from a Mac. I realized that even though I’ve blogged about some of the things that I’ve done with Indigo I haven’t really mentioned my overall experience with the software.
It’s now on version 7 and though the cost has risen this is largely due to improved software support and the inclusion of the required licensed technology needed to control Z-Wave compatible door locks. Indigo is very extensible; one can find a number of community-built plugins and it also supports scripting via Python.
I wouldn’t recommend it for someone that isn’t very tech savvy; there are other consumer appliances more suitable for basic home usage, but if you want to do anything more than have a few automated tasks (for example, anything that requires a good bit of logic and virtual devices or variables) you’ll need something like Indigo.
At our house I do use a Wink system and it works fine there but it’s not capable of doing much more than running a few automated tasks; consumer appliances (usually cloud-connected) currently don’t offer very much in this realm. But at the apartment I’m still using Indigo and have moved into some more advanced home automation interactions.
With Indigo I now have several actions that are dependent on the status of other devices, virtual devices and variables. I’m also using some Bluetooth proximity detectors to provide additional enhancements and in the past I’ve done some more interesting things that I currently don’t have setup.
I highly encourage anyone with more than a passing interest in home automation, and a Mac that you’re willing to leave powered on all of the time, to look into Indigo. The initial cost may seem high but when you consider the basic cost just to purchase a consumer appliance hub such as Wink or SmartThings, and then potential issues with any of your existing equipment, you may find that the savings aren’t really there in the long run. Indigo works with X10, Insteaon and Z-Wave devices as well as some other devices that don’t use those protocols.
Back at the house the cable modem and router usually operate just fine but every now and then something hangs up and unfortunately it’s not always practical to go by to reset the gear. And asking a friend to do it for me, even when they’re eager to do it, just seems unfair.
So I searched for a device on Amazon.com, as usual, and sure enough someone has a product that is intended for exactly this need. The NetReset NR100US, which cost about $45, can be set to automatically reset the power to both outlets on the device using a set delay between them. It will turn off one outlet for a minute, turn it back on, and then a minute later do the same for the next.
We’ve had a threat or two of a hurricane in our area over the summer and into the fall so more than once we filled up the tubs to store water for flushing the toilets and rinsing things. The largest tub in our place can hold a lot of water but unfortunately it had a slow leak at the drain that over the course of several hours was too severe.
Fortunately I found a very simple solution: electrical tape.
Building a seal around the drain and the drain cap slowed the leak to a point that I couldn’t even tell if it was leaking any more.
A few years ago I purchased a Blitz 6.5 Gallon Water Can just in case we had a major hurrican that would knock out power at the house. Though I did fill it a couple of times we did not end up using it (yet).
But one day I lost a cap to a gas can and was in desperate need to replace it. I discovered that the water can’s cap would fit perfectly and so that’s where it ended up. Of course, once used on a gas can it simply wouldn’t be good to use on the water can again.
This year I decided to bring the can to our apartment to prep for hurricane season but unfortunately it still lacked a cap.
Our run as cord-cutters has come to an end after several years though it wasn’t by choice; the apartment complex where we live has made a fee mandatory that includes the cost of cable and since there’s no point paying for cable and not using it we decided to cut some of the online streaming services that we’ve been using and get a DVR from our cable provider.
Living as cord-cutters for over six years worked great but that’s a post for another time.
I opted to get an X1 DVR from Comcast so we could record shows (we chose to drop Hulu and HBO) that we would have watched via Hulu as well as some other series that we’ve been purchasing through iTunes over the years.
I don’t know what causes this problem but recently I discovered that the “Default web browser” setting in the General preferences tab was blank. Clicking on the drop-down showed no browser names so I could not change the use of Safari as the default browser.
The fix was relatively simple. I opened Chrome and via settings within Chrome I set it to be the default web browser. After completing this action I then had the names of the installed browsers in the “Default web browser” drop-down.
This fix may work using any browser that allows you to set it as the default from within the browser settings itself.
Sometimes it’s practical for the same person to setup multiple accounts on one machine for distinct purposes. While the fast user switching feature in OS X does make it easy to quickly move between accounts some people may find it more practical to be able to interact with the desktop of a different account while still logged into another one. If you’re this kind of person then you may find this post useful.
The method I’m using, which is based on information that I found in some forums, involves using Screen Sharing to connect to a different account on the same machine.
All of the necessary features are already built into OS X but unfortunately they won’t work in this scenario (by default). If one enables Screen Sharing, and then attempts to use the Screen Sharing app to connect to the local host, the screen sharing app will not connect and instead state that it cannot connect to the same computer. I’m not certain why this check is actually needed but it turns out that the check for enforcing this is not sophisticated.
It appears to only be checking for a connection to the local machine on port 5900 so changing the service to use a different port will work.