The smart meter demo is based on two open source project, open energy monitoring and webinos
project. Open energy monitoring provides a flexible hardware platform for monitoring the energy
consumption while webinos project offers a distributed, secure environment for data management,
and most importantly in our case scenario, is the ability allowing the third party managed service to
run independent of the specific energy provider.

Considering the smart meter case in webinos, smart meter should be running PZP and communicating
and send the energy data to the third party energy provider, which is running on a cloud PZH.
https://cacoo.com/diagrams/WxaOWfzN2B9TP4TW-F9F8C.png gives a short overview on the
implementation of PZP.

-           PZP – normal PZP implementation

-          MicroPZP – fully implemented on the same device

-          Virtual PZP – Implemented on two devices ie webinos core and device APIs are implemented
separately from the hardware

Given to the hardware limitation (nanode – a arduino compatible board limited capability to run
on javascript), are working with the virtual PZP option, that the capability of PZP is essentially split
into two parts, the first part is consisting emonbase, emontx, actuator, all of which are responsible
for receiving the energy and environmental data in wireless radio frequency and sends the data to a
home server running on PZP respectively.

• EmonBase:

EmonBase is used to serve as a simple gateway, for dealing with ethernet, 852HZ wireless
communication.Since it is based on nanode, – a arduino compatible board. Limited memory
essentially prevents us from building more meaningful web interfaces, and richer web server
functionality.

• EmonTX:

is the emonTx component (wireless RF module) reading the energy context data(
electricity, voltage ) and environmental context data ( temperature sensor, optionally add
more sensors like light sensor, humidity sensor).

• Actuators:

Same with emontx, is all working on the same wireless radio frequency 852HZ, but use relay
for remote control instead of sensors.

The second part is a home server running in virtual PZP, primarily responsible for dealing with web
application, device management and establishment of secure data transmission with third party
services. For bridging the communication between emonbase and virtual PZP, a restful service
interface and data structure standard is defined between them. So virtual PZP knows how to parse
the incoming sensor data, retrieve the sensor, actuator list, detailed information, and command the
actuator remotely

image

As webinos is to enable web applications and services to be used and shared consistently and

securely over a broad spectrum of connected devices. This is partly accomplished by working with a

board of standard APIs. In the webinos project, sensor and actuator API are defined, so help the web

application developer to get access to the sensor and actuator consistently without concerning any

device platform.

A web mobile application is built upon these standard APIs. In our scenario the device owner can

view the energy consumption of his home devices and the environmental data in his living space

such as temperature, humidity, light, and control his remote plug to switch on/off.

Moreover, the user can get a list of energy provider, switch to the different energy provider while

maintaining a secure session. In some cases, webinos also allows different users to share with

the trust and control, for example in the office, the user can control his lights remotely, while

at the same time, the user can delegate or share this control with the building administrator,

webinos can ease this type of application.

Advertisements