search

grimmpp / home-assistant-eltako

Integration for Eltako 14 series in Home Assistant
MIT License
28 stars 5 forks source link

Actuators show no status - ELTAKO ´14 Devices #72

Closed FloCodeRian closed 4 months ago

FloCodeRian commented 4 months ago

Hi their,

I´m very happy about this repo because I´m trying to get my setup working for a very long time.

Unfortunately I´ve experienced a problem with it. Within Homeassistant I can't see any status updates of control actuators. Is this behavior normal ? beside this problem binary sensors are working perfectly.

My setup is eltako only ... fam, fsr, fgw, fud, fstem
in the moment some of those actuators are controlled with a Homee in parallel. the Homee can see all states of the actuators.

In homeassistant I see changes are somehow recognized, because every command via home or fst14em - the "last message received" - updates

Automatisierungen

but the FUD´s remain "grey"

Logbuch

as well as the state of the FSR 14 keeps of , while the light turns on be triggering it with ha

Aus

i´ll get some "fake" states of the actuators with this text in configuration.yaml "general_settings: fast_status_change: False # True: Changes status in HA immediately without waiting for actuator response. Default: False"

but that's not what I need

I´d love if someone can help me with any further advices.

grimmpp commented 4 months ago

I've tried to reproduce it. I used a FUD14 (connected via FGW14-USB to HA) and a regular EnOcean Switch from Eltako. When dimming by using the wall mounted switch I get e.g.: image and it shows the status correctly in HA, without doing something in HA: image image

The same happens when I choose a dim to e.g. 60%. For a very short moment is is displayed in grey and then it changes to yellow.

On which version did you test. My tests were on v1.3.7.

Could it be that your id of FUD in the configuration is not matching? This would explain wait you see incoming messages but HA entity is not reacting. Sending working independent of it. Some people forget that the ids must be defined in hexadecimal. (If your device e.g. has got address 10 in PCT14 then that would result in 00-00-00-0A) You can also see the id (= address) in the debug logs.

FloCodeRian commented 4 months ago

I´m very sorry for the confusion.

As you expected ... change the ID to the one with a lot of zeros ... like 00-00-00-11 and 00-00-00-13 ... it is working perfect as expected ... All my ID´s had like the BASE ID included... because of my old setup with the built-in enocean integration. Probably it was because my setup contains an additional FTS14FA. Which I´m actually no sure if I really need it.

nevertheless - thanks for your support!

your integration work just perfect :)