Open williz23 opened 7 months ago
Hi @williz23,
Thank you very much for this detailed issue. I will apply your solution. Apart from that, do you have any other problems with your A5-20-01 or is it working OK ?
Hi @mak-gitdev , So far this is the only issue I found with my A5-20-01, everything else is working OK.
The problem
Hi, I'm currently testing my EnOcean devices with this AddOn. I've got a lot of EnOcean devices (mostly Eltakos) controlled by FHEM. I want to change to HA in the long run but the EnOcean support has been quiet poor until know. With this module the situation seems to improve, great work so far! Anyway, here is the problem: I am using Kieback&Peter MD15-FTL-HE actuators for my radiators which supports the EEP A5-20-01. Almost everything works perfectly but there is a problem with an RCU temperature provided to the actuator. This value is scaled twice before sent, resulting in unusable raw values. I analysed the issue and found the problem in the mapping.yaml file (lines 3666 and 3667):
{% elif entity is search('config_t_RCU$',ignorecase=True) %}
{% set ns.TMP = ((states(entity)|int(default=0))*255/40)|int %}
Here the temperature value of the RCU is scaled to the raw value which is supposed to be used by the actuator. However, since this data is used for an outgoing payload, the scaling will be done in the EnOcean library with the help of the EEP.xml file. The library takes the calculated raw value and scales it once again because it expects the temperature value and not the raw value. The correction to the problem is to do no scaling at all in line 3667:
{% set ns.TMP = (states(entity)|float(default=0)) %}
I also changed the type of the entity to "float" because the temperature is a floating point number, otherwise using "int" would truncate it losing some accuracy during a calculation (e.g. 19.75 would be changed into 19, which is a significant difference). The same applies to line 3665, the temperature value type should be "float" and only the result is an "int".
What type of installation are you running?
Standalone
What version of HA_enoceanmqtt has the issue?
0.1.28-1
What was the last working version of HA_enoceanmqtt?
No response
What type of Home Assitant installation are you running?
Home Assistant OS
Anything in the logs that might be useful to solve the issue? (Strongly recommended if applicable)
Additional information
No response