Pairing - NodOn Enocean Einbaumodul 2 Kanal - D2-01-12

Deutsche Foren Geräte
#1

Ich versuche, bisher vergeblich, einen Enocean Aktor der Firma NodOn in mein Homegear Setup einzubinden. Folgendes habe ich bisher erreicht:

Soweit so gut…
Sobald ich einen der Taster betätige, empfängt homegear lediglich den RSSI Wert des Aktors hier ein Auszug aus dem Log dazu:

09/30/17 15:20:41.411 EnOcean packet received (My-EnOcean-Interface, RSSI: -91 dBm): 55000707017AF61001Axxxxx3001FFFFFFFF5B003E - Sender address: 0x01Axxxxx
09/30/17 15:20:41.411 Info: Publishing topic homegear/instance/json/35/0/RSSI_DEVICE
09/30/17 15:20:41.414 Info: Publishing topic homegear/instance/plain/35/0/RSSI_DEVICE
09/30/17 15:20:41.415 Info: Publishing topic homegear/instance/jsonobj/35/0
09/30/17 15:20:41.474 EnOcean packet received (My-EnOcean-Interface, RSSI: -94 dBm): 55000707017AF60001Axxxxx2001FFFFFFFF5E0037 - Sender address: 0x01Axxxxx
09/30/17 15:20:41.490 EnOcean packet received (My-EnOcean-Interface, RSSI: -92 dBm): 550009070156D20460E401Axxxxx0001FFFFFFFF5C0053 - Sender address: 0x01Axxxxx

Setze ich den Wert eines Kanal über Homegear tut sich ebenfalls nichts am Aktor. Hier die Log Ausgabe:

09/30/17 15:54:41.993 Module EnOcean: Info: STATE of peer 35 with serial number EOD01Axxxxx:1 was set to 0x64.
09/30/17 15:54:41.993 Module EnOcean: EnOcean USB 300 "My-EnOcean-Interface": Info: Sending packet 550009070156D2010064FFA2BA00000301Axxxxx000039
09/30/17 15:54:42.014 Info: Publishing topic homegear/instance/json/35/1/STATE
09/30/17 15:54:42.016 Info: Publishing topic homegear/instance/plain/35/1/STATE
09/30/17 15:54:42.017 Info: Publishing topic homegear/instance/jsonobj/35/1
09/30/17 15:54:42.062 Module EnOcean: EnOcean USB 300 "My-EnOcean-Interface": Info: Ignoring packet from myself: 550009070156D2010064FFA2BA00810101Axxxxx5E00F6

Kann mir hier jemand weiterhelfen? Muss ich noch etwas am Aktor einstellen, oder mit Homegear bestätigen, dass die Signale akzeptiert werden?

Homegear Version: 0.7.9-1375

#2

Hi @dpm,

@sathya hatte hier mal beschrieben, wie man EnOcean Geräte anlernt: EnOcean Pi 868 GPIO

Ich kann leider nicht sagen, ob es über pon genauso funktionieren würde.
Schau dir sicherheitshalber mal das Log mit debuglevel 5 an. Du kannst das Loglevel in der homegear Konsole mit dl 5 zur Laufzeit ändern.

so long,
p

#3

Vielen Dank für die schnelle Antwort!

Lege ich den Aktor manuell mit peers create an, komme ich zu dem gleichen Ergebnis wie mit pon

Hier ein Log Auszug mit Debug Level 5 vom Betätigen des Tasters:

10/01/17 12:58:52.370 Debug (My-EnOcean-Interface): Packet  enters raisePacketReceived.
10/01/17 12:58:52.370 Debug (My-EnOcean-Interface): Packet  is now passed to the EventHandler.
10/01/17 12:58:52.370 EnOcean packet received (My-EnOcean-Interface, RSSI: -95 dBm): 55000707017AF60001Axxxxx2001FFFFFFFF5F0022 - Sender address: 0x01Axxxxx
10/01/17 12:58:52.371 Debug (My-EnOcean-Interface): Packet processing of packet  took 0 ms.
10/01/17 12:58:52.418 Debug (My-EnOcean-Interface): Packet  enters raisePacketReceived.
10/01/17 12:58:52.418 Debug (My-EnOcean-Interface): Packet  is now passed to the EventHandler.
10/01/17 12:58:52.417 EnOcean packet received (My-EnOcean-Interface, RSSI: -89 dBm): 55000707017AF61001Axxxxx3101FFFFFFFF590007 - Sender address: 0x01Axxxxx
10/01/17 12:58:52.418 Debug (My-EnOcean-Interface): Packet processing of packet  took 0 ms.
10/01/17 12:58:52.465 Debug (My-EnOcean-Interface): Packet  enters raisePacketReceived.
10/01/17 12:58:52.466 Debug (My-EnOcean-Interface): Packet  is now passed to the EventHandler.
10/01/17 12:58:52.465 EnOcean packet received (My-EnOcean-Interface, RSSI: -89 dBm): 550009070156D20460E401Axxxxx0101FFFFFFFF590001 - Sender address: 0x01Axxxxx
10/01/17 12:58:52.466 Debug (My-EnOcean-Interface): Packet processing of packet  took 0 ms.

Und hier vom Ändern eines Kanals über Homegear:

10/01/17 13:09:20.864 Module EnOcean: Info: STATE of peer 35 with serial number EOD01Axxxxx:1 was set to 0x00.
10/01/17 13:09:20.865 Module EnOcean: EnOcean USB 300 "My-EnOcean-Interface": Info: Sending packet 550009070156D2010000FFA2BA00000301Axxxxx000062
10/01/17 13:09:20.907 Module EnOcean: EnOcean USB 300 "My-EnOcean-Interface": Info: Ignoring packet from myself: 550009070156D2010000FFA2BA00810101Axxxxx5C0087

@sathya hat hier mal angemerkt, dass Sie eines der NodOn Module im Einsatz hat: Events sehr langsam

Gruß,
dpm

#4

HI,

I get my FUD61NPN-230 not connected.
How do I associate this with the homegear?

Thanks

#5

As described here: EnOcean Pi 868 GPIO, maybe use google translate.

#6

Hi,
My window handle is paired successful

The problem witd fud61npn is that the eep is not supported
I use EEP A53808 for this dimmer but device is not supported.
Do I use the wrong eep?

#7

I use the FUD61 with A53802:

  ID │ Name                      │ Serial Number │  Address │     Type │ Type Description                             
─────┼───────────────────────────┼───────────────┼──────────┼──────────┼───────────────────────────────────────────────
  23 │                           │   EOD01AXXXXX │ 01A2XXXX │  1A53802 │ Eltako FUD61NPN-230V                         
─────┴───────────────────────────┴───────────────┴──────────┴──────────┴───────────────────────────────────────────────
#8

OK this works thanks.
Do I have to pair the dimmer in homegear?
I have now read the serial number through the logs and use them.
Do I have to do something else?

#9

In openhab it is only possible to read the values.
I can not send a valvue or toggle On/Off

#10

I think this should be possible, as I don’t have any problem dimming and switching my FUD61 via mqtt over homegear.

#11

Hey,

the EEP for the Eltako FUD61NPN is “01A53802” as there are some differences to “A53802”.

Cheers,

Sathya

1 Like
Pairing vom FUD61NPN will nicht klappen