EnOcean with HA_enoceanmqtt

[mak-dev]

Hi,

This topic is a follow-up of discussions started in WTH is the enocean support that basic where I introduced a solution I developed to use EnOcean devices in HA through MQTT.
It can be installed as an addon, via docker or standalone.
More details on this solution on github (development version), github (stable version) and latest news.
At the moment, the development version is the recommended one.

EDIT: Proper support for Eltako devices is currently being added. For more details, please have a look at this post.

To contextualize this topic, unfold to see the related previous posts.

@cubertt

Anybody tried one of the two mqtt bridges?:

GitHub - rosenloecher-it/enocean-mqtt-bridge: Bridges and translates Enocean messages between a (USB) gateway to a MQTT broker for specific devices.

and:

GitHub - mak-gitdev/HA_enoceanmqtt: Home Assistant wrapper for enocean-mqtt (https://github.com/embyt/enocean-mqtt)

@mak-dev

Hi,

I am the developer of HA_enoceanmqtt.
Like you I was frustrated by the EnOcean integration and I saw that many pull requests where blocked by the Home Assistant developers.
So I decided to make something based on MQTT.

Up to date, the following devices are available:

- [x] `D2-01-0B` 
- [x] `D2-01-0C`
- [ ] `D2-01-0F` (not tested)
- [x] `D2-01-12`
- [x] `D2-05-00`
- [x] `F6-02-01`
- [x] `F6-02-02`
- [x] `F6-05-02`
- [x] `D5-00-01`
- [ ] `A5-12-00` (not tested)
- [x] `A5-12-01`

Adding new devices should not be difficult.

So feel free to try it and I am available to provide support.

@cubertt

Hi mak-dev,

Thanks for visiting us here! I will try it ASAP (hopefully this year ;-)) .

Right now, i am using iobroker with mqtt to controll some enocean devices (TF61-L , https://www.eltako.com/fileadmin/downloads/de/_bedienung/TF61L-230V_30100032-2_dt.pdf and TRF61-j, Jalousie actor (blinds?!) https://www.eltako.com/fileadmin/downloads/de/_bedienung/TF61J-230V_30200032-1_dt.pdf)

It works ok-ish, but i am eager to try something lighter .

Are these two devices supported with your approach?

Cubertt

EDIT: Just read the discription again on github and this is even an Home Assistant Addon !!!Great!

@mak-dev

Yes, the addon is in experimental phase.

Do you have the EEP of your modules ?
I need that to know whether they are already supported or not.
And if not, to know how I could add support for these modules.

@cubertt

Perhaps:
H5-3F-7F or A5-3F-7F
(source: EnOcean-TF61J-Eltako-TippFunk-Jalousieaktor – FHEMWiki )
for the TRF61-j, Jalousie actors

which is after: EEPs - EnOcean Alliance
137 A5-3F-7F Universal

But i m still googeling…

@mak-dev

A5-3F-7F is a universal EEP. It means that it is manufacturer-dependent.
So it is not supported as it stands.
I will need to find more information about this module to integrate it.
I will let you know once I have something ok.

@JAD

Hi,
I came across your Enocean integration yesterday and installed it on my system. So far everything seems to work and I see the devices and entities.
However, I still have a very basic question.
Could you describe the underlying function in more detail? I’m having a bit of a hard time understanding the exact process.
Example: I had an electrician install an Enocean system here in my house. Based on the 14 series from Eltako.
Exactly I have in use Eltako FAM14, Eltako F4SR14-LED, Eltako FSB14 and EnOcean PTM210.
The PTM210 are the buttons and switch lights and shutters. FAM14 is the radio antenna module and if I understand it correctly the center of the whole thing. The FSB14 are for the shutter control and the F4SR14 LED then for the lighting.

I think so far so clear. Currently, therefore, rather a closed system without connection to a smart home solution.

How does Home Assistant and the USB300 fit into the picture. Sends and receives the USB300 commands via Home Assistant and works so to speak as a gateway to the Enocean system, or will the USB300 with Home Assistant to a new center with which I can control all individual sensors and actuators. However, then I have to teach them again on the USB300. Similar to a Zigbee device and ZHA.

What I then also do not understand is how I switch on, for example, a light via Home Assistant.

I realize I really lack the basics here. Could someone help me here?

Thank you very much,

Greetings

Joe

@cubertt

My explanation would be:
Homeassistant and the USB300 represent a (new) “center”.

So you would need to teach in every device you want to control with homeassistant.
In the moment you can just see what happens in the enocean network, like if you use the enocean dolphin softwear for windows.

After teach in, i would expect that the enocen device will be integrated into homeassistant as a device → so look for it in the settings → devices&services and add it to lovelace , for example to control it.

@mak-dev

Hi @JAD,

I may be wrong as I really don’t know Eltako devices but it is my understanding that your installation looks like this:

Your only EnOcean devices are the FAM14 and the PTM210.
All other devices are RS485 devices wired to and control by the FAM14.

From what I read on the FAM14, it is able to control RS485 devices depending on data received from EnOcean devices.
Your electrician must have configured your FAM14 to control this shutter or that light depending on the PTM210 button you press.
This configuration is done on the FAM14 directly.
Whether the FAM14 can learn new EnOcean control devices is still unclear to me.
Should this be possible, then HA thanks to the USB300, would be able to control your RS485 devices through your FAM14, just like it is done with the PTM210.

At the moment, in HA, you should only see actions from PTM210. I am not sure whether you could see actions from the FAM14.

Once again I may be wrong as I am not at all familiar with Eltako and this kind of EnOcean use.

@JAD

Hi mak-dev,
thank you very much for your answer.
I think you have recognized the principle quite correctly.
If I understand you correctly, you mean I would have to teach the USB300 to the FAM14 first, correct?
Each of the RS485 devices seems to have an Enocean address even if it does not speak Enocean. The FAM14 is then the mediator. Hope this is correct…?
How would I have to program the whole thing in Home Assistant? Simply as in your example each device with its ID and the EEP in the Config file. How would I then switch on a lamp, for example???
Thanks for the help.
Greetings
Joe

@mak-dev

Hi,

@JAD

If I understand you correctly, you mean I would have to teach the USB300 to the FAM14 first, correct?

Yes, this is what I understood from my FAM14 readings.

@JAD

Each of the RS485 devices seems to have an Enocean address even if it does not speak Enocean. The FAM14 is then the mediator. Hope this is correct…?

Yes.

@JAD

How would I have to program the whole thing in Home Assistant? Simply as in your example each device with its ID and the EEP in the Config file. How would I then switch on a lamp, for example???

For that, I think I would need to have a better view of your EnOcean network.
Could you run the app with the debug option enabled and share your log file (privately if you prefer).
This way, I could see the EnOcean traffic and better understand what should be done.
EDIT: I may have misread your last question. The answer is yes. As simple as that !
Once you have the addresses and EEPs of your EnOcean devices, you just have to set them in the device config file like in the example and that’s it.
You will have in Home Assistant, under the MQTT integration, new devices and entities that you can then use to control and monitor your EnOcean devices.
By the way, you can also try to run the app with the devices in the example to see how it looks like in Home Assistant.
My previous answer was related to the FAM14 and how we could find the EEP of your devices to set the config file accordingly.

@wallenium

Hi mak-dev

These would be really great: The best would be my hora… they are pretty good and I don’t want to remove them…

• A5-20-04 (Hora SmartDRIVE Mx valve)
• 10 bit EEP for enocean temp/humidity sensors (EEP A5-04-03) not supported
• Binary window sensors (EEP D5-00-01)

I would like to have a docker container for that, and how to integrate. As I am running a plain rasbianOS Pi, the addon does not work for me.

@mak-dev

Hi @wallenium,

D5-00-01 is already supported.
I will have a look at your A5 devices.

@wallenium

I would like to have a docker container for that, and how to integrate. As I am running a plain rasbianOS Pi, the addon does not work for me.

Yes the docker image is in the to-do list.
But I didn’t get why the addon installation doesn’t work for you.
You also have the standalone installation.

@mak-dev

@wallenium
Initial support for A5-04-03 is now available.
A5-20-04 require just a little more time which I am missing these days. I will do it as soon as I have a little time.

@JAD
Please have a look at this discussion on Github.

@cubertt
I found the telegrams to transmit for your TF61J and TF61L.
No particular problem for TF61L. Just missing a little more time at the moment.
But for TF61J, as it is a universal profile, it means that another device can define a completely different telegram and should that other device require to be supported, then problems may arise.
I have to figure out how to handle this case to avoid problems.

@JAD

@mak-dev:
Hi,

thank you very much for your message. Please excuse my late response, I was quite involved familywise.

I have read through the individual posts and also the discussion on Github several times and my head is still buzzing.
Actually, I thought I had some understanding about such things. But there I am out.

What I have understood so far.

1. I have to teach my USB300 stick with the Eltako FAM14 with a “Base ID”.
2. I simulate via the “Devices File” various buttons which can then be addressed in Home Assistant via MQTT. For this I use variations of the “Base ID” of the USB300, in total I have 128 addresses. Each “virtual” button switches the light on or off, or raises or lowers the blinds.

I hope this is correct.

What I do not understand now is:

1. how does for example the actuator for the light (F4SR14-LED) know that the pressed virtual switch addresses it and not another actuator?
2. via this method I can switch the light and the blinds, but not the current status. Is this generally not possible or have I misunderstood something?

I think first up to here. Over the weekend I will have another look at the Enocean integration of FHEM, OpenHAB, ioBrocker and NodeRed. These are supposed to be very well documented in some cases. Maybe that will help me a little in understanding.

Thanks again.

Greetings

Joe

@mak-dev

Hi @JAD

@JAD

What I have understood so far.

1. I have to teach my USB300 stick with the Eltako FAM14 with a “Base ID”.
2. I simulate via the “Devices File” various buttons which can then be addressed in Home Assistant via MQTT. For this I use variations of the “Base ID” of the USB300, in total I have 128 addresses. Each “virtual” button switches the light on or off, or raises or lowers the blinds.

Exactly!

@JAD

What I do not understand now is:

1. how does for example the actuator for the light (F4SR14-LED) know that the pressed virtual switch addresses it and not another actuator?
2. via this method I can switch the light and the blinds, but not the current status. Is this generally not possible or have I misunderstood something?

1. You have to pair your virtual switch with your desired actuator. Normally you should have a LEARN button or LEARN position on your F4SR14-LED. You should put the desired F4SR14-LED (And only this one) into LEARN mode then press and release your virtual switch.
2. To have the status, the FAM14 must generate radio telegrams which indicate the status of the actuators. As I don’t have and don’t know Eltako devices, I don’t know if this is the case. If this is the case, then it should be easy to retrieve the status of the actuator.
   Thus my previous comment:

@mak-dev

For that, I think I would need to have a better view of your EnOcean network.

Could you run the app with the debug option enabled and share your log file (privately if you prefer).
This way, I could see the EnOcean traffic and better understand what should be done.

I wonder whether I should create a new topic to not “hijack” this one with my proposed MQTT-based solution

@JAD

Thank you for your quick reply.

I also think we should possibly open a separate topic. Makes the whole thing a little clearer.

Can you please tell me again briefly what I should prepare when I create the log. Currently I am not sure if I have even one device correctly entered in the Config…

Thanks a lot

Greetings
Joe

@justone

After this glorious addon mak-dev did, I have another EnOcean related question someone might be able to answer.

In the specs of the EnOcean USB stick it says that it’s recommended to not directly stick it into a machine but to use a cable to reduce interference and a better coverage.
I did remember that, when I started playing with some EnOcean buttons and suffered some problems in rooms far from the HA machine.

So I had a closer look and stumbled across the note that such a stick could also be configured acting as a n EnOcean repeater. If comparing prices for EnOcean repeaters using a stick might save some bucks, anyone in here with more experience if this really works?
Or a recommendation which repeater to go for?

And about the topic of this thread … no it wasn’t yet “basic” it was more like a “concept approval that it could have been implemented”. With the addon it’s now as easy as adding Tasmota or Zigbee devices.

[mak-dev]

Hi @JAD,

@JAD

Thank you for your quick reply.

I also think we should possibly open a separate topic. Makes the whole thing a little clearer.

Can you please tell me again briefly what I should prepare when I create the log. Currently I am not sure if I have even one device correctly entered in the Config…

Thanks a lot

Greetings
Joe

Sorry for my late response.
You can start with no device configured in your device list.
Just start the addon with debug and log_packets enabled.
Then just generate some EnOcean traffic.
Then your log should be filled with lines like unknown sensor XX:XX:XX:XX and packet information.

[magic2910]

Maybe this can help (from Iobroker)

GitHub - Jey-Cee/ioBroker.enocean: Connect and control your EnOcean devices...

[CHTHSCH (Thomas Schmidt)]

Thanks for providing this Add-On!

I got it installed but get the following error messages:

2023-01-10 06:16:29,115 DEBUG: FF:BD:74:80->FF:FF:FF:FF (-79 dBm): 0x01 ['0xa5', '0xff', '0x6', '0x98', '0x49', '0xff', '0xbd', '0x74', '0x80', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4f', '0x0'] OrderedDict()
2023-01-10 06:16:29,116 INFO: received: FF:BD:74:80->FF:FF:FF:FF (-79 dBm): 0x01 ['0xa5', '0xff', '0x6', '0x98', '0x49', '0xff', '0xbd', '0x74', '0x80', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4f', '0x0'] OrderedDict()
2023-01-10 06:16:29,119 WARNING: message not interpretable: enoceanmqtt/contact/wohnzimmer
2023-01-10 06:16:29,121 DEBUG: FF:E4:1B:00->FF:FF:FF:FF (-88 dBm): 0x01 ['0xa5', '0xff', '0x2', '0x61', '0x49', '0xff', '0xe4', '0x1b', '0x0', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x58', '0x0'] OrderedDict()
2023-01-10 06:16:29,123 INFO: received: FF:E4:1B:00->FF:FF:FF:FF (-88 dBm): 0x01 ['0xa5', '0xff', '0x2', '0x61', '0x49', '0xff', '0xe4', '0x1b', '0x0', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x58', '0x0'] OrderedDict()
2023-01-10 06:16:29,126 WARNING: message not interpretable: enoceanmqtt/contact/bibliothek

This is my device file:

[contact/wohnzimmer]
address         = 0xFFBD7480
rorg            = 0xD5
func            = 0x00
type            = 0x01

[contact/bibliothek]
address         = 0xFFE41B00
rorg            = 0xD5
func            = 0x00
type            = 0x01

Would appreciate, if I could get some help or hint. Thanks for that

[mak-dev]

Hi @CHTHSCH,

From your log, it seems that the EEP you set in your device file is not correct.
As you can see, the first byte of the packet is 0xA5 which means that your device have rorg = 0xA5 instead of rorg = 0xD5. Hence I am sure that func and type are also different.

What is the reference of your device ? I can help you find your EEP.

[CHTHSCH (Thomas Schmidt)]

It is this one AFRISO Tür-/Fensterkontakt AMC 20 and this one OPUS Tür-/Fensterkontakt

basically the same product. And in the specs it says EEP D5-00-01

[mak-dev]

Strange that !

Ok so either the specs are wrong or you may have used a wrong device address.
Because for sure, the devices with addresses 0xFFBD7480 and 0xFFE41B00 have their RORG equal to 0xA5.

How did you generate the log ? How did you find the device addresses ?

Also, if these devices have a learn button, please press it and report the log. You should have something like “learn message not emitted to MQTT” in the log.

[CHTHSCH (Thomas Schmidt)]

The log is the one, that the add-on generates. How I found the address I sent in the private mail

[Ewoodster81 (Steffen Ewald)]

Hello everyone:

I got two questions and would appreciate any help:

1. Can anyone please tell me how I can figure out the base ID of my EnOcean USB300 stick? This is needed to transmit any signals. Receiving works fine, but so far I cant transmit anything.

2. I am currently trying to figure our how to switch an individual (virtual) button. For example, I try to mimik my 2 rocker switches, EEP F6-02-01. They have two rockers with two states each: “on” or “off”. Since they only show up as binary_senors in MQTT, I can’t set them individually. If I trigger an event: “button_pressed”, it will change the state on all 4 binary sensors simultaneously. I need to set them individually to turn the lights “on” or “off”

All off:

All on:

Thanks!

[mak-dev]

Hi @Ewoodster81,

1- EnOcean Base ID is reported in the MQTT integration on ENOCEANMQTT device. Look at the What’s new discussion on github for more details (on 2022/11/25).

2- If I correctly understood, you want HA to generate F6-02-01 telegrams ? This is not yet available but can be achieved with a kind of a hack of the existing code. See this github discussion for more details.

[heubie]

I’ve been running an Eltako setup for more then 10 years now on a FHEM system. But since we installed a SMA solar installation and Heliotherm heatpump FHEM is not up to the task of running my domotica. So I switched to Home assistant.

Everything is running except… you guest Enocean.

I do have a good understanding on how everything works on FHEM and I bought a USB300 and cloned the starting adress of my tcm120 (which is the interface on my old system)

This gives me the oportunitie to keep the old system running and migrate step by step to HA.
I have seen in the logging that the USB300 is working and the packages do show.

Next step is to see if I can get some of my FUD12 (dimmer) and FSR12 (relay) showing up in MQTT and here where it gets dificult. I did copy the “enoceanmqtt.devices.sampl” and changed the address of rocker 1 to one of my FSR’s but how do I switch this device.

I’m running Generic X86 on a NUC and EnOcean MQTT (dev) as an addon.

Could someone explain me how to control one of the two devices so I can build my knowledge from there.

[DarkDaniel1974]

HI i try to add a EIMSIG window sensor with vibration seonsor. The id is A5-14-0A.

from log:
Device enoceanmqtt/terrace_left (@: 0599F0E8 / EEP: A5-14-0A) updated on device database

2023-01-31 12:34:19,614 DEBUG: 05:99:F0:E8->FF:FF:FF:FF (-53 dBm): 0x01 [‘0xa5’, ‘0x99’, ‘0x0’, ‘0x0’, ‘0xe’, ‘0x5’, ‘0x99’, ‘0xf0’, ‘0xe8’, ‘0x0’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x35’, ‘0x0’] OrderedDict()
2023-01-31 12:34:19,615 INFO: received: 05:99:F0:E8->FF:FF:FF:FF (-53 dBm): 0x01 [‘0xa5’, ‘0x99’, ‘0x0’, ‘0x0’, ‘0xe’, ‘0x5’, ‘0x99’, ‘0xf0’, ‘0xe8’, ‘0x0’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x35’, ‘0x0’] OrderedDict()
2023-01-31 12:34:19,618 WARNING: Cannot find type in EEP!
2023-01-31 12:34:19,619 WARNING: message not interpretable: enoceanmqtt/terrace_left

[heubie]

Update:

I implemented 3 switches and added them to a dashboard to do some testing. If I press this is visible in the dashboard. So al is good.

If I intergrade the USB300 as a “normal intergration” and add a light in configuration.yaml i’m able to add this light (controlled by a FUD12) to the same dashboard.
code:

light:

• platform: enocean
  id: [0xFF,0x8C,0xE8,0x88]
  sender_id: [0xFF,0x8C,0xE8,0x88]
  name: waseiland

I can control it On, Off and Dim. But of coarse the USB300 is now controlled by the “normal intergration” and the MQTT part does not work anymore.

So my question is, how do add a device in (I guess in mapping.yaml) to act as if is does when using the light.py from the “normal Enocean Intergration”

[mak-dev]

Hi @DarkDaniel1974,

This is because it is not yet supported.
I will release support for this EEP and others this week.

[mak-dev]

Hi @heubie,

@heubie

So my question is, how do add a device in (I guess in mapping.yaml) to act as if is does when using the light.py from the “normal Enocean Intergration”

Sorry, I don’t understand your question. What do you mean by add a device ?
Depending on that, the answer can be either enoceanmqtt.devices or mapping.yaml.

In general, Eltako devices have some particularities and are not well supported yet.
But some of them are supported out of the box.
As it seems FUD12 works with the EnOcean integration, then there is a high probability that it is controllable by A5-38-08 telegrams.
A5-38-08 is in the To-Do list.

[heubie]

If I understand how it works… and that is a BIG IF of course… I hope I did the right thing by:

I made a copy of the mapping.yaml and placed it in /config and made sure in de config to use this one.
I copied the light D2-01-12 and made a D2-01-13 to do some testing.
In devices I made the following device:

[eltako/test light]
address = 0xFF8CE888 ← is id learned in FHEM (base +8)
rorg = 0xD2
func = 0x01
type = 0x013
sender_id = 0xFF8CE888 ← used as above since this works in the “normal enocean”

I looked up in light.py from enocean what they send

command = [0xA5, 0x02, bval, 0x01, 0x09]
command.extend(self._sender_id)
command.extend([0x00])
self.send_command(command, , 0x01)
#bval is dimm value between 0 an 64 (0 to 100%)

So to start of I want to edit the mapping file to get two buttons:
one who sends A5 02 64 01 09 sender_id 00 ?? 01 ← for on because 64 = 100%
one who sends A5 02 00 01 09 sender_id 00 ?? 01 ← for off 0%

?? for the which I don’t understand.

In a later stage I would like to be able to send also a value which is determined by a slider to dim the light.

I hope this makes sense since I new to Home Assistant.

I think you are right with the telegram since I looked up the FUD12 EEP (G5-38-08)

[justone]

Hi mak-dev … spent some more time on the D2-01-0E and tried to understand what you do in the mappings against comparing the eep-viewer documents.
Learning from your feedback I think and got what the changed payloads are doing in the ‘switch’ section of the mappings file.

Perhaps not reporting power/energy got to do with CMD5 missing? And a question, would it be that easy to simply add such buttons to the mappings or does is need more code from your side under the hood?

[heubie]

Like justone I’m trying to work out how the mapping file works.
I added the 0x38 0x08 to the mapping file and adjusted the device file.
I do get the switch(SW) to work and come back with “on” and “off”

2023-02-01 21:58:49,947 DEBUG: Sending PUBLISH (d0, q0, r1, m48), ‘b’homeassistant/light/enocean_A53808_FF8CE888_FUD12/config’‘, … (434 bytes)
2023-02-01 21:58:49,948 DEBUG: Sending PUBLISH (d0, q0, r1, m49), ‘b’homeassistant/light/enocean_A53808_FF8CE888_Dimming value/config’’, … (354 bytes)
2023-02-01 21:58:49,948 DEBUG: Sending PUBLISH (d0, q0, r1, m50), ‘b’homeassistant/light/enocean_A53808_FF8CE888_Command ID/config’‘, … (312 bytes)
2023-02-01 21:58:49,948 DEBUG: Sending PUBLISH (d0, q0, r1, m51), ‘b’homeassistant/sensor/enocean_A53808_FF8CE888_rssi/config’’, … (399 bytes)
2023-02-01 21:58:49,948 DEBUG: Sending PUBLISH (d0, q0, r1, m52), ‘b’homeassistant/button/enocean_A53808_FF8CE888_delete/config’‘, … (351 bytes)
2023-02-01 21:58:49,948 DEBUG: Sending SUBSCRIBE (d0, m53) [(b’enoceanmqtt/lights/waseiland/__system/#’, 0)]
2023-02-01 21:58:49,951 DEBUG: 0x02 [‘0x0’, ‘0xff’, ‘0x8c’, ‘0xe8’, ‘0x80’] [‘0x9’] OrderedDict()
2023-02-01 21:58:49,951 INFO: got response packet: OK
2023-02-01 21:58:49,952 INFO: Device enoceanmqtt/lights/waseiland (@: FF8CE888 / EEP: A5-38-08) updated on device database
2023-02-01 21:58:49,952 DEBUG: Sending PUBLISH (d0, q0, r1, m54), ‘b’homeassistant/switch/enoceanmqtt_learn_FF8CE880/config’', … (374 bytes)

but when I send a dim value of 50 the I cannot get this value(EDIM) to show up.

2023-02-01 22:07:14,631 DEBUG: FF:8C:E8:88->FF:FF:FF:FF (-57 dBm): 0x01 [‘0xa5’, ‘0x2’, ‘0x32’, ‘0x1’, ‘0x9’, ‘0xff’, ‘0x8c’, ‘0xe8’, ‘0x88’, ‘0x0’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x39’, ‘0x0’] OrderedDict()
2023-02-01 22:07:14,632 INFO: received: FF:8C:E8:88->FF:FF:FF:FF (-57 dBm): 0x01 [‘0xa5’, ‘0x2’, ‘0x32’, ‘0x1’, ‘0x9’, ‘0xff’, ‘0x8c’, ‘0xe8’, ‘0x88’, ‘0x0’] [‘0x0’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0xff’, ‘0x39’, ‘0x0’] OrderedDict()
2023-02-01 22:07:14,636 DEBUG: enoceanmqtt/lights/waseiland: COM (Command ID)=Command ID 2
2023-02-01 22:07:14,637 DEBUG: enoceanmqtt/lights/waseiland: TIM (Time in 1/10 seconds. 0 = no time specifed)=1280.1 s
2023-02-01 22:07:14,637 DEBUG: enoceanmqtt/lights/waseiland: LCK (Lock for duration time if time >0, unlimited time of no time specified. Locking may be cleared with “unlock”. During lock phase no other commands will be accepted or executed)=Unlock
2023-02-01 22:07:14,638 DEBUG: enoceanmqtt/lights/waseiland: DEL (Delay or duration (if Time > 0); 0 = Duration (Execute switching command immediately and switch back after duration) 1 = Delay (Execute switching command after delay))=Duration
2023-02-01 22:07:14,638 DEBUG: enoceanmqtt/lights/waseiland: SW (Switching command ON/OFF)=On
2023-02-01 22:07:14,639 DEBUG: enoceanmqtt/lights/waseiland: Sent MQTT: {“RSSI”: -57, “COM”: 2, “TIM”: 1280.1, “LCK”: 0, “DEL”: 0, “SW”: 1}
2023-02-01 22:07:14,640 DEBUG: Sending PUBLISH (d0, q0, r1, m58), ‘b’enoceanmqtt/lights/waseiland’', … (67 bytes)

So is there somewhere were I can read how the mapping of actuator (like relay’s dimmers and switches) works. On the part where the readout is sensors there are a lot of examples.

ps. it is quit a steep learning curve…

[mak-dev]

It is not that difficult I think
Did you have a look at the Contributing section of the wiki ?

The mapping.yaml file is used to map EEPs to HA entities thanks to MQTT discovery.
It is used as a link between enocean-mqtt and Home Assistant as shown on the wiki.

For a device to be supported, it has to be supported both by the Python EnOcean library through the EEP.xml file and by the mapping.yaml file.

The most important things are the EEP documentation and the MQTT discovery documentation. Both links are available on the wiki in the contributing section.
The EEP documentation details the content of the telegram(s) sent by the EEP. Each field of the telegram(s) are sent to MQTT thanks to enocean-mqtt.

The mapping job is then to see which MQTT discovery supported entities are best suited to map the content of the telegram. These entities are declared as EEP components in the mapping.yaml file.
The MQTT configuration is then reported in the config section of the component.
The device_config section is used to set parameters for enocean-mqtt to correctly handle the EEP.

[heubie]

Thanks for the quick reply.

I guess some more reading to do.

So if a telegrams is presented the values are updated, but how do I add a on and off button and slider to control the dimmer in a dashboard.