Closed t-ice closed 1 year ago
As I do not have such device myself I am not that familiar with profiles supporting various commands.
However, as I understand pull request #27 from @mak-gitdev, this got implemented there. Thus, you could specify command=ID
(ID
from your log or CMD
as in EEP.xml
?) in the config file to enable this.
See communicator.py:220ff
as the correspondig part in the source code.
Hi @romor,
Yes it has been implemented.
@t-ice can enable it using command = ID
as A5-13-xx EEPs define ID
as the command identifier.
Unfortunately it didn't work for me, see log. I tried also just one definition for the address and different formats of the command value, e.g. 0x02.
...
DEBUG: Created sensor: {'name': 'enocean2mqtt/Wetterstation_1', 'address': 94295962, 'rorg': 165, 'func': 19, 'type': 1, 'command': '1'}
DEBUG: Created sensor: {'name': 'enocean2mqtt/Wetterstation_2', 'address': 94295962, 'rorg': 165, 'func': 19, 'type': 1, 'command': '2'}
...
DEBUG: Sending SUBSCRIBE (d0, m26) [(b'enocean2mqtt/Wetterstation_1/req/#', 0)]
DEBUG: Sending SUBSCRIBE (d0, m27) [(b'enocean2mqtt/Wetterstation_2/req/#', 0)]
...
DEBUG: 05:9E:D7:9A->FF:FF:FF:FF (-70 dBm): 0x01 ['0xa5', '0x0', '0x5f', '0xa', '0x18', '0x5', '0x9e', '0xd7', '0x9a', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()
INFO: received: 05:9E:D7:9A->FF:FF:FF:FF (-70 dBm): 0x01 ['0xa5', '0x0', '0x5f', '0xa', '0x18', '0x5', '0x9e', '0xd7', '0x9a', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()
DEBUG: enocean2mqtt/Wetterstation_1: DWS (Dawn sensor)=0.0 lx
DEBUG: enocean2mqtt/Wetterstation_1: TMP (Temperature)=4.705882352941174 °C
DEBUG: enocean2mqtt/Wetterstation_1: WND (Wind speed)=2.7450980392156863 m/s
DEBUG: enocean2mqtt/Wetterstation_1: ID (Identifier)=Identifier 1
DEBUG: enocean2mqtt/Wetterstation_1: DN (Day / Night)=Day
DEBUG: enocean2mqtt/Wetterstation_1: RAN (Rain Indication)=No Rain
DEBUG: enocean2mqtt/Wetterstation_1: Sent MQTT: {"RSSI": -70, "DWS": 0.0, "TMP": 4.705882352941174, "WND": 2.7450980392156863, "ID": 1, "DN": 0, "RAN": 0}
DEBUG: Sending PUBLISH (d0, q0, r1, m314), 'b'enocean2mqtt/Wetterstation_1'', ... (106 bytes)
DEBUG: 05:9E:D7:9A->FF:FF:FF:FF (-70 dBm): 0x01 ['0xa5', '0x0', '0x0', '0x0', '0x28', '0x5', '0x9e', '0xd7', '0x9a', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()
INFO: received: 05:9E:D7:9A->FF:FF:FF:FF (-70 dBm): 0x01 ['0xa5', '0x0', '0x0', '0x0', '0x28', '0x5', '0x9e', '0xd7', '0x9a', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()
DEBUG: enocean2mqtt/Wetterstation_1: DWS (Dawn sensor)=0.0 lx
DEBUG: enocean2mqtt/Wetterstation_1: TMP (Temperature)=-40.0 °C
DEBUG: enocean2mqtt/Wetterstation_1: WND (Wind speed)=0.0 m/s
DEBUG: enocean2mqtt/Wetterstation_1: ID (Identifier)=Identifier 2
DEBUG: enocean2mqtt/Wetterstation_1: DN (Day / Night)=Day
DEBUG: enocean2mqtt/Wetterstation_1: RAN (Rain Indication)=No Rain
DEBUG: enocean2mqtt/Wetterstation_1: Sent MQTT: {"RSSI": -70, "DWS": 0.0, "TMP": -40.0, "WND": 0.0, "ID": 2, "DN": 0, "RAN": 0}
DEBUG: Sending PUBLISH (d0, q0, r1, m315), 'b'enocean2mqtt/Wetterstation_1'', ... (79 bytes)
DEBUG: 05:9E:D7:9A->FF:FF:FF:FF (-70 dBm): 0x01 ['0xa5', '0x0', '0x5f', '0xa', '0x18', '0x5', '0x9e', '0xd7', '0x9a', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x46', '0x0'] OrderedDict()
...
BTW @mak-gitdev I'm using the dev version of your HA addon.
Seems that you defined your device as:
[Wetterstation_1]
address = 0x59ED79A
rorg = 0xA5
func = 0x13
type = 0x01
command = 1
As explained by @romor and I, it should be:
[Wetterstation_1]
address = 0x59ED79A
rorg = 0xA5
func = 0x13
type = 0x01
command = ID
As the issue is related to the Home Assistant extension of enoceanmqtt, please open an issue there if that doesn't fix your issue.
Sorry, I misunderstood that. Unfortunately, that didn't help either. I will close this issue and create a new issue as suggested. Thanks a lot
Hello,
I'm using a FWS61 in combination with a multisensor MS. The EEP profiles a5-13-01 and a5-13-02 are supported on the same address. The identifier can be used to distinguish. I found these entries in the EEP.xml https://github.com/kipe/enocean/commit/33151e925f111adde19cea1e2c6b34234c621d5b. Currently, A5-13-02 telegrams are interpreted as A5-13-01 telegrams (see log). Is it possible to get the data published as SNW, SNS, SNE... for identifier 2?
Thanks for your work Christian