Looking for implementation of Eltako FSB14

[Ewoodster]

Hello.

Thanks to the great work so far, I am now able to control all the lights, sensors and blinds in my house. What is missing so far is the feedback from the actors. This means I can turn on and off the ligths from home assistant, and I can see the status when I do so, but I can't see the status change, when the lights or blinds were activated via the normal wall-mounted switches.

I know that Mak-dev is already working on the LED actors FSR-14 which is great, but I haven't seen the request for the blinds actors FSB14, yet. They will be a tougher nut to crack as their EEP is A5-3F-7F. So far I can open and close the shutters and blinds, and I even managed to control their position with a sort of work around in node-red (measure the run time, then divert it by the time needed to reach the intended position), but I am missing the feedback loop. The FSB14 send their runtime back, so once they are implemented, I have a closed loop control of the shutter positions.

I am willing to give any support needed.

Thank you very much in advance.

[schlegel]

Would be really a cool feature! I'm going crazy with the experiment to calculate the blinds with node red :)

[mak-gitdev]

Hi, @Ewoodster, @schlegel

Sorry for the long delay.
Are you still interested in this one ?
I am having a look at it right now and would require help for field tests.

If so, which kind of installation are you using ? Addon, docker, standalone ?
As well, what is your HA installation ? HAOS, Supervised, Container, Core ?

Thanks

[mak-gitdev]

Hi @schlegel,

Everything seems ok from your log.
The warning is just indicating that A5-3F-7F is not supported in the mapping.yaml, which is just as expected.

Try generating data from your device, if your EEP file is correctly read, the telegrams from the device will be decoded.

[mak-gitdev]

Hi @schlegel,

Anything new ?

[schlegel]

@mak-gitdev I still get the same info messages as before

2023-08-27 12:26:02,410 INFO: received: FF:9B:63:9C->FF:8B:B0:1C (-42 dBm): 0x01 ['0xa5', '0x0', '0xb', '0x2', '0xa', '0xff', '0x9b', '0x63', '0x9c', '0x80'] ['0x0', '0xff', '0x8b', '0xb0', '0x1c', '0x2a', '0x0'] OrderedDict()
2023-08-27 12:26:02,410 INFO: unknown sensor: FF:9B:63:9C
2023-08-27 12:26:02,986 INFO: received: FF:8B:B0:1C->FF:FF:FF:FF (-70 dBm): 0x01 ['0xf6', '0x2', '0xff', '0x8b', '0xb0', '0x1c', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()
2023-08-27 12:26:02,986 INFO: learn request not emitted to mqtt
2023-08-27 12:26:05,639 INFO: received: FF:8B:B0:1C->FF:FF:FF:FF (-70 dBm): 0x01 ['0xa5', '0x0', '0xb', '0x2', '0xa', '0xff', '0x8b', '0xb0', '0x1c', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()

I added your EEP additions and configured the FSB14 like this

[cover/tv_room]
address         = 0xFF8BB01C
rorg            = 0xA5
func            = 0x3F
type            = 0x7F

Any ideas what I do wrong?

[mak-gitdev]

Hi @schlegel,

Could you please activate debug, generate again data from your device and share the entire log, not just a subset ?

Thanks

[niederradenberg]

Hi @mak-gitdev,
great to see that you are working on Eltako FSB14 - I'm also willing to help. I currently have FSR14, FSB14 and FDG14 all working in FHEM homeautomation and want to switch to HA now. Enocean is pretty complete in FHEM. I did some research already:

FHEM/Enocean: https://github.com/mhop/fhem-mirror/blob/master/fhem/FHEM/10_EnOcean.pm
Eltako Protokol description: https://www.eltako.com/fileadmin/downloads/de/Technische_Daten/Inhalte_der_Eltako-Funktelegramme.pdf
Eltako4Homeassistant: https://github.com/JBosecker/home-assistant-eltako/tree/fgw14-communication

I'm pretty sure, that the required information is already there but I'm not skilled enough to integrate this into your framework.
I'm happy to help and test.

Best regards,

Peter

[Ewoodster]

Sorry for my late reply. Lots of work, but now I got one week of vacation.

I have implemented everything as per instruction and get the following feedback:

2023-10-22 16:04:23,579 DEBUG: FF:87:FF:9F->FF:FF:FF:FF (-82 dBm): 0x01 ['0xa5', '0x0', '0xd', '0x2', '0xa', '0xff', '0x87', '0xff', '0x9f', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x52', '0x0'] OrderedDict()
2023-10-22 16:04:23,580 INFO: received: FF:87:FF:9F->FF:FF:FF:FF (-82 dBm): 0x01 ['0xa5', '0x0', '0xd', '0x2', '0xa', '0xff', '0x87', '0xff', '0x9f', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x52', '0x0'] OrderedDict()
2023-10-22 16:04:23,586 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer links: DB3 (Data Byte 3)=0.0 
2023-10-22 16:04:23,588 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer links: DB2 (Data Byte 2)=13.0 
2023-10-22 16:04:23,587 DEBUG: FF:87:FF:A0->FF:FF:FF:FF (-80 dBm): 0x01 ['0xa5', '0x0', '0xf', '0x2', '0xa', '0xff', '0x87', '0xff', '0xa0', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x50', '0x0'] OrderedDict()
2023-10-22 16:04:23,590 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer links: DB1 (Data Byte 1)=2.0 
2023-10-22 16:04:23,591 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer links: DB0 (Data Byte 0)=10.0 
2023-10-22 16:04:23,593 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer links: Sent MQTT: {"_RSSI_": -82, "_DATE_": "2023-10-22T16:04:23.579033", "DB3": 0.0, "DB2": 13.0, "DB1": 2.0, "DB0": 10.0}
2023-10-22 16:04:23,593 DEBUG: Sending PUBLISH (d0, q0, r1, m1082), 'b'enoceanmqtt/Aktor/Rolladen/Schlafzimmer links'', ... (105 bytes)
2023-10-22 16:04:23,594 INFO: received: FF:87:FF:A0->FF:FF:FF:FF (-80 dBm): 0x01 ['0xa5', '0x0', '0xf', '0x2', '0xa', '0xff', '0x87', '0xff', '0xa0', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x50', '0x0'] OrderedDict()
2023-10-22 16:04:23,597 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer rechts: DB3 (Data Byte 3)=0.0 
2023-10-22 16:04:23,598 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer rechts: DB2 (Data Byte 2)=15.0 
2023-10-22 16:04:23,599 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer rechts: DB1 (Data Byte 1)=2.0 
2023-10-22 16:04:23,599 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer rechts: DB0 (Data Byte 0)=10.0 
2023-10-22 16:04:23,600 DEBUG: enoceanmqtt/Aktor/Rolladen/Schlafzimmer rechts: Sent MQTT: {"_RSSI_": -80, "_DATE_": "2023-10-22T16:04:23.587530", "DB3": 0.0, "DB2": 15.0, "DB1": 2.0, "DB0": 10.0}
2023-10-22 16:04:23,601 DEBUG: Sending PUBLISH (d0, q0, r1, m1083), 'b'enoceanmqtt/Aktor/Rolladen/Schlafzimmer rechts'', ... (105 bytes)
2023-10-22 16:04:26,186 DEBUG: FF:87:FF:9F->FF:FF:FF:FF (-82 dBm): 0x01 ['0xf6', '0x1', '0xff', '0x87', '0xff', '0x9f', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x52', '0x0'] OrderedDict()
2023-10-22 16:04:26,188 INFO: received: FF:87:FF:9F->FF:FF:FF:FF (-82 dBm): 0x01 ['0xf6', '0x1', '0xff', '0x87', '0xff', '0x9f', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x52', '0x0'] OrderedDict()
2023-10-22 16:04:26,189 INFO: learn request not emitted to mqtt
2023-10-22 16:04:26,288 DEBUG: FF:87:FF:A0->FF:FF:FF:FF (-82 dBm): 0x01 ['0xf6', '0x1', '0xff', '0x87', '0xff', '0xa0', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x52', '0x0'] OrderedDict()
2023-10-22 16:04:26,290 INFO: received: FF:87:FF:A0->FF:FF:FF:FF (-82 dBm): 0x01 ['0xf6', '0x1', '0xff', '0x87', '0xff', '0xa0', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x52', '0x0'] OrderedDict()
2023-10-22 16:04:26,292 INFO: learn request not emitted to mqtt

[Ewoodster]

This contains one down and one up command from both of my shutters in the bedroom

[mak-gitdev]

Hi @Ewoodster,

From your log, everything is OK now.
I will later share an mqtt cover code to map the decoded telegram data to a cover entity in HA.
In the mean time, you can try to do it if you want 😉

[Ewoodster]

Thank you so much. I would love to help with the mapping, but this may exceed my skill level

[schlegel]

@mak-gitdev When I look into the telegram, I see that I get the travel time back from the actor. Do you have a similar mapping example at hand where values are summed up and compared to a total travel time (which can be set by settings?) ? I would try to support with the template.

[mak-gitdev]

Hi @schlegel,

First of all, sorry because I went missing on this topic.
As I got lots of notification, I lost track of our discussion.
Deeply sorry for that.

Do you have an account on HA community forum ? My ID there is mak-dev

[fabi9163]

Hi together,
already got all lights (including state_feeback) working. Now trying to get also covers working to remove the "Wibutler".

My Setup:

• HA-Addon
• EnOcean MQTT (dev)
• Current version: 0.1.28

If I see it correctly, the EEP-file modification above is not necessary anymore cause its added in the default. (I've added it anyways)

I pressed the original switch and listend for the "feedback" ID of the fsr14. Then added the following in devices-file:

[cover_state/arbeitszimmer]
address = 0xFF83XXXX <-Feedback adress of fsr14
rorg = 0xA5
func = 0x3F
type = 0x7F

triggered the switch, but only got:
2023-12-02 16:54:32,427 INFO: unknown sensor: FE:E2:01:1F (<- Switch Id of arbeitszimmer)
2023-12-02 16:54:32,603 INFO: unknown sensor: FE:E2:01:1F
2023-12-02 16:54:33,659 INFO: learn request not emitted to mqtt (whats this?)

Thought I should get the feedback-telegram now in Protocol-Log. But nothing shows up...have I forgot something? @mak-gitdev.

I've also no clue how to convert this feedback-telegram to a HA-Cover-Entity which can be used in UI-elements and I am also very interested to get the glue-code which you announced previous.

Go on with your great work!

[t-ice]

Hi together,

the FSB14 sends different rorgs as feedback depending on whether a final state has been reached or not, see last page. It would be very helpful to get mqtt message for two defined devices with the same address but different rorg. Currently, just the first matching address is processed further. This means either I miss the final state feedback or run times in case the shutter was stopped before reaching the final state.

Examples:

for receiving run times:
[Raffstore_EG_Wohnzimmer_Rechts_state]
address=0xFF94CE9C
rorg=0xA5
func=0x3F
type=0x7F

for receiving final states:
[Raffstore_EG_Wohnzimmer_Rechts_state2]
address=0xFF94CE9C
rorg=0xF6
func=0x02
type=0x01

Is it possible to support such a configuration?

Thank you for your great work!

[mak-gitdev]

Hi @t-ice,

Yes, it is possible and, in fact, there is a preview version that supports this configuration.
I'll let you know how to test this version.

[einfachtimo]

Hey, would it be possible to get the same Test version? I am using the FSB14 as well :-)

[mak-gitdev]

Hi @einfachtimo,

#57 (comment)

[mak-gitdev]

Hi everyone,

There is a preview version available for the support of Eltako devices.

Supported devices are listed here and you can have a look at this discussion to set up your devices.
If your device is not listed there, note that actuators are controlled by sending GFVS telegrams, so look into the user manual of your device to know how to configure it to work with GFVS.
If you manage to set up a device not listed in that discussion, please add the instructions there so others can benefit from your experience 🙂.

This version will later be merged in HA_enoceanmqtt 0.2.1.
In the meantime, you can use it and let me know if you have any issues.
To report an issue with this preview version or discuss about this version, please use the discussion panel of the dedicated repository.