PM101 einbinden

[aorta]

Hallo
Ich habe einen PM101 geschenkt bekommen. Bekomme den aber nicht eingebunden. Habe schon eine verschiedene Möglichkeiten probiert. Aber die Werte für
die Helligkeit bekomme ich nicht hin. Verschiedene Werte werden aber gesendet. Das kann ich im DolphinView sehen.
Im Augenblick teste ich es so:

Code Auswählen Erweitern

define PM101S EnOcean FF801476
attr PM101S IODev TCM_ESP3_0
attr PM101S eep G5-ZZ-ZZ
attr PM101S manufID 00D
attr PM101S room EnOcean
attr PM101S subType PM101
attr PM101S teachMethod RPS
#
define FileLog_PM101S FileLog ./log/PM101S-%Y.log PM101S
attr FileLog_PM101S logtype EnO_motion:Motion,EnO_brightness4:Brightness,text
attr FileLog_PM101S room EnOcean
#
define PM101 EnOcean FF801477
attr PM101 IODev TCM_ESP3_0
attr PM101 eep G5-ZZ-ZZ
attr PM101 manufID 00D
attr PM101 room EnOcean
attr PM101 subType PM101
attr PM101 teachMethod 4BS
#
define FileLog_PM101 FileLog ./log/PM101S-%Y.log PM101
attr FileLog_PM101 logtype EnO_motion:Motion,EnO_brightness4:Brightness,text
attr FileLog_PM101 room EnOcean
Beim DolphinView kommt was im Bild zu sehen ist.
Wo steckt der Fehler?
Danke
Gruß
Patrick

[krikan]

Hallo Patrick!
Mir faellt nur auf, dass manufID falsch ist. Ansonsten kann ich aus dem fhem.cfg-Auszug nichts erkennen. Besser waere ein "list <device>" und ein log mit verbose 5 der empfangenen Telegramme.
Gruß, Christian

[aorta]

Hallo
Was für eine manufID muss ich vergeben? Ich werde mal mit 5 loggen.
Gruß
Patrick

[krikan]

manufId für AWAG(Omnio) ist 005.
Die wird so bei Anlage des FHEM-Devices mit dem inoffiziellen EEP G5-ZZ-ZZ vorbelegt.

[aorta]

Hallo
So habe ich jetzt gemacht. Bei 005 bekomme ich folgende Logs.

Code Auswählen Erweitern

2016.12.04 18:37:21 5: TCM_ESP3_0: dispatch EnOcean:1:F6:70:FF801476:30:01FFFFFFFF4700
2016.12.04 18:37:21 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:70:FF801476:30:01FFFFFFFF4700
2016.12.04 18:37:21 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 70 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:21 5: Triggering PM101S (3 changes)
2016.12.04 18:37:21 5: Starting notify loop for PM101S, 3 event(s), first is buttons: pressed
2016.12.04 18:37:21 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFF
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFFFFFF4900DE
2016.12.04 18:37:21 5: TCM_ESP3_0: dispatch EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4900
2016.12.04 18:37:21 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4900
2016.12.04 18:37:21 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 00 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:21 5: Triggering PM101S (2 changes)
2016.12.04 18:37:21 5: Starting notify loop for PM101S, 2 event(s), first is buttons: released
2016.12.04 18:37:21 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630FF8014763001FFFF
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630FF8014763001FFFFFFFF490039
2016.12.04 18:37:21 5: TCM_ESP3_0: dispatch EnOcean:1:F6:30:FF801476:30:01FFFFFFFF4900
2016.12.04 18:37:21 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:30:FF801476:30:01FFFFFFFF4900
2016.12.04 18:37:21 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 30 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:21 5: Triggering PM101S (3 changes)
2016.12.04 18:37:21 5: Starting notify loop for PM101S, 3 event(s), first is buttons: pressed
2016.12.04 18:37:21 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFF
2016.12.04 18:37:21 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFFFFFF470008
2016.12.04 18:37:22 5: TCM_ESP3_0: dispatch EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4700
2016.12.04 18:37:22 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4700
2016.12.04 18:37:22 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 00 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:22 5: Triggering PM101S (2 changes)
2016.12.04 18:37:22 5: Starting notify loop for PM101S, 2 event(s), first is buttons: released
2016.12.04 18:37:22 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF6B0
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF6B0FF8014763001FFFF
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF6B0FF8014763001FFFFFFFF4C0089
2016.12.04 18:37:22 5: TCM_ESP3_0: dispatch EnOcean:1:F6:B0:FF801476:30:01FFFFFFFF4C00
2016.12.04 18:37:22 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:B0:FF801476:30:01FFFFFFFF4C00
2016.12.04 18:37:22 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: B0 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:22 5: Triggering PM101S (3 changes)
2016.12.04 18:37:22 5: Starting notify loop for PM101S, 3 event(s), first is buttons: pressed
2016.12.04 18:37:22 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFF
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFFFFFF4900DE
2016.12.04 18:37:22 5: TCM_ESP3_0: dispatch EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4900
2016.12.04 18:37:22 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4900
2016.12.04 18:37:22 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 00 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:22 5: Triggering PM101S (2 changes)
2016.12.04 18:37:22 5: Starting notify loop for PM101S, 2 event(s), first is buttons: released
2016.12.04 18:37:22 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF6F0
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF6F0FF8014763001FFFF
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000707017AF6F0FF8014763001FFFFFFFF490033
2016.12.04 18:37:22 5: TCM_ESP3_0: dispatch EnOcean:1:F6:F0:FF801476:30:01FFFFFFFF4900
2016.12.04 18:37:22 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:F0:FF801476:30:01FFFFFFFF4900
2016.12.04 18:37:22 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: F0 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:22 5: Triggering PM101S (3 changes)
2016.12.04 18:37:22 5: Starting notify loop for PM101S, 3 event(s), first is buttons: pressed
2016.12.04 18:37:22 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5BB
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5BB005000FF80147700
2016.12.04 18:37:22 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5BB005000FF8014770001FFFFFFFF490070
2016.12.04 18:37:22 5: TCM_ESP3_0: dispatch EnOcean:1:A5:BB005000:FF801477:00:01FFFFFFFF4900
2016.12.04 18:37:22 4: EnOcean received via TCM_ESP3_0: EnOcean:1:A5:BB005000:FF801477:00:01FFFFFFFF4900
2016.12.04 18:37:22 4: EnOcean PM101 received PacketType: 1 RORG: A5 DATA: BB005000 SenderID: FF801477 STATUS: 00
2016.12.04 18:37:22 2: EnOcean PM101 4BS teach-in accepted. No EEP profile identifier and no Manufacturer ID
2016.12.04 18:37:22 5: Triggering PM101 (1 changes)
2016.12.04 18:37:22 5: Starting notify loop for PM101, 1 event(s), first is teach: 4BS teach-in accepted: No EEP profile identifier and no Manufacturer ID
2016.12.04 18:37:22 5: statistics myStatDevice: Notify.266 Notification of 'PM101' received. Device not monitored.
2016.12.04 18:37:23 5: TCM TCM_ESP3_0 received ESP: 55000707017AF650
2016.12.04 18:37:23 5: TCM TCM_ESP3_0 received ESP: 55000707017AF650FF8014763002FFFF
2016.12.04 18:37:23 5: TCM TCM_ESP3_0 received ESP: 55000707017AF650FF8014763002FFFFFFFF460099
2016.12.04 18:37:23 5: TCM_ESP3_0: dispatch EnOcean:1:F6:50:FF801476:30:02FFFFFFFF4600
2016.12.04 18:37:23 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:50:FF801476:30:02FFFFFFFF4600
2016.12.04 18:37:23 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 50 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:23 5: Triggering PM101S (3 changes)
2016.12.04 18:37:23 5: Starting notify loop for PM101S, 3 event(s), first is buttons: pressed
2016.12.04 18:37:23 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFF
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFFFFFF440037
2016.12.04 18:37:24 5: TCM_ESP3_0: dispatch EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4400
2016.12.04 18:37:24 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4400
2016.12.04 18:37:24 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 00 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:24 5: Triggering PM101S (2 changes)
2016.12.04 18:37:24 5: Starting notify loop for PM101S, 2 event(s), first is buttons: released
2016.12.04 18:37:24 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630FF8014763002FFFF
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF630FF8014763002FFFFFFFF4400B6
2016.12.04 18:37:24 5: TCM_ESP3_0: dispatch EnOcean:1:F6:30:FF801476:30:02FFFFFFFF4400
2016.12.04 18:37:24 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:30:FF801476:30:02FFFFFFFF4400
2016.12.04 18:37:24 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 30 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:24 5: Triggering PM101S (3 changes)
2016.12.04 18:37:24 5: Starting notify loop for PM101S, 3 event(s), first is buttons: pressed
2016.12.04 18:37:24 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFF
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000707017AF600FF8014763002FFFFFFFF470008
2016.12.04 18:37:24 5: TCM_ESP3_0: dispatch EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4700
2016.12.04 18:37:24 4: EnOcean received via TCM_ESP3_0: EnOcean:1:F6:00:FF801476:30:02FFFFFFFF4700
2016.12.04 18:37:24 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 00 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:24 5: Triggering PM101S (2 changes)
2016.12.04 18:37:24 5: Starting notify loop for PM101S, 2 event(s), first is buttons: released
2016.12.04 18:37:24 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA500
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA500056A0CFFD9B48200
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA500056A0CFFD9B4820003FFFFFFFF5200DD
2016.12.04 18:37:24 5: TCM_ESP3_0: dispatch EnOcean:1:A5:00056A0C:FFD9B482:00:03FFFFFFFF5200
2016.12.04 18:37:24 4: EnOcean received via TCM_ESP3_0: EnOcean:1:A5:00056A0C:FFD9B482:00:03FFFFFFFF5200
2016.12.04 18:37:24 4: EnOcean PM101S received PacketType: 1 RORG: F6 DATA: 00 SenderID: FF801476 STATUS: 30
2016.12.04 18:37:24 5: Triggering PM101S (2 changes)
2016.12.04 18:37:24 5: Starting notify loop for PM101S, 2 event(s), first is buttons: released
2016.12.04 18:37:24 5: statistics myStatDevice: Notify.266 Notification of 'PM101S' received. Device not monitored.
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5BB
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5BB685002FF80147700
2016.12.04 18:37:24 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5BB685002FF8014770001FFFFFFFF47007B
2016.12.04 18:37:24 5: TCM_ESP3_0: dispatch EnOcean:1:A5:BB685002:FF801477:00:01FFFFFFFF4700
2016.12.04 18:37:24 4: EnOcean received via TCM_ESP3_0: EnOcean:1:A5:BB685002:FF801477:00:01FFFFFFFF4700
2016.12.04 18:37:24 4: EnOcean PM101 received PacketType: 1 RORG: A5 DATA: BB685002 SenderID: FF801477 STATUS: 00
2016.12.04 18:37:24 2: EnOcean PM101 4BS teach-in accepted. No EEP profile identifier and no Manufacturer ID
2016.12.04 18:37:24 5: Triggering PM101 (1 changes)
2016.12.04 18:37:24 5: Starting notify loop for PM101, 1 event(s), first is teach: 4BS teach-in accepted: No EEP profile identifier and no Manufacturer ID
2016.12.04 18:37:24 5: statistics myStatDevice: Notify.266 Notification of 'PM101' received. Device not monitored.
2016.12.04 18:37:28 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA500
2016.12.04 18:37:28 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5000A080CFFFC290000
2016.12.04 18:37:28 5: TCM TCM_ESP3_0 received ESP: 55000A0701EBA5000A080CFFFC29000003FFFFFFFF4F00D0
2016.12.04 18:37:28 5: TCM_ESP3_0: dispatch EnOcean:1:A5:000A080C:FFFC2900:00:03FFFFFFFF4F00
Und:

Code Auswählen Erweitern

Internals:
   DEF        FF801477
   IODev      TCM_ESP3_0
   LASTInputDev TCM_ESP3_0
   MSGCNT     2
   NAME       PM101
   NR         74
   NTFY_ORDER 50-PM101
   STATE      D0
   TCM_ESP3_0_DestinationID FFFFFFFF
   TCM_ESP3_0_MSGCNT 2
   TCM_ESP3_0_PacketType 1
   TCM_ESP3_0_RSSI -71
   TCM_ESP3_0_ReceivingQuality excellent
   TCM_ESP3_0_RepeatingCounter 0
   TCM_ESP3_0_SubTelNum 1
   TCM_ESP3_0_TIME 2016-12-04 18:37:24
   TYPE       EnOcean
   Readings:
     2016-12-04 12:32:48   buttons         pressed
     2016-12-04 12:32:48   channelA        AI
     2016-12-04 12:32:47   channelB        B0
     2016-12-04 12:32:48   channelC        C0
     2016-12-04 12:32:48   channelD        D0
     2016-12-04 12:32:48   state           D0
     2016-12-04 18:37:24   teach           4BS teach-in accepted: No EEP profile identifier and no Manufacturer ID
   Helper:
Attributes:
   IODev      TCM_ESP3_0
   eep        G5-ZZ-ZZ
   manufID    005
   room       EnOcean
   subType    raw
   teachMethod 4BS
Und

Code Auswählen Erweitern

Internals:
   DEF        FF801476
   IODev      TCM_ESP3_0
   LASTInputDev TCM_ESP3_0
   MSGCNT     35
   NAME       PM101S
   NR         70
   NTFY_ORDER 50-PM101S
   STATE      BI
   TCM_ESP3_0_DestinationID FFFFFFFF
   TCM_ESP3_0_MSGCNT 35
   TCM_ESP3_0_PacketType 1
   TCM_ESP3_0_RSSI -76
   TCM_ESP3_0_ReceivingQuality good
   TCM_ESP3_0_RepeatingCounter 0
   TCM_ESP3_0_SubTelNum 1
   TCM_ESP3_0_TIME 2016-12-04 19:07:48
   TYPE       EnOcean
   Readings:
     2016-12-04 19:07:48   buttons         released
     2016-12-04 19:07:48   channelA        AI
     2016-12-04 18:57:37   channelB        BI
     2016-12-04 18:37:24   channelC        C0
     2016-12-04 18:37:22   channelD        D0
     2016-12-04 18:57:37   state           BI
   Helper:
Attributes:
   IODev      TCM_ESP3_0
   eep        G5-ZZ-ZZ
   manufID    005
   room       EnOcean
   subType    PM101
   teachMethod RPS
Gruß
Patrick

[krikan]

Bitte den subType des Devices "PM101" auf PM101 aendern.
Wurden die geposteten Telegramme für das Devices PM101 per manuellem Versand/Tastendruck der Teach-In Nachricht erzeugt?
Falls ja, bitte nach Aenderung des subType auf neue Nachricht warten und schauen, ob erfolgreich.

[aorta]

Hallo
Beide Kanäle (FF801476, FF801477) haben doch als subType PM101??
Nein, das waren Telegramme die im laufenden Betrieb gesendet wurden.
Gruß
Patrick

[krikan]

Laut Deiner list-Ausgabe für PM101 ist der subType raw.
Du hast den learningMode auf always stehen oder der TCM befand sich waehrend des Empfangs vermutlich im Teach-Mode!?
Wenn der learningMode nicht an ist und ich Deine Nachricht in meinem System einspeise, kommen in meinem Log solche Hinweise:

Code Auswählen Erweitern

2016.12.04 20:11:02.138 4: EnOcean Testschalter received PacketType: 1 RORG: A5 DATA: BB685000 SenderID: FF801477 STATUS: 00
2016.12.04 20:11:02.139 4: EnOcean Testschalter teach-in with subType PM101 locked, set transceiver in teach mode.
Bedeutet mMn, dass der PM101 immer Teach-In Telegramme schickt, die von FHEM geblockt werden oder -wie bei Dir- bei eingeschaltetem Teach-Mode zum Verstellen der Attribute des bereits korrekt angelegten Devices führen. Bin mir nur unsicher, ob das ein Problem Deines PM101 oder eine Besonderheit des PM101 ist.

Mir faellt keine Lösung dazu ein, bitte auf klaus.schauer (Modulmaintainer) warten.