Unable to set cover #93

didi31 · 2023-11-13T10:36:37Z

didi31
Nov 13, 2023

I would like to move from Domoticz to Home assistant.
I have 3 covers module EVOLOGY (Leroy merlin) which are provided by Nodon and Nodon told me that they are exactly the same than the Nodon ones.
I got the identity of each module from the enocean hardware of Domoticz.
Contact switch are working perfectly.
I did the following for the cover.

Set the conf:
[Volet/chambre]
address = 0x05A21EE5
rorg = 0xD2
func = 0x05
type = 0x00
Switch the learn button to On
Follow the procedure for pairing.

The module does not react as written In the EVOLOGY procedure but I can move the cover up with HA.
However as soon as the cover is open, the arrow to move the cover down is greyed and I cannot close it.
Is there something wrong in what I did?

Answered by didi31

Nov 14, 2023

I removed:

position_open
position_closed
tilt_status_topic
tilt_status_template
tilt_command_topic
tilt_command_template

changed:

position_template to "{{ 100 - value_json.POS }}"
set_position_template to {"CMD":"1","POS":"{{ 100 - position }}","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}

and it work fine.

            - 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","…

View full answer

mak-gitdev · 2023-11-13T11:19:03Z

mak-gitdev
Nov 13, 2023
Maintainer

Hi @didi31,

What happens if you press the cover up button ?
UP and DOWN commands may be inverted.

0 replies

didi31 · 2023-11-13T13:11:04Z

didi31
Nov 13, 2023
Author

For a position in-between (where both arrows are active) it works as expected. Left arrow move the cover UP and right arrow move the cover down. But when the cover is fully open or closed, the greyed arrow is not the correct one. When cover is closed I cannot open it and when it is open, I cannot close it. 13 nov. 2023 12:19:15 mak-gitdev ***@***.***>:

…

Hi @didi31[https://github.com/didi31], What happens if you press the cover up button ? UP and DOWN commands may be inverted. — Reply to this email directly, view it on GitHub[#93 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ALFRFYL3VW7N424QOX4ZIULYEH63FAVCNFSM6AAAAAA7I5XH3CVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKNJSHA3DG]. You are receiving this because you were mentioned. [Image de pistage][https://github.com/notifications/beacon/ALFRFYMEFSHP6YQ6H2SSGHDYEH63FA5CNFSM6AAAAAA7I5XH3CWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAOM7V6.gif]

0 replies

didi31 · 2023-11-13T14:34:36Z

didi31
Nov 13, 2023
Author

Something strange on the cover properties. [cid:eu.faircode.email.544] ![Screenshot_2023-11-13-15-29-51-177_com android chrome](https://github.com/mak-gitdev/HA_enoceanmqtt/assets/46863073/879ac76c-ce03-4757-bab5-9c142891b295) Cover is open in the Real life lol When I installed the add-on, I had 2 choices, Deprecated and dev I selected the dev version.

0 replies

mak-gitdev · 2023-11-14T08:51:40Z

mak-gitdev
Nov 14, 2023
Maintainer

Hi @didi31,

Ok I see.
Please use a custom mapping file and replace the current D2-05-00 mapping by this one:

   0x05:
      0x00:
         device_config:
            command: "CMD"
            channel: "CMD"
            log_learn: ""
            direction: ""
            answer: ""
         entities:
            - 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: "{{ value_json.POS }}"
                 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: "{{ value_json.ANG }}"
                 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: "{{ value_json.POS }}"
                 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: "{{ value_json.ANG }}"
                 tilt_command_topic: "req"
                 tilt_command_template: >-
                    {"CMD":"1","POS":"127","ANG":"{{ tilt_position }}","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}

Then use the cover2 entity and report the behavior please.

2 replies

didi31 Nov 14, 2023
Author

Hi
I found the way to create the mapping file but how to use the cover2 settings?

mak-gitdev Nov 14, 2023
Maintainer

@didi31,

Simply restart the addon.
You will then have a second cover entity named e2m_xxx.cover2

didi31 · 2023-11-14T12:25:00Z

didi31
Nov 14, 2023
Author

I have nothing more. 😔 I attached the log and the mapping file 14 nov. 2023 11:44:11 mak-gitdev ***@***.***>:

…

@didi31[https://github.com/didi31], Simply restart the addon. You will then have a second cover entity named e2m_xxx.cover2 — Reply to this email directly, view it on GitHub[#93 (reply in thread)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ALFRFYKIV2TUAEMESKGGFPLYENDPXAVCNFSM6AAAAAA7I5XH3CVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKNRUGEYTE]. You are receiving this because you were mentioned. [Image de pistage][https://github.com/notifications/beacon/ALFRFYIGS6AI45EIXOZUFNTYENDPXA5CNFSM6AAAAAA7I5XH3CWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAONVVA.gif]

6 replies

mak-gitdev Nov 14, 2023
Maintainer

@didi31,

I attached the log and the mapping file
There are no file attached. Could you resend them please ?

didi31 Nov 14, 2023
Author

log.docx
mapping.txt

didi31 Nov 14, 2023
Author

I see them inside MQTT explorer but not in the MQTT integration
However, it seems that the position is not correct. When the cover is fully opened, it should be 100 whilst it return 0.
If I set the position to 90% it close the cover to 10%.

mak-gitdev Nov 14, 2023
Maintainer

@didi31,

If you look at the mapping for cover2 entity, you will see that I indicate open as 0 and close as 100 as this is what is reported by the EEP.
That's why I would like you to test that cover2 entity.
Could you please regenerate the log with debug activated ?
Also could you please share a screenshot of the device page in the MQTT integration ?

Thanks.

didi31 Nov 14, 2023
Author

Inside HA the rule seems to be inverted.
If I look at the cover template:

position_template [template](https://www.home-assistant.io/docs/configuration/templating/) (Optional)

Defines a template to get the position of the cover. Legal values are numbers between 0 (closed) and 100 (open). If the template produces a None value the current position will be set to unknown.

enoceanmqtt.log

mak-gitdev · 2023-11-14T14:27:26Z

mak-gitdev
Nov 14, 2023
Maintainer

@didi31,

I made a mistake in the mapping for cover2. Please change the lines:

                 position_open: "0"
                 position_closed: "100"

by:

                 position_open: 0
                 position_closed: 100

The cover2 entity should appear now.

Inside HA the rule seems to be inverted.
If I look at the cover template:

Yes, I know and that's why for cover2 entity, I added that position_open is 0 and position_closed is 100 so that HA knows that when the EEP sends 0 for position, it means open and 100 means closed.
You can have a look at cover.mqtt for more details.
I know we can do what you did in your template but I just want to check that this can work as well 😉.

4 replies

didi31 Nov 14, 2023
Author

I removed:

position_open
position_closed
tilt_status_topic
tilt_status_template
tilt_command_topic
tilt_command_template

changed:

position_template to "{{ 100 - value_json.POS }}"
set_position_template to {"CMD":"1","POS":"{{ 100 - position }}","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}

and it work fine.

            - 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_template: "{{ 100 - value_json.POS }}"
                 set_position_topic: "req"
                 set_position_template: >-
                    {"CMD":"1","POS":"{{ 100 - position }}","ANG":"127","REPO":"0","LOCK":"0","CHN":"0","send":"clear"}

Thanks a lot for your support and the big work you did on this module.

Answer selected by didi31

mak-gitdev Nov 14, 2023
Maintainer

@didi31,

Did you see my previous reply ?

@didi31,

I made a mistake in the mapping for cover2. Please change the lines:
                 position_open: "0"
                 position_closed: "100"
by:
                 position_open: 0
                 position_closed: 100
The cover2 entity should appear now.

Inside HA the rule seems to be inverted.
If I look at the cover template:

Yes, I know and that's why for cover2 entity, I added that position_open is 0 and position_closed is 100 so that HA knows that when the EEP sends 0 for position, it means open and 100 means closed. You can have a look at cover.mqtt for more details. I know we can do what you did in your template but I just want to check that this can work as well 😉.

didi31 Nov 14, 2023
Author

yes but it doesn't solved all issues.
I was able to close the cover when it was open or open when it was closed.
However, when I set the position to 90% it closed the cover at 10%.
Both issues are solved with the modifications above.
The til function is useless for such a module.

mak-gitdev Nov 14, 2023
Maintainer

@didi31,

However, when I set the position to 90% it closed the cover at 10%.

It means that set_position doesn't use position_open and position_closed.
That's exactly what I wanted to know. Thanks for the test.

Regarding tilt, it may be useless for your EVOLOGY module but not for other modules also using EEP D2-05-00 as tilt is used in that EEP.
Hence it should not be removed.

Thanks again for testing.

didi31 · 2023-11-14T16:20:58Z

didi31
Nov 14, 2023
Author

👍 Thanks again Have a good evening. Didier 14 nov. 2023 17:16:08 mak-gitdev ***@***.***>:

…

@didi31[https://github.com/didi31], However, when I set the position to 90% it closed the cover at 10%. It means that *set_position* doesn't use *position_open* and *position_closed*. That's exactly what I wanted to know. Thanks for the test. Regarding tilt, it may be useless for your EVOLOGY module but not for other modules also using EEP D2-05-00 as tilt is used in that EEP. Hence it should not be removed. Thanks again for testing. — Reply to this email directly, view it on GitHub[#93 (reply in thread)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ALFRFYJJBKLMIL7A2YLOIPDYEOKMRAVCNFSM6AAAAAA7I5XH3CVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TKNRXGMZTA]. You are receiving this because you were mentioned. [Image de pistage][https://github.com/notifications/beacon/ALFRFYKO4GVMF7UUDE5QH7DYEOKMRA5CNFSM6AAAAAA7I5XH3CWGG33NNVSW45C7OR4XAZNRIRUXGY3VONZWS33OINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAON36E.gif]

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to set cover #93

{{title}}

Replies: 7 comments 12 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

Unable to set cover #93

didi31 Nov 13, 2023

Replies: 7 comments · 12 replies

mak-gitdev Nov 13, 2023 Maintainer

didi31 Nov 13, 2023 Author

didi31 Nov 13, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

didi31 Nov 14, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

mak-gitdev Nov 14, 2023 Maintainer

didi31 Nov 14, 2023 Author

didi31
Nov 13, 2023

Replies: 7 comments 12 replies

mak-gitdev
Nov 13, 2023
Maintainer

didi31
Nov 13, 2023
Author

didi31
Nov 13, 2023
Author

mak-gitdev
Nov 14, 2023
Maintainer

didi31 Nov 14, 2023
Author

mak-gitdev Nov 14, 2023
Maintainer

didi31
Nov 14, 2023
Author

mak-gitdev Nov 14, 2023
Maintainer

didi31 Nov 14, 2023
Author

didi31 Nov 14, 2023
Author

mak-gitdev Nov 14, 2023
Maintainer

didi31 Nov 14, 2023
Author

mak-gitdev
Nov 14, 2023
Maintainer

didi31 Nov 14, 2023
Author

mak-gitdev Nov 14, 2023
Maintainer

didi31 Nov 14, 2023
Author

mak-gitdev Nov 14, 2023
Maintainer

didi31
Nov 14, 2023
Author