Integration of NodOn Motion PIR Sensor

[apfeuti]

Hi
First, thanks for your great work.

I would be happy, if I could integrate my NodOn Motion PIR Sensor into HomeAssistant.
Since I have such devices, I can help by testing.

NodeOn PIR 2-1-00 Motion Sensor: https://nodon.fr/en/nodon/enocean-motion-sensor/
Manual: https://nodon.fr/wp-content/uploads/2017/11/NodOn-PIR-2-1-xx-UserGuide-170911-EN-interactive.pdf

From the enoceanmqtt-log:

Pairing:
2023-03-25 09:51:27,214 INFO: received: 05:8E:8E:CE->FF:FF:FF:FF (-45 dBm): 0x01 ['0xa5', '0x1c', '0x18', '0x46', '0x80', '0x5', '0x8e', '0x8e', '0xce', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2d', '0x0'] OrderedDict()
2023-03-25 09:51:27,214 INFO: unknown sensor: 05:8E:8E:CE

Detect Motion start:
2023-03-25 09:54:47,129 INFO: received: 05:8E:8E:CE->FF:FF:FF:FF (-46 dBm): 0x01 ['0xa5', '0x96', '0xa', '0x40', '0x88', '0x5', '0x8e', '0x8e', '0xce', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2e', '0x0'] OrderedDict()
2023-03-25 09:54:47,130 INFO: unknown sensor: 05:8E:8E:CE

Motion stop:
2023-03-25 09:56:27,656 INFO: received: 05:8E:8E:CE->FF:FF:FF:FF (-45 dBm): 0x01 ['0xa5', '0x96', '0xb', '0xc0', '0x8', '0x5', '0x8e', '0x8e', '0xce', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2d', '0x0'] OrderedDict()
2023-03-25 09:56:27,657 INFO: unknown sensor: 05:8E:8E:CE

(From integration into openHAB I know, that this motion-sensor also transmitss battery-voltage)

Thank you very much!

[mak-gitdev]

Hi @apfeuti,

It is already supported but not tested.
Use EEP A5-07-03 like in this example:

[my_nodon_pir]
address = 0x058E8ECE
rorg = 0xA5
func =0x07
type=0x03

Please report if everything is OK. Thanks.

[apfeuti]

I use standalone (followed the guidlines in your readme - pip install )

pip list
enocean 0.60.1
enocean-mqtt 0.1.3

[apfeuti]

I see - let me retry with the mapping.yaml from develop-banch

[apfeuti]

Ok, I use the versions listed above (standalone enocean-mqtt 0.1.3). As mapping.yaml I took the one from your develop-branch.

The startup warning is gone, but the message received by motion can still not be interpreted:

2023-03-25 16:29:20,785 INFO: Device enoceanmqtt/nodon_pir_wozi (@: 058E8ECE / EEP: A5-07-03) updated on device database
2023-03-25 16:29:20,788 INFO: Device enoceanmqtt/eltako_ftke_essen2 (@: FEEF21A2 / EEP: F6-10-00) updated on device database
2023-03-25 16:29:44,874 INFO: received: 05:8E:8E:CE->FF:FF:FF:FF (-49 dBm): 0x01 ['0xa5', '0x96', '0xf', '0x0', '0x88', '0x5', '0x8e', '0x8e', '0xce', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x31', '0x0'] OrderedDict()
2023-03-25 16:29:44,875 WARNING: Cannot find type in EEP!
2023-03-25 16:29:44,875 WARNING: message not interpretable: enoceanmqtt/nodon_pir_wozi

We can chat here, if you like: https://test-qbe2657.slack.com/archives/C0509EYAXR8

[mak-gitdev]

Ok I see,

I thought it was indicated in the wiki.
You have to replace the EEP.xml file the enocean directory with the one in the develop branch (enocean/protocol/).
To do that, in the HA_enoceanmqtt directory, do:

cp -rf enocean/protocol/EEP.xml \ 
$(find / -path ./ -prune -o -name "EEP.xml" -print -quit 2>/dev/null)

[apfeuti]

Thanks!
In the meantime I switched to the docker-version from develop-branch - and all is fine!

Some hints anayway:

• I followed the README on the master-branch (the default of your repo) and I haven't seen the WIKI. Maybe a hint on the master-README to the Wiki would be useful. And also a hint to switch to develop-branch, since this is supporting much more devices
• There's no hint (even not with --debug) in the log, when enocenmqtt cannot connect to the mqtt-broker. I had 'mqtt_host = localhost' in the config, which does not work from inside the docker-container.
• I could integrate different Enocean-Devices now - I will make a own post for this, so you know which one I could successfuly test.