Requesting support for EEP D02-05-02 #105
Replies: 12 comments 28 replies
-
|
Hi @OlwinFroon, I will have a look 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, much appreciated. Also, pairing a remote to a drive is covered by the documentation, but I didn't find anything about how to pair a shutter drive to the system. |
Beta Was this translation helpful? Give feedback.
-
|
Yep. |
Beta Was this translation helpful? Give feedback.
-
|
This is explained here in the wiki. Then, once your device is in pairing mode, simply follow the procedure described in the link shared above to send that pairing telegram to complete the learn process. |
Beta Was this translation helpful? Give feedback.
-
|
Okay, I tried that. Power cycling is the only way to put these shutter drives in pairing mode for three minutes. So I did that and switched ENOCEAN_LEARN on. Nothing happened. According to the logs, the drive sends on power-up, followed by "message not interpretable". If I'm not mistatken, that's a RORG D1 message ... which isn't defined by the EnOcean Alliance, right? Immediately after that, the drive sends which would be the current shutter state (0%, unknown angle). 3 minutes later (end of pairing mode): again followed by "message not interpretable". :( |
Beta Was this translation helpful? Give feedback.
-
|
So, the D1 telegram might be manufacturer code for "install mode on/off". I guess I need to live with virtual F6-02-01 switches, those work at least. |
Beta Was this translation helpful? Give feedback.
-
|
It's normal that you get D1 telegram are MSC (Manufacturer Specific Communication). This means that the decoding of such telegram is manufacturer-dependent and mostly not public. The manufacturer in this case seems to be For pairing, D2 devices normally use D4 telegrams (UTE - Universal TEach in). |
Beta Was this translation helpful? Give feedback.
-
|
Yep, those are Becker drives, and they don't send D4 telegrams. I didn't find anything about pairing in the docs. |
Beta Was this translation helpful? Give feedback.
-
|
Yes aware of that and a very interesting feature. At least you can use virtuals, so that's a good starting point. By the way, regarding virtuals, starting from 0.1.28, I added virtual switches in addition to the existing virtual select. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I tried pairing a virtual switches to one of the drives, and that went nicely. Per intuition I thought that switching AI on and then off would be the equivalent to tapping a wall switch's AI button and close the shutter. I was about to peruse the communication logs to find out why, but then HA decided to auto-update to e2m version 0.1.28-1. My wife wasn't too thrilled about the bedroom wall switch not working anymore :o) This morning it occured to me it might be my custom mappings and EEP. I had jury-rigged D2-05-02 support by copying and renaming the D2-05-00 section and jeez, editing those files is a major PITA. Anyway, I disabled them for the time being, wall switch and sensors are working again. Unfortunately, I won't have time to look into this again for the next 4 hrs... |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon,
Note that the virtual switches represent the exact same device as the select, it is just a different UI to control that virtual device. However, I couldn't quite get the hang of how it was supposed to work. Yes it doesn't work like that.
😅 Sorry for that.
Yes I know, |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, long day. Virtual switches ...: ... and how they work: Failing bedroom switch: EEP and mapping files: Whatever, I'll try and squeeze an hour or 3 off my schedule tomorrow, to track down what went wrong with those v-switches. Stay tuned. |
Beta Was this translation helpful? Give feedback.
-
|
Meh. Another looong day. On the bright side: My contact sent me the complete tech specs of their EnOcean interface, including a command to directly pass low level commands to the drive's Modbus controller. On a lesser bright side: pairing with HA and basically anything useful requires ReCOM. Well, that reduces the issue at hand to merely adding D2-05-02 support to the EEP and mapping files. Re v-switches: I'll be swamped until monday and won't be able to test those virtuals before tuesday. No promises, though ... |
Beta Was this translation helpful? Give feedback.
-
|
Okay, time for a bit of recollection and current status: Initially after installing E2M, I edited the default EEP and mapping files to rig them for D2-05-02 by simply copying the D2-05-00 stuff. I tried to restart, it didn't work until I removed the custom EEP.xml. No idea what went wrong there, and I'm not exactly fond of the EEP monster, so I just removed the custom config and will wait for the official D2-05-02 support. Meanwhile, I redefined my shutters as D2-05-00 (my OCD spidey senses are punishing me for that), restarted E2M and now I can see my shutter drives' current states. Next up I created a bunch of virtual switches to pair with the real drives, in order to gain SOME control over them, and it worked like a charm. So I started testing those virtual switches (see here) and found that the action select mode produces proper telegrams while the switch-and-send approach doesn't. Right now the drives aren't responding to those, at all. Might be a range issue, now, since I had to rebuild my test rig in my man cave. I'm gonna go find a repeater and put this on the backburner until I do. Why can't anything be easy? Sigh... :( |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, Thanks for your feedback. EEP and mapping files: Virtual switches: So a button with tap/release action like a real wall switch (you click it, it sends AI, you release it, it sends "released") would be nice. Not sure the HA UI can do that, though...Quite sure this can be done with some custom cards, but I am not a frontend expert. ReCom: Support for D2-05-02: Issues: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for those files. Unfortunately, I have the same problem like before: using the custom EEP.xml doesn't agree with E2M: That's the complete log, debug mode an all. Removing the custom EEP results in E2M starting and running as expected. The mapping file alone doesn't cause any trouble. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, I just saw your message. Ok I see. EEP_FILE_LOCATION=$(find / -path /config -prune -o -name 'EEP.xml' -print -quit 2>/dev/null)If you are comfortable with Linux, VI file editor and more or less Docker, you can follow this wiki to modify the addon files and test both the fix and the support for D2-05-02. |
Beta Was this translation helpful? Give feedback.
-
|
Ugh. I'd love to, but this is a bit too deep for the old school tech afficionado that I am. I'm comfy-ish with Linux and VI, but not at all with Docker. Hints are welcome. |
Beta Was this translation helpful? Give feedback.
-
|
Hrm. Note to self: try the obvious next time. So plugging in a keyboard and display worked. Kinda. However, I edited run.sh as requested. No success, even after restarting everything. I gather the problem was me putting EEP.xml in a separate directory instead of adding to the clutter /config, right? Either the fix didn't work or I screwed up the edit. I need to calm down from the annoying keyboard disaster before I take another look... |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, So you've been able to get access to the addon docker container, right ? Perfect.
Just to clarify, to restart the addon with your changes, you have to run the command indicated in the wiki: docker restart $(docker ps | grep ha_enoceanmqtt | cut -d" " -f 1)If you restart the addon using the restart button of the addon, your changes are lost. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I did the docker restart thingy and afterwards I was assaulted by a bunch of phone calls. Alright, I'll try again. |
Beta Was this translation helpful? Give feedback.
-
|
Um. I guess that's a bit harder than anticipated. If I put my custom EEP in the configuration, E2M stops right away and I can't access the container. If I don't, I CAN access the container to try and fix run.sh, but it won't be able to see the effect until I put my custom EEP in the configuration again, |
Beta Was this translation helpful? Give feedback.
-
|
If it stops, it means that there is an error. |
Beta Was this translation helpful? Give feedback.
-
|
This is weird. I think there's more wrong with the custom configuration. Back to square one: I set the configuration to
I started E2M, the live log came up like the one posted above (services start, services stop). Then I put the new EEP.xml in /config directory, too. The log: followed by lots of other unsuspicious stuff and then, when I interacted with one of my shutters which indicates that E2M doesn't use either of the custom EEP files. FYI: I defined 3 of my drives as D2-05-00 and the other two as D2-05-02 for this test. Okay, now I have a situation where the container still works with the configuration I want to use. |
Beta Was this translation helpful? Give feedback.
-
|
I did. It didn't work. Same as before, docker restart resulted in a stopped E2M with empty log file. Can I catch you on discord? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, Sorry just saw you message. Regarding Docker, first of all thanks for your tests, but I don't want you to loose your mind ( 😅 ) so you can stop your tests 🙂 . |
Beta Was this translation helpful? Give feedback.
-
|
My mind thanks you 😅 I chimed in on a year old thread about the console keymap issue, perhaps somebody will take pity on us non-americans. So, no discord. Slack, perhaps? I guess we save the custom EEP problem for later, I'll make a spin-off issue report for that. Regarding the issue at hand (missing D2-05-02 coverage), I'll just wait for the next E2M version and hope you add it anyway, without the need for custom EEP files. Once that works, I'll explore the curious action vs. switches thing and perhaps take a peek at the ReMAN/ReCOM business. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for your help so far! Back to testing: I configured all my shutter drives as D2-05-02 using your test EEP and mapping files. The drives show up in HA just fine, no error messages. And here comes issue number 1: One of my drives kept acting up during installation, it refused to self-teach the lower boundary. Back to topic: We know I can't pair my drives with HA without ReCOM (and I won't play with that anytime soon), so the controls on the device page won't work. ... which brings us to issue number 2: When I send an "OPEN" or "CLOSE" command to a drive, it immediately responds with The position attribute in HA, however, never shows 0x7f, 127 or "unknown". It always translates 0x7f to "100", which makes it impossible to say if the shutters are really open (100) or in motion, ... or make a template sensor for the current state of a shutter (see above). Issue number 3 is not directly related to E2M: One of the drives seems to have a poorly adjusted antenna and won´t receive all commands right away. In order to end up with unattended shutter control, I'll try and fix this with a repeater and/or a blueprint that listens for a response from the drive and tries again if there is none. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, First of all, thanks for your feedback 👍 Issue 1: Only problem: the "closed" position is not at 0, but at 3. So even if this one is fully closed, the icon says "open" and the interface would allow to hit the "close" button. I could of course have a bunch of template sensors telling me the shutter states (open, moving, closed, unknown) instead of the device sensors, but perhaps there's a more elegant way to solve this.For now, unfortunately I have no other solution than using a template sensor to handle this case. Issue 2: Yes you're right, the mapping as currently done doesn't correctly handle the position value 127. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, For #2, you can replace: position_template: "{{ value_json.POS }}"
tilt_status_template: "{{ value_json.ANG }}"By: position_template: >-
{% if (value_json.POS <= 100) and (value_json.POS >= 0) %}
{{ value_json.POS }}
{% else %}
{{ state_attr(entity_id,"current_position")|int(default=0) }}
{% endif %}
tilt_status_template: >-
{% if (value_json.ANG <= 100) and (value_json.ANG >= 0) %}
{{ value_json.ANG }}
{% else %}
{{ state_attr(entity_id,"current_tilt_position")|int(default=0) }}
{% endif %}Full mapping - component: "cover"
name: "cover"
config:
command_topic: "req"
payload_open: >-
{"CMD":"1","POS":"0","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
payload_close: >-
{"CMD":"1","POS":"100","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
payload_stop: >-
{"CMD":"2","CHN":"0","send":"clear"}
position_topic: "CMD4"
position_template: >-
{% if (value_json.POS <= 100) and (value_json.POS >= 0) %}
{{ value_json.POS }}
{% else %}
{{ state_attr(entity_id,"current_position")|int(default=0) }}
{% endif %}
set_position_topic: "req"
set_position_template: >-
{"CMD":"1","POS":"{{ position }}","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
tilt_status_topic: "CMD4"
tilt_status_template: >-
{% if (value_json.ANG <= 100) and (value_json.ANG >= 0) %}
{{ value_json.ANG }}
{% else %}
{{ state_attr(entity_id,"current_tilt_position")|int(default=0) }}
{% endif %}
tilt_command_topic: "req"
tilt_command_template: >-
{"CMD":"1","POS":"127","ANG":"{{ tilt_position }}","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
- component: "cover"
name: "cover2"
config:
command_topic: "req"
payload_open: >-
{"CMD":"1","POS":"0","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
payload_close: >-
{"CMD":"1","POS":"100","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
payload_stop: >-
{"CMD":"2","CHN":"0","send":"clear"}
position_topic: "CMD4"
position_open: 0
position_closed: 100
position_template: >-
{% if (value_json.POS <= 100) and (value_json.POS >= 0) %}
{{ value_json.POS }}
{% else %}
{{ state_attr(entity_id,"current_position")|int(default=0) }}
{% endif %}
set_position_topic: "req"
set_position_template: >-
{"CMD":"1","POS":"{{ 100 - position }}","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}
tilt_status_topic: "CMD4"
tilt_status_template: >-
{% if (value_json.ANG <= 100) and (value_json.ANG >= 0) %}
{{ value_json.ANG }}
{% else %}
{{ state_attr(entity_id,"current_tilt_position")|int(default=0) }}
{% endif %}
tilt_command_topic: "req"
tilt_command_template: >-
{"CMD":"1","POS":"127","ANG":"{{ tilt_position }}","REPO":"0","LOCK":"0","CHN":"0","send":"clear"} |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, Did you have time to test the code above for your D2-05-02 ? I am about to make a new release, do you have any remaining bugs ? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
I did, but it didn't seem to make much of a difference, so I reverted to the original version. At this point, there are only a few minor things that are bothering me mildly: A few of my shutters are running on 'cover', the others on 'cover2'. Two of my drives don't always accept commands right away for reasons I'm still investigating. My drives support the "angle" aspect through their EEP, but my shutters don't. But to be honest, all of the above are merely tweaks. That is a solid basis to work with, the tweaks can wait. I am not aware of any real bugs with D2-05-02 so far, so I guess this is safe to use for the first official stable version. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, Thanks for your feedback and I agree that those are minor issues that we can deal with later. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Guys, just saw your discussion and I am really excited that support for D2-05-02 comes soon. I am also have some Becker shutters installed. @mak-gitdev, |
Beta Was this translation helpful? Give feedback.
-
|
@mak-gitdev do you think it might be useful to add important information and peculiarities directly to the Wiki / Supported devices? In this case: D2-05-02 Becker shutter drives are not fully supported yet. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @OlwinFroon, I was also thinking about that since your comments on D2-03-0A. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Greetings!
This would be for my 5 Becker blinds controls.
I've checked the official EEP documentation and it looks like D02-05-02 is just a subset of D02-05-00. There are just a few minor differences:
CMD 1: Go to position and angle
00: values 0 (channel 1) .. 3 (channel 4), 15 (all channels)
02: values 0 (channel 1), rest is "reserved"
CMD 2: Stop
00: values 0 (channel 1) .. 3 (channel 4), 15 (all channels)
02: values 0 (channel 1), rest is "reserved"
CMD 3: Query Position and Angle
00: values 0 (channel 1) .. 3 (channel 4), 15 (all channels)
02: values 0 (channel 1), rest is "reserved"
CMD 4: Reply Position and Angle
00: 0 (no lock), 1 (blockage), 2 (alarm)
00: 0 (no lock), 1 (blockage), rest is "reserved"
00: values 0 (channel 1) .. 3 (channel 4), 15 (all channels)
02: values 0 (channel 1), rest is "reserved"
CMD 5: Set parameters
Doesn't exist in 02.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions