[Gelöst]HMCCUDEV mit unveränderten Defaults: Fehler " ... Invalid datapoint"

supernova1963 · 29 März 2017, 19:08:56

Super, ich habe alles auf Vollzugriff gestellt und den rpc neu gestartet.

Logeinträge:


2017.03.29 19:03:58 2: HMCCURPC: Starting thread for data processing
2017.03.29 19:03:58 2: HMCCURPC: Started thread for data processing. TID=16
2017.03.29 19:03:58 2: CCURPC: Thread DATA processing RPC events. TID=16
2017.03.29 19:03:58 2: HMCCURPC: RPC server thread started for interface BidCos-RF with TID=17
2017.03.29 19:03:58 2: CCURPC: Initializing RPC server CB2001 for interface BidCos-RF
2017.03.29 19:03:58 2: HMCCURPC: Callback server CB2001 created. Listening on port 7411
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for events for server CB2001
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for new devices for server CB2001
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for deleted devices for server CB2001
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for modified devices for server CB2001
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for replaced devices for server CB2001
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for readded devices for server CB2001
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for list devices for server CB2001
2017.03.29 19:03:58 2: CCURPC: CB2001 accepting connections. TID=17
2017.03.29 19:03:58 2: HMCCURPC: RPC server thread started for interface BidCos-Wired with TID=18
2017.03.29 19:03:58 2: CCURPC: Initializing RPC server CB2000 for interface BidCos-Wired
2017.03.29 19:03:58 2: HMCCURPC: Callback server CB2000 created. Listening on port 7410
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for events for server CB2000
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for new devices for server CB2000
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for deleted devices for server CB2000
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for modified devices for server CB2000
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for replaced devices for server CB2000
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for readded devices for server CB2000
2017.03.29 19:03:58 2: HMCCURPC: Adding callback for list devices for server CB2000
2017.03.29 19:03:58 2: CCURPC: CB2000 accepting connections. TID=18
2017.03.29 19:03:59 2: HMCCURPC: RPC server thread started for interface HmIP-RF with TID=19
2017.03.29 19:03:59 2: CCURPC: Initializing RPC server CB2010 for interface HmIP-RF
2017.03.29 19:03:59 2: HMCCURPC: Callback server CB2010 created. Listening on port 7420
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for events for server CB2010
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for new devices for server CB2010
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for deleted devices for server CB2010
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for modified devices for server CB2010
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for replaced devices for server CB2010
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for readded devices for server CB2010
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for list devices for server CB2010
2017.03.29 19:03:59 2: CCURPC: CB2010 accepting connections. TID=19
2017.03.29 19:03:59 2: HMCCURPC: RPC server thread started for interface VirtualDevices with TID=20
2017.03.29 19:03:59 2: CCURPC: Initializing RPC server CB9292 for interface VirtualDevices
2017.03.29 19:03:59 2: HMCCURPC: Callback server CB9292 created. Listening on port 14702
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for events for server CB9292
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for new devices for server CB9292
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for deleted devices for server CB9292
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for modified devices for server CB9292
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for replaced devices for server CB9292
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for readded devices for server CB9292
2017.03.29 19:03:59 2: HMCCURPC: Adding callback for list devices for server CB9292
2017.03.29 19:03:59 2: CCURPC: CB9292 accepting connections. TID=20
2017.03.29 19:04:00 1: HMCCURPC: RPC server(s) starting
2017.03.29 19:04:00 1: HMCCURPC: Received SL event. RPC server DATA enters server loop
2017.03.29 19:04:00 1: HMCCURPC: Received SL event. RPC server CB2001 enters server loop
2017.03.29 19:04:00 1: HMCCURPC: Received SL event. RPC server CB2000 enters server loop
2017.03.29 19:04:00 1: HMCCURPC: Received SL event. RPC server CB2010 enters server loop
2017.03.29 19:04:00 1: HMCCURPC: Received SL event. RPC server CB9292 enters server loop
2017.03.29 19:04:00 1: HMCCURPC: All threads working
2017.03.29 19:04:00 1: HMCCURPC: Registering callback http://192.168.1.5:7411/fh2001 with ID CB2001 at http://192.168.1.4:2001/
2017.03.29 19:04:00 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.29 19:04:00 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7411/fh2001 registered
2017.03.29 19:04:00 1: HMCCURPC: Registering callback http://192.168.1.5:7410/fh2000 with ID CB2000 at http://192.168.1.4:2000/
2017.03.29 19:04:00 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7410/fh2000 registered
2017.03.29 19:04:00 1: HMCCURPC: Registering callback http://192.168.1.5:7420/fh2010 with ID CB2010 at http://192.168.1.4:2010/
2017.03.29 19:04:00 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7420/fh2010 registered
2017.03.29 19:04:00 1: HMCCURPC: Registering callback http://192.168.1.5:14702/fh9292 with ID CB9292 at http://192.168.1.4:9292/groups
2017.03.29 19:04:00 2: CCURPC: CB2001 NewDevice received 64 device specifications
2017.03.29 19:04:00 1: CCURPC: CB2010 ListDevices. Sending init to HMCCU
2017.03.29 19:04:00 1: CCURPC: CB9292 ListDevices. Sending init to HMCCU
2017.03.29 19:04:10 1: HMCCURPC: RPC callback with URL http://192.168.1.5:14702/fh9292 registered
2017.03.29 19:04:10 1: HMCCURPC: Received IN event. RPC server CB2001 running.
2017.03.29 19:04:10 1: HMCCURPC: Received IN event. RPC server CB2010 running.
2017.03.29 19:04:10 1: HMCCURPC: Received IN event. RPC server CB9292 running.
2017.03.29 19:04:56 3: netatmo_M06_00_00_02_49_48: poll (MODULE)
2017.03.29 19:04:56 3: netatmo_M06_00_00_02_49_48: requestDeviceReadings (WindStrength,WindAngle,GustStrength,GustAngle)
2017.03.29 19:04:56 2: netatmo_M06_00_00_02_49_48: next dynamic update at 2017-03-29 19:14:59
2017.03.29 19:05:02 3: netatmo_D70_ee_50_20_fb_8e: poll (DEVICE)
2017.03.29 19:05:02 3: netatmo_D70_ee_50_20_fb_8e: requestDeviceReadings (Temperature,CO2,Humidity,Noise,Pressure)
2017.03.29 19:05:02 2: netatmo_D70_ee_50_20_fb_8e: next dynamic update at 2017-03-29 19:15:02
2017.03.29 19:05:40 2: HMCCURPC: Checking if all threads are running
2017.03.29 19:05:40 1: HMCCURPC: Only 4 of 5 threads are running. Cleaning up
2017.03.29 19:05:40 1: HMCCURPC: Housekeeping called. Cleaning up RPC environment
2017.03.29 19:05:40 2: HMCCURPC: Stop I/O handling
2017.03.29 19:05:40 2: HMCCURPC: Close child socket
2017.03.29 19:05:40 2: HMCCURPC: Close parent socket
2017.03.29 19:05:40 2: HMCCURPC: Sending signal INT to thread CB2010 TID=19
2017.03.29 19:05:40 2: HMCCURPC: Sending signal INT to thread CB9292 TID=20
2017.03.29 19:05:40 2: HMCCURPC: Sending signal INT to thread CB2000 TID=18
2017.03.29 19:05:40 2: HMCCURPC: Sending signal INT to thread DATA TID=16
2017.03.29 19:05:40 2: HMCCURPC: Sending signal INT to thread CB2001 TID=17
2017.03.29 19:05:40 2: CCURPC: DATA stopped event processing. TID=16
2017.03.29 19:05:40 2: CCURPC: RPC server CB2001 stopped handling connections. TID=17
2017.03.29 19:05:40 2: CCURPC: RPC server CB2010 stopped handling connections. TID=19
2017.03.29 19:05:40 2: CCURPC: RPC server CB9292 stopped handling connections. TID=20
2017.03.29 19:05:41 2: CCURPC: RPC server CB2000 stopped handling connections. TID=18
2017.03.29 19:05:42 2: HMCCURPC: Thread CB2010 with TID=19 has been stopped. Deleting it
2017.03.29 19:05:42 2: HMCCURPC: Thread CB9292 with TID=20 has been stopped. Deleting it
2017.03.29 19:05:42 2: HMCCURPC: Thread CB2000 with TID=18 has been stopped. Deleting it
2017.03.29 19:05:42 2: HMCCURPC: Thread DATA with TID=16 has been stopped. Deleting it
2017.03.29 19:05:42 2: HMCCURPC: Thread CB2001 with TID=17 has been stopped. Deleting it
2017.03.29 19:05:54 3: Nmap (nmap) - starting network scan
adjust_timeouts2: packet supposedly had rtt of -86725 microseconds.  Ignoring time.
adjust_timeouts2: packet supposedly had rtt of -60241 microseconds.  Ignoring time.
2017.03.29 19:06:05 3: Nmap (nmap) - network scan done

zap · 29 März 2017, 19:28:18

Ok, es werden nur 3 von 4 RPC-Servern gestartet, daher werden die 3 auch wieder beendet. Der RPC-Server für Wired-Devices kann nicht gestartet werden. Hast Du Wired Devices in der CCU? Falls nicht, bitte diesen Eintrag im I/O Device (Atribut rpcport oder rpcinterface) deaktivieren.

Problem: Wenn Du keine Wired Devices hast, startet die CCU auch keinen Prozess dafür. Daher kann der RPC-Server für Wired nicht auf FHEM Seite gestartet werden.

supernova1963 · 29 März 2017, 19:53:36

Hat insoweit funktioniert. Status hmccu: running/busy, Status hmccurpc: running/busy.
Kann ich trotzdem "get d_ccu devicelist" aufrufen?

log:

Code Auswählen


2017.03.29 19:33:28 2: HMCCURPC: Starting thread for data processing
2017.03.29 19:33:29 2: HMCCURPC: Started thread for data processing. TID=21
2017.03.29 19:33:29 2: CCURPC: Thread DATA processing RPC events. TID=21
2017.03.29 19:33:29 2: HMCCURPC: RPC server thread started for interface BidCos-RF with TID=22
2017.03.29 19:33:29 2: CCURPC: Initializing RPC server CB2001 for interface BidCos-RF
2017.03.29 19:33:29 2: HMCCURPC: Callback server CB2001 created. Listening on port 7411
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for events for server CB2001
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for new devices for server CB2001
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for deleted devices for server CB2001
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for modified devices for server CB2001
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for replaced devices for server CB2001
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for readded devices for server CB2001
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for list devices for server CB2001
2017.03.29 19:33:29 2: CCURPC: CB2001 accepting connections. TID=22
2017.03.29 19:33:29 2: HMCCURPC: RPC server thread started for interface HmIP-RF with TID=23
2017.03.29 19:33:29 2: CCURPC: Initializing RPC server CB2010 for interface HmIP-RF
2017.03.29 19:33:29 2: HMCCURPC: Callback server CB2010 created. Listening on port 7420
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for events for server CB2010
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for new devices for server CB2010
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for deleted devices for server CB2010
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for modified devices for server CB2010
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for replaced devices for server CB2010
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for readded devices for server CB2010
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for list devices for server CB2010
2017.03.29 19:33:29 2: CCURPC: CB2010 accepting connections. TID=23
2017.03.29 19:33:29 2: HMCCURPC: RPC server thread started for interface VirtualDevices with TID=24
2017.03.29 19:33:29 2: CCURPC: Initializing RPC server CB9292 for interface VirtualDevices
2017.03.29 19:33:29 2: HMCCURPC: Callback server CB9292 created. Listening on port 14702
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for events for server CB9292
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for new devices for server CB9292
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for deleted devices for server CB9292
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for modified devices for server CB9292
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for replaced devices for server CB9292
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for readded devices for server CB9292
2017.03.29 19:33:29 2: HMCCURPC: Adding callback for list devices for server CB9292
2017.03.29 19:33:29 2: CCURPC: CB9292 accepting connections. TID=24
2017.03.29 19:33:30 1: HMCCURPC: RPC server(s) starting
2017.03.29 19:33:30 1: HMCCURPC: Received SL event. RPC server DATA enters server loop
2017.03.29 19:33:30 1: HMCCURPC: Received SL event. RPC server CB2001 enters server loop
2017.03.29 19:33:30 1: HMCCURPC: Received SL event. RPC server CB2010 enters server loop
2017.03.29 19:33:30 1: HMCCURPC: Received SL event. RPC server CB9292 enters server loop
2017.03.29 19:33:30 1: HMCCURPC: All threads working
2017.03.29 19:33:30 1: HMCCURPC: Registering callback http://192.168.1.5:7411/fh2001 with ID CB2001 at http://192.168.1.4:2001/
2017.03.29 19:33:30 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.29 19:33:30 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7411/fh2001 registered
2017.03.29 19:33:30 1: HMCCURPC: Registering callback http://192.168.1.5:7420/fh2010 with ID CB2010 at http://192.168.1.4:2010/
2017.03.29 19:33:30 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7420/fh2010 registered
2017.03.29 19:33:30 1: HMCCURPC: Registering callback http://192.168.1.5:14702/fh9292 with ID CB9292 at http://192.168.1.4:9292/groups
2017.03.29 19:33:30 2: CCURPC: CB2001 NewDevice received 64 device specifications
2017.03.29 19:33:30 1: CCURPC: CB2010 ListDevices. Sending init to HMCCU
2017.03.29 19:33:30 1: CCURPC: CB9292 ListDevices. Sending init to HMCCU
2017.03.29 19:33:40 1: HMCCURPC: RPC callback with URL http://192.168.1.5:14702/fh9292 registered
2017.03.29 19:33:40 1: HMCCURPC: Received IN event. RPC server CB2001 running.
2017.03.29 19:33:40 1: HMCCURPC: Received IN event. RPC server CB2010 running.
2017.03.29 19:33:40 1: HMCCURPC: Received IN event. RPC server CB9292 running.
2017.03.29 19:33:40 1: HMCCURPC: All RPC servers running
2017.03.29 19:33:40 2: HMCCU: No client devices matching .*
2017.03.29 19:33:40 2: HMCCURPC: Updated devices. Success=0 Failed=0

zap · 29 März 2017, 20:37:53

ja, das busy ist noch ein Fehler. Mit dem Update morgen verschwindet das. Wenn vorne "running" steht, kannst Du das busy ignorieren.

supernova1963 · 29 März 2017, 21:18:06

Nachdem ich get devicelist aufgerufen habe, ist der status auf running/OK umgesprungen.

Leider hat das Alles nichts gebracht. Ich stehe wieder auf dem Stand von gestern und vorgestern.
Selbst der Aufruf get HM_03_DimmerDeckenleuchten_DEV1 devstate funktioniert nicht.

Code Auswählen


2017.03.29 21:13:39 1: HMCCUDEV: HM_03_DimmerDeckenleuchten_DEV1 Invalid datapoint

Keine Ahnung, was ich noch machen kann oder soll,

Gernot

zap · 29 März 2017, 21:33:03

Mach mal bitte folgendes:

Code Auswählen


attr HM_03_DimmerDeckenleuchten_DEV1 ccuflags trace

Alternativ über die FHEM Oberfläche das Attribut ccuflags auf trace setzen.
Dann den Befehl nochmal ausführen.
Dann die Logausgabe bitte.

supernova1963 · 29 März 2017, 21:42:31

Hab' ich gemacht, aber ...

Code Auswählen


2017.03.29 21:41:01 1: HMCCUDEV: HM_03_DimmerDeckenleuchten_DEV1 Invalid datapoint

supernova1963 · 29 März 2017, 22:34:46

Ich habe mal das System neu gestartet.

Hier das log:

Code Auswählen


2017.03.29 22:20:58 0: Server shutdown
2017.03.29 22:20:58 1: HMCCURPC: Found 4 threads. Stopping ...
2017.03.29 22:20:58 1: HMCCURPC: Deregistering RPC server http://192.168.1.5:7420/fh2010 with ID CB2010 at http://192.168.1.4:2010/
2017.03.29 22:20:58 1: HMCCURPC: RPC callback for server CB2010 deregistered
2017.03.29 22:20:58 1: HMCCURPC: Deregistering RPC server http://192.168.1.5:14702/fh9292 with ID CB9292 at http://192.168.1.4:9292/groups
2017.03.29 22:20:58 1: HMCCURPC: RPC callback for server CB9292 deregistered
2017.03.29 22:20:58 1: HMCCURPC: Deregistering RPC server http://192.168.1.5:7411/fh2001 with ID CB2001 at http://192.168.1.4:2001/
2017.03.29 22:20:58 1: HMCCURPC: RPC callback for server CB2001 deregistered
2017.03.29 22:20:58 2: HMCCURPC: Sending signal INT to thread CB2010 TID=3
2017.03.29 22:20:58 2: HMCCURPC: Sending signal INT to thread CB9292 TID=4
2017.03.29 22:20:58 2: HMCCURPC: Sending signal INT to thread CB2001 TID=2
2017.03.29 22:20:59 2: CCURPC: RPC server CB9292 stopped handling connections. TID=4
2017.03.29 22:20:59 2: CCURPC: RPC server CB2010 stopped handling connections. TID=3
2017.03.29 22:20:59 2: CCURPC: RPC server CB2001 stopped handling connections. TID=2
2017.03.29 22:20:59 1: HMCCURPC: Found 1 threads. Stopping ...
2017.03.29 22:21:02 1: Including fhem.cfg
2017.03.29 22:21:02 1: telnetPort: Can't open server port at 7072: Address already in use. Exiting.
2017.03.29 22:28:26 1: Including fhem.cfg
2017.03.29 22:28:26 3: telnetPort: port 7072 opened
2017.03.29 22:28:27 3: WEB: port 8083 opened
2017.03.29 22:28:27 3: WEBphone: port 8084 opened
2017.03.29 22:28:27 3: WEBtablet: port 8085 opened
2017.03.29 22:28:27 2: eventTypes: loaded 2721 events from ./log/eventTypes.txt
2017.03.29 22:28:27 3: DbLog logdb: Creating Push-Handle to database mysql:database=fhem;host=localhost;port=3306 with user fhem
2017.03.29 22:28:27 3: DbLog logdb: Push-Handle to db mysql:database=fhem;host=localhost;port=3306 created
2017.03.29 22:28:28 3: Wetterstation: encrypt crypt:045c410b57431a47521376525d075e0e4a01575b/crypt:26575400545f554757120503 to crypt:045c410b57431a47521376525d075e0e4a01575b/crypt:26575400545f554757120503
2017.03.29 22:28:28 1: PERL WARNING: Constant subroutine main::SHIFT redefined at /usr/share/perl/5.22/constant.pm line 171, <$fh> line 252.
2017.03.29 22:28:28 3: TS.Mortsiefer: Defined with URL http://www.clever-tanken.de/tankstelle_details/15953 and interval 600
2017.03.29 22:28:28 3: TS.JaegerWiehl: Defined with URL http://www.clever-tanken.de/tankstelle_details/1685 and interval 600
2017.03.29 22:28:28 3: TS.MundorfWaldbroel: Defined with URL http://www.clever-tanken.de/tankstelle_details/46249 and interval 600
2017.03.29 22:28:28 2: ESPEasy espBridge: Opening bridge on port tcp/8383 (v1)
2017.03.29 22:28:28 3: espBridge: port 8383 opened
2017.03.29 22:28:29 3: Opening miniCUL device /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0
2017.03.29 22:28:29 3: Can't open /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0: No such file or directory
2017.03.29 22:28:29 1: HMCCU: Initialized version 3.9.010. Updating devices from 192.168.1.4
2017.03.29 22:28:29 1: Including ./log/fhem.save
2017.03.29 22:28:29 3: WARNING: unsupported character in reading * (not A-Za-z/\d_\.-), notify the dummy module maintainer.
2017.03.29 22:28:29 3: WARNING: unsupported character in reading * (not A-Za-z/\d_\.-), notify the dummy module maintainer.
2017.03.29 22:28:29 3: FIRMATA: port 3030 opened
2017.03.29 22:28:29 3: FR: ssdp responder started
2017.03.29 22:28:29 3: FR: listener started
2017.03.29 22:28:29 3: Opening MyBroker device 192.168.1.5:1883
2017.03.29 22:28:29 3: MyBroker device opened
2017.03.29 22:28:29 3: PLEX: restoring token from reading
2017.03.29 22:28:29 3: PLEX: multicast server discovery started
2017.03.29 22:28:29 3: PLEX: broadcast server discovery started
2017.03.29 22:28:29 3: PLEX: multicast client discovery started
2017.03.29 22:28:29 3: PLEX: broadcast client discovery started
2017.03.29 22:28:29 3: PLEX: pht client discovery started
2017.03.29 22:28:29 3: PLEX: timeline listener started
2017.03.29 22:28:30 3: Wetterstation: refreshing token
2017.03.29 22:28:30 3: Wetterstation getDevices (devicelist)
2017.03.29 22:28:30 0: HMCCU: Start of RPC server after FHEM initialization in 12 seconds
2017.03.29 22:28:30 1: usb create starting
2017.03.29 22:28:31 1: usb create end
2017.03.29 22:28:31 3: Opening mqtt device 192.168.1.10:1883
2017.03.29 22:28:31 3: mqtt device opened
2017.03.29 22:28:31 3: netatmo_D70_ee_50_20_fb_8e: I/O device is Wetterstation
2017.03.29 22:28:31 3: Wetterstation: refreshing token
2017.03.29 22:28:31 3: Wetterstation getDevices (devicelist)
2017.03.29 22:28:31 3: Wetterstation getHomecoachs (homecoachlist)
2017.03.29 22:28:32 3: netatmo_M02_00_00_20_b7_9c: I/O device is Wetterstation
2017.03.29 22:28:32 3: netatmo_M06_00_00_02_49_48: I/O device is Wetterstation
2017.03.29 22:28:32 1: PERL WARNING: Use of uninitialized value $ipV4 in rindex at ./FHEM/99_myUtils.pm line 33.
2017.03.29 22:28:32 1: PERL WARNING: Use of uninitialized value $ipV4 in substr at ./FHEM/99_myUtils.pm line 33.
2017.03.29 22:28:32 0: Featurelevel: 5.8
2017.03.29 22:28:32 0: Server started with 152 defined entities (fhem.pl:13828/2017-03-28 perl:5.022001 os:linux user:fhem pid:1114)
2017.03.29 22:28:32 3: telnetForBlockingFn_1490819312: port 39501 opened
2017.03.29 22:28:32 3: ABFALL_UPDATE
2017.03.29 22:28:33 3: CALVIEW Abfuhrtermine - CALENDAR:Abfallkalender triggered, updating CALVIEW Abfuhrtermine ...
2017.03.29 22:28:33 3: ABFALL myAbfall - CALENDAR:Abfallkalender triggered, updating ABFALL myAbfall ...
2017.03.29 22:28:33 3: ABFALL_UPDATE
2017.03.29 22:28:36 2: 32_HauptschalterFunktion:     save config    set ESPEasy_Terrassensteuerung_Relais_2_Licht check: Wrote configuration to config    set ESPEasy_Terrassensteuerung_Relais_2_Licht check
2017.03.29 22:28:36 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_3_Markise: set ESPEasy_Terrassensteuerung_Relais_3_Markise status gpio 5
2017.03.29 22:28:36 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_4_Markise: set ESPEasy_Terrassensteuerung_Relais_4_Markise status gpio 4
2017.03.29 22:28:36 2: 32_HauptschalterFunktion:        save config: Wrote configuration to config
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_3_Markise: set ESPEasy_Terrassensteuerung_Relais_3_Markise gpio 5 on
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_4_Markise: set ESPEasy_Terrassensteuerung_Relais_4_Markise gpio 4 on
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_2_Licht: set ESPEasy_Terrassensteuerung_Relais_2_Licht gpio 16 on
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_2_Licht: Device disabled
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_2_Licht: Readings [state] wiped out
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_3_Markise: Device disabled
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_3_Markise: Readings [presence,GPIO5,GPIO5_mode,state] wiped out
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_4_Markise: Device disabled
2017.03.29 22:28:38 3: ESPEasy ESPEasy_Terrassensteuerung_Relais_4_Markise: Readings [state] wiped out
2017.03.29 22:28:38 2: 32_HauptschalterFunktion:     save config: Wrote configuration to config
2017.03.29 22:28:41 3: UWZ Unwetterzentrale: Run.964 Done fetching data
2017.03.29 22:28:42 2: HMCCURPC: Starting thread for data processing
2017.03.29 22:28:43 2: HMCCURPC: Started thread for data processing. TID=1
2017.03.29 22:28:43 2: CCURPC: Thread DATA processing RPC events. TID=1
2017.03.29 22:28:43 2: HMCCURPC: RPC server thread started for interface BidCos-RF with TID=2
2017.03.29 22:28:43 2: CCURPC: Initializing RPC server CB2001 for interface BidCos-RF
2017.03.29 22:28:43 2: HMCCURPC: Callback server CB2001 created. Listening on port 7411
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for events for server CB2001
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for new devices for server CB2001
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for deleted devices for server CB2001
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for modified devices for server CB2001
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for replaced devices for server CB2001
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for readded devices for server CB2001
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for list devices for server CB2001
2017.03.29 22:28:43 2: CCURPC: CB2001 accepting connections. TID=2
2017.03.29 22:28:43 2: HMCCURPC: RPC server thread started for interface HmIP-RF with TID=3
2017.03.29 22:28:43 2: CCURPC: Initializing RPC server CB2010 for interface HmIP-RF
2017.03.29 22:28:43 2: HMCCURPC: Callback server CB2010 created. Listening on port 7420
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for events for server CB2010
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for new devices for server CB2010
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for deleted devices for server CB2010
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for modified devices for server CB2010
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for replaced devices for server CB2010
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for readded devices for server CB2010
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for list devices for server CB2010
2017.03.29 22:28:43 2: CCURPC: CB2010 accepting connections. TID=3
2017.03.29 22:28:43 2: HMCCURPC: RPC server thread started for interface VirtualDevices with TID=4
2017.03.29 22:28:43 2: CCURPC: Initializing RPC server CB9292 for interface VirtualDevices
2017.03.29 22:28:43 2: HMCCURPC: Callback server CB9292 created. Listening on port 14702
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for events for server CB9292
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for new devices for server CB9292
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for deleted devices for server CB9292
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for modified devices for server CB9292
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for replaced devices for server CB9292
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for readded devices for server CB9292
2017.03.29 22:28:43 2: HMCCURPC: Adding callback for list devices for server CB9292
2017.03.29 22:28:43 2: CCURPC: CB9292 accepting connections. TID=4
2017.03.29 22:28:44 1: HMCCURPC: RPC server(s) starting
2017.03.29 22:28:44 1: HMCCURPC: Received SL event. RPC server DATA enters server loop
2017.03.29 22:28:44 1: HMCCURPC: Received SL event. RPC server CB2001 enters server loop
2017.03.29 22:28:44 1: HMCCURPC: Received SL event. RPC server CB2010 enters server loop
2017.03.29 22:28:44 1: HMCCURPC: Received SL event. RPC server CB9292 enters server loop
2017.03.29 22:28:44 1: HMCCURPC: All threads working
2017.03.29 22:28:44 1: HMCCURPC: Registering callback http://192.168.1.5:7411/fh2001 with ID CB2001 at http://192.168.1.4:2001/
2017.03.29 22:28:44 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2017.03.29 22:28:44 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7411/fh2001 registered
2017.03.29 22:28:44 1: HMCCURPC: Registering callback http://192.168.1.5:7420/fh2010 with ID CB2010 at http://192.168.1.4:2010/
2017.03.29 22:28:44 1: HMCCURPC: RPC callback with URL http://192.168.1.5:7420/fh2010 registered
2017.03.29 22:28:44 1: HMCCURPC: Registering callback http://192.168.1.5:14702/fh9292 with ID CB9292 at http://192.168.1.4:9292/groups
2017.03.29 22:28:44 2: CCURPC: CB2001 NewDevice received 64 device specifications
2017.03.29 22:28:44 1: CCURPC: CB2010 ListDevices. Sending init to HMCCU
2017.03.29 22:28:44 1: CCURPC: CB9292 ListDevices. Sending init to HMCCU
2017.03.29 22:28:54 1: HMCCURPC: RPC callback with URL http://192.168.1.5:14702/fh9292 registered
2017.03.29 22:28:54 1: HMCCURPC: Received IN event. RPC server CB2001 running.
2017.03.29 22:28:54 1: HMCCURPC: Received IN event. RPC server CB2010 running.
2017.03.29 22:28:54 1: HMCCURPC: Received IN event. RPC server CB9292 running.
2017.03.29 22:28:54 1: HMCCURPC: All RPC servers running
2017.03.29 22:28:54 3: HMCCU: Device NEQ0948654 has no readable datapoints
2017.03.29 22:28:54 2: HMCCU: Addr=NEQ1143221 Name=03_DimmerDeckenleuchten_DEV1
2017.03.29 22:28:54 2: HMCCU: Script response = 
0

2017.03.29 22:28:54 2: HMCCU: Script = 

string chnid;
string sDPId;
string sDevName;
string sDevList = "03_DimmerDeckenleuchten_DEV1";
integer c = 0;
foreach (sDevName, sDevList.Split(",")) {
  object odev = dom.GetObject (sDevName);
  if (odev) {
    foreach (chnid, odev.Channels()) {
	   object ochn = dom.GetObject(chnid);
      if (ochn) {
		  foreach(sDPId, ochn.DPs()) {
		    object oDP = dom.GetObject(sDPId);
          if (oDP) {
            if (OPERATION_READ & oDP.Operations()) {
              WriteLine (ochn.Name() # "=" # oDP.Name() # "=" # oDP.Value());
              c = c+1;
            }
          }
        }
      }
    }
  }
}
WriteLine (c);
		
2017.03.29 22:28:54 3: HMCCU: Device NEQ1143221 has no readable datapoints
2017.03.29 22:28:54 3: HMCCU: Device NEQ1770358 has no readable datapoints
2017.03.29 22:28:54 2: HMCCURPC: Updated devices. Success=1 Failed=3
2017.03.29 22:29:28 2: FR: unhandled request: GET /ecp_SCPD.xml HTTP/1.1
Host: 192.168.1.5:37421
User-Agent: FSL DLNADOC/1.50 UPnP Stack/1.0


2017.03.29 22:30:00 3: Wetterstation: poll (ACCOUNT)
2017.03.29 22:30:02 3: netatmo_D70_ee_50_20_fb_8e: poll (DEVICE)
2017.03.29 22:30:02 3: netatmo_D70_ee_50_20_fb_8e: requestDeviceReadings (Temperature,CO2,Humidity,Noise,Pressure)
2017.03.29 22:30:02 3: netatmo_M02_00_00_20_b7_9c: poll (MODULE)
2017.03.29 22:30:02 3: netatmo_M02_00_00_20_b7_9c: requestDeviceReadings (Temperature,Humidity)
2017.03.29 22:30:02 3: netatmo_M06_00_00_02_49_48: poll (MODULE)
2017.03.29 22:30:02 3: netatmo_M06_00_00_02_49_48: requestDeviceReadings (WindStrength,WindAngle,GustStrength,GustAngle)
2017.03.29 22:30:03 2: netatmo_D70_ee_50_20_fb_8e: next dynamic update at 2017-03-29 22:32:38
fhem@SERVERFHEM:~$

supernova1963 · 30 März 2017, 07:49:27

Guten morgen, ich schon wieder.
Diesesmal mit einer positiveren Nachricht:

den Namen in der WebUI geändert (wegen Unterstriche bzw. zu lang oder nicht mit Zahl beginnend: Deckeneinbauleuchten03)
das Device in FHEM gelöscht und neu angelegt.
die Defaults noch nicht geladen.
Jetzt funktionierte "get Deckeneinbauleuchten03 deviceinfo" und "get Deckeneinbauleuchten03 datapoint" enthält eine Auswahl von datapoints.
!!! Endlich die Fehlermeldung ist weg !!!
da die get Deckeneinbauleuchten datatpoint xxx zwar keinen Fehler verursachten aber auch kein Ergebnis brachten, habe ich das dazu gehörende CHN Device (ohne Namensänderung!) geladen.
die Defaults mit "set Deckeneinbauleuchten03 defaults" geladen
die angebotenen Schalter für an / aus und Slider hoch / runter ausprobiert
!!! Es funktioniert !!!
die Defaults im CHN-Device mit "set 03_DimmerDeckenleuchten_DEV1CHN01 defaults" geladen
!!! Es funktioniert auch direkt am CHN-Device !!!
da DEV-Device Deckeneinbauleuchten03 gelöscht:
!!! Es funktioniert immer noch alles am CHN-Device !!!

Was habe ich gelernt: Das Dimmer funktioniert über das CHN-Device!

Vielen lieben Dank an zap für deine Unterstützung. Nur weil du nicht aufgegeben hast, habe ich weiter gemacht. Das Modul ist, insbesondere mit dem viel schnelleren HMCCURPC, Spitzenklasse.

Gernot

P.S.: Als nächstes werde ich den Namen in der WebUI wieder zurück ändern. So funktioniert es:

Code Auswählen


defmod HM_03_DimmerDeckenleuchten_DEV1CHN01 HMCCUCHN NEQ1143221:1
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 IODev d_ccu
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 ccureadingfilter (^LEVEL$|DIRECTION)
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 ccuscaleval LEVEL:0:1:0:100
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 cmdIcon on:general_an off:general_aus
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 controldatapoint LEVEL
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 hmstatevals ERROR_REDUCED!1:error_reduced;;ERROR_OVERHEAT!1:error_overheat;;ERROR_OVERLOAD!1:error_overload
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 room Homematic
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 statedatapoint LEVEL
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 statevals on:100,off:0
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 stripnumber 1
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 substexcl control
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 substitute ERROR_OVERHEAT,ERROR_OVERLOAD,ERROR_REDUCED!(0|false):no,(1|true):yes;;LEVEL!#0-0:off,#1-100:on;;DIRECTION!0:none,1:up,2:down,3:undefined
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 webCmd control:on:off
attr HM_03_DimmerDeckenleuchten_DEV1CHN01 widgetOverride control:slider,0,10,100

setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 off
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:38:19 1.DIRECTION none
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:27:11 1.ERROR_OVERHEAT 0
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:27:11 1.ERROR_OVERLOAD 0
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:27:11 1.ERROR_REDUCED 0
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:38:19 1.LEVEL off
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:27:11 1.LEVEL_REAL 0.200000
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:27:11 1.WORKING 0
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:38:19 control 0
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:38:19 hmstate off
setstate HM_03_DimmerDeckenleuchten_DEV1CHN01 2017-03-30 07:38:19 state off

supernova1963 · 30 März 2017, 14:41:55

Hallo nochmal,

Zunächst: Es funktioniert alles.

Nur zur Information:

Man kann in der Firewall der CCU2 den Eintrag Remote HomeMatic-Script API auf eingeschränkt stehen lassen, wenn man zumindest die IP des FHEM Servers in der Liste IP-Adressen für den eingeschränkten Zugriff eingibt
Änderungen über die WebUI sind tricky, unabhängig, ob der rpcserver an oder aus ist! Es funktionierte, wenn ich alle hmccu devices gelöscht und gesichert habe, den FHEM Server neu gestartet und erst danach Änderungen in der WebUI vorgenommen habe, die ich danach sicherheitshalber auch neu gestartet habe bevor ich die hmccu devices in FHEM neu definierte.
Die Raumzuordnung bei dem "get d_ccu devicelist create ... " Befehl hat bei mir nicht funktioniert
Schön wäre, wenn unter dem hmccu device alle zugehörigen/abhängigen devices gelistet würden
Mir hätte es wahrscheinlich sehr geholfen, wenn mit dem Befehl "set d_ccu rpcserver off" wirklich alle Prozesse und Threads usw. beendet und bei dem starten neu initialisiert würden
Idealerweise stände der Status des d_ccu Devices bei dem Start oder Neustart nicht auf OK, wenn keine Datapoints erreichbar oder Scripts ausführbar sind. Er springt erst auf Error, wenn ein entsprechender Befehl "vor die Pumpe läuft"!

Unsicher bzw. offen verbleibt bei mir:

Kann es sein, dass Device oder Kanalnamen, die mit Zahl(en) beginnen, kritisch sind?
Kann es sein, dass verschiedene Änderungen and CCU2 über die WebUI in der Remote HomeMatic-Script API erst nach einem Neustart wirksam werden?
~~Wird man irgendwann einmal auch den bei den CCU2 Kanälen den Übertragungsmodus: gesichert verwenden können?~~

Vielleicht hilft's einem bei der Fehlersuche,

Gernot

zap · 30 März 2017, 19:10:10

Danke für die Hinweise. Ich schaue mir die einzelnen Punkte an.

Was meinst Du mit "Verwendung gesicherter Übertragungsmodus"? Wenn Du für ein Gerät in der CCU das AES Flag setzt (sofern es eins gibt), dann wird das auch verwendet. Das hat mit HMCCU nichts zu tun.

supernova1963 · 31 März 2017, 11:45:36

Sorry, hab's gerade probiert. AES Verschlüsselung funktioniert!
Ich streiche es durch.

Gernot