Instead of creating the doorbell.bat file, create a KWGSrecord.bat file as described in this post: DIY online radio recorder (KWGS update). Change the number of seconds in that file from 10800 (3 hours) to 1800 (1/2 hour), or whatever length of time you want.
Alter the text in DashButton.bat from the first post so it executes KWGSrecord.bat instead of doorbell.bat.
There, wasn’t that easy?
But it can be done, because I just tested it from both our garage and driveway.
You could also keep the button near your home radio for spur-of-the-moment KWGS recording.
Here is a fun and cheap home automation trick I did last week.
Our house came with a wireless doorbell, which sadly has gone to that Great Electronics Recycling Depot in the sky. What to do?
I recalled reading somewhere that the Amazon Dash button is capable of being repurposed via a hack. (By the way, the first button is basically free).
“Amazon Dash Button is a Wi-Fi connected device that reorders your favorite product with the press of a button. Each Dash Button is paired with a product of your choice, which is selected during the set-up process. When you’re running low, simply press Dash Button—ensuring you never run out of your essentials again.”
The hack involves starting up a .bat (batch) file that “watches” for your button push, then runs any other .bat or .exe file on your PC that you have selected, rather than ordering an Amazon product.
Since I was able to create a batch file that activates our X10 chime module, we now have a free wireless doorbell!
Download the latest version of the software, which is in .zip format. Unzip it into a folder on your PC (I put it into C:\DashButton).
Then connect a new, unpaired Amazon Dash Button to your home wifi network. A smartphone Amazon app is needed to do this. First make sure to update the Amazon app to the most recent version. Subprocedure at Instructables; do Steps 1 and 2 only.
Next, I found that “pushing the button you wish to pair repeatedly” per the Readme file’s Normal Usage Instructions didn’t work that well for me.
You can skip directly to the “If you already know the IP of your button” section for testing if you do the following:
Open up a browser on a PC directly connected to your wireless router and type in “http://192.168.1.1” (or whatever the correct IP address is for your particular router’s make and model) to access the router’s management GUI.
You will be asked to enter both a username and password. Typically, they are both “admin” if you haven’t changed it previously. Check your manual.
Find the “DHCP Clients Table” (on my Linksys router, it’s under Status/Local Network). Look at it or take a screenshot.
Push your Dash Button, then refresh the DHCP table and compare. You should see a new “Generic Amazon” device along with its IP address and its MAC address.
Copy down the IP address (e.g., 192.168.1.105) and the associated hardware (MAC) address (e.g., AB:78:BF:8C:9D:19).
Download the free Fing app to your smartphone. When you hit the app’s refresh button, it shows a list of all your locally-connected network devices.
Push your Dash Button, then immediately refresh Fing. You should see listed a new “Generic Amazon” device with its IP address and its MAC address.
Copy them down.
Try again if at first you don’t succeed.
It’s fine to use the IP address from the above for testing in the “If you already know the IP of your button” section of the Readme page, but it needs to not change over time. To accomplish this, go into your router’s GUI as mentioned above, and reserve an IP address for your button. This is where you use the button’s MAC address you noted above. Look through your router’s GUI menu to find where to reserve the IP address by MAC address.
Our router is set up to dynamically hand out IP addresses to devices on our network (that’s what DHCP means), starting at 192.168.1.100. You should reserve an unused IP in the range 192.168.1.2 through 192.168.1.99, or the equivalent non-DHCP range on your router.
My permanent batch file to execute the hack is named “DashButton.bat”. This is needed if you want the hack to run every time you reboot. Here is the text contained in it:
C:\DashButton\AmazonButton_v4.0.exe 192.168.1.10 C:\Users\User\Desktop\doorbell.bat “Comment: place this file in Startup.”
Change the text above to include your button’s IP address, and the location of the .bat file on your PC that you want to execute.
Change the comment to something meaningful to you, or just delete it.
Be sure the quote marks are the straight up and down kind (“dumb”) not the curly type (“smart”).
(I show below how to create the doorbell.bat. You can use any other executable file on your PC for testing, or just to do a different action at a push of the button.)
Double-click DashButton.bat to activate the hack.
Push your Dash button.
If the doorbell batch file (or the file you selected) is executed, then your DashButton.bat is working.
Put a copy of it into your PC’s Startup folder. That way, when Windows is rebooted, the it will be executed during Startup.
The batch file to use with the Dash button hack:
You can use any batch or .exe file you have, but I wanted to activate our X10 Chime module.
I mentioned in the previous post that we already have an X10 home automation system, including a CM15A USB Transceiver Module plugged into our desktop Windows PC.
With the CM15A and free AHSDK software in place, any of our X10 devices (including our Chime module) can be activated over our local network.
My doorbell.bat file has this text in it:
start /d “C:\Program Files (x86)\AHSDK\bin” ahcmd.exe sendplc A9 on
The folder with my ahcmd.exe executable file is C:\Program Files (x86)\AHSDK\bin. Our Chime module is at X10 address A9 (house code A, unit code 9).
Adjust your batch file text to match the location of your ahcmd.exe and the module you want to activate.
Again, be sure the quote marks are “dumb”, not “smart”.
So a new wireless doorbell at zero additional cost.
I could have installed HA-Bridge on one of my Linux-based Raspberry Pi computers (see Corey’s Write for a procedure), but I preferred not to disturb the existing arrangement on our Win 10 computer.
Luck was with me. Just last month, Tuicemen wrote a Windows-based program, Alex10, that uses HA-Bridge (included) to talk with Alexa. It is also more user-friendly than HA-Bridge. So Alex10 was the way to go. (Tuicemen deserves a PayPal tip for his good work if you use it.)
I won’t go into further technical detail about how to do it, but here are the resources I used:
Windows 7 PCs / free Plex &
Emby software to serve music/TV/movie libraries.
Windows 7 PC / free Windows
Media Center DVR with
recordings on external drive.
Raspberry Pi computer w/ free OSMC, PleXBMC, & ServerWMC software
to access content on Win 7 PCs
X10 analog video sender / receiver
Powerline network adapter (4)
Gigabit Ethernet switch (2)
Kinovo HDMI switch
Powered USB hub (2)
(You may have seen the list entitled “Our cord-cutting arsenal” appearing at the bottom-right of this blog. It shows the hardware and software we use for all five of our TVs. But since you can’t tell which items are in each room, I will break it down by room, highlighting the hardware in light yellow.)
The kitchen is now a simple TV room. The TiVo Mini is responsible for that change.
Years ago, because of my wife’s need to watch “General Hospital” recordings while cooking, I put together a too-complicated Rube Goldberg setup. But it was either that, or renting a cable box with DVR dedicated to the kitchen.
She had to switch the den TV to VIDEO1, change its audio setting to SPEAKERS OFF, FIXED AUDIO OUT, and turn on the den X10 video sender. Then she could control the den cable DVR box via the kitchen X10 receiver’s IR extender. (The extender relayed the Cox remote’s commands to the sender, which converted them to pulses from its IR emitter, which was attached to the Cox cable box.)
Then she (or I) had to switch it all back to watch in the den.
Since X10 is old analog technology, it looks best on a tube TV rather than a new flatscreen. We bought a new 13″ tube TV back in 2006 from Best Buy. The picture tube eventually faded, and it had to be whacked sometimes to make the sound work. The microwave fritzed the X10 radio frequency whenever it was used, so the TV had to be muted.
Not great, then barely serviceable.
Enter the TiVo Mini and a new LED TV.
Now all she has to do is turn on the new LED TV and the TiVo Mini, both with the kitchen-dedicated TiVo remote, and select episodes recorded on the TiVo Roamio in the den.
It means discontinuing cable/satellite TV service and getting rid of a landline phone.
Alternatives include over-the-air antenna TV, Netflix and other streaming services, cell and internet phone.
About the two blogs:
Cord-Cutting: The final frontier (achieved on 2/7/2015). Our continuing mission: to explore strange new shows, to seek out new tech and new implementations, to boldly kludge where no one has kludged before. And save $$.
GroupBlog: Posts by readers are primary. Topics include local TV & radio. drive-in theaters, Tiki, general T-Town pop culture. The reverse blog of Tulsa TV Memories, started in 1998.
There is an interesting facebook (Forgive me all) discussion going on that was started by Price Wooldridge, who was a producer for OETA out of Oklahoma city regarding the changes over the years and lamenting some of the losses due to technology. There are a few names that may ring as familiar, and at least […]
Was the German restaurant Paul William Smart asking about Helmut's Alpine Kitchen where Village Inn is now around 27th & Harvard. Also, Bob & Ginny Lazzaro and other family members owned an Italian restaurant somewhere in Tulsa...maybe in 50s? Is Lazzaro part of their family? I grew up across the street from them.
TVs: plasma, LED (2), flat-tube, ’83 CRT
TiVo Roamio OTA 4-tuner DVR
TiVo Mini extender (2)
Mohu Sky 60 powered outdoor antenna
Mohu Curve 50 powered indoor ant
Winegard FlatWave pwrd indoor ant (2)
Winegard FlatWave unpwrd indoor ant
Roku streaming media player (3)
Chromecast streaming media player