-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
82 lines (80 loc) · 7.01 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>LamPI 433Mhz controller for RaspberryPI</title>
</head>
<body>
<h1>LamPI Introduction</h1>
<h5>LamPI is a Home Automation project for switching equipment in the house over 444 MHz transmitters/receivers on a RaspberryPI.</h5>
<p>You can find its GIT repository on <a href="https://github.com/platenspeler">https://github.com/platenspeler</a>, documentation on http://platenspeler.github.io</p>
<p><img src="gh-pages/screenshots/room_screen_grey.JPG" width="962" height="632" /></p>
<p>The screen above is one of the main screens of LamPI, and should give you a taste of what LamPI is about. As you see, the GUI interface is designed to operate (and manage) all tasks for the connected devices and minimize the need for manual changing of configuration files etc. let alone making configuration changes at compile time.</p>
<p>In case I missed something, please send me an email or make a note on this page. For the moment I'm the only author of LamPI so it can take a few days before I answer...</p>
<h1>LamPI Introduction</h1>
<p>The goal of my project was to provide an easy interface to the family to control the lights in our house. We had klikaanklikuit.nl switches and we have an iPad (and some Android phones and Laptops) and want to control our light switches with an easy-to-use GUI interface. This meant that I needed at least 2 components: A component that would control transmitter and receiver and handle low-level device commands, and a GUI in JavaScript/jQuery that would handle the human interaction. In order to store configuration information and for timing commands and unattended use, we would also need a daemon process serving in the background as well as a database (written in MySQL) to store configuration information.</p>
<p>Although I woul expect that you like to use te complete package, it is quite good possible to only use the RaspberryPI transmitter and receiver shell executables (see below)</p>
<p><More information is available HERE></p>
<h1>Main LamPI Functions</h1>
<p>LamPI contains 5 main screens: Rooms, Scenes, Timers, Handsets and Config. For every screen I have assembled a few pages that contain instructions on common tasks you will perform. </p>
<p>The documentation for the LamPI functions can be found on this site on the following pages.</p>
<ul>
<li><a href="gh-pages/setup.html">Initial Setup</a></li>
<li><a href="gh-pages/rooms.html">The Rooms Screen</a></li>
<li><a href="gh-pages/scenes.html">The Scenes Screen</a></li>
<li><a href="gh-pages/timers.html">The Timers Screen</a></li>
<li><a href="gh-pages/handsets.html">The Handsets Screen</a></li>
<li><a href="gh-pages/config.html">The Config Screen</a></li>
<li>Transceiver interface; If you only want to use the <a href="gh-pages/transceiver.html">LamPI-receiver command-line</a> to send/receive 433MHz messages </li>
<li><a href="gh-pages/hardware.html">Background information 433MHz hardware for RaspberryPI</a></li>
<li>Background information on the <a href="gh-pages/architecture.html">Architecture</a></li>
</ul>
<h1>What Switches, Dimmers and other devices are supported?</h1>
<p>LamPI can support receiver devices (making transmitter modules for various brands is often easy). Also, several brand share almost the same protocol or work or can be made to work with minor modifications, Therefore, the list below is probably just a snapshot of a much larger list...</p>
<h4>Receivers, Switches, Dimmers</h4>
<ul>
<li>Klikaanklikuit switches, the new type</li>
<li>Action or Impuls switches</li>
<li>Livolo switches</li>
<li>Kopou switches</li>
<li>Elro (not tested, software is installed)</li>
<li>Blokker (not tested, software is installed)</li>
<li>Klikaanklikuit (old model with two wheels at he back, not tested)</li>
</ul>
<h4>Handsets and Remote Controls</h4>
<ul>
<li>Klikaanklikuit remotes</li>
<li>Livolo 4-button keychain</li>
<li>Kopou 4-button keychain</li>
</ul>
<h4>Temperature Sensors</h4>
<ul>
<li>WT-440H, mae by UPM/Esic</li>
</ul>
<h1>What Platform(s) does LamPI run on?</h1>
<ul>
<li>The web GUI of LamPI runs on every webserver in your network as it is implemented in Javascript/jQuery. That means that if you install it on a webserver in your network you can access the GUI User Interface from every browser in your network (and soon also from the internet). By default, the webserver runs fine on the RaspberryPI (you need the Raspberry anyway).<br>
<br>
<strong>The current web front-end works VERY well on iPad, and can be installed as an app...</strong><br>
<br>
</li>
<li>If you want, you can setup the MySQL database on another server (that is what I did), but this is optional.<br>
<br>
</li>
<li>The low-level device functions for transmitter and receiver, will at the moment only run on the RaspberryPI, although making an Arduino version is probably not much work. The executables are all found in the ~/exe directory. The source code for these functions can be found in the ~/receivers directory.</li>
</ul>
<p> </p>
<h1>Architectural Considerations</h1>
<p>I did make an architecture document which can be found <<a href="gh-pages/architecture.html">HERE</a>>.</p>
<p> </p>
<h1>Planned Functions</h1>
<p>Of course I'm always thinking about new functions, as long as I do not have to put the current system up-side-down too much. After all, I do have other day-time work to do and it has to make sense for me to spend additional time. Therefore, you are welcome to ask for new functions, but if it will cost me days to implement them and I will not benefit from them in any way I will probably give priority to other changes.</p>
<ul>
<li>Add support for Android phones. This is in beta at the moment and I use PhoneGap technology of Adobe to make such version. All Javascript/jQueryMobile code is already in the LamPI-x.y.js file, the index.html file will determine what libraries to load. I will probably publish a separate branch for Android with the same version number as its web equivalent.</li>
<li>Adding new handsets at this moment still requires manual editing of the database.cfg file. I like to add more options to the OPTIONS screen for setup of new switch types and handset types, so that adding such switches and handsets at runtime is a lot easier.</li>
<li>Add support for Z-Wave or Zigbee. I have not decided what is next, but as the LamPI-daemon is quite universal in its setup adding transmitter/receivers for these technologies is relatively easy.</li>
<li>I like (at some time) be integrating my front-end with the new standards for Home Automation as soon as stacks become available for the Raspberry.</li>
<li>And I'm always looking for cheap new designed wall switches to add to the set..</li>
<li>Internationalization; Probably not worth spending too much time on this, as most people that will use this projects do not mind English versions anyway. So probably just making an alternative startup file for ''database.cfg" would be enough for international customers to get a good feel for the software.</li>
</ul>
</body>
</html>