How to setup a home automation server with EnOcean Pi

RE: How to setup a home automation server with EnOcean Pi

e14 Contributor — Wed, 27 Jul 2016 08:49:41 GMT

Hi,

I have the EnOcean sensorkit and a raspberry pi 2 B, I followed each point of this tutorial and tried many other (one of them was the "Raspberry talks enocean" for example). But in each case I always have the same problem : the "EnOcean" button doesn't appear on the side in fhem and I can't continue the configuration.

Does anyone had this problem ? Any help would be welcome [View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-9a5ca1c5-055a-4138-aed3-d67f3e6176f7/contentimage_5F00_1.png:16:16]

RE: How to setup a home automation server with EnOcean Pi

e14 Contributor — Tue, 28 Jul 2015 22:24:22 GMT

I have the EnOcean Sensor Kit ( using EnOcean Pi ) that came with the Raspberry Pi 2 B model, and I've installed everything (FHEM + dependancies), updated my Pi, disabled my serial console, but what ever I do I cannot seem to get my EnOcean Pi sensor to recognize the sensor data, going to "Events Monitor" and trying to click the rocker switch, numerous guides have told me this should be seen via the browser and an individual log file, and it does not seem to be working .(Rebooted numerous times as well)

The only difference I can see from my setup to what is documented here is that , I am using the newest package for FHEM, 5.6, the web interface is pretty much the same, but slightly different

(On the second menu on the left down, instead of having "EnOcean, Unsorted, Everything" my FHEM 5.6 interface has only "Unsorted, Everything" .

My /opt/fhem/log/fhem*.log file seems file, but the last line in the log file states that "En0cean Cryptographic functions are not available"

I am 99% certain that my En0cean Pi is seated corrected onto my Raspberry Pi, and the antenna wire is sticking up as shown in the diagram.

Need some help, please assist if possible ...

RE: How to setup a home automation server with EnOcean Pi

e14 Contributor — Mon, 23 Jun 2014 16:24:24 GMT

Hi Todd,

Good overview here. I wanted to point out that the unique 32 it EnOcean IDs are known as chip IDs and are similar to MAC addresses in functionality. The manufacturer ID is something a little bit different and can be used to establish who created the device in your hand. The EnOcean Alliance is in charge of handling Manufacturer IDs.

In the line, "define EnO_sensor_0088F03E EnOcean 0088F03E attr EnO_sensor_0088F03E manufID 00B" You can see the manufID is 0x00B which happens to be EnOcean's manufacturer ID.