Difference between revisions of "Project:Java-Rako"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
Project maintained by teabot, contact via IRC | Project maintained by teabot, contact via IRC | ||
==Summary== | ==Summary== | ||
| − | A Java API for controlling [http://www.rakocontrols.com/ Rako] lighting systems. | + | A Java API for controlling [http://www.rakocontrols.com/ Rako] home lighting systems. |
Initial project goals are to allow the setting of room scenes from a Java based API via the Rako Ethernet bridge. If this is successful the plan is to also implement features necessary to configure/program Rako devices in a similar manner to RakoSoft. | Initial project goals are to allow the setting of room scenes from a Java based API via the Rako Ethernet bridge. If this is successful the plan is to also implement features necessary to configure/program Rako devices in a similar manner to RakoSoft. | ||
Revision as of 15:10, 10 February 2010
Project maintained by teabot, contact via IRC
Summary
A Java API for controlling Rako home lighting systems.
Initial project goals are to allow the setting of room scenes from a Java based API via the Rako Ethernet bridge. If this is successful the plan is to also implement features necessary to configure/program Rako devices in a similar manner to RakoSoft.
Current equipment
- 500w dimmer
- 7 button control panel
- Rako Ethernet bridge
- RakoSoft
- iPhone with Rako app
Proposed method
- Construct a minimal Rako system with one channel and an Ethernet bridge [Complete]
- Contact Rako to see if they have an API available [In progress]
- Obtain connectivity between the bridge and the iPhone app and/or RakoSoft on a network that allows snooping [In progress]
- Monitor traffic between iPhone app/RakoSoft/Bridge Web UI to determine a suitable candidate for reverse engineering
- Create some simple tests that deliver observed packets to the bridge
- Reverse enginner protocol
- Implement the protocol with Java :-)
Notes
I have had a little snoop on the RakoSoft traffic with WireShark and it appears to use non-trivial protocol - darn...