Hello smoke-breathing brethren. Ole’ Sopwith is about to embark on another hacking adventure. This time it is all about home automation. Yes, it seems I am a little late to the party – but hey – at least I showed up!
There are two goals to this project. 1) To learn something new, and 2) To have fun. Wait a minute! Those are the goals of every Sopwith project! Yes – but this project should be really interesting. In this multi-part blog series, I am going to compare the two leading open-source home automation platforms: OpenHab and Home Assistant.
OpenHab is a Germany based open source project founded in 2010. It is written in Java and is based on the Eclipse SmartHome platform. It has a very active community with a very large pool of developers. It provides the ability to integrate hundreds of home automation devices, regardless of manufacturer or whether is it open or closed hardware. The cool thing about OpenHab is that it provides a mechanism to build a complete home automation environment and keep it private.
Home Assistant is another very active open-source home automation platform written in Python3. It also has a vibrant and active community. Founded in 2013 by Paulus Schoutsen, it began as a simple Python script to turn on some lights when the sun set.
In my previous posts in this series (I-III), I added night vision capabilities to the very cool NatureBytes wildlife camera kit. As in all maker projects – improvements had to be made.
Once I placed the night-vision capable camera in the field for testing, I discovered the LISIPAROI IR light board cannot be used in the wild. The device is just not powerful enough. If is fine for close-up work, but outside? Forget it.
It was time to turn disappointment into action. Plus, if it worked out of the box – what fun is that? Time to get serious. As I searched the web, I discovered weatherproof 12V IR lamps are cheap. These are designed to be used with CCTV cameras, most of which are 12 or 24 VDC powered. I purchased a pair for around $16 USD. The one I chose is made by a company called Phenas.
In Part-I and Part-II of this blog series, I assembled the terrific NatureBytes Camera Kit and mounted it on a tripod. I had to wait for parts to arrive before I could add night-vision to the kit. This blog post shows how I modified the camera kit so it can see in the dark.
The goal was to somehow mount and power the LISIPAROI IR light board while still maintaining the weather-proof integrity of the NatureBytes camera kit. The night-vision hack turned out to be pretty simple.
I found a small plastic box with a latching lid in the office supply aisle at a local Wal-Mart. It was designed to store paper clips on a desk, but Ol’ Sopwith had other ideas. The box was the perfect size to install a battery pack, trigger wire and IR light board. Continue reading
In Part-I of this series, I introduced the NatureBytes KickStarter project and finally got around to building the kit I ordered in 2015. I want to hack it so I can capture photos/ videos at night. I need to identify what nocturnal animals are exploring my yard overnight.
The Camera Kit is simply – Fantastic! Details of the kit and the build instructions can be found here. The first thing that struck me was the quality of the bright green case. This thing is an engineering marvel.
On June 24, 2015, a NGO named NatureBytes began a KickStarter campaign to raise money for a wildlife camera kit based on the Raspberry PI. Based in Berkshire UK, west of London, this conservation group set out to encourage kids to get off the couch and explore nature.
Within a month, the campaign raised £34,164 from 303 backers. This was 108% over the goal of £28,995. At that time, Ol’ Sopwith was living in London and was one of 50 backers who pledged £85.
It was expected the kits would ship in December of 2015, but there were delays caused by the complicated molding process used in creating the cases. I followed the updates closely because I felt their pain. Anybody who has ever been involved in the injection molding process of plastics knows how difficult this can be.
As promised, I have updated the AM2315 temperature sensor “How-To” document for modern times. The changes include:
- The removal of the obsolete quickwire library that caused so much pain.
- Removing quickwire also removed the dependency on Python3.
- Added the very capable i2c library tentacle-pi written by lexruee.
- Use of the Raspian Switch OS means these instructions work on any Pi.
- Streamlined 6-Step process.
I have tested the new procedures on every Pi that I have in the drawer. This includes a Pi v1, v2, vA+, v3, and the Pi Zero. Yup – they all work using the same software and the same pinout. Sweet!
You can download the new document and test script here.
For all of you that have contacted me in the last couple of months trying to get your sensor working, I apologize for the delay in getting this document updated.
Hello fellow smoke-breathers. Sorry about the very long absence from my blogging duties. I intend to be more active now that I no longer travel so much.
Over the last several months I have received some Emails telling me the AM2315 temperature sensor code I wrote long ago no longer works. There are a lot of reasons for this. First, the Google code repository has been taken down and folks are having trouble finding the quick2wire code libraries. They are now posted here.
Second, there were some hardware changes made to the Pi-3 and Pi Zero that broke the sensor detection code in my AM2315.py script. Finally, the use of the quickwire code is difficult due to its size and complexity. There are better i2c code libraries available now.
Since the AM2315 is still a popular hacking sensor, I will plug in an alternative i2c library, test the code on the latest Pi’s, and update the ‘How-To’ document.
Standby for the update – ‘ol Sopwith is working on it.
In my last post, I railed about the HP decision to lock down their printer firmware to prevent third party print cartridges from working. Interestingly enough, there has been enough of a backlash that HP decided to respond.
This article from ars TECHNICA describes how HP reacted to the consumer backlash by providing a special firmware upgrade that will bypass the new 3rd party cartridge restriction.
It appears HP has backed off from this crazy nonsense (temporarily) because of pressure from the Electronic Frontier Foundation (EFF) summarized in a letter from Cory Doctorow.
Here is the response from Jon Flaxmen, CEO of HP, Inc. Read it carefully and note the nuance.
I came across this interesting article over at the Wired web site this week. Seems like HP does not like customers who buy their printers to use non-HP ink cartridges. HP has modified the firmware in their OfficeJet, OfficeJet Pro, and OfficeJet Pro X printers to reject any ink cartridge that is not theirs. Essentially they have DRM’d these printers.
It is one thing to know this going in when you bought the printer; but to lock down the device after you purchase it, is evil. For example, if I walked in, say a BestBuy, and was interested in buying a new printer, and the sales guy says, “Remember, if you buy this HP printer, you can only use genuine HP printer cartridges.” Knowing this in advance, I can make an informed decision if I am OK with this “limitation.” If not, I buy something else.
This is not what happened here.
As you well know, the theme of this blog is: “It is works out of the box – what fun is that?” Ol’ Sopwith loves it when things don’t work! That means you have to fix it. Fun!
Today was one of those days when “fixing it” was not fun.
I run a backup server that takes care of all my backup chores. Had it running for years. On all my computers, I run an rsync backup script that backs up everything to this server. The server has a pair of hot-swap SATA drives that get rotated to a fire safe on a regular basis. This setup has served me well.