Request for adding new device

[Alex2952696]

1. Please add a new device - Eltako FSR14-4x. These are 4 relays in one housing.
2. The manual does not specify where the file "mapping.yaml" must be placed and how to integrate it.

[mak-gitdev]

Hi @Alex2952696,

Thanks for your interest.

1. Please add a new device - Eltako FSR14-4x. These are 4 relays in one housing.

I am not at all familiar with Eltako devices and after some readings about the FSR14-4x, it seems that this is not an EnOcean device.
It is my understanding that this is a wired RS485 device which can be controlled by Eltako FAM14 which instead is a kind of EnOcean to RS485 gateway.
Am I right or am I missing something ?
To integrate it, I would need its EnOcean EEP. Do you have it ?

2. The manual does not specify where the file "mapping.yaml" must be placed and how to integrate it.

What is your installation ? Standalone or HA addon ?
By the way, the chapter Adding new devices explains how this file works. You can find the mapping.yaml file in enoceanmqtt/overlays/homeassistant.

[mak-gitdev]

Ok I see.
I never imagine HA to generate such telegrams. I always thought they would always came in to HA.
I may have to rethink mapping.yaml to support that case.
Except F6-02-02 telegrams, do you see any other telegram I should support as generated by HA for Eltako devices ?

Regarding the mapping.yaml file, I am sorry but I still don't understand your question.
It is a file that is used by my python script to map an EnOcean EEP to a list of entities in Home Assistant.
You don't have to focus on it unless you want to modify it to add support for new devices. Is it your case ?
Have a look at standalone installation or HA addon installation for details on how to install HA_enoceanmqtt.

[Alex2952696]

This task is relevant for most Enocean actuators. HA must acts as a pushbutton. So, we have to use different IDs for different puphbuttons. Further, any actuators can be paired with this telegram from HA. The sender ID is set as an increment of the base gateway ID = +0x01h, +0x02h, ..., 0x7Fh.
In the parameters of the new device, you need to set a profile, for example, F6-02 for a two-roker pushbutton, and the value of the increment ID, for example, 0x12h.

[mak-gitdev]

EDIT: The proposed procedure below is a hack of the existing code. The feature is not supported yet.
So for the moment you will only be able to emulate a single device in HA.
Do not try with more devices as it will corrupt the device database and you will have to uninstall then reinstall the addon.

It looks like generating such telegrams from HA is almost already available.

In fact, what you would have to do is to define a sensor like in this example:

[eltako/test]
address         = 0xFFFFFFFF
rorg            = 0xF6
func            = 0x02
type            = 0x01
sender          = 0x<YOUR_SELECTED_SENDER_ID>

where <YOUR_SELECTED_SENDER_ID> is one of the 128 additional IDs of your USB300 dongle.

This will create a new device in HA that can be found in the MQTT integration

Then in HA, I would like you to test the following before I could implement it.
So, for the moment, please define 2 MQTT sensors like this:

mqtt:
  button:
    - name: "eltako_test_f60201_pressed_B0"
      unique_id: man_eltako_test_f60201_pressed_B0
      command_topic: "enoceanmqtt/eltako/test/req"
      payload_press: >-
        {"R1":3,"EB":1,"R2":0,"SA":0,"T21":1,"NU":1,"send":"clear"}
    - name: "eltako_test_f60201_released_B0"
      unique_id: man_eltako_test_f60201_released_B0
      command_topic: "enoceanmqtt/eltako/test/req"
      payload_press: >-
        {"R1":0,"EB":0,"R2":0,"SA":0,"T21":1,"NU":0,"send":"clear"}

Those are two buttons, the first for the press action and the second for the release action of the B0 button of the rocker.
Note that you can replace name and unique_id by the ones you want.
payload_press should be exactly the same as defined above.
For command_topic, it is in the form <DEVICE_ROOT_TOPIC>/req. In my case, DEVICE_ROOT_TOPIC = enoceanmqtt/eltako/test.
You could find your device root topic as follow

Then restart HA or simply reload your manually configured MQTT entities

Then you could add these entities in Lovelace

Finally you should put your Eltako device into LEARN mode and press on the pressed_B0 button then the release_B0 button just after to emulate a brief press on the B0 switch.

If this works OK, then I will make modifications to automatically create press and release button for each of the 4 contacts of the rocker.

Just a reminder that this is not supported yet. The proposed procedure is just a hack of the existing code.
For the moment you will only be able to emulate a single device in HA.
Do not try with more devices as it will corrupt the device database and you will have to uninstall then reinstall the addon.

[mak-gitdev]

Hi,

Did you have a look at my previous message ?

[Mafin-dev]

Hi, any updates on this or is there still no real enocean support in HA? Just listening without sending any telegrams?

[Alex2952696]

Hello, I'm trying to figure it out. I expected to get a switch-type object, which I click on and generate a telegram on the dongle. Which I continue to learn with an actuator. Aleksandr From: mak-gitdev ***@***.*** Sent: Tuesday, November 15, 2022 6:04 PM To: mak-gitdev/HA_enoceanmqtt Cc: Alex2952696; Mention Subject: Re: [mak-gitdev/HA_enoceanmqtt] Request for adding new device (Discussion #1) Hi, Did you have a look at my previous message ? — Reply to this email directly, view it on GitHub <#1 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV4AMR2JB2RSKW624ME5C6DWIOQ63ANCNFSM6AAAAAAR5MG3NU> . You are receiving this because you were mentioned.Рисунок удален отправителем.Message ID: ***@***.***>

[Alex2952696]

Yes It turned out to create buttons eltako_test_f60201_released_B0 and eltako_test_f60201_pressed_B0 ID = 0x00000033 2022-11-15 20:53:45,053 DEBUG: 00:00:00:33->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x0', '0x0', '0x0', '0x33', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})]) 2022-11-15 20:53:45,156 DEBUG: 0x02 ['0x0'] [] OrderedDict() but only a telegram with a basic ID goes on the air see attached file From: mak-gitdev ***@***.*** Sent: Tuesday, November 15, 2022 6:04 PM To: mak-gitdev/HA_enoceanmqtt Cc: Alex2952696; Mention Subject: Re: [mak-gitdev/HA_enoceanmqtt] Request for adding new device (Discussion #1) Hi, Did you have a look at my previous message ? — Reply to this email directly, view it on GitHub <#1 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV4AMR2JB2RSKW624ME5C6DWIOQ63ANCNFSM6AAAAAAR5MG3NU> . You are receiving this because you were mentioned.Рисунок удален отправителем.Message ID: ***@***.***>

[mak-gitdev]

I am surprised that the sender is 00:00:00:33.
If your base id is for example 0xFFEEDD00 and you want to use the offset 0x33 to control an Eltako actuator, then you should define for example:

[eltako/test]
address         = 0xFFFFFFFF
rorg            = 0xF6
func            = 0x02
type            = 0x01
sender          = 0xFFEEDD33

Is your telegram example the result of a press on eltako_test_f60201_released_B0 ?
Otherwise, please also double-check that you used the same payloads as defined in my previous message for press and release.

[Alex2952696]

BaseID = 0x01862BD6 I set BaseID+0x22 = 0x01862BF8 2022-11-15 22:10:27,888 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/eltako/test/req', ... (59 bytes) 2022-11-15 22:10:27,889 DEBUG: Got MQTT message: enoceanmqtt/eltako/test/req 2022-11-15 22:10:27,892 DEBUG: enoceanmqtt/eltako/test: req={'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 0} 2022-11-15 22:10:27,893 DEBUG: Trigger message to: enoceanmqtt/eltako/test 2022-11-15 22:10:27,899 DEBUG: sensor data: {'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 0} 2022-11-15 22:10:27,910 INFO: sending: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})]) 2022-11-15 22:10:27,911 DEBUG: Clearing data buffer. 2022-11-15 22:10:27,944 INFO: Sending packet The same result - telegrams have only BaseID In standard integration, it is also not possible to change the sender's ID. I see a problem in this. From: mak-gitdev ***@***.*** Sent: Tuesday, November 15, 2022 9:25 PM To: mak-gitdev/HA_enoceanmqtt Cc: Alex2952696; Mention Subject: Re: [mak-gitdev/HA_enoceanmqtt] Request for adding new device (Discussion #1) I am surprised that the sender is 00:00:00:33. If your base id is for example 0xFFEEDD00 and you want to use the offset 0x33 to control an Eltako actuator, then you should define for example: [eltako/test] address = 0xFFFFFFFF rorg = 0xF6 func = 0x02 type = 0x01 sender = 0xFFEEDD33 Is your telegram example the result of a press on eltako_test_f60201_released_B0 ? Otherwise, please also double-check that you used the same payloads as defined in my previous message for press and release. — Reply to this email directly, view it on GitHub <#1 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV4AMR7PVW6H4C3AWFVUD3TWIPIP7ANCNFSM6AAAAAAR5MG3NU> . You are receiving this because you were mentioned.Рисунок удален отправителем.Message ID: ***@***.***>

[mak-gitdev]

Ok.

I see two "problems" with your log.

First, your log indicates that you are acting on the button eltako_test_f60201_released_B0.
Could you please press on the button eltako_test_f60201_pressed_B0 and report the log ?

Second, your log also indicates that you successfully change the sender:

01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])

But 0x01862BD6 is not the base ID you should use for what you want to do.
You can in fact, find your base id by doing:

Then

Finally

This is the one you should use as the base for the 128 additionnal IDs.
I will make this information easily accessible in a next update.

[mak-gitdev]

Hi, any news on this one ?
On my side, I have been able to generate the telegrams by following previously described instructions.
Hope it is the same for you.

[Alex2952696]

Hello !

Log for pressing eltako_test_f60201_released_B0 and eltako_test_f60201_pressed_B0 twice.

2022-11-21 21:34:45,150 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/eltako/test/req', ... (59 bytes)
2022-11-21 21:34:45,153 DEBUG: Got MQTT message: enoceanmqtt/eltako/test/req
2022-11-21 21:34:45,168 DEBUG: enoceanmqtt/eltako/test: req={'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 0}
2022-11-21 21:34:45,169 DEBUG: Trigger message to: enoceanmqtt/eltako/test
2022-11-21 21:34:45,173 DEBUG: sensor data: {'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 0}
2022-11-21 21:34:45,178 INFO: sending: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2022-11-21 21:34:45,182 DEBUG: Clearing data buffer.
2022-11-21 21:34:45,266 INFO: Sending packet
2022-11-21 21:34:45,268 DEBUG: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2022-11-21 21:34:45,372 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2022-11-21 21:34:45,372 INFO: got response packet: OK
2022-11-21 21:34:46,647 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/eltako/test/req', ... (59 bytes)
2022-11-21 21:34:46,649 DEBUG: Got MQTT message: enoceanmqtt/eltako/test/req
2022-11-21 21:34:46,654 DEBUG: enoceanmqtt/eltako/test: req={'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2022-11-21 21:34:46,659 DEBUG: Trigger message to: enoceanmqtt/eltako/test
2022-11-21 21:34:46,667 DEBUG: sensor data: {'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2022-11-21 21:34:46,680 INFO: sending: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2022-11-21 21:34:46,683 DEBUG: Clearing data buffer.
2022-11-21 21:34:46,685 INFO: Sending packet
2022-11-21 21:34:46,689 DEBUG: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2022-11-21 21:34:46,793 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2022-11-21 21:34:46,793 INFO: got response packet: OK
2022-11-21 21:34:47,527 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/eltako/test/req', ... (59 bytes)
2022-11-21 21:34:47,527 DEBUG: Got MQTT message: enoceanmqtt/eltako/test/req
2022-11-21 21:34:47,539 DEBUG: enoceanmqtt/eltako/test: req={'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 0}
2022-11-21 21:34:47,542 DEBUG: Trigger message to: enoceanmqtt/eltako/test
2022-11-21 21:34:47,559 DEBUG: sensor data: {'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 0}
2022-11-21 21:34:47,570 INFO: sending: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2022-11-21 21:34:47,576 DEBUG: Clearing data buffer.
2022-11-21 21:34:47,603 INFO: Sending packet
2022-11-21 21:34:47,604 DEBUG: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2022-11-21 21:34:47,706 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2022-11-21 21:34:47,707 INFO: got response packet: OK
2022-11-21 21:34:48,324 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/eltako/test/req', ... (59 bytes)
2022-11-21 21:34:48,324 DEBUG: Got MQTT message: enoceanmqtt/eltako/test/req
2022-11-21 21:34:48,324 DEBUG: enoceanmqtt/eltako/test: req={'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2022-11-21 21:34:48,325 DEBUG: Trigger message to: enoceanmqtt/eltako/test
2022-11-21 21:34:48,325 DEBUG: sensor data: {'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2022-11-21 21:34:48,344 INFO: sending: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2022-11-21 21:34:48,353 DEBUG: Clearing data buffer.
2022-11-21 21:34:48,415 INFO: Sending packet
2022-11-21 21:34:48,418 DEBUG: 01:86:2B:F8->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0x1', '0x86', '0x2b', '0xf8', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2022-11-21 21:34:48,522 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2022-11-21 21:34:48,523 INFO: got response packet: OK

Then, MQTT info :

And corresponding real enocean telegrams, wich I listening by Dolphin View program :

The real USB gateway BaseID is 0x01862BD6.

[KaiKorla]

Hi,

do you discussing this on another topic? I have also a setup with FAM14 + FSR14 + FUD14. So I could help with testing and could providing logs.

regards
Kai

[mak-gitdev]

Hi @balticer,

Sorry I missed your message.

No there is no discussion on this specific topic.
It is still on the To Do list and I will start working on it very soon.
For the moment, you can control your Eltako devices by emulating physical buttons like F6-02-01(-02).
It is now fully supported starting from version 0.1.24.
This is what I called "virtual buttons" and there are a lot of discussions on this topic in the discussion panel.
There is also this wiki page explaining how to configure such virtual buttons.

[KaiKorla]

Hi @mak-gitdev,

i could manage to add it and i can switch the light on and off. I use version 0.1.25.

My configuration:

[Room1_Licht]
address = 0xFFB28888
rorg = 0xA5
func = 0x38
type = 0x08
sender = 0xFFB7B581

But there is a problem. A status change is not recognized by HASS, when i press the wall button. The packet produced by the FAM16 is received, but nothing happens:

2023-03-10 17:26:15,625 INFO: received: FF:B2:88:88->FF:FF:FF:FF (-86 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xb2', '0x88', '0x88', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x56', '0x0'] OrderedDict()
2023-03-10 17:26:15,627 INFO: learn request not emitted to mqtt

Any suggestions?

/edit
Is it right that enocean-mqtt/communicator.py needs an update @https://github.com/mak-gitdev/enocean-mqtt/blob/8c0cd1ec5e1a1ca04e4211f27f948241c07e44c6/enoceanmqtt/communicator.py#L481 to support answer packets from actor-devices, isn`t?

regards
Kai

[mak-gitdev]

Hi @balticer,

Sorry I wasn't that available these days.
The behavior you observe is the expected one.
The fact is that your Eltako device uses a single address with two EEPs, one for control and another one for status.
I may be wrong but my understanding is that this is not very compliant with the EnOcean standard.
Having developed HA_enoceanmqtt with a strong focus on the EnOcean standard, this is not yet supported.
But it is in the ToDo list and it may be available in the next release.

[sipodd]

Hi @mak-gitdev
i just came across your project trying to figure things out and if it might work for me.
However, i recignized some of your comments (here and in HA Forum) on Eltako which make me want to comment here :-)

Eltako is quite a big company and on of the biggest enocean alliance partners,
Actually they got one of the biggest EnOcean Ecosystem on the market....and quality components.
Unfortunatly, they focus on properitary UI's for their equipment with no open source support.

Anyway, not want to promote them...just want to say: i'm sure they stick to the standard and rather use advanced features.

They got a Excel with all Devices and EEPs on their Website Link unfortunatly, in German ...but if needed i could translate it.
The Inforation are in hidden worksheets, but not password protected.

[Alex2952696]

Hello ! There are changes. Now the real gateway ID is specified in the real telegram. But when the sender's ID is changed, the base gateway ID remains in the real telegram.
[eltako/test]
address = 0xFFFFFFFF
rorg = 0xF6
func = 0x02
type = 0x01
sender = 0xFF95EB05 (this is new sender ID)

Base ID is 0xFF95EB00

Real telegram :

[Alex2952696]

Logs:
2022-12-09 19:04:10,385 INFO: Sending packet
2022-12-09 19:04:10,487 INFO: got response packet: OK
2022-12-09 19:04:10,901 INFO: sending: FF:95:EB:00->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0xff', '0x95', '0xeb', '0x0', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2022-12-09 19:04:10,993 INFO: Sending packet
2022-12-09 19:04:11,095 INFO: got response packet: OK
2022-12-09 19:04:11,438 INFO: sending: FF:95:EB:00->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0xff', '0x95', '0xeb', '0x0', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2022-12-09 19:04:11,499 INFO: Sending packet
2022-12-09 19:04:11,603 INFO: got response packet: OK
2022-12-09 19:04:11,949 INFO: sending: FF:95:EB:00->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0xff', '0x95', '0xeb', '0x0', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])

[mak-gitdev]

Hi,

Did you restart the addon after changing the sender in the device file ?

[Alex2952696]

Everything works ! It was necessary to restart the addon !

[mak-gitdev]

Yes.
Each time the device file or mapping.yaml are modified, it is required to restart the addon.
These files are read only once at addon startup.

[Alex2952696]

Great ! Thank you !!!
Could you add following devices :
A5-02-05: Temperature Sensor Range 0°C to +40°C
A5-06-01: Light Sensor Range 300lx to 60.000lx
A5-07-03: Occupancy with Supply voltage monitor and 10-bit illumination measurement
A5-20-01: HVAC Components Battery Powered Actuator (BI-DIR)

[mak-gitdev]

Hi,

A5-02-05, A5-06-01 and A5-07-03 have been added with the latest release.
Please report in #25 if everything is OK. Thanks

[Alex2952696]

Another question: could you help me to create in HA single pushbutton similar as phisical Enocean pushbutton with sending push and release commands ?

[mak-gitdev]

Sorry I completely missed this one.
Did you manage to achieve what you wanted to do ?

[Alex2952696]

Hello ! Unfortunately, I could not take up this project earlier. Testing the project now, I noticed that there are differences between the Enocean standard and its implementation in Eltako equipment. For example, for motion sensors from Eltako (A5-07, A5-08), motion is set by byte D0: 0x0D = motion, 0x0F = no motion. You can add additional information to the "enoceanmqtt.devices.sample" file about which bits are responsible for which function. What do you think about it? I attach a file with a description of communications for Eltako sensors. Alex From: mak-gitdev ***@***.*** Sent: Saturday, December 31, 2022 4:12 AM To: mak-gitdev/HA_enoceanmqtt Cc: Alex2952696; Mention Subject: Re: [mak-gitdev/HA_enoceanmqtt] Request for adding new device (Discussion #1) Sorry I completely missed this one. Did you manage to achieve what you wanted to do ? — Reply to this email directly, view it on GitHub <#1 (reply in thread)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV4AMR6TCF2WM5LYZAISRPTWP6B6BANCNFSM6AAAAAAR5MG3NU> . You are receiving this because you were mentioned.Рисунок удален отправителем.Message ID: ***@***.***>

[mak-gitdev]

Hi @Alex2952696,

In the case you are describing, the differences should not impact the correct interpretation of motion status.

For example, in A5-08-01, the motion status is given by byte D0 as well: motion = 0x08 (or 0x09 depending on button status), no motion = 0x0A (or 0x0B depending on button status).
Expressing all that at the binary level:
Motion:

• 0x0D = 0b00001101 (Eltako)
• 0x08 = 0b00001000 (EnOcean with button pressed)
• 0x09 = 0b00001001 (EnOcean with button released)
  No motion:
• 0x0F = 0b00001111 (Eltako)
• 0x0A = 0b00001010 (EnOcean with button pressed)
• 0x0B = 0b00001011 (EnOcean with button released)
  As you can see, in all cases, the motion status marked in bold is always the same so the motion will always be correctly decoded.

But in general, Eltako devices will have to be handled specifically as explained above:

Otherwise, it may require almost a separate path in the software architecture to deal with that.
Maybe a file eltako.py to support Eltako devices.
The only question would then be at which software layer the EnOcean messages have to be sent to and received from that eltako.py file so that the software architecture remains clean and "smooth".

[tbarbette]

Hi all! I'm hijaking a bit this thread because I have the same setup. With the current dev version, I got everything to work, which is nice :)

However, I've got two questions:

Can we somehow parse the feedback from the FSR14/FAM14?
Here's a view of the answer I get after pressing the ON button of an eltako with 4 push buttons, then the OFF one.

2023-04-03 13:07:34,679 INFO: received: FE:F0:76:FB->FF:FF:FF:FF (-54 dBm): 0x01 ['0xf6', '0x50', '0xfe', '0xf0', '0x76', '0xfb', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x36', '0x0'] OrderedDict()
2023-04-03 13:07:34,858 INFO: received: FE:F0:76:FB->FF:FF:FF:FF (-54 dBm): 0x01 ['0xf6', '0x0', '0xfe', '0xf0', '0x76', '0xfb', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x36', '0x0'] OrderedDict()
2023-04-03 13:07:35,674 INFO: received: FF:E8:0D:13->FF:FF:FF:FF (-74 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xe8', '0xd', '0x13', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4a', '0x0'] OrderedDict()
2023-04-03 13:07:35,674 INFO: unknown sensor: FF:E8:0D:13
2023-04-03 13:07:36,841 INFO: received: FE:F0:76:FB->FF:FF:FF:FF (-49 dBm): 0x01 ['0xf6', '0x70', '0xfe', '0xf0', '0x76', '0xfb', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x31', '0x0'] OrderedDict()
2023-04-03 13:07:37,001 INFO: received: FE:F0:76:FB->FF:FF:FF:FF (-49 dBm): 0x01 ['0xf6', '0x0', '0xfe', '0xf0', '0x76', '0xfb', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x31', '0x0'] OrderedDict()
2023-04-03 13:07:37,849 INFO: received: FF:E8:0D:13->FF:FF:FF:FF (-74 dBm): 0x01 ['0xf6', '0x50', '0xff', '0xe8', '0xd', '0x13', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4a', '0x0'] OrderedDict()
2023-04-03 13:07:37,850 INFO: unknown sensor: FF:E8:0D:13

We can see the call for the two on/off and then we receive an "unknown sensor" after each press.

If I press the on/off button for the relay just next to that one, I get those feedback :

2023-04-03 13:17:55,040 INFO: received: FF:E8:0D:14->FF:FF:FF:FF (-76 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xe8', '0xd', '0x14', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4c', '0x0'] OrderedDict()
2023-04-03 13:17:55,042 INFO: unknown sensor: FF:E8:0D:14
[pressing button for off...]
2023-04-03 13:17:57,200 INFO: received: FF:E8:0D:14->FF:FF:FF:FF (-74 dBm): 0x01 ['0xf6', '0x50', '0xff', '0xe8', '0xd', '0x14', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4a', '0x0'] OrderedDict()
2023-04-03 13:17:57,201 INFO: unknown sensor: FF:E8:0D:14

So I'd bet this is a feedback and I could get the state of my actual relays as the first one is FF:E8:0D:13 and then FF:E8:0D:14 for the next relay. It's probably there but I have no idea what might be the EEP? However I'd say the second byte is the state.

**Second question: what's the best way to get a on/off switch in HA that calls **
So I programmed one virtual BS1 per relay, with AI press turning off the relay, and AO press turning it on.
I've got 20 of those relays :) I'd like to have a standard on/off switch in HA to turn on/off.
Is my best option to create 20 switch.template like that, or did I miss something? :)

switch:
  - platform: template
    switches:
      dining_room_light:
        turn_on:
          - service: select.select_option
            data:
              option: AO
            target:
              entity_id: select.e2m_relay_diningroomlight_action_2
        turn_off:  
          - service: select.select_option
            data:
              option: AI
            target:
              entity_id: select.e2m_relay_diningroomlight_action_2

I think you discussed something like this but I'm not sure to understand everything. Else, a suggestion might be to add in the configuration an option to make the device appear as a real "rocker switch", that is an ensemble of 4 push buttons? Or, like my configuration, a dual on/off.

Thanks for making an Enocean integration that works ! :)

[tbarbette]

Any input @mak-gitdev or @Alex2952696 ? Of maybe a better place to discuss eltako fam14 specifics? Thanks!

[mak-gitdev]

Hi @tbarbette,

So I'd bet this is a feedback and I could get the state of my actual relays as the first one is FF:E8:0D:13 and then FF:E8:0D:14 for the next relay. It's probably there but I have no idea what might be the EEP? However I'd say the second byte is the state.

Try using F6-02-01 as EEP.

**Second question: what's the best way to get a on/off switch in HA that calls **
So I programmed one virtual BS1 per relay, with AI press turning off the relay, and AO press turning it on.
I've got 20 of those relays :) I'd like to have a standard on/off switch in HA to turn on/off.
Is my best option to create 20 switch.template like that, or did I miss something? :)

At the moment, that's the only option you have.
I may have to see how switches can be defined in mapping.yaml in addition of select entities so that users can select the entity that suits best.

[tbarbette]

So that EEP "works" but it's a little hacky. It interprets the relay being ON as B1 being pressed and OFF as B0 being pressed. There's no A1/A0 of course. The nice point is that after a timeout (F4SR14 can turn off lights after a configurable amount of time), I do get the feedback and I have the means to set the state of my switch using the feedback, which is nice.

Off:

On:

I asked eltako for the EEP... We never know, it might work :)

Then, my template becomes this :

switch:
  - platform: template
    switches:
      dining_room_light:
        value_template: "{{ is_state('binary_sensor.e2m_light_state_diningroom_bo_pressed', 'on') }}"
        turn_on:
          - service: select.select_option
            data:
              option: AO
            target:
              entity_id: select.e2m_relay_diningroomlight_action_2
        turn_off:  
          - service: select.select_option
            data:
              option: AI
            target:
              entity_id: select.e2m_relay_diningroomlight_action_2

Except having a proper state EEP which displays as a binary_state, I'm not sure how this could be more easily integrated. Sure we could change the mapping to have the rocker display as a switch, but then the state comes from an unrelated address... So I'd have to do a template switch anyway.

[Mafin-dev]

so you are able to switch lights on and off via HA? This sounds like a huge breakthrough to me. Can you confirm?

[tbarbette]

Got the answer from Eltako. "our F4SR14 is sending the same feedback telegrams as pushbutton telegrams (on and off)". It seems a bit hacky to get the state as the second button of a switch, but I can live with that.

[LutzDi]

Hi all,

I read everything I found without success finding what I'm searching for. I got my Enocean components running so far with HA (Eltako with FAM14 etc.), but only the FSR14-x switches. There is everything working also if I use a physical switch, the status is matched accordingly. Many thx to all for providing the needed information...

But I'm struggling with the FUD14 dimmer switch. The communication is possible between a virtual switch in HA and the FUD14, what I can see is if the light is on and I'm using the virtual switch in HA the light is dimmed up and down...So far, communication between HA and the FUD14 is possible, but I'm missing the following:

• I can't switch the light on or off in the actual config with the virtual switch. I can only dim it if the light is already switched on. And dimming down is not switching of the light but keeps the lowest dim setting.
• I need a dim switch in HA where I can adjust the dim level for the FUD14 accordingly

Any idea how I can solve and achieve these issues? I appreciate your help... Thx a lot...

Cheers
Lutz

[FloCodeRian]

Dear @LutzDi

Would be nice if you could explain particially or share your work somehow.

I'm new to this but very interested in gaining more experiences to help zu halb figuring out

Greets
Flo

[LutzDi]

Hi @FloCodeRian,

I would recommend contacting @mak-gitdev directly because there are other discussions with explanations of how to achieve this with Eltako devices... I think this would be the best way because many of these things are written there... OK?

Thx and brgds
Lutz