This page last changed on Mar 23, 2013 by homer.

Hi,

I'm new in this community and hopeing that openremote will be the right Server for me. Let's see.
Now my Question:
I want to configure my RCM250 device, but I cannot find enocean as decribed in the HowTo...

Where can i search?

Homer


Device_EnOcean.JPG (image/jpeg)
Device_EnOceanOn.JPG (image/jpeg)
configForControllerEnOcean .JPG (image/jpeg)
Serial01.JPG (image/jpeg)
CmdSwitchOnRCM250.png (image/png)
CmdPTMRockerA.png (image/png)
Switch.JPG (image/jpeg)
image.jpg (image/jpeg)
EnOceanPTMStatusCmd.png (image/png)
EnOceanPTMSensor.png (image/png)
EnOceanPTMStatusLabel.png (image/png)
billed.jpg (image/jpeg)
ZWave_config.png (image/png)

Will prepare a binary for you. It has been developer only source release so far. Thanks for volunteering to become a guinea pig

Posted by admin at Mar 21, 2013 17:59

The controller binary is available here: OpenRemote-Controller-2.1.0_EnOcean.zip

For the EnOcean designer configuration you MUST use http://composer.openremote.org/preview (preview release) – please DO NOT use your account in the previously released 2.13 version at http://designer.openremote.org. You may lose your account data if you do so.

I'll need to ping Rainer to help you with the rest as it looks like the How To is not yet complete.

Posted by admin at Mar 21, 2013 19:25

I will give you a feedback, if any problems occur.
Thank so much for your help.
Eberhard

Posted by homer at Mar 22, 2013 06:19

There is the first problem. I think that's a major problem. I don't know how to solve.

Error message:
Command failed
The command was sent to an invalid URL.

How can I check the URL?

Eberhard

Problem solved - It was the wrong controller. I have to use the local controller if i want reach local device.

Posted by homer at Mar 22, 2013 16:22

Now here the first real Problem:

The Interface is an BSC EnOcean Smart Connect USB on COM18:

First I've setup an new Device:

Then defined the Status on and Off

The Off-Command for EnOcean F6-02-1 is "70".

The problem is: No command reaches the USB-Interface, because you can't see the LED working.

Testing the USB-Interface with the DolphinViewAdvanced Software you see that in additional a status is sent. In my case "0x30". The Telegramm that is sent out should be:

Why does nothing reaches the interface?

Eberhard

Posted by homer at Mar 23, 2013 12:54

Now I realised why there are less pictures in this forum — horrible. I'm sure that's my fault...

Posted by homer at Mar 23, 2013 13:04

Hi Eberhard,

the 'EnOcean How To' is not ready yet but I'll work on that in the near future.

The ON-Command for the RCM250 should work with the following configuration:

In case of a "send" command, the 'Device ID' is not an absolute device ID, it's a relative number which has to be in the following range 0...127. This relative number is added to the base ID of the USB interface. Furthermore, the 'Device ID' can be defined with hexadecimal or decimal notation. If you choose hexadecimal, prepend the ID with 0x.

I've checked that the controller is working correctly you've received. The serial port configuration for you BSC EnOcean Smart Connect USB seems to be OK.

Posted by rhitz at Mar 23, 2013 16:50

Hi Rainer,
thanks a lot!

Now somthing is going trough the UCB interface.

Normally a 2-Rocker send a broadcast FFFFFF to all of the RCM250. I have two of them. I learned the Interface-ID in one of the the RCM250. With the test-program of EnOcan it works, but now: Nothing happens. I cannot see what is going out of the stick because the COM-port is not available by DolphinView Advanced while using OR.

Do have to teach in the new ID again?

Eberhard

Posted by homer at Mar 23, 2013 17:24

Glad to hear that something is going on.

The addition of the relative ID with the base ID of the EnOcean interface results in a regular EnOcean device ID, which is in this case related to a "virtual switch". The teach-in procedure of this "virtual switch" is exactly the same as with a physical switch.

  1. Press the LRN button of the RCM250
  2. Load the panel with the ON button and press the button

After this teach-in procedure the RCM knows the device ID of the "virtual switch". If you configure the OFF command afterwards, use the same relative device ID from the OFF command because it's related to the same "virtual switch". If you've choosen the same ID, do not repeat the teach-in procedure with the OFF command - this would result in an teach-out procedure.

Hope this helps.

Rainer

Posted by rhitz at Mar 23, 2013 18:33

thank you
i see outgoing wireless life in USB300DA controller....
but... can't find the way to watch clicks on my hardware remote control Eltako FF8 (or simple PTM) and indicate it on designer

Posted by tscheebis at Mar 24, 2013 09:00

Hi Rainer,

short feedback: it works fine - really fantastic!! Does this mean that I have now 128 different witches?

Next step: If I push the normal switch on the wall I want to change the status on my OR-Console. How does this works?

Eberhard

Posted by homer at Mar 24, 2013 09:35

Hi,

in your case try the following command for sensing the left rocker (rocker A) of a regular PTM switch:

The command for sensing the right rocker would be STATUS_ROCKER_B. Replace the 'Device ID' value with the ID of your PTM switch. Note that the 'Device ID' value is an absolute ID. Determine the device ID with a viewer tool from EnOcean. Unfortunately these tools are only available for Windows. If that's a problem activate EnOcean device ID logging:

  1. Open webapps/controller/WEB-INF/classes/log4j.properties
  2. set log4j.appender.enocean-file.Threshold = DEBUG
  3. Press the PTM switch several times
  4. Take a look into the EnOcean log file (logs/enocean/enocean.log)

I'm not sure if the Eltako FF8 works out of the box. If the FF8 is an assembly of two regular PTM EnOcean modules, then it should be no problem.

Posted by rhitz at Mar 24, 2013 10:21

Eberhard,

thanks for the feedback.

You've got it - an EnOcean gateway, like the BSC USB interface, provides a range with 128 unique IDs for sending EnOcean radio telegrams. It's possible to link each of the 128 ID's with the F6-02-01 EnOcean equipment profile. As a result it's possible to simulate 128 different switches. Note that it doesn't have to be the F6-02-01 profile. It would also be conceivable to link a different profile but currently only the F6-02-01 profile is supported for sending EnOcean radio telegrams.

For the answer of your second question see my previous posting in this thread.

Rainer

Posted by rhitz at Mar 24, 2013 11:09

Greets,
Rainer

yes, it works but only in RT-mode (2 rockers 2 position (on - of), but how to write logic when use UT-mode (Universal Mode - each next click just change state from ON to OFF roundly)?
and of course how to use/select Enocean USB on OR-server as Repeater (class 1 or 2) - when i use hardware control (Eltako Remote Control or Eltako PTM Buttons or Eltako F8S12 Module)

p.s. i see list of all available Enocean command (incl. switches, temperature controllers, valves actuators end etc) in my dreams

Maksim

Posted by tscheebis at Mar 24, 2013 11:14

Rainer,
so far so good. The status is shown on a new-built switch. Excellent! But - the sitch does not work! Can you tell me why?

Here is the switch:

Where is the problem? The sensor shows the switch with ID 00101ABC. The swich on the console has the ID=0x01. When I switch with a button it work, but the status is not changing, because the ID is different to the sensor. Multiple sensors possible?

Eberhard

Posted by homer at Mar 24, 2013 14:40

Eberhard,

gratulation - you've uncovered the most difficult part of EnOcean in combination with OpenRemote - integrating typical EnOcean actuators into OpenRemote.

Typical EnOcean actuators like the RCM250 are unidirectional. The RCM250 contains only a receiver module for receiving commands from a switch. It's not possible for the RCM250 to send it's current state. In addition, the communication with actuators is based on the unidirectional profile F6-02-01. The profile specifies only the direction from the sensor (switch) to the actuator. That's the reason why it's currently not easily possible to have status feedback.

The described problem is not OpenRemote specific. All EnOcean GUI's are struggling with these limitations. I know an EnOcean system which solved this problem with a very hard restriction in combination with status persistency. With this system it's not possible to link a switch directly with an actuator, only indirectly via the controller (switch --> controller --> actuator). The problem with this solution is, that the switch doesn't work without a running controller. I do not want to follow this solution.

EnOcean is advertising their bidirectional dolphin chips. With these transceiver chips it's no problem to build bidirectional actuators. What's currently missing is a bidirectional profile which has to be defined by the EnOcean Alliance. I'm currently investigating bidirectional actuators from Eltako. Problem is, that they've implemented their own bidirectional communication because as I've mentioned there is no bidirectional standard profile. I expect that there will be bidirectional actuators based on bidirectional profiles in the future. Maybe we will in the meantime add support for the proprietary Eltako actuators, but I'm not sure about that. Rest assured that I'm constantly working on a solution for this problem.

I've developed a solution, for your switch status feedback problem. The solution consists of a virtual command for storing the current switch state and a couple of rules. The solution is NOT a 100% solution because the switch state of the virtual command doesn't survive controller restarts. It doesn't make sense to describe the solution in this thread because it's too complicated. I think it's better to describe it with a how to.

Rainer

Posted by rhitz at Mar 24, 2013 17:33

Rainer,

thank you for your words. I understand. Than we will wait for the dophin-based profile.

Can You say one word to the switch? Or shall I realize switching with two different buttons?

Eberhard

Posted by homer at Mar 24, 2013 18:06

Rainer,

thank you for your words. I understand. Than we will wait for the dophin-based profile.

Can You say one word to the switch? Or shall I realize switching with two different buttons?

Eberhard

Posted by homer at Mar 24, 2013 18:06

thats right words about actuators state...
now i use this scheme:
switch directional to actuator, switch directional to server (as repeater - server recieve and repeat commands from all enocean devices)
p.s. of course one losed signal and this state-system can be halted.. but i cant see another way to work with run-selected server... and one think about state on the controller (server) after restart, possible restart all actuators with server (just install one actuator to all power input line or do it manually - preffered)

Max

Posted by tscheebis at Mar 24, 2013 18:16

Hi Maksim,

I know that it's possible to activate the built-in repeater of the EnOcean TCM 3XX dolphin modules but it's currently not supported by OpenRemote.

If your EnOcean devices have been implemented in accordance with the EnOcean equipment profile (EEP) specification then the chance is high that the device is already supported. A list of all supported EEP profiles will appear in the EnOcean how to. Valve actuators are on my todo list.

Honestly, I've never encountered the terms RT-mode and UT-mode in the EnOcean specification. Is this Eltako talk ?

Posted by rhitz at Mar 24, 2013 19:03

Rainer,

UT/RT Mode - actually on Eltako FSA12/FSR12 actuators - you can see it on Eltako documentation:

cheers

Max

Posted by tscheebis at Mar 25, 2013 05:47

Hello,

i want to include EnoCean actors too into a openremote showcase.
Unfortunately it don't work ;-(
I think i have some troubles with the commands of EnOcean (like On / Off or STATUS_ROCKER_A)

this is from the enocean log:
WARN 2013-04-04 09:27:47,446 (EnOcean): Unknown EnOcean property '<property name = "name" value = "PTM_1_ROCKER_A"/>'.
INFO 2013-04-04 09:27:47,446 (EnOcean): Created EnOcean Command (ID = '0x008BDB3B', EEP (Type = 'F6-02-01', Rocker A = 'Off')).

Maye someone can give me a template from a working enocean actor or a little hint to setup my actors so that i can adapt it to my IDs and actors.
At the moment i work with the enocean devkit ESK300 with an USB300 Gateway, PTM200, STM330 and a PTM330.

Many thanks in advance for your replies.

Christoph

Posted by wu3mi at Apr 04, 2013 08:34

To create a showcase with your ESK300 devices create a 'STATUS_ROCKER_A' EnOcean command and link this command with a sensor of type 'switch'. Place a label on a panel and link it with the sensor.



Does the temperature sensor STM330 work ?

Posted by rhitz at Apr 04, 2013 09:15

I have done it concerning your description but unfortunately no success.

enocean log:
WARN 2013-04-04 10:50:06,353 (EnOcean): Unknown EnOcean property '<property name = "name" value = "SWITCH_1_STATUS_ROCKER_A"/>'.
INFO 2013-04-04 10:50:06,353 (EnOcean): Created EnOcean Command (ID = '0x008BDB3B', EEP (Type = 'F6-02-01', Rocker A = 'Off')).
WARN 2013-04-04 10:51:46,379 (EnOcean): Unknown EnOcean property '<property name = "name" value = "tmp"/>'.
WARN 2013-04-04 10:51:46,384 (EnOcean): Unknown EnOcean property '<property name = "name" value = "SWITCH_1_STATUS_ROCKER_A"/>'.
INFO 2013-04-04 10:51:46,385 (EnOcean): Created EnOcean Command (ID = '0x008BDB3B', EEP (Type = 'F6-02-01', Rocker A = 'Off')).

The temperature sensor don't work too ;-(

I can't find the problem at the moment. I suggest, that there is another problem. I will try something else with the whole system.

many thanks ...

Posted by wu3mi at Apr 04, 2013 10:13

Modify the EnOcean log threshold in /controller/WEB_INF/classes/log4j.properties with the following setting to see if the serial port communication is working:

log4j.appender.enocean-file.Threshold = ALL

Activate the switch several times and check the enocean log file if there is some traffic from the serial port. If that's not the case there is a problem with your serial port configuration.

btw the ESK300 switches are assembled only partially - there is only one rocker - therefore it may help to try the switch status command with the STATUS_ROCKER_B (rocker on the right side) setting.

Posted by rhitz at Apr 04, 2013 10:50

okay,
it seems to be a problem with the serial port

DEBUG 2013-04-04 12:50:58,964 (EnOcean): Adding shutdown hook to manage unclosed EnOcean connections in case of controller exit.
WARN 2013-04-04 12:50:59,035 (EnOcean): Unknown EnOcean property '<property name = "name" value = "SWITCH_1_STATUS_ROCKER_B"/>'.
INFO 2013-04-04 12:50:59,119 (EnOcean): Created EnOcean Command (ID = '0x0088F141', EEP (Type = 'F6-02-01', Rocker B = 'Off')).

there is no traffic on the port.
I work on Win7 64bit machine.
I will try it at home on my own computer and maybe on a Linkux machine...

thanks for inputs

Posted by wu3mi at Apr 04, 2013 12:07

If it's possible for the 'DophinView Basic' tool from the 'ESK300 Starter Kit' to communicate with the USB300 stick it should be possible for the OpenRemote EnOcean protocol too. Use the same COM port which is working with the 'DolphinView Basic' tool (for example COM4). Note that you have to close the 'DolphinView Basic' tool before running OpenRemote.

Posted by rhitz at Apr 04, 2013 12:34

I forgot that there is something special with Windows 64 bit related to RXTX. The RXTX Windows DLL's from the OpenRemote runtime have to be replaced in case of a 64 bit system.

  • Go to http://www.cloudhopper.com/opensource/rxtx/ and download the Windows-x64 RXTX installation
  • Replace the file rxtxParallel.dll and rxtxSerial.dll inside the /controller/WEB-INF/lib/native directory with the downloaded files

Will add this to the 'EnOcean How To'.

Posted by rhitz at Apr 04, 2013 13:39

HoHo,

so now there is some traffic in the enocean logfile ...

I don't want to post the whole log file so this are the last 4 sentences:

TRACE 2013-04-04 14:50:28,175 (EnOcean): Received serial data from [COM port: COM16, 
Protocol: ESP3, Communication Layer: RXTX] : 0x00 0x0A 0x07 0x01 0xEB 0xA5 0x00 0x00 
0x5C 0x08 0x00 0x88 0xF1 0x41 0x00 0x03 0xFF 0xFF 0xFF 0xFF 0x2E 0x00 0x3A 
DEBUG 2013-04-04 14:50:28,175 (EnOcean): Received radio telegram : [RADIO: RORG=4BS, 
sender ID=0x0088F141, payload=0x00 0x00 0x5C 0x08, status=0x00]
WARN 2013-04-04 14:50:28,176 (EnOcean): Discarded received radio telegram from device
with ID 0x0088F141 because of a configuration error: Command for device with ID 
0x0088F141 has been configured with an invalid EEP F6-02-01 for this device.
WARN 2013-04-04 14:50:28,182 (EnOcean): Discarded received radio telegram from device 
with ID 0x0088F141 because of a configuration error: Command for device with ID 
0x0088F141 has been configured with an invalid EEP F6-02-01 for this device.

The last 2 are a little bit "scary". So maybe the EEP Protocol "F6-02-01" isn't the right one. I will try some setups and compare with the dolphin viewer.
At the screen of "localhost:8080/webconsole" i get only "N/A" instead of OnA or OffA / OnB / OffB.

But I think I am on the right way ... many thanks

Christoph

Posted by wu3mi at Apr 04, 2013 13:54

I'm pretty much sure that the ID 0x0088F141 is not the ID of a switch, it is presumably the ID of your temperature sensor. The profile F6-02-01 is the right one if you want to show the status of your switch. Use the profile A5-02-05 if you want to show the temperature value of the STM330.

Posted by rhitz at Apr 04, 2013 16:32

good morning,

oh, this was my fault, sorry ... bad ID
I updated the ID but now there is following case in the enocean log:

INFO 2013-04-05 07:09:55,644 (EnOcean): Started reader thread for port 
[COM port: COM16, Protocol: ESP3, Communication Layer: RXTX]
INFO 2013-04-05 07:09:55,682 (EnOcean): Received EnOcean gateway base 
ID : 0xFFF17280
WARN 2013-04-05 07:09:55,682 (EnOcean): Unknown EnOcean property 
'<property name = "name" value = "SWITCH_1_STATUS_ROCKER_B"/>'.
WARN 2013-04-05 07:09:55,810 (EnOcean): Unknown EnOcean property 
'<property name = "name" value = "SWITCH_1_STATUS_ROCKER_A"/>'.
WARN 2013-04-05 07:10:01,867 (EnOcean): Unknown EnOcean property 
'<property name = "name" value = "SWITCH_1_STATUS_ROCKER_B"/>'.
WARN 2013-04-05 07:10:01,872 (EnOcean): Unknown EnOcean property 
'<property name = "name" value = "SWITCH_1_STATUS_ROCKER_A"/>'.

Is there a conflict or a problem with the proberty name?

Christoph

Posted by wu3mi at Apr 05, 2013 06:26

Great!
You now have a running OpenRemote/EnOcean system with devices from the EnOcean 'ESK 300 Starter Kit'.
The warnings shouldn't be in the log file but it's not your fault and it's nothing you have to worry about or has an impact on the system behavior.

So go ahead and design your showcase panel.

Posted by rhitz at Apr 05, 2013 18:21

hello,
now i have tried it on a Win Xp machine and it works fine
Rocker A, Rocker B and temp sens work.

Now i want to integrate other enocean modulels and a HOPPE secusignal window handle.
Is there a list of enocean commands for openremote? (modul | command | protocol)

many thanks for your inputs

Posted by wu3mi at Apr 07, 2013 10:02

Hi Christoph,

depending on the EEP 2.5 your window-handle should belong to the profile F6 (RPS-Telegram), class F6-10(Mechanical Handle) and there F6-10-00 (Window handle).
Take a look at this document: http://www.enocean-alliance.org/eep/

In the directory controller/protocol/enocean/profile you find only a file for EepF60201$CommandType.class but no EepF61000$commandType.class. That means to me your window-handle is not (yet) supported.

Rainer is definetily deeper involved to this system than me. Perhaps he can help.

Eberhard

Posted by homer at Apr 07, 2013 13:02

I've added a list of all currently supported 'EnOcean Equipment Profiles (EEP)' and a section which describes the configuration of sensor commands to the 'EnOcean How To'.

Unfortunately, the EEP F6-10-00 for the window handle is currently not supported. This is a bit intentionally because I'm not a big fan of these handles. These handles contain a electromechanical energy harvester which generates energy when the handle is activated. With this generated energy it's only possible to send a single radio telegram while activating the handle. After that there is no way to determine the state of the window handle and the window handle does not send it's state periodically.

My advise is to use a window contact (EEP : D5-00-01) instead of a window handle. Typical window contacts have a solar cell as energy harvester and send the contact state periodically.

Posted by rhitz at Apr 07, 2013 18:53

Short question to Rainer:
in the 'How-To' you write that the EnOcean Command in the EnOcean attributes is equal to the shortcut in the EEP. For my RM250 (F6-02-01) the shortcuts in the EnOcean-document are: R1(Rocker 1st action) and R2 (Rocker 2nd action). In my case it works with ON and OFF. Will it be changed in future or can I change it by myself?

Eberhard

Posted by homer at Apr 08, 2013 07:15

The section I added to the EnOcean how to is the general procedure for typical EnOcean sensors like temperature, humidity, CO2, motion ... . The switch is an exception to the rule because it's a bit more complicated. For example there is also a 4 rocker switch, but it has only the shortcuts R1 and R2. In the future you'll find the documentation for all exceptions in the how to.

So don't change the configuration for your switches.

Posted by rhitz at Apr 08, 2013 07:45

I can report some success!
Running openremote Enocean system on WinXP, as written in the reply above, and on a Win7 64bit machine. I have had a problem with the serial port.
Rainer said on 4th april:

  • Go to http://www.cloudhopper.com/opensource/rxtx/ and download the Windows-x64 RXTX installation
  • Replace the file rxtxParallel.dll and rxtxSerial.dll inside the /controller/WEB-INF/lib/native directory with the downloaded files
    So at the file there ist a java file too > this copy/paste to the <JAVA_HOME>/lib folder

Further i included the EnOcean Dolphin PTM330 module too with the F6-02-01 protocol. > success

@Rainer: Concerning the HOPPE SecuSignal Window Handle:
energyless / energy harvesting is the main point of my research. So electromechanical sensors are very interesting for me. Is there any possibility to include some protocols for my own or can i give some input?

@Eberhard:
Thanks for the input for the commands, but this is very confusing and need a lot of work for reading the files. I will need some time to read it and include the commands to my devices.

thanks
Christoph

I will try some activities with my other modules/sensors and will give a feedback, if this is required?

Posted by wu3mi at Apr 08, 2013 10:23

Hello,

its me again.
As reported my OR system runs on a Win7 64bit and on a WinXp 32bit machine with some EnOcean Sensors.

Now in want to minimize my Hardware and want to port my setup to a raspberry pi.

Openremote runs and i can see my screens in my network (webconsole/iPhone) The only thing is, that there is no communication to the USB300 gateway (/dev/ttyUSB0) (no led blinks when actuator is pressed and in the log i can't see any kind of Comport communication).

Maybe someone can give me hint or a spes for including the USB300 gateway on a raspberry pi.
I have tried the same workaround as at the Win7 64bit machnine with the RXTX from cloudhopper but no positive result.

Many thanks for your answers in advance ...

Christoph

Posted by wu3mi at Apr 09, 2013 13:20

See the comments in OpenRemote How to Install Controller on Rasperry Pi for details how to install ARM compiled version of RXTX.

Posted by juha at Apr 09, 2013 13:47

I have not tested it on the Raspberry Pi but I think other users have solved your serial port problem by the following procedure:

sudo apt-get install librxtx-java

Copy /usr/lib/jni/librxtxSerial.so to /webapps/controller/WEB-INF/lib/native/librxtxSerial.so
Posted by rhitz at Apr 09, 2013 13:49

HoHo,
Success!
OpenRemote with EnOcean Sensors and USB300 Gateway is running on a raspberry pi.
Thanks to Rainer, Eberhard and Juha.

Thanks for the hint with the lirxtx > i have copied not only librxtxSerial.so also librxtxSerial-2.2pre1.so

I will give you further more infos after some tries on the raspberry.

Christoph

Posted by wu3mi at Apr 10, 2013 06:43

Hi

I just programmed most of my house using Enocean and EltakoFVS.
When I am about to finish and pay to make the demo permanent, the program it gone

I change to OpenRemote.

It works so far, except for one major drawback. For the switches OR use the oncommand "10"
All my switches are programmed for on=50 and off=70.
They are hidden well in the house and it will be very time consuming to dig them all out again for reprogramming.
Any way to change commands?

Thanks for a very impressive work

Rikard Larsen

Posted by atata at May 29, 2013 20:26

Hi Rikard,

execution of the "ON" and "OFF" command is equivalent to pressing the left rocker (rocker A) of a regular EnOcean switch.

The following commands can be used to be more specific: ON_ROCKER_A, OFF_ROCKER_A, ON_ROCKER_B and OFF_ROCKER_B.

I could imagine that in this case the use of the commands ON_ROCKER_B and OFF_ROCKER_B could solve the problem.

Posted by rhitz at May 30, 2013 14:28

Hi
Thanks a lot.

The B switch it is, and you saved me taking the house apart once more.

Thank you again!

Regards

Rikard

Posted by atata at May 30, 2013 15:16

Glad to hear you were able to keep your house in one piece. Rainer is the man

Posted by juha at May 30, 2013 19:56

Yes he certainly is.
Now it's up and running again with all lightning with the keyboard as the only tool.
Great start with the Enocean implementation.

Thanks!

Posted by atata at Jun 01, 2013 09:27

Hi

Now it's EEP 1BS(D5-00-01)and EEP 4BS(A5-02-04) that's behaving badly.

I put the ID and "OC" and "TMP" into commands make labels and get something out, but not the truth.
It's not 27 degrees here and both doors are closed.

Are those EEP's supported yet?

Regards

Rikard

Posted by atata at Jun 04, 2013 17:07

Both EEPs are supported.

In case of the window contact (D5-00-01) use the command "CO" (instead of "OC").

How did you determine the EEP of the temperature sensor ? Maybe it's the wrong temperature profile - there are 25 different temperature sensor EEPs (A5-02-01, A5-02-02, A5-02-03...).

Posted by rhitz at Jun 04, 2013 17:51

Hi

The door switch works fine. I just pulled the wrong door. Sorry to be so stupid.

Temp.: I had it running before under the discontinued "EltakoFVS" scaled to 0 to 40, so I do not really know for sure.
It's the temp. sensors from the USB development kit.
I'l try some other options even though I have been through most.

...and thank you very much for your support.

Posted by atata at Jun 04, 2013 19:22

The profile A5-02-05 covers the range 0°C to +40°C.

Posted by rhitz at Jun 04, 2013 19:37

Yes it does.
It's still 37 degrees C though.
DolphinView adv. shows 37.65 too, so my sensor is bad right now.
Outdoor sensor is 19 now.
Thats very plausible.

Thanks!

Edit: I got some light sensors tucked away in the garage.
The hot temp. was a light sensor living almost in the dark and transmitting!

Not one of my best days.

Posted by atata at Jun 04, 2013 20:04

Hi

I can turn on the lights with a command.
I can collect the transition of a real light switch on the wall with a command and a sensor and show it.
I can not collect the transition from a virtual switch (line one) and save it and show that.

Is that right or is it just me that am in the dark again?

Regards

Rikard

Posted by atata at Jun 06, 2013 15:25

I've already written about the unidirectional communication model of the F6-02-01 profile (see this thread). The problem is that the F6-02-01 profile was not intended for bidirectional actuators with status feedback.

Status feedback can be simulated with 2 additional virtual commands, 1 additional sensor and rules.

  1. Create 2 commands to turn the actuator on/off ("CmdSwitchON", "CmdSwitchOFF")
  2. Create 2 virtual commands to store the the actuator status in memory ("CmdVirtualSwitchON", "CmdVirtualSwitchOFF"). Both commands should have the same address parameter. The ON/OFF commands have the "on"/"off" parameters.
  3. Create a command to sense if a physical EnOcean switch has been turned on/off with the commands STATUS_ROCKER_A or STATUS_ROCKER_B
  4. Create a sensor ("SwitchSensor") and link it with the command created in step 3.)
  5. Create a sensor ("VirtualSwitchSensor") and link it with the virtual off command ("CmdVirtualSwitchOFF")
  6. Create a switch object and link it with the virtual commands ("CmdVirtualSwitchON", "CmdVirtualSwitchOFF") and the switch sensor ("SwitchSensor")
  7. Add the following rules
package org.openremote.controller.protocol

global org.openremote.controller.statuscache.SwitchFacade switches;
global org.openremote.controller.statuscache.CommandFacade execute;

rule "Turn Switch Sensor ON"

when               

  Event( source == "VirtualSwitchSensor",  value == "on" )

then
 
  switches.name("SwitchSensor").on();

end
                                                   

rule "Turn Switch Sensor OFF"

when

  Event( source == "VirtualSwitchSensor", value == "off" )

then                                              
                                                                                                        
  switches.name("SwitchSensor").off();

end


rule "Turn Switch ON"

when               

  Event( source == "SwitchSensor", value == "on" )

then
 
  execute.command("CmdVirtualSwitchON");                                               
  execute.command("CmdSwitchON");

end


rule "Turn Switch OFF"

when               

  Event( source == "SwitchSensor", value == "off" )

then
 
  execute.command("CmdVirtualSwitchOFF");                                               
  execute.command("CmdSwitchOFF");

end
Posted by rhitz at Jun 08, 2013 08:19

Hi

My house has now 26 actuators and 21 switches and will get at least 10 more of each before long.
Some switches change several actuators and som actuators is changes by more switches.

The method outlined will be very time consuming and still does not get me all the way to full status memory.

Don't get me wrong I already have this wonderful OpenRemote system for controlling so much in my house, showing pushed switches, reading temperatures and motion from every PC, phone and PAD we have, sending macros etc. and all is for absolutely free.

I am very grateful for this great product, and will do fine without memory for virtual switches.

Regards
Rikard Larsen

Posted by atata at Jun 08, 2013 13:52

Hi

My system is very stable and running on a small Intel Atom PC all the time.
The only thing that makes it stop responding is MicroTorrent.
Luckily I never use that stuff, but it's restart of OR if somebody do

Also labet texts chosen by eg door switches do not work. Allways just showing"on" and "off".

Just for info.

Thanks for a great program

Rikard Larsen

Posted by atata at Jun 15, 2013 10:20

Also labet texts chosen by eg door switches do not work. Allways just showing"on" and "off"

May have to do with http://jira.openremote.org/browse/WEBCONSOLE-57

Posted by pz1 at Jun 15, 2013 10:33

Very nice UI design for your house, Rikard.

This might be worth highlighting further as a OpenRemote/EnOcean use case. Would you be interested in doing a write up, maybe for the next newsletter?

Posted by juha at Jun 18, 2013 23:24

Do you know what tool did he used to create the design?

Posted by nsalazar at Aug 06, 2013 19:01

Hi,

I too am having problems with serial communication on Win7 64bit.
I'm using Aeotec Z-wave and after flowing How To - Z-Wave instructions I get in zwave log file:

Z-Wave communication layer configuration was not found. Defaulting to RXTX...
Z-Wave gateway was not started: Z-Wave communication port was not configured. RXTX gateway not started...

As if I didn't set up Configuration for the Z-Wave protocol in openremote composer.
Would these DLL's fix my problem? If yes, is there a new link to these files cause cloudhopper.com/opensource/rxtx/ is dead.

Thanks!
Nino

Posted by naaaf at Mar 06, 2014 15:36

The listed log entries do not indicate a problem related to the RXTX Windows DLL but I'm sure that you have to replace the existing RXTX DLL in case of a 64bit Windows system.

It seems that the Designer Z-Wave settings are not properly synchronized with the Controller. Did you download the settings to the Controller by means of the following web interface ?

http://<IP of controller>:8080/controller
Posted by rhitz at Mar 06, 2014 16:27

Thanks for quick reply.

I Sync with online designer every time I start open remote. (http://localhost:8080/controller/)

Posted by naaaf at Mar 07, 2014 07:19

After synchronization there should be a controller.xml file in the following directory:
<OpenRemote>/webapps/controller/controller.xml

The <config> section of this file contains the Z-Wave configuration parameters. Do you see something like the following ?

...
<config>
  ...
  <property name="zwave.pad.port" value="7876" />
  <property name="zwave.comPort" value="/dev/ttyUSB0" />
  <property name="zwave.pad.host" value="localhost" />
  <property name="zwave.commLayer" value="RXTX" />
  ...
</config>
Posted by rhitz at Mar 07, 2014 19:42

After every synchronization this file is generated or updated but with some values, that are set in Z-Wave configuration in Designer, missing:

...
<config>
...
<property name="zwave.pad.port" value="7876" />
<property name="zwave.comPort" value="" />
<property name="zwave.pad.host" value="localhost" />
<property name="zwave.commLayer" value="" />
...
</config>

Manual editing of this file does not help.

Posted by naaaf at Mar 10, 2014 11:27

Does your Z-Wave configuration in the OpenRemote Designer look like the following ?

Posted by rhitz at Mar 10, 2014 19:25

Yes it does. Except comPort is "COM6" cause I'm on Windows system.
And "Reset to defaults" option isn't present in my designer. I use Free designer.
No matter what changes I make to this configuration, after sync the controller.xml file stays the same.

After manually editing controller.xml and downloading RXTX JAVA Communication API 2.1-7 and copying "RXTXcomm" to ...\OpenRemote-Controller-2.1.0_SNAPSHOT-2013-06-17\webapps\controller\WEB-INF\lib
communication is now working =)

Still can't synchronize with OR Composer properly.

Posted by naaaf at Mar 11, 2014 11:57

Do I understand it right that client panels are synchronized but only the Z-Wave configuration is not updated ?

Posted by rhitz at Mar 13, 2014 21:03

Hello to all, with the great help on this topic I was able to get the status of my EnOcean switch on my Iphone. Unfortunately I can't get the actual switch to work. For the status I use the command: STATUS_ROCKER_B. When I push the EnOcean switch on my wall, the status changes. But when I push the button on my Iphone nothing happens. I tried all suggestions in this topic but can't get it working. In my Log file I see the following error when I push the button on my Iphone:

WARN 2014-06-17 11:16:15,109 (EnOcean): Unknown EnOcean property '<property name = "name" value = "ON_ROCKER_B"/>'.
INFO 2014-06-17 11:16:15,110 (EnOcean): Created EnOcean Command (ID = '0x00252006', EEP (Type = 'F6-02-01', Command = 'ON_ROCKER_B')).
ERROR 2014-06-17 11:16:15,110 (EnOcean): Failed to send 'Command (ID = '0x00252006', EEP (Type = 'F6-02-01', Command = 'ON_ROCKER_B'))': Base ID offset value '0x00252006' is too large (valid range: 0x00 - 0x7F)

I already tried 0x70 and 0x50 as commands for ON and OFF. According to DolphinViewer these where the commands the switch uses...

Anyone any idea how to solve this? Many thanks in advance.

Posted by koenvdheijden at Jun 17, 2014 10:30

Each EnOcean device has it's own unique ID. If an EnOcean device sends a message, the EnOcean device ID is part of this message. Other EnOcean devices filter received messages based on the included device ID in order to detect if they are interested in the received message. This filter is established by means of the teach-in procedure (e.g. the physical EnOcean switch must be programmed into the lighting actuator by means of the teach-in procedure).
The EnOcean USB interface has not only a unique ID but a whole unique ID range (0x7F=127 unique ID's). In order to configure an EnOcean command that sends a command, you have to provide a relative ID like 1, 2, 3... . The absolute base ID of the EnOcean USB interface is not required. The calculation of the absolute EnOcean ID (absolute base ID of EnOcean interface + relative ID) is automatically done in the background.

The 'ON_ROCKER_B' command should work if you replace the ID '0x00252006' with a relative ID (1, 2, 3...).

Posted by rhitz at Jun 17, 2014 11:20

Dear Rainer,

Thank you very much for your Quick response. I now understand how it works. Is there some way to see what these relative id's are, for instance with Dolphin Viewer (basic)? The "Learn" proces is done by electricians so I was not involved in that. Of course I can always try all relative id's but that are many. Are there also only 127 id's for the acuators? Or is this only for the USB-interface and therfore it's possible that my actuators have a wider range?

Also I tried to replace the id with an relative id (0x01). When I look in the java screen I see this:

WARN HTTP\-Thread\-5: Unknown EnOcean property '<property name = "name" value = "ON_ROCKER_B"/>'.
INFO HTTP\-Thread\-5: Created EnOcean Command (ID = '0x00000001', EEP (Type = 'F6-02-01', Command = 'ON_ROCKER_B')).
TRACE EnOcean serial port reader: Received serial data from [COM port: /dev/cu.usbserial-FTXEZJVQ, Protocol: ESP3, Communication Layer: RXTX] : 0x55 0x00 0x01 0x00 0x02 0x65 0x00 0x00
TRACE EnOcean serial port reader: Received serial data from [COM port: /dev/cu.usbserial-FTXEZJVQ, Protocol: ESP3, Communication Layer: RXTX] : 0x55 0x00 0x01 0x00 0x02 0x65 0x00 0x00

I see here the id is made much longer (as long as the original id), is that correct?

Many thanks!

Posted by koenvdheijden at Jun 17, 2014 12:04
Document generated by Confluence on Jun 05, 2016 09:40