Autor Thema: NODON D2-01-12  (Gelesen 3760 mal)

asterix86

  • Gast
NODON D2-01-12
« am: 12 April 2017, 01:13:44 »
Hi,

I'm trying to activate a NODON double switch from FHEM EEP is D2-01-12. I saw a related post here:
https://forum.fhem.de/index.php/topic,66476.0.html
That I tried to follow. now my config is this one :

list VMC gives me that:
Internals:
   DEF        019D4D95
   IODev      TCM310_0
   LASTInputDev TCM310_0
   MSGCNT     5
   NAME       VMC
   NR         65
   NTFY_ORDER 50-VMC
   STATE      046180
   TCM310_0_DestinationID FFFFFFFF
   TCM310_0_MSGCNT 5
   TCM310_0_PacketType 1
   TCM310_0_RSSI -71
   TCM310_0_ReceivingQuality excellent
   TCM310_0_RepeatingCounter 0
   TCM310_0_SubTelNum 3
   TCM310_0_TIME 2017-04-12 00:51:03
   TYPE       EnOcean
   Readings:
     2017-04-12 00:51:27   channel0        off
     2017-04-12 00:51:26   channel1        off
     2017-04-12 00:51:27   dim0            0
     2017-04-12 00:51:26   dim1            0
     2017-04-12 00:23:06   state           046180
   Helper:
Attributes:
   IODev      TCM310_0
   comMode    biDir
   defaultChannel 0
   devChannel 2
   eep        D2-01-12
   manufID    046
   room       EnOcean
   subDef     019D4D95
   subType    actuator.01
   
   
list VMC_0 gives me:

Internals:
   DEF        VMC:channel0
   DEVICE     VMC
   NAME       VMC_0
   NOTIFYDEV  global,VMC
   NR         66
   NTFY_ORDER 50-VMC_0
   READING    channel0
   STATE      off
   TYPE       readingsProxy
   Content:
     VMC        1
   Readings:
     2017-04-12 00:51:27   lastCmd         off
     2017-04-12 00:51:27   state           off
Attributes:
   group      VMC
   room       SDB
   setFn      {($CMD eq "on") ?"on 0":"off 0"}
   setList    on off
   webCmd     on:off
   

And finaly list VMC_1 gove me:
Internals:
   DEF        VMC:channel1
   DEVICE     VMC
   NAME       VMC_1
   NOTIFYDEV  global,VMC
   NR         67
   NTFY_ORDER 50-VMC_1
   READING    channel1
   STATE      off
   TYPE       readingsProxy
   Content:
     VMC        1
   Readings:
     2017-04-12 00:51:26   lastCmd         off
     2017-04-12 00:51:26   state           off
Attributes:
   group      VMC
   room       SDB
   setFn      {($CMD eq "on") ?"on 1":"off 1"}
   setList    on off
   webCmd     on:off


But When I press the on or off button, nothing happen on the NODON :/

I activated logs, and when I press the on link of VMC_0, here is what I see:

2017.04.12 01:00:11 5 : Cmd: >set VMC_0 on<
2017.04.12 01:00:11 4 : VMC_0: set hash->{DEVICE} on 0
2017.04.12 01:00:11 5 : Starting notify loop for VMC, 1 event(s), first is channel0: on
2017.04.12 01:00:11 5 : createNotifyHash
2017.04.12 01:00:11 5 : Starting notify loop for VMC_0, 1 event(s), first is on
2017-04-12 01:00:11 readingsProxy VMC_0 on
2017.04.12 01:00:11 5 : End notify loop for VMC_0
2017-04-12 01:00:11 EnOcean VMC channel0: on
2017.04.12 01:00:11 5 : End notify loop for VMC
2017.04.12 01:00:11 5 : Starting notify loop for VMC, 1 event(s), first is dim0: 100
2017-04-12 01:00:11 EnOcean VMC dim0: 100
2017.04.12 01:00:11 5 : End notify loop for VMC
2017.04.12 01:00:11 3 : EnOcean set VMC on
2017.04.12 01:00:11 4 : EnOcean VMC sent PacketType: 1 RORG: D2 DATA: 010064 SenderID: 019D4D95 STATUS: 00 ODATA:
2017.04.12 01:00:11 5 : TCM TCM310_0 sent ESP: 55000900013DD2010064019D4D9500DE
2017.04.12 01:00:11 5 : SW: 55000900013DD2010064019D4D9500DE

Could you help me controlling this device please?

Offline Eisix

  • Hero Member
  • *****
  • Beiträge: 1095
Antw:NODON D2-01-12
« Antwort #1 am: 16 Mai 2017, 11:18:08 »
Hi,

from a first look at your config I would say it's OK.

I would do a reset of the Nodon and start a new teach in using the readingsproxy switches as teach-signal.

Regards
Eisix