MAXLAN aufgehangen...

Begonnen von tucka, 04 Januar 2013, 18:13:51

Vorheriges Thema - Nächstes Thema

ChrisW

Hallo,
heute morgen war mein FHEM auch abgestürzt letzer Log eintrag:
2013.01.22 02:39:37 3: ml device opened
2013.01.22 02:42:58 3: Opening ml device 192.168.2.22:62910
2013.01.22 02:42:58 3: ml device opened
2013.01.22 02:46:20 3: Opening ml device 192.168.2.22:62910
2013.01.22 02:46:20 3: ml device opened
2013.01.22 02:49:41 3: Opening ml device 192.168.2.22:62910
2013.01.22 02:49:41 3: ml device opened
2013.01.22 02:53:03 3: Opening ml device 192.168.2.22:62910
2013.01.22 02:53:03 3: ml device opened
2013.01.22 02:53:09 1: MAXLAN_ReadSingleResponse: timeout while reading from socket, disconnecting
2013.01.22 02:53:09 1: MAXLAN_ExpectAnswer: Error while waiting for answer H:
Raspberry PI3 mit allem möglichen.

stobor

Trotz des Updates von Matthias?
Intel NUC (Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-73-generic x86_64))  mit CUL V3.2 (Firmware 1.57 CUL868) für FS20 und CUL V3.4 (Firmware 1.57 CUL868) für HM + Arduino Mega
FHEM Revision: 27642
FS20-Schalter und Dimmer
HM Fensterkontakte, Heizungsthermostate, Temperatursensoren

ChrisW

Da sist um 2:49 Nachts passiert. Letztes Update habe ich gestern gegen 11 Uhr gemacht.
Raspberry PI3 mit allem möglichen.

stobor

Warum wird eigentlich da sLog immer mit solchen Dingen vollgeknallt:

2013.01.22 19:52:15 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:15 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:16 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:17 2: Got message for undefined device, and failed to guess type from msg 'WallThermostatConfig' - ignoring
2013.01.22 19:52:17 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 19:52:17 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 19:52:17 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
Intel NUC (Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-73-generic x86_64))  mit CUL V3.2 (Firmware 1.57 CUL868) für FS20 und CUL V3.4 (Firmware 1.57 CUL868) für HM + Arduino Mega
FHEM Revision: 27642
FS20-Schalter und Dimmer
HM Fensterkontakte, Heizungsthermostate, Temperatursensoren

stobor

Könnte man nicht einfach unbekannte Devices ignorieren, um Systemlast zu sparen?
Ich habe das Gefühl, immer, wen MAX! in FHEM genutzt wird, reagiert FHEM deutlich langsamer.
Man sieht ja auch im Lag, dass das System mehrere sec. mit MAX! beschäftigt ist:
2013.01.22 20:11:08 3: Opening ml device 192.168.1.21:62910
2013.01.22 20:11:08 3: ml device opened
2013.01.22 20:11:12 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:12 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:12 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:12 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:13 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:14 2: Got message for undefined device, and failed to guess type from msg 'WallThermostatConfig' - ignoring
2013.01.22 20:11:14 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:14 2: Got message for undefined device, and failed to guess type from msg 'HeatingThermostatConfig' - ignoring
2013.01.22 20:11:14 2: Got message for undefined device, and failed to guess type from msg 'Error' - ignoring
2013.01.22 20:11:14 2: Got List response for undefined device with addr 008ab9
2013.01.22 20:11:14 2: Got List response for undefined device with addr 010358
2013.01.22 20:11:14 2: Got List response for undefined device with addr 007649
2013.01.22 20:11:14 2: Got List response for undefined device with addr 038f14
2013.01.22 20:11:14 2: Got List response for undefined device with addr 011246
2013.01.22 20:11:14 2: Got List response for undefined device with addr 009668
2013.01.22 20:11:14 2: Got List response for undefined device with addr 010e58
2013.01.22 20:11:14 2: Got List response for undefined device with addr 016ee4
2013.01.22 20:11:14 2: Got List response for undefined device with addr 038f2b


Ich habe jetzt nur noch die Cube und 8 Fensterkontakte definiert. Meine Thermostate sind nicht mehr in der fhem.cfg definiert:

define ml MAXLAN 192.168.1.21 60 ondemand
define MAX_00bd68 MAX Cube 00bd68
attr MAX_00bd68 alias Cube
attr MAX_00bd68 fm_name Cube
attr MAX_00bd68 room MAX
#define MAX_008ab9 MAX HeatingThermostat 008ab9
#attr MAX_008ab9 room MAX
define MAX_00701c MAX ShutterContact 00701c
attr MAX_00701c alias BadezimmerFenster
attr MAX_00701c fm_name BadezimmerFenster
attr MAX_00701c room MAX
...


Kommentiere ich generell alles MAX!-bezogene aus, läuft FHEM deutlich flüssiger.
Intel NUC (Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-73-generic x86_64))  mit CUL V3.2 (Firmware 1.57 CUL868) für FS20 und CUL V3.4 (Firmware 1.57 CUL868) für HM + Arduino Mega
FHEM Revision: 27642
FS20-Schalter und Dimmer
HM Fensterkontakte, Heizungsthermostate, Temperatursensoren

Matthias Gehre

Wenn dir das hilft, dann kommentiere am besten MAX aus.
Ansonsten freue ich mich natürlich auch über Patches.

stobor

Na ja, MAX wieder komplett rauszunehmen find ich nicht so toll. Ich möchte es ja schon gern nutzen. Liegt es vielleicht auch daran, dass fhem 1x pro Minute pollt?
Konnte man nicht auch MAX direkt per Funk abfragen (also ohne Cube)? Bzw. das fhem dem MAX Funkverkehr lauscht? Oder wurde/wird das wieder deaktiviert? Weiß jemand, wie das dann genau zu konfigurieren ist? Muss der CUL dafür noch verändert werden?
Intel NUC (Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-73-generic x86_64))  mit CUL V3.2 (Firmware 1.57 CUL868) für FS20 und CUL V3.4 (Firmware 1.57 CUL868) für HM + Arduino Mega
FHEM Revision: 27642
FS20-Schalter und Dimmer
HM Fensterkontakte, Heizungsthermostate, Temperatursensoren

Matthias Gehre

Klar, per CUL gehts auch ohne Cube. Steht z.B. im Wiki. Das Modul dafür ist CUL_MAX.

ChrisW

und heute morgen wieder im bad das Thermostat 15c Manuell ..
Denke es passietr hier durch:
2013.02.05 19:34:42 3: ml device opened
2013.02.05 19:34:45 1: MAXLAN_ReadSingleResponse: timeout while reading from socket, disconnecting
2013.02.05 19:34:45 1: MAXLAN_ExpectAnswer: Error while waiting for answer H:
2013.02.05 19:34:47 3: Opening ml device 192.168.2.22:62910
2013.02.05 19:34:47 3: ml device opened


2013.02.06 00:26:52 1: MAXLAN_ReadSingleResponse: timeout while reading from socket, disconnecting
2013.02.06 00:26:52 1: MAXLAN_ExpectAnswer: Error while waiting for answer H:
2013.02.06 00:26:54 3: Opening ml device 192.168.2.22:62910
2013.02.06 00:26:54 3: ml device opened
2013.02.06 00:28:35 3: Opening ml device 192.168.2.22:62910
2013.02.06 00:28:35 3: ml device opened


Er baut aber Zukünftig wie gewollt neue Verbindungen auf.Aber beim 1. mal um 19:34 schaut dann das Log was von Thermostat kommt schon komisch aus das ist NIE so ..

2013-02-05_17:37:27 MAX_Bad desiredTemperature: 24.0
2013-02-05_17:37:27 MAX_Bad valveposition: 100
2013-02-05_17:37:27 MAX_Bad 24.0 °C
2013-02-05_18:57:58 MAX_Bad mode: manual
2013-02-05_18:57:58 MAX_Bad desiredTemperature: 15.0
2013-02-05_18:57:58 MAX_Bad 15.0 °C
2013-02-05_19:01:27 MAX_Bad valveposition: 0
2013-02-05_19:01:27 MAX_Bad temperature: 24.5
2013-02-05_21:57:59 MAX_Bad valveposition: 9
2013-02-05_21:57:59 MAX_Bad temperature: 20.6
2013-02-05_22:33:30 MAX_Bad valveposition: 0
2013-02-05_22:33:30 MAX_Bad temperature: 21.8
2013-02-06_00:01:25 MAX_Bad valveposition: 9
2013-02-06_00:01:25 MAX_Bad temperature: 20.6
2013-02-06_00:37:04 MAX_Bad valveposition: 0
2013-02-06_00:37:04 MAX_Bad temperature: 21.5
2013-02-06_01:49:46 MAX_Bad valveposition: 9
2013-02-06_01:49:46 MAX_Bad temperature: 20.4
2013-02-06_02:33:44 MAX_Bad valveposition: 0
2013-02-06_02:33:44 MAX_Bad temperature: 21.5
2013-02-06_03:39:40 MAX_Bad valveposition: 9
2013-02-06_03:39:40 MAX_Bad temperature: 20.5
2013-02-06_04:37:10 MAX_Bad valveposition: 1
2013-02-06_04:37:10 MAX_Bad temperature: 21.3
2013-02-06_04:49:00 MAX_Bad valveposition: 0
2013-02-06_04:49:00 MAX_Bad temperature: 21.4
2013-02-06_05:39:44 MAX_Bad valveposition: 8
2013-02-06_05:39:44 MAX_Bad temperature: 20.4
2013-02-06_06:25:29 MAX_Bad valveposition: 0
2013-02-06_06:25:29 MAX_Bad temperature: 21.7
2013-02-06_06:30:33 MAX_Bad mode: auto
2013-02-06_06:30:33 MAX_Bad desiredTemperature: 30.0
2013-02-06_06:30:33 MAX_Bad valveposition: 100
2013-02-06_06:30:33 MAX_Bad temperature: 21.3
2013-02-06_06:30:33 MAX_Bad 30.0 °C
2013-02-06_07:25:12 MAX_Bad desiredTemperature: 14.0
2013-02-06_07:25:12 MAX_Bad valveposition: 0
2013-02-06_07:25:12 MAX_Bad temperature: 22.4
2013-02-06_07:25:12 MAX_Bad 14.0 °C
2013-02-06_07:56:31 MAX_Bad mode: manual
2013-02-06_07:58:35 MAX_Bad temperature: 21.4


Das komisch 7:56 habe ich ECO gesetzt !!! Aber er schreibt manual rein ?? Früher stand doch da immer ECO seit dem 30.1. aber nicht mehr ?? Verstehe da snicht es liegt nun 2-3 Tage alles rund jetz wieder so was wer soll das noch verstehen.
Raspberry PI3 mit allem möglichen.

Matthias Gehre

Da stand noch nie "eco", weil "eco" kein Modus, sondern eine Temperatur ist.

ChrisW


2013-01-15_19:40:29 MAX_Bad desiredTemperature eco
2013-01-15_19:40:31 MAX_Bad 17.0 °C

So war es damals ;D
Raspberry PI3 mit allem möglichen.

Matthias Gehre

  2013-01-15_19:40:29 MAX_Bad desiredTemperature eco
ist kein Readings, sondern das Echo des Set-Befehls
  set MAX_Bad desiredTemperature eco

In "mode" stand wirklich noch nie "eco".