Configuring of docker version #65

LarsKoeppel · 2023-04-21T18:57:49Z

LarsKoeppel
Apr 21, 2023

I'm trying to use enoceanmqtt's docker image.
Since some things don't work as expected, I tried to use logging and custom mappings. Is there a way to set the paths to these files in the config?

I have already tried the following:

mapping_file = /config/mapping.yaml
log_file        = /config/enoceanmqtt.log

The problem I'm trying to figure out is a misrepresented cover.
Although it reports position 0, it is represented as closed in HA. Is this a problem of enoceanmqtt or of HA?

mak-gitdev · 2023-04-22T09:47:29Z

mak-gitdev
Apr 22, 2023
Maintainer

Hi @LarsKoeppel,

Regarding the docker configuration, I strongly recommend to have a look at the wiki.
You just have to add your enoceanmqtt.conf file in your /config volume.
Then in this file, supposing you have also a mapping.yaml file in the /config volume, add:

mapping_file = /config/mapping.yaml

For the log file, as explained in the wiki, run docker with this additional option:

--logfile /config/enoceanmqtt.log

Now regarding the problem, I think this is not an issue neither on my side nor on HA side.

This is well known and it happens from cover to cover. Some may report the correct position while others may report inverted position.
I still don't have the final answer to this but my feeling is that some covers may have inverted cables, or may be a bad physical configuration of the EnOcean device.
Changing the mapping.yaml to invert the reported position may correct the inverted covers but will certainly break the correct covers. I don't recommend to go this way.
In my opinion, the best solution to date is to create a template cover on top of the ha_enoceanmqtt cover to invert the position.

I have some ideas to better deal with such cases at ha_enoceanmqtt level though.

0 replies

mak-gitdev · 2023-04-23T17:32:56Z

mak-gitdev
Apr 23, 2023
Maintainer

Hi @LarsKoeppel,

Anything new ?

0 replies

LarsKoeppel · 2023-04-23T18:23:00Z

LarsKoeppel
Apr 23, 2023
Author

Hi @mak-gitdev,

unfortunately I didn't had time to work on it this weekend. I'll get back to it in a few days.

To set the direction of a shutter, I could imagine a parameter in the config. Something like "reversed".

0 replies

LarsKoeppel · 2023-04-29T18:13:01Z

LarsKoeppel
Apr 29, 2023
Author

Hi @mak-gitdev,

I managed to start the docker container with the appropriate options and write the log. Since I wanted to do this from the TrueNas Scale interface, it was a bit more cumbersome to achieve.

For everyone who is interested:
Each part of the option must be entered individually for the "Container Args". (See image)

But I still have problems with the template. I'm brand new to HA and don't really know much about it. So far I have copied this from the documentation. Could you possibly help me a bit?
Especially when it comes to the control, I don't know what to do, because I have to use a virtual switch in enocean.

cover:
  - platform: template
    covers:
      rolladen:
        device_class: shutter
        friendly_name: "Rolladen"
        #value_template: "{{ is_state('sensor.rolladen', 'closed') }}"
        position_template: "{{ 100 - states('sensor.rolladen') }}"
        open_cover:
          service: script.open_rolladen
        close_cover:
          service: script.close_rolladen
        stop_cover:
          service: script.stop_rolladen

I would be very happy about any help.

0 replies

mak-gitdev · 2023-04-30T20:00:51Z

mak-gitdev
Apr 30, 2023
Maintainer

Hi @LarsKoeppel,

As in the end, this is not an issue, I will convert it to a discussion.
Let's continue there then

0 replies

mak-gitdev · 2023-04-30T20:12:43Z

mak-gitdev
Apr 30, 2023
Maintainer

First, I think instead of sensor.rolladen you should use the name of your ha_enoceanmqtt sensor.
It should be something in the form e2m_<your_selected_sensor_name>_xxx.

Then regarding actions, may be you could explain in further details what is your current behavior so that we can better understand what needs to be changed.

0 replies

LarsKoeppel · 2023-05-02T16:41:16Z

LarsKoeppel
May 2, 2023
Author

Hi @mak-gitdev,

I implemented your suggested changes, but I couldn't display any data in HA. That's why I've added the following two parameters to the mapping file for now:

position_open: 0
position_closed: 100

That inverts everything in HA. It is currently not a problem for me that all shutters are now inverted, as I currently only have one with enocean.

0 replies

LarsKoeppel · 2023-05-02T16:45:03Z

LarsKoeppel
May 2, 2023
Author

While trying to implement the control, I probably found a bug with the virtual switches. For a F6-02-02 (VIRTUAL) switch, the EEP defines the data for the status field. To transmit a pressed butten, the T21 and NU value should be 1. But in the log of HA_enoceanmqtt bouth are 0.

2023-05-02 16:22:39,527 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/RolladenSteuerung/Wohnzimmer/req', ...  (44 bytes)
2023-05-02 16:22:39,527 DEBUG: Got MQTT message: enoceanmqtt/RolladenSteuerung/Wohnzimmer/req
2023-05-02 16:22:39,527 DEBUG: enoceanmqtt/RolladenSteuerung/Wohnzimmer: req={'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0}
2023-05-02 16:22:39,527 DEBUG: Trigger message to: enoceanmqtt/RolladenSteuerung/Wohnzimmer
2023-05-02 16:22:39,528 DEBUG: sensor data: {'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0}
2023-05-02 16:22:39,528 INFO: sending: FF:AB:F3:01->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xab', '0xf3', '0x1', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': False, 'raw_value': 0}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2023-05-02 16:22:39,528 DEBUG: Clearing data buffer.
2023-05-02 16:22:39,532 INFO: Sending packet
2023-05-02 16:22:39,532 DEBUG: FF:AB:F3:01->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xab', '0xf3', '0x1', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': False, 'raw_value': 0}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2023-05-02 16:22:39,633 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2023-05-02 16:22:39,633 INFO: got response packet: OK
2023-05-02 16:22:41,215 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/RolladenSteuerung/Wohnzimmer/req', ...  (44 bytes)
2023-05-02 16:22:41,215 DEBUG: Got MQTT message: enoceanmqtt/RolladenSteuerung/Wohnzimmer/req
2023-05-02 16:22:41,215 DEBUG: enoceanmqtt/RolladenSteuerung/Wohnzimmer: req={'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0}
2023-05-02 16:22:41,216 DEBUG: Trigger message to: enoceanmqtt/RolladenSteuerung/Wohnzimmer
2023-05-02 16:22:41,217 DEBUG: sensor data: {'R1': 0, 'EB': 0, 'R2': 0, 'SA': 0}
2023-05-02 16:22:41,218 INFO: sending: FF:AB:F3:01->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0xff', '0xab', '0xf3', '0x1', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': False, 'raw_value': 0}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2023-05-02 16:22:41,218 DEBUG: Clearing data buffer.
2023-05-02 16:22:41,239 INFO: Sending packet
2023-05-02 16:22:41,240 DEBUG: FF:AB:F3:01->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x0', '0xff', '0xab', '0xf3', '0x1', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'released', 'raw_value': 0}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': False, 'raw_value': 0}), ('NU', {'description': 'NU', 'unit': '', 'value': False, 'raw_value': 0})])
2023-05-02 16:22:41,341 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2023-05-02 16:22:41,341 INFO: got response packet: OK

Here is the log of my current pysical switch. I think bouth should habe the same data and status.

2023-05-02 16:23:23,532 DEBUG: FE:EA:66:00->FF:FF:FF:FF (-79 dBm): 0x01 ['0xf6', '0x70', '0xfe', '0xea', '0x66', '0x0', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4f', '0x0'] OrderedDict()
2023-05-02 16:23:23,532 INFO: received: FE:EA:66:00->FF:FF:FF:FF (-79 dBm): 0x01 ['0xf6', '0x70', '0xfe', '0xea', '0x66', '0x0', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4f', '0x0'] OrderedDict()
2023-05-02 16:23:23,534 DEBUG: enoceanmqtt/Schalter1: R1 (Rocker 1st action)=Button BO
2023-05-02 16:23:23,534 DEBUG: enoceanmqtt/Schalter1: EB (Energy bow)=pressed
2023-05-02 16:23:23,534 DEBUG: enoceanmqtt/Schalter1: R2 (Rocker 2nd action)=Button AI
2023-05-02 16:23:23,535 DEBUG: enoceanmqtt/Schalter1: SA (2nd action)=No 2nd action
2023-05-02 16:23:23,535 DEBUG: enoceanmqtt/Schalter1: T21 (T21)=True
2023-05-02 16:23:23,535 DEBUG: enoceanmqtt/Schalter1: NU (NU)=True
2023-05-02 16:23:23,535 DEBUG: enoceanmqtt/Schalter1: Sent MQTT: {"_RSSI_": -79, "_DATE_": "2023-05-02T16:23:23.532303", "R1": 3, "EB": 1, "R2": 0, "SA": 0, "T21": true, "NU": true}
2023-05-02 16:23:23,536 DEBUG: Sending PUBLISH (d0, q0, r1, m40), 'b'enoceanmqtt/Schalter1'', ... (116 bytes)
2023-05-02 16:23:23,741 DEBUG: FE:EA:66:00->FF:FF:FF:FF (-77 dBm): 0x01 ['0xf6', '0x0', '0xfe', '0xea', '0x66', '0x0', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4d', '0x0'] OrderedDict()
2023-05-02 16:23:23,741 INFO: received: FE:EA:66:00->FF:FF:FF:FF (-77 dBm): 0x01 ['0xf6', '0x0', '0xfe', '0xea', '0x66', '0x0', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x4d', '0x0'] OrderedDict()
2023-05-02 16:23:23,743 DEBUG: enoceanmqtt/Schalter1: R1 (Rocker 1st action)=Button AI
2023-05-02 16:23:23,743 DEBUG: enoceanmqtt/Schalter1: EB (Energy bow)=released
2023-05-02 16:23:23,743 DEBUG: enoceanmqtt/Schalter1: R2 (Rocker 2nd action)=Button AI
2023-05-02 16:23:23,743 DEBUG: enoceanmqtt/Schalter1: SA (2nd action)=No 2nd action
2023-05-02 16:23:23,743 DEBUG: enoceanmqtt/Schalter1: T21 (T21)=True
2023-05-02 16:23:23,744 DEBUG: enoceanmqtt/Schalter1: NU (NU)=False
2023-05-02 16:23:23,744 DEBUG: enoceanmqtt/Schalter1: Sent MQTT: {"_RSSI_": -77, "_DATE_": "2023-05-02T16:23:23.741283", "R1": 0, "EB": 0, "R2": 0, "SA": 0, "T21": true, "NU": false}
2023-05-02 16:23:23,744 DEBUG: Sending PUBLISH (d0, q0, r1, m43), 'b'enoceanmqtt/Schalter1'', ... (117 bytes)

0 replies

mak-gitdev · 2023-05-03T05:21:12Z

mak-gitdev
May 3, 2023
Maintainer

Hi @LarsKoeppel,

Yes I know that T21 and NU are not correctly set.
In fact, the possibility to set the status bits is not yet available at enoceanmqtt level.
As it seems to work even in these conditions, I wasn't in the rush to implement that missing feature.

0 replies

LarsKoeppel · 2023-05-03T16:27:02Z

LarsKoeppel
May 3, 2023
Author

Hi @mak-gitdev,

could you point me to the point, where this should be implementet?
I would like to try to implement it.

0 replies

LarsKoeppel · 2023-05-07T15:06:55Z

LarsKoeppel
May 7, 2023
Author

Hi @mak-gitdev,

for my model of shutter it looks like, that the status bits are relevant. Without them, it does not respond. I tested it with the DolphinView App from EnOcean. So i tried to implement it in HA_enoceanmqtt. For this i did the following steps:

I changed in the mapping.yaml beginning in line 2941 to the following code to add the status bits.

        virtual:
            - component: select
              name: "action"
              config:
                 options:
                    - "None"
                    - "AO"
                    - "AI"
                    - "BO"
                    - "BI"
                    - "AO + BO"
                    - "AO + BI"
                    - "AI + BO"
                    - "AI + BI"
                    - "BO + AO"
                    - "BO + AI"
                    - "BI + AO"
                    - "BI + AI"
                 command_topic: "req"
                 command_template: >-
                   {% set R1, EB, R2, SA, T21, NU = 0, 0, 0, 0, 1, 0 %}
                   {% set id = {"AI":"0","AO":"1","BI":"2","BO":"3"} %}
                   {% set action = value.split(" + ") %}
                   {% if value is not search('None') %}{% set EB, NU, R1 = 1, 1, id[action[0]] %}{% endif %}
                   {% if action|length==2 %}{% set SA, R2 = 1, id[action[1]] %}{% endif %}
                   {"R1":{{R1}},"EB":{{EB}},"R2":{{R2}},"SA":{{SA}},"T21":{{T21}},"NU":{{NU}},"send":"clear"}

And the log shows, that the information was processed correctly. But in the generation of the byte arrays it was ignored.

2023-05-06 23:16:26,688 DEBUG: Received PUBLISH (d0, q0, r0, m0), 'enoceanmqtt/RolladenSteuerung/Wohnzimmer/req', ...  (59 bytes)
2023-05-06 23:16:26,689 DEBUG: Got MQTT message: enoceanmqtt/RolladenSteuerung/Wohnzimmer/req
2023-05-06 23:16:26,689 DEBUG: enoceanmqtt/RolladenSteuerung/Wohnzimmer: req={'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2023-05-06 23:16:26,689 DEBUG: Trigger message to: enoceanmqtt/RolladenSteuerung/Wohnzimmer
2023-05-06 23:16:26,690 DEBUG: sensor data: {'R1': 3, 'EB': 1, 'R2': 0, 'SA': 0, 'T21': 1, 'NU': 1}
2023-05-06 23:16:26,690 INFO: sending: FF:AB:F3:01->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xab', '0xf3', '0x1', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2023-05-06 23:16:26,690 DEBUG: Clearing data buffer.
2023-05-06 23:16:26,754 INFO: Sending packet
2023-05-06 23:16:26,754 DEBUG: FF:AB:F3:01->FF:FF:FF:FF (-255 dBm): 0x01 ['0xf6', '0x70', '0xff', '0xab', '0xf3', '0x1', '0x0'] ['0x3', '0xff', '0xff', '0xff', '0xff', '0xff', '0x0'] OrderedDict([('R1', {'description': 'Rocker 1st action', 'unit': '', 'value': 'Button BO', 'raw_value': 3}), ('EB', {'description': 'Energy bow', 'unit': '', 'value': 'pressed', 'raw_value': 1}), ('R2', {'description': 'Rocker 2nd action', 'unit': '', 'value': 'Button AI', 'raw_value': 0}), ('SA', {'description': '2nd action', 'unit': '', 'value': 'No 2nd action', 'raw_value': 0}), ('T21', {'description': 'T21', 'unit': '', 'value': True, 'raw_value': 1}), ('NU', {'description': 'NU', 'unit': '', 'value': True, 'raw_value': 1})])
2023-05-06 23:16:26,855 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2023-05-06 23:16:26,856 INFO: got response packet: OK

I diged down to the enoceanmqtt/communicator.py in line 461 where the byte array is created. And for a quick look i counld not figure out, why it would not set the status bits. Because all the other functions are already setting it correctly up.

Can you help me at this point?

5 replies

mak-gitdev May 8, 2023
Maintainer

Hi @LarsKoeppel,

If I remind correctly, status bits are handled separately from data bits at the Python EnOcean library level.
The fact is that the status bits are not yet handled by enoceanmqtt.
So if you want to add this feature, you have to do it directly at the enoceanmqtt repository.

You will have to understand how the status bits are handled in the Python EnOcean library then find a smooth way to add the support for setting these bits in enoceanmqtt.

I suggest you to open a new thread with this specific topic as title so that we can exchange there and make this interesting discussion more explicit.
And/Or open an issue directly in the enoceanmqtt repository so that we can discuss with the repository owner to find a way to implement it.

LarsKoeppel May 27, 2023
Author

Hi @mak-gitdev,

how long will it take to apply the upstream changes and provide new docker images?

mak-gitdev Jun 5, 2023
Maintainer

Hi @LarsKoeppel,

Sorry for the delay.
It will be done tonight.

I will also release the Dockerfile so that next time you can build your docker image without waiting for the "official" one.

LarsKoeppel Jun 5, 2023
Author

Hi @mak-gitdev,

many thanks for everything. I will test it in the next days.

LarsKoeppel Jun 8, 2023
Author

Hi @mak-gitdev,

Thanks again. Now the control of my shutter works perfectly.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Configuring of docker version #65

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 11 comments 5 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Configuring of docker version #65

LarsKoeppel Apr 21, 2023

Replies: 11 comments · 5 replies

mak-gitdev Apr 22, 2023 Maintainer

mak-gitdev Apr 23, 2023 Maintainer

LarsKoeppel Apr 23, 2023 Author

LarsKoeppel Apr 29, 2023 Author

mak-gitdev Apr 30, 2023 Maintainer

mak-gitdev Apr 30, 2023 Maintainer

LarsKoeppel May 2, 2023 Author

LarsKoeppel May 2, 2023 Author

mak-gitdev May 3, 2023 Maintainer

LarsKoeppel May 3, 2023 Author

LarsKoeppel May 7, 2023 Author

mak-gitdev May 8, 2023 Maintainer

LarsKoeppel May 27, 2023 Author

mak-gitdev Jun 5, 2023 Maintainer

LarsKoeppel Jun 5, 2023 Author

LarsKoeppel Jun 8, 2023 Author

LarsKoeppel
Apr 21, 2023

Replies: 11 comments 5 replies

mak-gitdev
Apr 22, 2023
Maintainer

mak-gitdev
Apr 23, 2023
Maintainer

LarsKoeppel
Apr 23, 2023
Author

LarsKoeppel
Apr 29, 2023
Author

mak-gitdev
Apr 30, 2023
Maintainer

mak-gitdev
Apr 30, 2023
Maintainer

LarsKoeppel
May 2, 2023
Author

LarsKoeppel
May 2, 2023
Author

mak-gitdev
May 3, 2023
Maintainer

LarsKoeppel
May 3, 2023
Author

LarsKoeppel
May 7, 2023
Author

mak-gitdev May 8, 2023
Maintainer

LarsKoeppel May 27, 2023
Author

mak-gitdev Jun 5, 2023
Maintainer

LarsKoeppel Jun 5, 2023
Author

LarsKoeppel Jun 8, 2023
Author