This shows you the differences between two versions of the page.
chumbysoftware [2010/07/14 14:16] gonium |
chumbysoftware [2012/10/30 10:27] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
=== Update your Flukso === | === Update your Flukso === | ||
+ | |||
+ | NOTE: This should not be needed anymore, as the Flukso has an automated update process. | ||
The Chumby software relies in part on the availability of the Flukso local interface. If you have a "/tmp/sensor" directory with some sensor hashes in it, you're good to go. Otherwise, you need to update your Flukso Installation. See [[FluksoUpdate]]. | The Chumby software relies in part on the availability of the Flukso local interface. If you have a "/tmp/sensor" directory with some sensor hashes in it, you're good to go. Otherwise, you need to update your Flukso Installation. See [[FluksoUpdate]]. | ||
Line 5: | Line 7: | ||
PLEASE NOTE: The current Flukso does not provide the local interface. It can be installed by replacing the LUA scripts in /usr/share/lua/flukso with the ones from the Flukso Git Repository. Then: "ln -s /tmp/sensor /www/sensor". Stay tuned. | PLEASE NOTE: The current Flukso does not provide the local interface. It can be installed by replacing the LUA scripts in /usr/share/lua/flukso with the ones from the Flukso Git Repository. Then: "ln -s /tmp/sensor /www/sensor". Stay tuned. | ||
- | === Get the software package === | + | === Installation of the chumby software (the new way) === |
+ | * Go to the mySmartGrid website and select "Download chumby image" from the website. | ||
+ | * Fill in and submit the form. | ||
+ | * Download the created image. | ||
+ | * Unzip the image to an usb stick | ||
+ | * Plug the usb stick in your chumby | ||
+ | * Restart your chumby | ||
+ | |||
+ | With a control panel version %%<=%% 2.8.74 the usb stick with the file profile.xml has to be present whenever you want to see the visualizations. | ||
+ | |||
+ | === Installation of the Chumby software (the old way) === | ||
+ | == Get the software package == | ||
See [[ChumbyImageDownload]]. | See [[ChumbyImageDownload]]. | ||
- | === Installation of the Chumby Software === | + | == Installation of the Chumby Software == |
You need a recent version of the Chumby Software Image, as described here: [[ChumbyImageHowto]]. The image contains various Ruby scripts to retrieve data from external sources and exposes it to Flash frontends. All software is installed to /mnt/storage so that it runs from the internal SD card. By convention, this is the filesystem layout for our components: | You need a recent version of the Chumby Software Image, as described here: [[ChumbyImageHowto]]. The image contains various Ruby scripts to retrieve data from external sources and exposes it to Flash frontends. All software is installed to /mnt/storage so that it runs from the internal SD card. By convention, this is the filesystem layout for our components: | ||
Line 23: | Line 36: | ||
</code> | </code> | ||
- | === Setting up the environment for internal use === | + | == Setting up the environment for internal use == |
If you log into the Chumby via SSH, run | If you log into the Chumby via SSH, run | ||
<code> | <code> | ||
Line 35: | Line 48: | ||
</code> | </code> | ||
Since the integrated ash does not support sourcing files, it opens a new shell in the end. | Since the integrated ash does not support sourcing files, it opens a new shell in the end. | ||
- | === Configuring the daemon === | + | == Configuring the daemon == |
The Ruby daemon "msg-chumby-daemon" retrieves the current power consumption from your Flukso. It depends on an configuration file which you need to adjust. A template can be found in "/mnt/storage/usr/lib/ruby/gems/1.8/gems/msg-chumby-display-0.2.0/etc/msgchumbydaemonrc" (depending on the version of the gem). Copy it to "/mnt/storage/usr/etc" and edit it to reflect your local Flukso settings. For example: | The Ruby daemon "msg-chumby-daemon" retrieves the current power consumption from your Flukso. It depends on an configuration file which you need to adjust. A template can be found in "/mnt/storage/usr/lib/ruby/gems/1.8/gems/msg-chumby-display-0.2.0/etc/msgchumbydaemonrc" (depending on the version of the gem). Copy it to "/mnt/storage/usr/etc" and edit it to reflect your local Flukso settings. For example: | ||
Line 51: | Line 64: | ||
Access token and sensor id are needed to retrieve longterm values from the website. The FLUKSO_* variables describe where the Flukso lives on the local LAN, and what sensor ID should be queried. Copy this template to "/mnt/storage/usr/etc" and edit it. | Access token and sensor id are needed to retrieve longterm values from the website. The FLUKSO_* variables describe where the Flukso lives on the local LAN, and what sensor ID should be queried. Copy this template to "/mnt/storage/usr/etc" and edit it. | ||
- | === Running the daemon === | + | == Running the daemon == |
For interactive use, you can start the daemon like this: | For interactive use, you can start the daemon like this: | ||
<code> | <code> | ||
Line 58: | Line 71: | ||
</code> | </code> | ||
- | === The Flash Widgets === | + | == The Flash Widgets == |
The widgets for presenting the current power consumption are distributed as a part of the Ruby gem. You can find them in "/mnt/storage/usr/lib/ruby/gems/1.8/gems/msg-chumby-display-0.2.0/widget". To run a widget manually, follow these steps: | The widgets for presenting the current power consumption are distributed as a part of the Ruby gem. You can find them in "/mnt/storage/usr/lib/ruby/gems/1.8/gems/msg-chumby-display-0.2.0/widget". To run a widget manually, follow these steps: | ||
Line 68: | Line 81: | ||
</code> | </code> | ||
- | === Linking the software into the startup process === | + | == Linking the software into the startup process == |
For demos I configure the Chumby so that the standard control panel is not started. Instead, before the control panel ist started, I run the widgets manually. You can adjust the userhook2 to do this, see [[http://wiki.chumby.com/mediawiki/index.php/Chumby_Rootdisk_-_RFS1_(analyzed)]]. A startup script looks like this | For demos I configure the Chumby so that the standard control panel is not started. Instead, before the control panel ist started, I run the widgets manually. You can adjust the userhook2 to do this, see [[http://wiki.chumby.com/mediawiki/index.php/Chumby_Rootdisk_-_RFS1_(analyzed)]]. A startup script looks like this | ||
Line 93: | Line 106: | ||
fi | fi | ||
+ | stop_control_panel | ||
# give the ruby stuff some time for startup | # give the ruby stuff some time for startup | ||
- | sleep 7 | + | sleep 15 |
if [ -x $FLASHPLAYER_BIN ]; then | if [ -x $FLASHPLAYER_BIN ]; then | ||
Line 107: | Line 121: | ||
exit | exit | ||
fi | fi | ||
+ | |||
+ | # Do not leave the script to prevent the control panel to be restarted automatically | ||
+ | while : | ||
+ | do | ||
+ | sleep 360 | ||
+ | done | ||
</code> | </code> | ||