Fehlermeldung bei gleichzeitigem Einsatz Cube und CUL

[netwalk]

Hallo,

ich habe meine MAX Komponenten mit dem Cube gepaired und nutze den CUL nur als Lauscher. Im Logfile erhalte ich immer wieder folgende Fehlermeldungen:

Code Auswählen Erweitern

2016.02.26 09:41:59 1: PERL WARNING: Use of uninitialized value in pattern match (m//) at ./FHEM/10_MAX.pm line 839.
2016.02.26 09:41:59 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 841.
2016.02.26 09:41:59 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 843.
2016.02.26 09:41:59 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 845.
2016.02.26 09:41:59 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 847.
2016.02.26 09:41:59 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/10_MAX.pm line 850.
2016.02.26 09:41:59 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 09:57:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:02:18 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:14:13 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:14:57 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:20:38 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:31:25 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:33:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:39:13 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:41:59 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 10:57:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 11:02:18 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.26 11:20:38 2: MAX_Parse: Don't know how to interpret Ack payload for

Nach Recherchen im Forum vermute ich, das diese Meldungen von den Nachrichten des Cubes kommen. Ich habe einen Hinweis gefunden, wonach man den Cube als dummy-Device definieren solle. Das habe ich auf verschiedene Arten versucht, jedoch verschwinden diese Fehler im Log leider nicht.

Kann mir da vielleicht jemand auf die Sprünge helfen?

[ggaljoen]

Ich benutze das gleiche Setup (Cube und CUL), die beide die gleiche Radio-Adresse teilen .
Es gibt nur von Zeit zu Zeit einen ack Fehler.
Nicht vollständig ideal, aber es funktioniert ...

[netwalk]

Im 10_MAX.pm steht ab Zeile 837:

Code Auswählen Erweitern

    #with unknown meaning plus the data of a State broadcast from the same device
    #For HeatingThermostats, it does not contain the last three "until" bytes (or measured temperature)
    if($shash->{type} =~ /HeatingThermostat.*/ ) {
      return MAX_Parse($hash, "MAX,$isToMe,ThermostatState,$addr,". substr($args[0],2));
    } elsif($shash->{type} eq "WallMountedThermostat") {
      return MAX_Parse($hash, "MAX,$isToMe,WallThermostatState,$addr,". substr($args[0],2));
    } elsif($shash->{type} eq "ShutterContact") {
      return MAX_Parse($hash, "MAX,$isToMe,ShutterContactState,$addr,". substr($args[0],2));
    } elsif($shash->{type} eq "PushButton") {
      return MAX_Parse($hash, "MAX,$isToMe,PushButtonState,$addr,". substr($args[0],2));
    } elsif($shash->{type} eq "Cube") {
      ; #Payload is always "00"
    } else {
      Log3 $hash, 2, "MAX_Parse: Don't know how to interpret Ack payload for $shash->{type}";


Wie ich das verstehe, wird dort der payload für die verschiedenen Typen kalkuliert. Bei type "Cube" steht "00", ich verstehe jedoch nicht, wie ich den Cube korrekt definieren muss, damit ich diese nervigen Fehlermeldungen los werde.

Kostprobe:

Code Auswählen Erweitern

2016.02.28 13:42:01 1: PERL WARNING: Use of uninitialized value in pattern match (m//) at ./FHEM/10_MAX.pm line 839.
2016.02.28 13:42:01 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 841.
2016.02.28 13:42:01 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 843.
2016.02.28 13:42:01 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 845.
2016.02.28 13:42:01 1: PERL WARNING: Use of uninitialized value in string eq at ./FHEM/10_MAX.pm line 847.
2016.02.28 13:42:01 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/10_MAX.pm line 850.
2016.02.28 13:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 13:54:14 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 13:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 14:22:12 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 14:24:09 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 14:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 14:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 14:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 14:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 15:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 15:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 15:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 15:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 15:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 15:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 16:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 16:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 16:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 16:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 16:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:41:41 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:41:55 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:43:22 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:46:58 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:47:10 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:47:28 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:47:47 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 17:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:50:08 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:51:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:52:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:57:08 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:57:27 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:57:52 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 18:58:23 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:01:42 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:03:40 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:03:45 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:03:57 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:04:18 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:04:26 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:18:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 19:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 20:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 20:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 20:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 20:42:01 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 20:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 21:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 21:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 21:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 21:37:51 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 21:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 21:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:41:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:42:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:43:26 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:44:08 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:45:54 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 22:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:10:34 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:11:12 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:11:26 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:11:44 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:13:04 3: DUOFERN no ACK, request Status
2016.02.28 23:13:05 3: DUOFERN no ACK, request Status
2016.02.28 23:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.28 23:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 00:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 00:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 00:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 00:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 01:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 01:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 01:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 01:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 01:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 01:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 02:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 02:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 02:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 02:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 02:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 03:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 03:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 03:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 03:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 03:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 03:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 04:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 04:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 04:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 04:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 04:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 04:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 05:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 05:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 05:33:04 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 05:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 05:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 05:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:27:14 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:28:33 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:31:33 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:31:38 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:31:46 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 06:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:47:40 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 07:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:01:08 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 08:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 09:20:37 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 09:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 09:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 09:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 09:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 10:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 10:20:36 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 10:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 10:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 10:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 10:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 11:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 11:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 11:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 11:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 11:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 12:02:19 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 12:20:36 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 12:33:05 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 12:37:50 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 12:42:02 2: MAX_Parse: Don't know how to interpret Ack payload for
2016.02.29 12:57:48 2: MAX_Parse: Don't know how to interpret Ack payload for

Kann mir da jemand helfen?

[ggaljoen]

So überprüft, mein FHEM System nicht stört an den Cube.
Es wird durch das Deaktivieren der automatischen Erstellen ignoriert 'autocreate': Global / Attributes

Delete Cube reference in fhem.cfg & fhem.save.

[netwalk]

Zur Zeit habe ich den Cube nur durch das MAXLAN Modul mit entsprechender IP-Adresse definiert, kein weiterer Eintrag.
Autocreate ist auch standardmäßig deaktiviert, trotzdem kommen ständig diese Fehlermeldungen.

Hat keiner sonst noch das Problem?

[vobo]

gibt es hier was neues zu ?
Ich bekommen ebenfalls diese Fehlermeldung beim parallelen Einsatz von Cube und CUL.

Viele Grüße
Volker