Can you please add Eltako FTKE EEP F6-10-00 and FRW Smoke detector ? [DONE]

[Ekgev]

I use a lot of enocean devices and would like to implement especially FTKE (F6-10-00) and FRW Smoke Detektor ? Would be very Great! Thanks!

[mak-gitdev]

Hi,

• F6-10-00 should be easy to add. If already done, how did you install HA_enoceanmqtt. Addon or standalone ?
• FRW seems to have EEP A5-30-03. Could you confirm ? Does it also have a temperature sensor ?

[Ekgev]

Hi, I use the Addon in Home Assistant. And yes, I guess EEP A5-30-03 could be right. It does not have a temp Sensor.

[stefanhofmann2]

I am using the Eltako window sensor FTKE EEP F6-10-00 too. Where can i find the mapping file? Thanks

[mak-gitdev]

Hi @stefanhofmann2,

Could you please open a new discussion. It will be easier to track in the case someone else has the same question 👍

[mak-gitdev]

Ok.

I have an initial support available for your F6-10-00.

As I don't have access to all EnOcean devices, I organized this script so that the end-user can do field tests when requesting a new device support.
For that, it requires that you modify your mapping.yaml file.

Here are the steps to follow:

• First please stop the addon.
• Then copy the mapping.yaml file to your home assistant /config/mapping.yaml. Note that /config/ is the directory where you have your Home Assistant configuration.yaml file.
• Then, as you are using the addon, you have a configuration entry named mapping_file. Set this entry to /config/mapping.yaml and save your configuration.
• Finally, add your F6-10-00 device in your device file then restart the addon.

After that you should see entities corresponding to your device in HA.
Please then report whether the created entities are OK or require modifications, with a picture if possible.

[Ekgev]

Sorry, I thought that a restart of HA would be sufficient. Seems not. Anyway, sorry for that!

[mak-gitdev]

No problem at all.
But you're right, that's strange. I would have thought that a restart of HA would be sufficient.

Oh wait ! I may just get it I think.
It is all about containers, the addon as well as HA. Restarting HA only restart the HA (core?) container but not the other containers (a.k.a the addons). That may be that.

[commentsonly]

Yep now both do work .... but you still missed the vital line, the "device_class"

            - component: binary_sensor
              name: "state_2p"
              config:
                 device_class: window
                 state_topic: ""
                 value_template: >-
                   {% if value_json.WIN == 3 %}OFF{% else %}ON{% endif %}

[mak-gitdev]

I added it first but I finally removed it because I wondered whether this EEP might be use for things other than windows.
But you may be right. I will add it.

[commentsonly]

you can overwrite a default device class if needed. What I rate a bad attitude is starting with no device class and then manually adjust each of the devices since you easily get lost since you can't easily figuere out at which point the current device class was defined.
From the specs in HA it says: window: Control of a physical window that opens and closes or may tilt. http://www.home-assistant.io/integrations/cover/#device-class I do wonder here since I never say a device_class aligned to a sensor but to a binary sensor. But perhaps I missed that because there's no 'tilt' icon anyway.
But I'm not a YAMLizer inside HA apart from the dashboard and ESPhome.

[Ekgev]

Obviously the standard enocean integration cannot be used parallely to your (much better) MQTT Addon.
Can this be solved of is it recommended to shift completely to your Addon?
thanks!

[mak-gitdev]

Thanks.

As long as they share the same USB300 dongle, their use is mutually exclusive.
So it is up to you.
If all your EnOcean devices are supported by my solution, then you could use it if you like it.
But if some devices are not yet supported, you may want to wait for them to be added and keep using the official EnOcean integration.

[mak-gitdev]

Note: I edited the title of the discussion for clarity.

[Ekgev]

Without any doubt, the official integration is relatively bad, so I would like to go with and support your Addon. - So would it be possible to Connect two USB300 sticks to the rasperry parallely and use one of them exclusively for your addon? Could you integrate also the FRW? Would ne Great. Thanks for all your efforts

[mak-gitdev]

Yes, of course you can use a second dongle. No problem for that.

For FRW, I will have a look this evening.
Just hope A5-30-03 is the correct EEP.

[Ekgev]

I have checked this with the Eltako docu, it seems to be this
FRW
ORG = 0x05
Data_byte3 = 0x10 = Alarm
0x00 = Alarm-Ende
0x30 = Batteriespannung < 7,2V

[Ekgev]

Please see here https://www.eltako.com/fileadmin/downloads/de/Gesamtkatalog/Eltako_Gesamtkatalog_KapT_low_res.pdf
Page 11, 12
Does this help?

[mak-gitdev]

Hi,

Sorry for late response.
It's even more confusing :).

But we can figure this out I think.
You should have a test button on the smoke detector as for all smoke detectors.
Press this button, it should generate an EnOcean telegram indicating an alarm.
Then report the log entries generated by this telegram.
For that, do not forget to enable debug and log_packets in the addon configuration.

[Ekgev]

I hope I did this correctly. The Result is

2022-11-20 16:49:41,273 DEBUG: 05:1D:95:70->FF:FF:FF:FF (-68 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x1d', '0x95', '0x70', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x44', '0x0'] OrderedDict()
2022-11-20 16:49:41,275 INFO: received: 05:1D:95:70->FF:FF:FF:FF (-68 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x1d', '0x95', '0x70', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x44', '0x0'] OrderedDict()
2022-11-20 16:49:41,277 INFO: unknown sensor: 05:1D:95:70
2022-11-20 16:49:41,545 DEBUG: 05:1D:95:70->FF:FF:FF:FF (-68 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x1d', '0x95', '0x70', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x44', '0x0'] OrderedDict()
2022-11-20 16:49:41,546 INFO: received: 05:1D:95:70->FF:FF:FF:FF (-68 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x1d', '0x95', '0x70', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x44', '0x0'] OrderedDict()
2022-11-20 16:49:41,549 INFO: unknown sensor: 05:1D:95:70

[mak-gitdev]

Ok.
So good news, your smoke detector is already supported.
Use EEP F6-05-02. It should be good.

[Ekgev]

Thank you very much. I will test it tomorrow

[Ekgev]

It works, thank you very much! Great work!

[Ekgev]

If you like, it would be nice to implement also Eltako FTFSB (A5-04-02). Then I would be able to avoid the original Enocean integration ;-)

[mak-gitdev]

Great it works fine.

Just open a new discussion for A5-04-02. It should be very easy to integrate.