Eltako "Baureihe 14 – RS485" (Enocean) Debugging

alq.cev · March 20, 2024, 10:57pm

the values of the target temperature can be accessed using temperature as well as current_temperature for the current temperature of a climate entity

it would be possible to use either events or create a fake eltako climate and set it using climate.set_temperature

eg. get the climate from tado using state_attr(‘climate.tado_smart_thermostat_su0658204416’, ‘current_temperature’) }} and state_attr(‘climate.tado_smart_thermostat_su0658204416’, ‘temperature’) }}

and either throw an event or set the temperature of a fake climate

basic home assistant example:

alias: Tado
description: Notify current temperature when a button is pressed
trigger:
  - platform: device
    device_id: 29214bf168d4e16d79746ce52d83d338
    domain: button
    entity_id: 7d64509ae89ba3dab5ce076ee1e51534
    type: pressed
action:
  - service: notify.mobile_app_ipad
    data:
      message: >-
        The current temperature is {{
        state_attr('climate.tado_smart_thermostat_su0658204416',
        'current_temperature') }} and {{
        state_attr('climate.tado_smart_thermostat_su0658204416', 'temperature') }} degrees
        Celsius.
mode: single

as you said, i think this could be kinda useful

alq.cev · March 21, 2024, 7:00pm

@philipp14

I have added a basic function to the gateway to send arbitrary telegrams. Since each gateway can be used with a different base id, I added the service function for each of them.

# This example allows to send a telegram to turn on the light.

Service: eltako.gateway_1_send_message
Data:
  id: FF-82-3E-04
  eep: A5-38-08
  Command: 1

You can find everything in this gist, the example in the gist can currently only be used for switchable lights and for setting the temperature.

Changed code at line 243 and 244 as well as 147 to 173.

Let me know your thoughts and if you have any questions.

gist.github.com

https://gist.github.com/christophheich/1a7d237dfd6ebdd6cb532a2796a0b69d

automation.yml

alias: Automation
description: ""
trigger: []
condition: []
action:
  - service: eltako.gateway_1_send_message
    data:
      id: FF-82-3E-04
      eep: A5-38-08
      command: 0 # Turn off light (1 turn on light)

This file has been truncated. show original

configuration.yml


# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml

This file has been truncated. show original

gateway.py

"""Representation of an Eltako gateway."""
from enum import Enum
import glob

from os.path import basename, normpath
import pytz
from datetime import datetime

import serial
import asyncio

This file has been truncated. show original

philipp14 · March 24, 2024, 9:34pm

Awesome!!!

Changed it a bit so that you don’t need to distinguish between the cases of EEPs. Meaning to say, you just specifies the arguments and it picks the right EEP. In the logs you can then see if something was missing:

github.com

grimmpp/home-assistant-eltako/blob/062b5372b4aaec84ab51d483318b387868ecfe7d/custom_components/eltako/gateway.py#L219


      
              # Register home assistant service for sending arbitrary telegrams.
              #
              # The service will be registered for each gateway, as the user
              # might have different gateways that cause the eltako relays
              # only to react on them.
              service_name = f"gateway_{self._attr_dev_id}_send_message"
              self.hass.services.async_register(DOMAIN, service_name, self.async_service_send_message)
          
          
          # Command Section
          async def async_service_send_message(self, event) -> None:
              """Send an arbitrary message with the provided eep."""
              LOGGER.debug(f"[Service Send Message: {event.service}] Received event data: {event.data}")
              
              try:
                  sender_id_str = event.data.get("id", None)
                  sender_id:AddressExpression = AddressExpression.parse(sender_id_str)
              except:
                  LOGGER.error(f"[Service Send Message: {event.service}] No valid sender id defined. (Given sender id: {sender_id_str})")
                  return

Hersfeld · March 25, 2024, 10:06am

@Vinnovic how did you get the position status working again?

I updated to v1.4 but its still showing opening/closing even after the shutter stopped. The percentage is show correct but status don’t switch to open.

Vinnovic · March 25, 2024, 7:07pm

I installed the main and that worked ok for me. I haven’t installed the 1.4 version yet

Hersfeld · March 25, 2024, 9:46pm

The changes from the main branch should be in v1.4

@philipp14 do you have any idea why the state of the roller shutters is not reflected correct?

philipp14 · March 26, 2024, 1:03pm

Did you restart home Assistent after the update?

I had once also trouble updating to the next version because HACS just didn’t change the deployment but this was longer ago.
Can you update HACS?

Hersfeld · March 26, 2024, 1:41pm

Yes, I did restart HA. HACS is up to date.

But I copied the covers.py from the main manually over to HA before updating to v1.4 back then. But from my understanding on an update all the files will be overwritten?

Maybe I have to uninstall the eltako integration and reinstall it?

Hersfeld · March 26, 2024, 2:43pm

I removed all eltako entities, deleted the integration and rebootet HA.

Then I downloaded the integration again from HACS, installed it and rebootet.

Unfortunately the state still stays at closing/opening event though the roller shutter stops at the correct percentage and also the percentage is show correctly:

alq.cev · March 26, 2024, 7:00pm

@Hersfeld You may try to copy over this file and check it again, you may need to remove the py cache folder within the eltako integration.

The link contains a bug fix that is available in the feature branch, maybe this fix will work for this situation as well.

github.com

grimmpp/home-assistant-eltako/blob/7fffacdc65fbb8b35def246deb7381ed8aa4ce86/custom_components/eltako/cover.py

"""Support for Eltako covers."""
from __future__ import annotations

from typing import Any

from eltakobus.util import AddressExpression
from eltakobus.eep import *

from homeassistant import config_entries
from homeassistant.components.cover import CoverEntity, CoverEntityFeature, ATTR_POSITION
from homeassistant.const import CONF_DEVICE_CLASS, Platform, STATE_OPEN, STATE_OPENING, STATE_CLOSED, STATE_CLOSING
from homeassistant.core import HomeAssistant
from homeassistant.helpers import entity_registry
from homeassistant.helpers.entity_platform import AddEntitiesCallback
from homeassistant.helpers.entity import DeviceInfo
from homeassistant.helpers.typing import ConfigType
from homeassistant.helpers import entity_registry as er

from .device import *
from . import config_helpers

This file has been truncated. show original

philipp14 · March 27, 2024, 8:34am

There is a merge mistake in it . I took over your corrected method in addition so we have now two times the same method but luckily it takes always the new and second one. That’s why tests worked and I haven’t recognized it.
So it work and will be cleanup soon.
So often it would be much easier to have a type-safe language.

alq.cev · March 27, 2024, 9:49am

Yeah, i see.

One more thing.

You changed the code to add an else, that may cause the cover position to show up as either 0 or 100 when stopping the cover mid flow, surely this will only happen once, after a full opening or closing it will be set.

The way i changed it without the else was more like this approach:

Your cover might be either 100% open or 100% closed at first launch, (there may be situations where the cover might be 50% closed or open, but i think this will happen rarely) therefore setting the value to 0 or 100 and calculate the position on top with:

self._attr_current_cover_position = max(self._attr_current_cover_position - int(time_in_seconds / self._time_closes * 100.0), 0)

may cause the cover to show up correct in most situations at first run, while the added else will cause the cover to show either fully opened or fully closed at first run, even when stopping the cover mid flow.

Just some thoughts

philipp14 · March 27, 2024, 10:25am

Thanks, I will change it back to your implementation. Could you please extend the tests so that I won’t change it back to a bad state.

I found also something which could explain the update problems although I’ve ignored it in the beginning completely and it worked anyways.
In the manifest I’ve forgot to increase the version number of the integration.

I rather think it is more an python cache issue.

Hersfeld · March 27, 2024, 12:37pm

I have deleted the pycache but still the state stays at opening/closing.

Hersfeld · March 27, 2024, 12:52pm

I also tried to delete the Integration and the eltako folder from custom_components. Then I tried both, main and v1.4 but for both I didnt worked.

Maybe there is an error in my configuration?

    - id: 00-00-00-1D
      eep: G5-3F-7F
      name: "Arbeitszimmer links"
      sender:
        id: FF-D6-30-1B
        eep: H5-3F-7F
      device_class: shutter
      time_closes: 16
      time_opens: 17

philipp14 · March 27, 2024, 9:58pm

Hello @Hersfeld,

you are right, I do have the same behavior.

For me the documentation about cover states is not really clear. In which state is it when half-open? Other integrations use always open if it is not completely closed. Then also both buttons work.

I made it now like in this example:

I pushed changes to main. Can you please test if it works like you would expect it?

Hersfeld · March 27, 2024, 10:06pm

@philipp14 Tested with the main branch and its working again as expected. State changes to Open X% and I can click open/close button.

Thank you very much for the fix!

philipp14 · March 27, 2024, 10:10pm

Sorry for me it was until now unclear what the correct in between state was.

I will write some unit-tests to ensure it won’t change back and then I probably will make a new release. There are already some new features on main.

philipp14 · March 27, 2024, 10:13pm

@Hersfeld Do the percentage values fit?

Hersfeld · March 27, 2024, 10:19pm

Yes, the values fit.