Add full support for A5-06-01 Eltako light sensor

[olivierkeke]

Hi,
Thanks for this nice work! I'm currently trying to get rid of my openhab server I'm keeping only as an enocean to mqtt gateway.

I have a light sensor from Eltako with EEP A5-06-01.
With profile A5-06-01 in HA_enoceanmqtt illuminance values are stuck above 300 lx.
I have not this problem with the openhab enocean addon (range 0lx to 30000lx) since it makes a specific case for Eltako light sensors : https://github.com/openhab/openhab-addons/tree/main/bundles/org.openhab.binding.enocean/src/main/java/org/openhab/binding/enocean/internal/eep/A5_06

Is a specific case for Eltako light sensor feasible in HA_enoceanmqtt?

[mak-gitdev]

Hi @olivierkeke,

Is it the FHD60SB ?

[olivierkeke]

Yes! I found this specifcation which seems clear concerning databytes description.

[mak-gitdev]

@olivierkeke,

Eltako devices are planned to be handled specifically as some of them use customized EEPs.
But as a temporary solution, you can use a custom mapping file and add the following entity code in the A5-06-01 section:

            - component: "sensor"
              name: "fhd60sb"
              config:
                 state_topic: ""
                 value_template: >-
                   {% if (value_json.ILL2|int) == 300 %}
                     {{ (value_json.SVC * 50) | round(1) }}
                   {% else %}
                     {{ value_json.ILL2 | round(1) }}
                   {% endif %}
                 device_class: "illuminance"
                 unit_of_measurement: "lx"

Not sure it is OK so please try it and report the outcome.

[olivierkeke]

Thanks @mak-gitdev! I've added the proposed mapping configuration. I will see the result tomorrow after sunrise (stuck at 0 lx for the moment...).

[olivierkeke]

Concerning the supported devices list, I also tested with success a A5_02_13 device (Trio2sys 02LINE 10020076).

[olivierkeke]

Not sure it is OK so please try it and report the outcome.

@mak-gitdev The device is working well with the mapping you proposed:

Will this be integrated in the develop branch?

[olivierkeke]

As previously said, Eltako devices are to be handled specifically, so I think you can keep it in your custom mapping file until the Eltako support is released.

Why not add each Eltako device as soon as it is confirmed working?
Is there a method to append the standard mapping file with some kind of extra mapping file containing only our additions?

[mak-gitdev]

Hi @olivierkeke,

Is there a method to append the standard mapping file with some kind of extra mapping file containing only our additions?

Not for the moment as I found it easy to browse into the mapping file by folding/unfolding the sections.
But good idea, I keep it in mind.

Why not add each Eltako device as soon as it is confirmed working?

In my local version, I am adding support for Eltako devices in a slightly different manner than the one we used here for your FHD60SB and I want all Eltako devices to use the same method.
Support for this device was quite easy as it didn't require to modify the current code but this is definitely not the case for most of Eltako devices.

Is it clearer now or do you see any issue in what I propose here ?

[olivierkeke]

But good idea, I keep it in mind.

Would you like I submit a pull request for that?

[mak-gitdev]

@olivierkeke,

Yes that would be nice but let's first discuss how to implement it.
I am available on HACF and HA forum: mak-dev

[olivierkeke]

I've just created an account on HACF: hollysaiqs
but I can't create a message for the moment (beginners restrictions)