grimmpp / home-assistant-eltako

Integration for Eltako 14 series in Home Assistant
MIT License
36 stars 7 forks source link

FTS14EM - Visu (Status remains unknown): #43

Closed LHBL2003 closed 8 months ago

LHBL2003 commented 8 months ago

Hi,   I can currently control FSR14_4x via home-assistant-eltako. Only for the FTS14EM I do not get the status displayed in HA. I can do it in FHEM.   Upper rotary switch position: 10 Lower rotary switch position: UT 1 Port 5

  Config

eltako:
  gateway:
    - id: 1
      base_id: FF-00-00-00
      device_type: fgw14usb
      devices:
        binary_sensor:
        - id: 00-00-10-15
          eep: F6-02-01
          name: FTS14EM - KG-S1 - Signal 5 (Frei)
          #device_class: presence 
          #invert_signal: False
 
logger:
  default: info
  logs:
    eltako: debug

  EEP: F6-02-01 is also set up by default in FHEM when FHEM scans the Eltako bus. 

Logging Message (It looks as if the signal is detected by HA.):

2024-01-15 20:25:52.653 DEBUG (Thread-2) [eltako] [Gateway] [Id: 1] Received message: <RPSMessage from 00 00 10 15, db0 = 70, status = 0x30 (T2, N, 0 repetitions)> 2024-01-15 20:25:52.656 DEBUG (SyncWorker_12) [eltako] [Binary Sensor] Send event: eltako.gw_1.btn_pressed.sid_00-00-10-15, pressed_buttons: '["RT"]' 2024-01-15 20:25:52.657 DEBUG (SyncWorker_12) [eltako] [Binary Sensor] Send event: eltako.gw_1.btn_pressed.sid_00-00-10-15.d_RT, pressed_buttons: '["RT"]' 2024-01-15 20:25:56.784 DEBUG (Thread-2) [eltako] [Gateway] [Id: 1] Received message: <RPSMessage from 00 00 10 15, db0 = 00, status = 0x20 (T2, U, 0 repetitions)> 2024-01-15 20:25:56.786 DEBUG (SyncWorker_23) [eltako] [Binary Sensor] Send event: eltako.gw_1.btn_pressed.sid_00-00-10-15, pressed_buttons: '[]' 2024-01-15 20:25:56.787 DEBUG (SyncWorker_23) [eltako] [Binary Sensor] Send event: eltako.gw_1.btn_pressed.sid00-00-10-15.d, pressed_buttons: '[]'

Bildschirmfoto 2024-01-15 um 20 27 18

Visu (Status remains unknown):

Bildschirmfoto 2024-01-15 um 20 28 11

Do you have any idea what I should configure?

With eep: D5-00-01 it gets even worse.

Bildschirmfoto 2024-01-15 um 21 27 43
grimmpp commented 8 months ago

Hello @LHBL2003,

So now you can use for switch telegrams F6-02-01 and F-02-02 and for contact telegrams you can use D5-00-01. If it's wrongly configured the warning will tell you that message type and eep does not fit together. I think in your case (FTS14EM) you can leave the configuration with eep F6-02-01.

LHBL2003 commented 8 months ago

I get no signal in the visualization. I have tested all 3 variants. Is there anything else I need to consider?

Preparation


Test 1

Bildschirmfoto 2024-01-19 um 19 54 09 Bildschirmfoto 2024-01-19 um 19 55 34

(unbekannt = Unknown)

Bildschirmfoto 2024-01-19 um 19 54 53

Test 2

Bildschirmfoto 2024-01-19 um 19 55 57 Bildschirmfoto 2024-01-19 um 20 00 47

(unbekannt = Unknown)

Bildschirmfoto 2024-01-19 um 19 57 45

Test 3

Bildschirmfoto 2024-01-19 um 20 01 15 Bildschirmfoto 2024-01-19 um 20 04 30

(unbekannt = Unknown)

Bildschirmfoto 2024-01-19 um 20 02 50
LHBL2003 commented 8 months ago

Sorry the pictures for the test were not uploaded correctly. I have just updated it.

grimmpp commented 8 months ago

Hallo @LHBL2003,

can you test with newest release V1.3.4?

LHBL2003 commented 8 months ago

Oh yes! You've found the problem ;) I get a status (Rock)

Bildschirmfoto 2024-01-22 um 19 02 03

Well then I can start adding FHEM. That was the last interface point I was missing :) Thank you very much for your help.


Perhaps this will help you to understand why the EM modules communicate so differently. In my case it says 13/17 on the back.