00_MYSENSORS.pm Fehler bei der Auswertung von Signaldaten?

Begonnen von eldrik, 08 Januar 2016, 09:50:45

Vorheriges Thema - Nächstes Thema
Drucken
Nach unten Seiten1
Benutzer-Aktionen

eldrik

08 Januar 2016, 09:50:45 Letzte Bearbeitung: 09 Januar 2016, 10:22:38 von eldrik
Hi,

ich benutze jetzt seit einigen Wochen mysensors als Erweiterung für meine Haussteuerung.

Vor einigen Tagen habe ich ein weiteres Serial Gateway, in die Umgebung hinzugefügt, um die zukünftigen Sensoren des Obergeschosses auf dieses binden zu können.

Nun tauchen im Fhem Log erwartungsgemäß die ignore Messages auf, da keine der bisherigen Sensoren das Gateway benutz bzw. bekannt ist.

Über die ignore Messages ist mir aufgefallen, dass hier in einigen Fällen scheinbar nicht korrekte Werte wiedergeben werden.

Hier ein Logauszug:
Code Auswählen
2016.01.08 09:11:38.165 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 1 for V_TRIPPED
2016.01.08 09:11:38.807 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:11:40.258 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:11:54.047 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:12:37.129 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 2 for V_HUM
2016.01.08 09:12:37.205 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:12:37.443 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 2 for V_HUM
2016.01.08 09:12:37.957 3: MYSENSORS: ignoring set-msg from unknown radioId 109, childId 1 for V_TRIPPED
2016.01.08 09:12:40.151 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 2 for V_PERCENTAGE
2016.01.08 09:12:40.263 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:12:54.047 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:13:37.214 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:13:37.955 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 1 for V_TRIPPED
2016.01.08 09:13:38.598 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:13:40.272 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:13:54.050 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:14:37.222 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:14:37.972 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 1 for V_TRIPPED
2016.01.08 09:14:38.572 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:14:40.277 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:14:54.054 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:15:24.913 3: CUL_HM set virtual_temp_Sensor_Buero virtTemp 18.5
2016.01.08 09:15:37.230 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:15:37.973 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 5 for V_TRIPPED
2016.01.08 09:15:38.578 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:15:40.291 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:15:40.302 3: MYSENSORS: ignoring set-msg from unknown radioId 73, childId 1 for V_TRIPPED
2016.01.08 09:15:54.063 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED


In meinem Sketch der Sensoren übermittel ich die Luftfeuchte ClientID 2 alle 5 Minuten, Bewegungsmelderänderungen ClientID 1 sofort und den aktuellen Bewegungsmelderstatus alle 60 Sekunden.

Es fällt auf, dass für die Radio ID 105 um 9:11:40 korrekt childID 1 V_TRIPPED gemeldet wird,

Code Auswählen
2016.01.08 09:11:40.258 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED

60 Sekunden später wird jedoch childId 2 und V_PERCENTAGE gemeldet.

Code Auswählen
2016.01.08 09:12:40.151 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 2 for V_PERCENTAGE

Dass sich eine gleiche radioId in meinem Umfeld befindet würde ich noch für möglich halten, dass diese aber zum selben Zeitpunkt sendet wie mein Sensor, halte ich dann doch für eher unwahrscheinlich.

Weitere Beispiele:
Logauszug:
Code Auswählen
2016.01.08 09:27:37.319 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:27:38.401 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 2 for V_HUM
2016.01.08 09:27:38.676 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:27:38.686 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:27:40.270 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 2 for V_HUM
2016.01.08 09:27:40.381 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:27:41.971 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:27:45.869 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:27:47.339 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:27:49.568 3: MYSENSORS: ignoring internal-msg from unknown radioId 100, childId 1 for I_GET_NONCE
2016.01.08 09:27:54.110 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:28:16.018 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:28:18.007 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:28:30.049 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:28:30.408 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:28:31.476 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:28:32.310 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:28:34.788 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 1 for V_TRIPPED
2016.01.08 09:28:37.330 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:28:38.115 3: MYSENSORS: ignoring set-msg from unknown radioId 111, childId 1 for
2016.01.08 09:28:38.678 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:28:38.984 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:28:40.430 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:28:54.153 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:29:37.334 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:29:38.111 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 5 for V_TRIPPED
2016.01.08 09:29:38.689 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:29:38.738 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:29:44.683 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:29:54.161 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:30:07.593 3: CUL_HM set virtual_temp_Sensor_Bad_klein virtTemp 19
2016.01.08 09:30:37.342 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:30:38.116 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 18 for V_TRIPPED
2016.01.08 09:30:38.701 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:30:40.438 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for
2016.01.08 09:30:54.169 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:31:37.347 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:31:38.702 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:31:40.418 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:31:54.138 3: MYSENSORS: ignoring set-msg from unknown radioId 200, childId 1 for V_TRIPPED
2016.01.08 09:32:37.277 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 2 for V_HUM
2016.01.08 09:32:37.355 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:32:38.466 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 2 for V_HUM
2016.01.08 09:32:38.740 3: MYSENSORS: ignoring set-msg from unknown radioId 100, childId 1 for V_TRIPPED
2016.01.08 09:32:40.422 3: MYSENSORS: ignoring set-msg from unknown radioId 105, childId 1 for V_TRIPPED
2016.01.08 09:32:40.432 3: MYSENSORS: ignoring internal-msg from unknown radioId 105, childId 1 for I_GET_NONCE


Radio ID 101 unterschiedliche childId und eventuelle Änderung der Radio ID
Code Auswählen
2016.01.08 09:28:34.788 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 1 for V_TRIPPED
Code Auswählen
2016.01.08 09:28:38.115 3: MYSENSORS: ignoring set-msg from unknown radioId 111, childId 1 for
Code Auswählen
2016.01.08 09:29:38.111 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 5 for V_TRIPPED
Code Auswählen
2016.01.08 09:30:38.116 3: MYSENSORS: ignoring set-msg from unknown radioId 101, childId 18 for V_TRIPPED


Radio ID 107 unterschiedliche childId
Code Auswählen

2016.01.08 09:21:37.271 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:22:37.282 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:22:46.556 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 3 for V_TRIPPED
2016.01.08 09:23:37.290 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:24:37.298 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED
2016.01.08 09:25:37.305 3: MYSENSORS: ignoring set-msg from unknown radioId 107, childId 1 for V_TRIPPED

Alles nur Zufall?

Kann mein Sketch zu solch einem Verhalten beitragen?

Über Unterstützung würde ich mich freuen.

Greetz
Eldrik
Drucken
Nach oben Seiten1
Benutzer-Aktionen