If you want to contact the developers, please use the mySmartGrid development mailing list: msg-dev@listserv.mysmartgrid.de

Another way to contact the team is using IRC - we have a channel #mysmartgrid on freenode.

The next elektro:camp(«2014.04») will be in Leuven. Please see EC1404-Coordination for more information.

• The 7th elektro:camp(«2013.11») has been on Texel. Please see EC1311-Coordination for more information.
• The 6th elektro:camp(«2013.04») has been in Kaiserslautern! Please see EC1304-Coordination for more information.
• The 5th elektro:camp(«2012.10») has been in Leuven! Please see EC1210-Coordination for more information.
• The 4th elektro:camp(«2012.05») has been in Offenburg! Please see EC1205-Coordination for more information.
• The third elektro:camp(«2011.10») has been in Groningen! Please see EC1110-Coordination for more information.
• The second elektro:camp(«2011.05») has been in Stuttgart! Please see EC1105-Coordination for more information.
• On Oct. 29th/30th 2010 we had the first elektro:camp(«2010») in Kaiserslautern. Please have a look at the CampCoordination page.

Our standards-based, open-source home automation system is now (almost) available. Each device has an unique IPv6 address and provides excellent interfaces for hacking (both hardware and software). Learn more on the HexaBus page.

We list the items we are currently working on here: FeatureArrivals

The new features deployment procedure is described here: DeploymentProcedure

Lessons we learned during the deployment of devices: LessonsDeployment

Monitoring our infrastructure: Monitoring

Almost all code in the project is released under an open-source license. Please add pointers to your repositories here.

Prototype of a bus system: Project Octobus

Flukso USB development board: FluksoUSBBoard

Generic Meter and Time Series Data Format: MeterTimeSeriesDataFormat

Building a Flukso using Flukso USB and an OpenWRT router CustomFlukso

Reading smart meter data via the optical interface: Optoreader (currently only documented in german)

Running long-running jobs within the infrastructure: JobQueue

http://www.thepowerbase.com/2012/01/openwrt-build-guide-start-to-finish/

Enable WLAN SSH Access: FluksoSSH

Updating the Flukso software (Flukso v1): FluksoUpdate

Updating the Flukso software (Flukso v2): Fluksov2Update

Aktualisieren der Flukso-Software (Flukso v2, DE): Fluksov2Aktualisierung

Dokumentation

Flukso behind a firewall: FirewallSettings

Hexabus on the Flukso: HexaDaemon

New Setup (draft): FluksoSetup

Please note: The Chumby comes with an operating system built-in that needs to be registered with Chumby.com before allowing Flash-based code to be executed. Whenever Chumby.com is down, as a side effect, the Chumby won't normally boot with the operating system delivered by the manufacturer. Please consider using the new image including the Qt-based code.

Setup procedure and download of latest Chumby image: ChumbyQtControlpanel

Einrichtung und Herunterladen des neuesten Chumby-Images: ChumbyQtControlpanel-DE

How to install Qt on the Chumby: ChumbyQt

Please note: Whenever the domain Chumby.com is down, as a side effect, the Chumby won't normally boot with the operating system delivered by the manufacturer.

How to install the software image on the Chumby: ChumbySoftware

How to create a software image for /mnt/storage: ChumbyImageHowto

Download Flash-based Chumby images: ChumbyImageDownload

Video of code running on Chumby: momentanverbrauch.avi

Alternative ways of using Chumby for monitoring energy: ChumbyCurrentCostHowto

Mobile devices need a generic mechanism for exchanging configuration information. We need to develop a webservice that allows us to exchange this information securely and easily. One way would be:

• Generate a secret on the mobile device.
• The user logs into the website and enters the secret. Then, the website provides a package with configuration information that is linked to the user.
• The user activates the configuration download manually. The device then uses the secret to download the configuration information.

Requirements:

• Display the current reading of a Flukso in the local LAN. The Flukso should be discovered using SD-DNS. It should also be possible to enter the Flukso IP manually.
• The Flukso sensor IDs should be named according to the website. The Flukso name can be discovered using the configuration webservice.
• The Graphs on the website should be rendered in a UIWebView. The website provides a minimal Javascript/HTML-page that will be cached by the iPhone. The user can refresh the local cache manually in the preference pane.

mySmartDroid

How to use a Volkszaehler setup for logging to both Volkszaehler and mySmartGrid servers.

How it basically works: http://wiki.volkszaehler.org/

Setup: http://wiki.volkszaehler.org/setup

Vzlogger Ubuntu packages: http://packages.mysmartgrid.de/ubuntu/

Vzlogger to mySmartGrid Howto: VzloggerHowto

The web service interface is described here: Web Service Interface 2.1.

The local data interface of the flukos is described here: Local Interface

How we want to use terms like power, energy,… Terms