romehein / homeassistant_enocean Goto Github PK

Hi @RomeHein
Many thank for your work !
It allowed me to integrate my cover in my home assistant (docker) !

Can i have some explanation on adding a soft remote ?
I used the example in the README.md (with button), however when I add a card on the dashboard it is seen as if it was a light, and i can change the state from the dashboard. That seems normal, as written is the README.md.

I set up "behavior: button", by doing so I have only 2 switch in home assistant whent is should be 4
Only one is linked.
Should modify switch in the confuguration.yaml ?

Here what is in my configuration.yaml:
`#Soft remote gris
switch 09-1:

platform: enocean
id: [0x00, 0x31, 0xCF, 0xA1]
name: interrupteur soft gris
channel: 0
behavior: button
platform: enocean
id: [0x00, 0x31, 0xCF, 0xA1]
name: interrupteur soft gris
channel: 1
behavior: button
`

PS : Also did you implement a teach in ? how does it work ?
PS2: I can help to translate the readme in french, if you wish, or test some products =)

Again thank you again, for all your work =)

Hi,

I'm currently developping a custom component for home assistant that handles some of the Eltako's products , which are based on EnOcean.
More especially :

• F4SR14 : non-dimmable light
• FUD14 : dimmable light
• FSB14 : cover

Because the F4SR14 is not dimmable, the message waited by the actuator is not the same and does not work with the enocean component.

My component is mostly based on this repo and the way I handled it is by creating classes for each type of light ( --> is class inheritance ) :

F4SR14Entity --> EltakoLightEntity --> EltakoEntity, LightEntity
FUD14Entity --> EltakoLightEntity --> EltakoEntity, LightEntity
# the following is not done yet
FSB14Entity --> EltakoCoverEntity --> EltakoEntity, CoverEntity

F4SR14Entity and FUD14Entity set the properties correctly (ColorMode.ONOFF, ColorMode.BRIGHTNESS, ...) and implement the turn_off, turn_on and value_changed methods.
Based on a device_class option in the config, the right class is used.

Implementing all of this in another component is not the best solution :

• I can't use any of other EnOcean devices because of multiples uses of dongle
• A certain part of the component is the same as EnOcean

My tought :

Can't we add a "device_class" config for each device type (light, cover, ...) so that we can specify which class to use ?
Adding more systems or devices to the code will be easier : simply add new classes.

What do you think ?

Vincent

I'd like to use my switch with two relais from Eltako: FMS61NP

I switch from FHEM to Home Assistant. I ve tried to config for my self but it dosn't work. So can you integrate it, please?

Thanks

Here is my protokoll from FHEM (i have replaced the Hex Device ID and the hex Sender ID and mark they bold)

2023.10.24 10:21:14 3: EnOcean set EnO_deviceID B0
2023.10.24 10:21:14 4: EnOcean EnO_deviceID sent PacketType: 1 RORG: F6 DATA: 70 SenderID: senderID STATUS: 30 ODATA:
2023.10.24 10:21:14 5: TCM TCM_ESP3_0 sent ESP: 550007000111F670senderID30EB
2023.10.24 10:21:14 5: DevIo_SimpleWrite TCM_ESP3_0: 550007000111F670senderID30EB
2023.10.24 10:21:14 5: TCM TCM_ESP3_0 received ESP: 5500010002650000
2023.10.24 10:21:14 5: TCM TCM_ESP3_0 RESPONSE: OK
2023.10.24 10:21:15 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630deviceID3002FFFFFFFF5000C6
2023.10.24 10:21:15 5: TCM_ESP3_0: dispatch EnOcean:1:F6:30:deviceID:30:02FFFFFFFF5000
2023.10.24 10:21:15 5: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:30:deviceID:30:02FFFFFFFF5000
2023.10.24 10:21:15 4: EnOcean EnO_deviceID received from IODev: TCM_ESP3_0 PacketType: 1 RORG: F6 DATA: 30 SenderID: deviceID STATUS: 30
2023.10.24 10:21:15 3: EnOcean set EnO_deviceID A0
2023.10.24 10:21:15 4: EnOcean EnO_deviceID sent PacketType: 1 RORG: F6 DATA: 30 SenderID: senderID STATUS: 30 ODATA:
2023.10.24 10:21:15 5: TCM TCM_ESP3_0 sent ESP: 550007000111F630senderID309D
2023.10.24 10:21:15 5: DevIo_SimpleWrite TCM_ESP3_0: 550007000111F630senderID309D
2023.10.24 10:21:15 5: TCM TCM_ESP3_0 received ESP: 5500010002650000
2023.10.24 10:21:15 5: TCM TCM_ESP3_0 RESPONSE: OK
2023.10.24 10:21:15 2: AttrTemplates: got 269 entries
2023.10.24 10:21:15 5: TCM TCM_ESP3_0 received ESP: 55000707017AF670deviceID3002FFFFFFFF530002
2023.10.24 10:21:15 5: TCM_ESP3_0: dispatch EnOcean:1:F6:70:deviceID:30:02FFFFFFFF5300
2023.10.24 10:21:15 5: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:70:deviceID:30:02FFFFFFFF5300
2023.10.24 10:21:15 4: EnOcean EnO_deviceID received from IODev: TCM_ESP3_0 PacketType: 1 RORG: F6 DATA: 70 SenderID: deviceID STATUS: 30