usambara
(Ulrich)
November 10, 2024, 8:34am
1
I have a new Eltako FTKB, an enocean window/door contact.
Unfortunately the signal it sends, is not recognized.
2024-11-10 09:20:26.824 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG Unknown for payload 31CF3F00000509D5815BAD05A363E90101FFFFFFFF5500 received
2024-11-10 09:20:26.824 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Received unknown RORG
2024-11-10 09:20:29.830 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - RADIO_ERP1 with RORG Unknown for payload 31E5430000050A7B3A719505A363E90001FFFFFFFF5B00 received
2024-11-10 09:20:29.830 [DEBUG] [ernal.transceiver.EnOceanTransceiver] - Received unknown RORG
This occurs independently if there is a thing defined or not. The problem seems to be a level below.
Any idea how to get it run?
Beasty
(Sebastian)
November 10, 2024, 4:03pm
2
Please tell more about your setup.
Which bridge do you use?
Which Thing configuration?
I got two of these contacs and they work flawlessly.
usambara
(Ulrich)
November 10, 2024, 5:04pm
3
I have already a couple of enocean devices. They all work without any problem. As gateway I have a USB300 USB-Gateway. There is also an additional repeater (Eltako FRP61) to bridge longer distances.
At the beginning I worked for a short period, I could learn the controller (for contact, but not for battery). But then it changed somehow and the signals sent are not recognized anymore.
My configuration is
Bridge enocean:bridge:FT1ZI6SV "EnOcean Gateway" @ "Flur EG"
[
path="/dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300_DB_FT1ZI6SV-if00-port0",
enableSmack=true,
espVersion="ESP3"
]
{
Thing contact FensterBadOG "Fenstersensor Bad OG" @ "Bad OG"
[
enoceanId="05A363E9",
receivingEEPId="D5_00_01",
receivingSIGEEP=true
]
}
Beasty
(Sebastian)
November 10, 2024, 6:23pm
4
As your Bridge seems to work with other devices, there should be no problem.
What about your Thing configuration?
As far as I know you don’t have to teach in these contacs into OH. You just add a Thing with the EnOcean ID from the contact and set your channels.
Edit: This config works for me:
UID: enocean:contact:4632083bac:6e2b6b40ec
label: Fensterkontakt 1
thingTypeUID: enocean:contact
configuration:
receivingSIGEEP: true
enoceanId: 052A779F
receivingEEPId:
- D5_00_01
bridgeUID: enocean:bridge:4632083bac
channels:
- id: contact
channelTypeUID: enocean:contact
label: ""
configuration: {}
- id: lastReceived
channelTypeUID: enocean:lastReceived
label: ""
configuration: {}
- id: repeatCount
channelTypeUID: enocean:repeatCount
label: ""
configuration: {}
- id: rssi
channelTypeUID: enocean:rssi
label: ""
configuration: {}
- id: batteryLevel
channelTypeUID: system:battery-level
label: ""
configuration: {}
usambara
(Ulrich)
November 11, 2024, 6:03am
5
Thanks for your assistance. Now I found out where the problem was. Accidentally I had enabled the encrypted communication. Since I disabled that, the contact works as it should. To get also the battery data, I still need to try.
usambara
(Ulrich)
November 11, 2024, 8:37pm
6
Hi Beasty, did you also manage to get the battery level from the device?
With my config I just get a NULL value.
Number:Dimensionless num_Bathroom_Window_Battery "Batterie-Zustand Sensor [%d %%]" <battery> ["Measurement", "Energy"] {channel="enocean:contact:FT1ZI6SV:FensterBadOG:batteryLevel", unit="%"}
Beasty
(Sebastian)
November 11, 2024, 10:22pm
7
No, sadly not.
Let me know, if you find a solution
usambara
(Ulrich)
November 13, 2024, 8:04pm
8
It seems not to be supported, therefor I created a feature request:
opened 08:28PM - 12 Nov 24 UTC
enhancement
This request is similar to
[ [enocean] Add support for Eltako TF-FKB battery st… atus telegram #4578 ](https://github.com/openhab/openhab-addons/issues/4578)
Eltako FTKB devices provide also the battery states in the status message.
[User guide from Eltako](https://www.eltako.com/fileadmin/downloads/en/_bedienung/FTKB-_30000424-1_gb.pdf)
It looks the same as for the TF-FKB, but for EEP: D5-00-01.
```
Voltage telegram:
ORG = 0x07
Data_byte0 = 0x08
Data_byte1 = 0x00
Battery voltage:
Data_byte2 = 0x00..0xFF equivalent to 0..5 V
Energy storage:
Data_byte3 = 0x00.. 0xFF equivalent to 0..5 V
```
Therefore I would propose to implement it also similar and call the new EEP D5-00-01_ELTAKO
The data received looks like this:
`RADIO_ERP1 with RORG _4BS for 059A0825 payload A5EA011A09059A08250001FFFFFFFF5600 received`