Q: How secure is EnOcean radio?
All EnOcean modules provide a basic security by sending a device specific ID.  This ID is fix programmed to the radio chip. Security enhanced devices like PTM 215 or sensors are also available, they are using additional state of the art security mechanisms defined within the EnOcean Alliance (e.g. rolling code, AES128). More information is available at: http://www.enocean.com/en/security-specification/
Q: Does FHEM support security features built into the EnOcean protocol?
Yes, for example it supports PTM 215 with rolling code.
Q: Can we use EnOcean module to count pulses from an energy monitoring system?
Yes, of course is it possible.
Q: We have water counter giving pulses by quantities used, thus we need EnOcean module to collect theses pulses. Do you have ref of this kind of modules?
Q: How do we manage sensors over multiple rooms with one Raspberry Pi, due to the range limitation of wireless communication?
EnOcean radio has a free field range of 300m, within buildings there is a range of about 30m.
If this is not enough there are two possibilities:
  1. Use one or two repeaters to get a range of 60-90m, this is done within residential buildings.
  2. Use a backbone e.g. LON, BACNET or IP (Ethernet/WiFi) with gateways, this is done within commercial buildings. There are buildings with 30.000 and more EnOcean powered sensors.
Q: Will there be a free alternative to EnOcean Link c++ library?
EnOceanLink is a middleware to professional OEM customers. It is used to build commercial solutions for building automation. For smart home servers there a several open source projects available e.g. FHEM and openHAB.
Q: Does an ip gateway exist?
You can use Raspberry Pi to build your own IP gateway or use commercial available products. You will find products at: http://www.enocean-alliance.org/en/products/.
Q: Do the solar cells work with led lighting to recharge the modules?
Yes, LED light will charge indoor/amorphous solar cells. Due to the limited spectrum of LED light it will take a little bit longer to be fully charged.
Q: Can EnOcean modules be customized freely? Can you modify the sensors to sense other things?  E.g. change normally open contact from a relay is closed?
Yes, there are two possibilities:
  • Configuration of parameters e.g. wake up timing, EEP, pin config, manufacturer ID,...This is easy and can be done with the developer kit EDK 350 and the EnOcean SW DolphinStudio.
  • Programming of customer specific applications. This is more effort, you need the developer kit EDK 350 and Keil 8051 compiler (Enocean tool set is optimized for this)
Details can be found at product user manual: http://www.enocean.com/en/products/
Q: Multiple EnOcean Pi device, can they communicate with each other like on a wireless network?
Yes, EnOcean protocol on EnOcean PI and USB 300 is bidirectional
Q: Is the protocol for the sensors proprietary or open source?
Protocol is based on ISO/IEC 14543-3-10 (network, data link, physical layer) and EnOcean Alliance (application layer). It can be used free of charge.
Q: EnOcean Pi use all the GPIO Pin? | Can I add other devices? | Can I connect a web cam in addition with sensors with the server, for live feed?
EnOcean Pi uses only the GPIO ports of the serial port. It can be used with other GPIO device if they do not use the serial port, you might need to extend the socket.
Q: You should probably remove the part of updating FHEM in the whitepaper. I tried multiple times to update the fhem software and every time the software broke beyond repair.
We did an update of FHEM via update command successfully just before the Webinar. Please state problems of FHEM to the FHEM forum: http://forum.fhem.de/index.php/board,27.0.html
Q: What is the security ? | Are the signals encrypted? | How do you ensure that they are not spoofed (recorded and replay) or something? | Can I receive all messages of my neighbor?
There are modules with different security levels available. With basic security (chip ID) you can receive and listen, but not send. Modules with additional security e.g. PTM 215 with rolling code are protected. Details see: http://www.enocean.com/en/security-specification/  
Q: Difference between EnOcean Pi and USB 300 dongle? | Does the USB300 work on the Pi as the EnoceanPi?
  • EnOcean Pi is connected via Raspberry Pi GPIO serial port, it does not block an USB port
  • USB 300 is connected to the Raspberry Pi USB port, it does not block GPIO port
Both can be used via FHEM and are recognized automatically.
Q: How do you control a relay, for example turning on or off a light bulb.  Where should I go to get more info on configuring actors in fhem. For example for light dimmers etc.?
If you want to switch lights by the Smart Home Server you have to learn one of the 128 transceiver IDs (EnOcean Pi or USB 300) to the actuator. Transceiver IDs are based on the "base ID". FHEM reports the base ID via the command "get TCM310_0 baseID". Use the reported base ID and increment this by one for the first transceiver ID.  Use this ID to define a switch at FHEM and learn this switch to the actor.
For details have a look at the FHEM command reference: http://fhem.de/commandref_DE.html
Some actors have manufacturer specific features, check FHEM forum: http://forum.fhem.de/index.php/board,27.0.html
Example with EnOcean RCM 250 is available within a whitepaper:    http://www.enocean.com/fileadmin/redaktion/pdf/white_paper/wp_Raspberry_talks_EnOcean.pdf
Q: Can I modify a single sensor module to measure multiple things? like a single mmodule modified for temperature and current.| Is there a way to combine multiple sensors to use the same radio module, sending multiple data or is it mandatory to have one radio module for each sensors?
Of course is it possible, see e.g. all our STM3xx devices. Typical use case are e.g. STM330 + USM100 (calibrated temperature and relative humidity sensor in one). All STM3xx devices have multiple analog and digital inputs and send the correspondingly data in the radio  telegram, see e.g. all the EEP profiles for 4BS telegrams: temperature + light + presence, CO2 + humidity + supply voltage and so on...)
Q: Can I get the links for the documents on how to modify the modules?
Support and knowledge base: http://www.enocean.com/en/knowledge-base/
Q: Is it possible to monitor the power available on the sensors (i.e. temp sensor) at any one time?
Of course, all STM3xx have this feature and this even w/o to use any external circuits therefore.  Means if desired the momentary value of the voltage supply can be additional to the sensor data also transmitted.
Q: Can we be pretty sure that third party devices work with Enocean Pi? for example Vimar, Eltako, etc
Most manufacturers of EnOcean products are members of the EnOcean Alliance. This Alliance standardizes the so called EnOcean Equipment Profiles (EEP). Based on this EEPs the devices understand each other. A description of EnOcean Equipment Profiles can be downloaded at: http://www.enocean-alliance.org/en/home/. EnOcean and OEM manufacturers list used EEPs within the product manuals. However, much fewer manufacturers prefer closed systems and use customer specific profiles.
Q: Are all EnOcean profiles recognized by the software?
EnOceanLink recognizes all EnOcean Equipment Profiles (EEP) standardized from the Enocean Alliance. Open software like FHEM and openHAB interpret a part of the profiles.
Q: Does PTM switch send info on push only, or on push and release?
PTM sends different telegrams for rocker push and release. This is available for a single rocker and for dual rocker with channel A and B. Each telegram consist of 3 sub-telegrams with the same content, this ensures the availability.