Missing Support for EEP A5-20-06 valve actuator Micropelt MVA009 #74
Replies: 9 comments 30 replies
-
|
Hi @stefanhofmann2, This EEP is not yet supported, neither at my level nor at the EnOcean library one. |
Beta Was this translation helpful? Give feedback.
-
|
Hello @mak-gitdev , thanks for your answer so far. One question where can i find the EEP.xml file? I want to add the telegram description. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, That would be nice. Thanks. The default EEP.xml is here. I also recommend to have a look at this wiki page. Do not hesitate if you have any question 👍 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@mak-gitdev In the mapping file their is a direction entry under section device_config. How can i define entities for both directions '1' and '2'. See below: 0x06:
device_config:
command: ""
channel: ""
log_learn: ""
direction: ???
answer: "1"
entities:
- component: "sensor" |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, Direction is used to indicate the direction of the received packet. To define entities for direction 2, you just have to add the corresponding entities to the Note that each device has an internal transmission buffer in enocean-mqtt to send packet to the device. Hope this makes things clearer now. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mak-gitdev , Any idea? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, Could you please share your mapping code for A5-20-06 ? EDIT: Could you please also share the EEP.xml entry for A5-20-06 ? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mak-gitdev see attached the mapping part and the EEP part for A5-20-06 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, I had a look at your files and the direction 2 entities are not correctly configured. This EEP has some subtleties that are not yet handled both in your EEP.xml and mapping file, such as multipurposed fields like SP for direction 2 or TMP for direction 1. 0x06:
device_config:
command: ""
channel: ""
log_learn: ""
direction: "1"
answer: "1"
entities:
- component: "sensor"
name: "curval"
config:
state_topic: ""
value_template: "{{ value_json.CV }}"
unit_of_measurement: "%"
icon: "mdi:valve"
- component: "sensor"
name: "feed_temperature"
config:
state_topic: ""
value_template: >-
{% if value_json.TSL == 1 %}
{{ (value_json.TMP) | round(1) }}
{% endif %}
device_class: "temperature"
unit_of_measurement: "°C"
- component: "sensor"
name: "setpoint_temperature"
config:
state_topic: ""
value_template: >-
{% if value_json.LOM == 1 %}
{{ (value_json.LO) | round(1) }}
{% endif %}
device_class: "temperature"
unit_of_measurement: "°C"
- component: "sensor"
name: "room_temperature"
config:
state_topic: ""
value_template: >-
{% if value_json.TSL == 0 %}
{{ (value_json.TMP) | round(1) }}
{% endif %}
device_class: "temperature"
unit_of_measurement: "°C"
- component: "binary_sensor"
name: "LOM"
config:
state_topic: ""
value_template: >-
{% if value_json.LOM == 1 %}ON{% else %}OFF{% endif %}
- component: "binary_sensor"
name: "TSL"
config:
state_topic: ""
value_template: >-
{% if value_json.TSL == 1 %}ON{% else %}OFF{% endif %}
- component: "binary_sensor"
name: "ENIE"
config:
state_topic: ""
value_template: >-
{% if value_json.ENIE == 1 %}ON{% else %}OFF{% endif %}
- component: "binary_sensor"
name: "ES"
config:
state_topic: ""
value_template: >-
{% if value_json.ES == 1 %}ON{% else %}OFF{% endif %}
device_class: "battery"
- component: "binary_sensor"
name: "DWO"
config:
state_topic: ""
value_template: >-
{% if value_json.DWO == 1 %}ON{% else %}OFF{% endif %}
device_class: "window"
- component: "binary_sensor"
name: "LRNB"
config:
state_topic: ""
value_template: >-
{% if value_json.LRNB == 0 %}ON{% else %}OFF{% endif %}
- component: "binary_sensor"
name: "RCE"
config:
state_topic: ""
value_template: >-
{% if value_json.RCE == 1 %}ON{% else %}OFF{% endif %}
device_class: "problem"
- component: "binary_sensor"
name: "RSS"
config:
state_topic: ""
value_template: >-
{% if value_json.RSS == 1 %}ON{% else %}OFF{% endif %}
device_class: "problem"
- component: "binary_sensor"
name: "ACO"
config:
state_topic: ""
value_template: >-
{% if value_json.ACO == 1 %}ON{% else %}OFF{% endif %}
device_class: "problem"
- component: "number"
name: "valve_position"
config:
command_topic: "req/SP"
min: "0"
max: "100"
step: "1"
mode: "slider"
unit_of_measurement: "%"
icon: "mdi:valve"
- component: "number"
name: "temperature_RCU"
config:
command_topic: "req/TMP"
command_template: "{{value|int(default=0) * 4}}"
min: "0"
max: "40"
step: "0.25"
mode: "slider"
unit_of_measurement: "°C"
icon: "mdi:thermometer"
- component: "switch"
name: "REF"
config:
command_topic: "req/REF"
payload_on: "1"
payload_off: "0"
- component: "switch"
name: "SB"
config:
command_topic: "req/SB"
payload_on: "1"
payload_off: "0"
- component: "switch"
name: "SPS"
config:
command_topic: "req/SPS"
payload_on: "1"
payload_off: "0"
- component: "switch"
name: "TSL"
config:
command_topic: "req/TSL"
payload_on: "1"
payload_off: "0"
- component: "switch"
name: "SBY"
config:
command_topic: "req/SBY"
payload_on: "1"
payload_off: "0"You can make a diff to see what changed and feel free to ask questions about those changes if any. Thanks for contributing, it is almost done 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @stefanhofmann2, Anything new ? |
Beta Was this translation helpful? Give feedback.
-
|
Hello @mak-gitdev , Only the data telegram is set, why? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, Could you share your device configuration for your MVA009 please ? |
Beta Was this translation helpful? Give feedback.
-
|
I think I am exactly at this step with my MVA009 TRV and it seems I am unable to set SPS to 1 (setpoint control). I set SPS to ON in the Controls section and press However during next communication from device and back, it seems that SPS=0 is still being sent: The first log message above mentions that it is sending default data as an answer. I wonder why is the predefined response not saved. |
Beta Was this translation helpful? Give feedback.
-
|
Scratch that. I waited for one more communication between MVA009 and the controller after posting this and now SPS=1 was sent. So maybe I messed up the sequence before. :) |
Beta Was this translation helpful? Give feedback.
-
|
Hello @mak-gitdev After a restart of the addon i always get empty values like in my last comment. |
Beta Was this translation helpful? Give feedback.
-
|
Something looks off. I setup an automation that sends external thermometer termerature to 
|
Beta Was this translation helpful? Give feedback.
-
|
Okay, so the RCU value that is sent to the TRV is floored to 18 and it is then the same like setpoint. So maybe it is still fine that valve is open. I will try to decrease the setpoint even more and see what happens. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @2m, Thank you very much for your tests. |
Beta Was this translation helpful? Give feedback.
-
|
Yup, even with decreased setpoint, it still does not close the valve. Here are the logs: |
Beta Was this translation helpful? Give feedback.
-
|
@2m, Thanks for the logs that confirms the bug.
The RCU temperature sent to the TRV is 0x30 (decimal 48) which translates to 12° at TRV level instead of the 19° that you wanted to send. Regarding the setpoint and the valve position, I can see that you wanted to set the setpoint to 15°C and this has been correctly sent.
The valve position being locked at 100% might be due to another issue or a misconfiguration. I need to have a closer look. In the meantime, if not yet done, you can have a look at the EEP documentation or your MVA009 documentation. Once again, thanks for your tests 👍 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, Glad that it works as you want 👍 Regarding coffee, I don't plan to set up such a thing as I am doing this for fun. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stefanhofmann2, Could you please confirm that you also have this issue #112 ? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to integrate the new Micropelt MVA009 valve actuator. But i saw that the required EEP is not supported yet.
I get the following log entries:
2023-07-15 17:02:43,656 DEBUG: 05:24:CA:4D->FF:FF:FF:FF (-83 dBm): 0x01 ['0xa5', '0x0', '0x80', '0x33', '0x28', '0x5', '0x24', '0xca', '0x4d', '0x80'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x53', '0x0'] OrderedDict()
2023-07-15 17:02:43,657 INFO: received: 05:24:CA:4D->FF:FF:FF:FF (-83 dBm): 0x01 ['0xa5', '0x0', '0x80', '0x33', '0x28', '0x5', '0x24', '0xca', '0x4d', '0x80'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x53', '0x0'] OrderedDict()
2023-07-15 17:02:43,659 WARNING: Cannot find rorg 0xa5 func 0x20 type 0x6 in EEP!
2023-07-15 17:02:43,660 WARNING: message not interpretable: enoceanmqtt/Radiator_Office
Can anyone help me.
Thanks
Stefan
Beta Was this translation helpful? Give feedback.
All reactions