X10 Ackis Module
From Makers Local 256
|
Creator: |
Contents
[hide]Overview
X10 allows users to add remote AC power management to any project.
The X10 Ackis Module provides an IRC (and other Ackis clients) interface for any user to control an X10 module.
This could include controlling lights, turning on\off hydroponic systems, turning on\off air conditioning window units,
hard cycling machines, etc.
This system is currently in place at Makers Local 256 as of 2/10/10.
It is not necessary to register an X10 module in order to control it with Ackis.
However, if you would like to password protect your module, please contact omegix@gmail.com
For quick information on how to use the X10 Ackis interface, type "!help" in a channel where Fedaykin or other Ackis instance is running.
Change log
Version 1
Version 1.1
Change log:
- Removed PrimaryON and PrimaryOFF methods
- Added config file support for password protecting X10 Modules
- Added password protection of X10 Modules.
- Added capabilities to run as an external module (running on a different system than ackis_core)
Version 1.0
- Accepts the following commands
- PrimaryON - Turns on the RF Lamp Module (hardset to A1 by manufacturer)
- PrimaryOFF - Turns off the RF Lamp Module (hardset to A1 by manufacturer)
- ModuleON [A-P][1-16] - Turns on any lamp module A1 through P16
- ModuleOFF [A-P][1-16] - Turns off any lamp module A1 through P16
Materials
- X10 Firecracker (in ML256 server closet) (Valued at $6.92)
- X10 RF reciever (in ML256 server closet) (Values at $10.00)
- Machine to host module (in ML256 server closet)
- Ackis Server (in ML256 server closet)
- Ackis Module (this is what was created)
- X10 Flourescent Switch (jeff has) (Valued at $11)
Resources
Software Resources
- http://www.linuxha.com/bottlerocket/
- Note: If using in Ubuntu, you will need to follow these instructions to make the serial connection persist after reboot
- http://www.computechgroup.com/?p=245
- http://wish.sourceforge.net/index1.html (This will likely not compile, it was not supported in Kernel 2.5, and we're on Kernel 2.6 now)
Hardware Resources
Progress
- Have mod_X10 system working at Makers Local 256. Omegix 21:16, 10 February 2010 (CST)
- Realized remote ackis module wasn't implemented fully. Am having trouble getting ackis_core to accept the authentication credentials. Omegix 21:41, 8 February 2010 (CST)
- Changed module access from an ACL to password protection. Omegix 10:29, 5 February 2010 (CST)
- Decided to add some potential functionality to Version 1. Can comment out if it's not ready by the time the swtich arrives. Tried to implement an ACL for individual modules. Startingout by hardcoding the ACL. the getVariable ackisComponent function is causing my method to return early. Omegix 23:46, 31 January 2010 (CST)
- Have ordered flourescent light switch for $11. Spacefelix is going to help me install it when it arrives. Omegix 10:44, 29 January 2010 (CST)
- Resolved !help issues (client_dirc needed a recompile) - Jan 29th
- Functionality of Version 1 is complete (libackis needed some code fixed for 64bit systems). Need to resolve issues with !help not responding. Omegix 17:35, 28 January 2010 (CST)
- Got the Ackis Core, and IRC client up and running. Currently the bot\module can turn on or off an X10 hardware module... once. The core is sending the module the triggers correctly, need to figure out why can't process the trigger more than once. Omegix 23:58, 26 January 2010 (CST)
- Ran into a strange dsss build error. Kinsey found an unterminated string (no end quote). For some reason the compiler didn't report it. Omegix 10:31, 26 January 2010 (CST)
- I've downloaded bottlerocket and got it working with my X10 system. Bottlerocket seems to loose track of the firecracker\serial port after a reboot of the computer.
- Started How_to_write_D_modules
- Kinsey helped me setup a D programming environment. I have D module examples to work with.
Future Functionality
- Allow authenticated user to disable password requirement for an X10 module
- Allow user to retrieve a full list of registered modules, so that no one adds a module to the system that already exists
- If user enters in bad request, have Ackis respond with error message from shell
- Allow users to custom name their X10 modules so that no ackis module maintenance needs to be done to add things like "!Toaster OFF"
- Could store these entries to database
- Could build in capability to write to config file
- Support for Motion detectors. Could use this as a shop occupancy indicator of some sort.
- Support for pulling module status (Ex: Is Module On / Off?)
- According to this page the firecracker hardware cannot receive data, it is transmit only. Will need to upgrade to PowerHome (not ActiveHome) hardware if this is a desired capability.
Misc
- I have posted my collection of X10 equipment here if anyone needs an X10 device: X10 Equipment
