Homematic Reichweite erweitern

m0wlheld · July 6, 2018, 12:57pm

Ja, aber -

zwischen dem Max!Cube und den Geräten sind ca. 3m Luft, Holz und etwas Steinwolle. Ich glaube die Sendeleistung ist nicht das Problem. Irgendwas stimmt grundsätzlich nicht in meinem Setup.

Vielleicht ziehe ich doch noch LAN in den Dachboden …

job · July 7, 2018, 12:14pm

Mach das! Ich bin so glücklich, dass ich in jedem Raum mindestens 2 Gigabit dosen habe, und ärgere mich total, dass ich keinen Strom in den Jalousiekästen habe.

Mein Pi steht in der 2. Etage in einer Ecke und ich komme problemlos in den Keller. Ich habe allerdings die 26cm Antenne auch horizontal angebracht

wolutator · July 9, 2018, 1:04pm

Ich kann da gerne helfen und die Antenne “vermessen”.

m0wlheld · July 10, 2018, 9:08am

Bzgl. PowerLAN vs. LAN: Ich glaube, dass PowerLan ausreichend stabil ist, bzw. sich ein Ausfall auf einen ganzen Schwung von Geräten auswirken müsste. Es sind aber aktuell immer die gleichen Geräte betroffen und diese befinden sich in “Schlagdistanz” des Max!Cube.

Heute waren über die Homematic Konfigurationsoberfläche wieder zwei Service-Meldungen zu vorübergehenden Kommunikationsproblemen mit 2 dieser 3 Geräte. Allerdings ohne Auswirkung, zu den notwendigen Zeitpunkten (Jalousie auf/zu) war die Kommunikation offenbar möglich.

Im homematic.err findet sich keine Meldung bzgl. gestörter Kommunikation mit dem Max!Cube oder dem CC1101 Modul.

m0wlheld · August 9, 2018, 8:20am

Ich hab jetzt den Max!Cube in ein andere Zimmer und an direktes LAN verschoben. Gleichzeitig den HM-CFG-LAN in den Keller verbannt und auch an LAN angeschlossen. Dennoch komme ich auch täglich 3-7 Meldungen über gestörte Kommunikation täglich!

Mit fällt auf, dass das Pairing nach Roaming äußerst obskure Ergebnisse liefert. So verbinden sich Geräte aus dem Obergeschoß mit dem HM-CFG-LAN im Keller. Andereseits ist ein Jalousie im Raum mit dem Max!Cube mit dem CC1101 Modul auf der anderen Etage verbunden.

@sathya Kannst Du bitte was zur Dynamik des Roamings sagen, was sind die Kriterien / Zeiträume an denen eine Neubewertung der Interface-Zuordnung stattfindet?

sathya · August 20, 2018, 11:50am

Siehe auch Homematic Gateways in Homegear ablernen.

Welches Kommunikationsmodul gewählt wird, wird anhand des vom Kommunikationsmodul zurückgegebenen RSSI bestimmt. Bei einer Differenz > 10 wird das Modul gewechselt. Im Log erscheint dann die Meldung “Info: Changing interface of peer to , because the reception is better.”. Das Ganze setzt also voraus, dass der RSSI korrekt gemessen ist. Beim HM-CFG-LAN und Max!Cube weiß ich nicht, ob das der Fall ist. Das Homegear-Log zeigt dir aber den übermittelten RSSI an, so dass du sehen kannst, ob die Werte sinnvoll sind. Falls diese das nicht sind, erklärt das das komische Verhalten.

Viele Grüße

Sathya

m0wlheld · August 20, 2018, 5:15pm

Die entsprechenden Events habe ich ihm Logfile gefunden. Alleine heute 323 Einträge. Interessant ist dabei folgendes:

homegear.log.1:08/20/18 06:23:15.232 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
homegear.log.1:08/20/18 06:23:16.376 Info: Changing interface of peer 33 to My-CC1101, because the reception is better.
homegear.log.1:08/20/18 06:23:17.216 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
homegear.log.1:08/20/18 06:23:18.570 Info: Changing interface of peer 33 to hm-cfg-lan-1, because the reception is better.
homegear.log.1:08/20/18 06:23:19.975 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.

Hier ist ein Gerät in 5 Sekunden über alle 3 Gateways gesprungen. Das betroffene Geräte (HM-Sec-SCo) befindet sich im Obergeschoss und ist aktuell mit dem HM-CFG-LAN im Keller verbunden.

sathya · August 20, 2018, 6:32pm

Kannst du mir einen vollständigen Logausschnitt posten? Ich brauche die zugehörigen Paketempfangszeiten und RSSIs.

m0wlheld · August 20, 2018, 7:40pm

Etwa so?

08/20/18 06:23:15.232 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D2DA610603C74FDCD9906010000
08/20/18 06:23:15.232 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
08/20/18 06:23:15.263 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D2DA610603C74FDCD9906010000
08/20/18 06:23:15.378 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 112DA002FDCD99603C74041E6DA843D4E800
08/20/18 06:23:15.408 HomeMatic BidCoS packet received (My-CC1101, RSSI: -86 dBm): 112DA002FDCD99603C74041E6DA843D4E800
08/20/18 06:23:15.445 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 112DA002FDCD99603C74041E6DA843D4E800
08/20/18 06:23:15.540 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 192DA603603C74FDCD998059D4A644398490CF9C0055B5D958B3
08/20/18 06:23:15.781 Info: r-Frame is: 192DA603603C74FDCD998059D4A644398490CF9C0055B5D958B3
08/20/18 06:23:15.781 HomeMatic BidCoS packet received (max-cube-1, RSSI: -63 dBm): 0D2DA610603C74FDCD9906010000
08/20/18 06:23:15.781 Module HomeMatic BidCoS: Info: ERROR on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:15.782 Module HomeMatic BidCoS: Info: LOWBAT on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:15.782 Module HomeMatic BidCoS: Info: STATE on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:15.782 Module HomeMatic BidCoS: Info: LOWBAT on channel 0 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:15.812 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D2EA610603C74FDCD9906010000
08/20/18 06:23:15.849 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D2EA610603C74FDCD9906010000
08/20/18 06:23:15.873 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 0E2D8002FDCD99603C7400B3157FB5
08/20/18 06:23:15.901 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0E2D8002FDCD99603C7400B3157FB5
08/20/18 06:23:15.938 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 0E2D8002FDCD99603C7400B3157FB5
08/20/18 06:23:15.994 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 112EA002FDCD99603C7404B17D7338C0EB00
08/20/18 06:23:16.024 HomeMatic BidCoS packet received (My-CC1101, RSSI: -86 dBm): 112EA002FDCD99603C7404B17D7338C0EB00
08/20/18 06:23:16.061 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 112EA002FDCD99603C7404B17D7338C0EB00
08/20/18 06:23:16.376 HomeMatic BidCoS packet received (My-CC1101, RSSI: -88 dBm): 0D2FA610603C74FDCD9906010000
08/20/18 06:23:16.376 Info: Changing interface of peer 33 to My-CC1101, because the reception is better.
08/20/18 06:23:16.377 Module HomeMatic BidCoS: Info: ERROR on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:16.377 Module HomeMatic BidCoS: Info: LOWBAT on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:16.377 Module HomeMatic BidCoS: Info: STATE on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:16.377 Module HomeMatic BidCoS: Info: LOWBAT on channel 0 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:16.407 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D2FA610603C74FDCD9906010000
08/20/18 06:23:16.524 HomeMatic BidCoS packet received (max-cube-1, RSSI: -63 dBm): 0D2FA610603C74FDCD9906010000
08/20/18 06:23:17.216 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D30A610603C74FDCD9906010000
08/20/18 06:23:17.216 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
08/20/18 06:23:17.278 Module HomeMatic BidCoS: TI CC110X "My-CC1101": Info: Sending (My-CC1101): 1130A002FDCD99603C74046F124005A77C00
08/20/18 06:23:17.339 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -90 dBm): 1130A002FDCD99603C74046F124005A77C00
08/20/18 06:23:17.360 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1130A002FDCD99603C74041215FB5E89EE00
08/20/18 06:23:17.390 HomeMatic BidCoS packet received (My-CC1101, RSSI: -86 dBm): 1130A002FDCD99603C74041215FB5E89EE00
08/20/18 06:23:17.391 HomeMatic BidCoS packet received (max-cube-1, RSSI: -85 dBm): 1130A002FDCD99603C74046F124005A77C00
08/20/18 06:23:17.428 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 1130A002FDCD99603C74041215FB5E89EE00
08/20/18 06:23:17.433 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 1930A603603C74FDCD99BA44E9BCCA222C63EFD2461E35B26EA0
08/20/18 06:23:17.515 Info: r-Frame is: 1930A603603C74FDCD99BA44E9BCCA222C63EFD2461E35B26EA0
08/20/18 06:23:17.515 Module HomeMatic BidCoS: CUNX "max-cube-1": Error: AES handshake failed for packet: 0D30A610603C74FDCD9906010000. Sender address: 603C74
08/20/18 06:23:18.570 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D31A610603C74FDCD9906010000
08/20/18 06:23:18.570 Info: Changing interface of peer 33 to hm-cfg-lan-1, because the reception is better.
08/20/18 06:23:18.611 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -87 dBm): 0D31A610603C74FDCD9906010000
08/20/18 06:23:18.612 Module HomeMatic BidCoS: Info: ERROR on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:18.612 Module HomeMatic BidCoS: Info: LOWBAT on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:18.612 Module HomeMatic BidCoS: Info: STATE on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:18.612 Module HomeMatic BidCoS: Info: LOWBAT on channel 0 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/20/18 06:23:18.753 HomeMatic BidCoS packet received (max-cube-1, RSSI: -63 dBm): 0D31A610603C74FDCD9906010000
08/20/18 06:23:19.974 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D32A610603C74FDCD9906010000
08/20/18 06:23:19.975 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
08/20/18 06:23:20.085 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1132A002FDCD99603C740486DC67E6710D00
08/20/18 06:23:20.101 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 1132A002FDCD99603C74044CDA7C32536E02
08/20/18 06:23:20.132 HomeMatic BidCoS packet received (My-CC1101, RSSI: -86 dBm): 1132A002FDCD99603C740486DC67E6710D00
08/20/18 06:23:20.169 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 1132A002FDCD99603C740486DC67E6710D00
08/20/18 06:23:20.233 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 1932A603603C74FDCD9958701400C048C8A376FF2A2D1647A79B
08/20/18 06:23:20.240 HomeMatic BidCoS packet received (max-cube-1, RSSI: -78 dBm): 08/20/18 06:23:20.240 Info: r-Frame is: 1932A603603C74FDCD9958701400C048C8A376FF2A2D1647A79B
1132A002FDCD99603C74044CDA7C32536E02
08/20/18 06:23:20.240 Module HomeMatic BidCoS: CUNX "max-cube-1": Error: AES handshake failed for packet: 0D32A610603C74FDCD9906010000. Sender address: 603C74
08/20/18 06:23:20.353 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0E328002FDCD99603C740061D701D9
08/20/18 06:23:20.377 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D32A610603C74FDCD9906010000
08/20/18 06:23:20.487 HomeMatic BidCoS packet received (max-cube-1, RSSI: -77 dBm): 0E328002FDCD99603C740061D701D9

sathya · August 21, 2018, 4:59pm

Hallo @m0wlheld,

das Problem ergibt sich dadurch, dass der AES-Handshake am MAX-Cube nie erfolgreich ist. Hier die Analyse:

Paket 0x2D:

08/20/18 06:23:15.232 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D2DA610603C74FDCD9906010000
08/20/18 06:23:15.232 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
08/20/18 06:23:15.263 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D2DA610603C74FDCD9906010000
08/20/18 06:23:15.781 HomeMatic BidCoS packet received (max-cube-1, RSSI: -63 dBm): 0D2DA610603C74FDCD9906010000

=> Schnittstellt ist max-cube-1

Paket 0x2E:

08/20/18 06:23:15.812 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D2EA610603C74FDCD9906010000
08/20/18 06:23:15.849 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D2EA610603C74FDCD9906010000
08/20/18 06:23:15.901 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0E2D8002FDCD99603C7400B3157FB5
08/20/18 06:23:15.938 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 0E2D8002FDCD99603C7400B3157FB5
08/20/18 06:23:15.994 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 112EA002FDCD99603C7404B17D7338C0EB00
08/20/18 06:23:16.024 HomeMatic BidCoS packet received (My-CC1101, RSSI: -86 dBm): 112EA002FDCD99603C7404B17D7338C0EB00
08/20/18 06:23:16.061 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -79 dBm): 112EA002FDCD99603C7404B17D7338C0EB00

=> Handshake nicht erfolgreich => Paket wird als nicht von max-cube-1 empfangen interpretiert.

Paket 0x2F:

08/20/18 06:23:16.376 HomeMatic BidCoS packet received (My-CC1101, RSSI: -88 dBm): 0D2FA610603C74FDCD9906010000
08/20/18 06:23:16.376 Info: Changing interface of peer 33 to My-CC1101, because the reception is better.
08/20/18 06:23:16.407 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D2FA610603C74FDCD9906010000
08/20/18 06:23:16.524 HomeMatic BidCoS packet received (max-cube-1, RSSI: -63 dBm): 0D2FA610603C74FDCD9906010000

=> Weil max-cube-1 gerade scheinbar nicht erreichbar, Schnittstellenwechsel auf CC1101. max-cube-1 hat wieder besten Empfang.

Paket 0x30:

08/20/18 06:23:17.216 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D30A610603C74FDCD9906010000
08/20/18 06:23:17.216 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.

=> Da max-cube-1 für das letzte Paket den besten Empfang hatte, Wechsel auf max-cube-1. Dieses Paket wird aber von max-cube-1 nicht empfangen.

Paket 0x31:

08/20/18 06:23:18.570 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D31A610603C74FDCD9906010000
08/20/18 06:23:18.570 Info: Changing interface of peer 33 to hm-cfg-lan-1, because the reception is better.
08/20/18 06:23:18.611 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -87 dBm): 0D31A610603C74FDCD9906010000
08/20/18 06:23:18.753 HomeMatic BidCoS packet received (max-cube-1, RSSI: -63 dBm): 0D31A610603C74FDCD9906010000

=> Wechsel auf hm-cfg-lan, da diser im letzen Paket den besten Empfang hatte.

Paket 0x32:

08/20/18 06:23:19.974 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0D32A610603C74FDCD9906010000
08/20/18 06:23:19.975 Info: Changing interface of peer 33 to max-cube-1, because the reception is better.
08/20/18 06:23:20.377 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0D32A610603C74FDCD9906010000

=> Wechsel auf max-cube-1, da dieser wieder den besten Empfang hatte.

Du hast sogar eine Sicherheitslücke entdeckt: STATE dürfte ohne erfolgreichen Handshake gar nicht gesetzt werden. Das schaue ich mir gleich an. Könntest du einmal verifizieren, ob der Handshake generell funktioniert, wenn du ROAMING deaktivierst und das Kommunikationsmodul fest setzt?

Viele Grüße

Sathya

m0wlheld · August 21, 2018, 5:09pm

Wenn Du mir sagst, was ich tun soll - gerne. Roaming aus krieg ich ja hin, “Kommunikationsmodul fest setzt” - $hg->setInterface()?

sathya · August 21, 2018, 5:11pm

Genau, von der Konsole aus:

homegear -e rc '$hg->setInterface("<Interface-Name wie in der Konfig definiert, z. B. max-cube-1 oder hm-cfg-lan-1>");'

m0wlheld · August 21, 2018, 5:21pm

in der Homegear console:

> rc '$hg->putParamset(33,0,"MASTER",array("ROAMING"=>false));'
> rc '$hg->setInterface(33,'max-cube-1');'

Gerät 33 ist lt. Anzeige unverändert mit Gateway “max-cube-1” verbunden. Ich mach mal Fenster auf/zu (Gerät 33 ist ein Fensterkontakt) und poste die Logs.

m0wlheld · August 21, 2018, 5:36pm

Also,

erstes Ergebnis: Der Fensterkontakt HM-Sec-SCo leuchtet rot (bei Zustandsänderungen), wo er vormals erst orange und dann grün leuchtete. Sein Zustand wird aber in Home Assistant korrekt wiedergegeben und die Direktverknüpfung mit dem Heizkörper-Thermostat funktioniert auch.

Durch’s Log rauscht eine Menge, ich hoffe es ist etwas dabei.

08/21/18 19:26:40.558 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -71 dBm): 0F3186104F06760000000AA9000B0000
08/21/18 19:26:40.962 HomeMatic BidCoS packet received (My-CC1101, RSSI: -88 dBm): 0C4FA641603C74FDCD99018AC8
08/21/18 19:26:40.999 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -92 dBm): 0C4FA641603C74FDCD99018AC8
08/21/18 19:26:41.144 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 114FA002FDCD99603C740409EC8A763C1D00
08/21/18 19:26:41.174 HomeMatic BidCoS packet received (My-CC1101, RSSI: -78 dBm): 114FA002FDCD99603C740409EC8A763C1D00
08/21/18 19:26:41.212 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -82 dBm): 114FA002FDCD99603C740409EC8A763C1D00
08/21/18 19:26:45.385 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0C50B641603C7452385C018B00
08/21/18 19:26:45.422 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -92 dBm): 0C50B641603C7452385C018B00
08/21/18 19:26:45.510 HomeMatic BidCoS packet received (max-cube-1, RSSI: -60 dBm): 0C50B641603C7452385C018B00
08/21/18 19:26:45.511 Info: Ignoring broadcast packet from peer 33 to other peer, because AES handshakes are enabled for this peer.
08/21/18 19:26:45.513 HomeMatic BidCoS packet received (My-CC1101, RSSI: -82 dBm): 0A50800252385C603C7400
08/21/18 19:26:45.544 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -69 dBm): 0A50800252385C603C7400
08/21/18 19:26:45.656 HomeMatic BidCoS packet received (My-CC1101, RSSI: -84 dBm): 0C51A641603C74FDCD99018B00
08/21/18 19:26:45.687 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -93 dBm): 0C51A641603C74FDCD99018B00
08/21/18 19:26:45.758 HomeMatic BidCoS packet received (max-cube-1, RSSI: -46 dBm): 0A50800252385C603C7400
08/21/18 19:26:45.851 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1151A002FDCD99603C74044063F6280BEC00
08/21/18 19:26:45.881 HomeMatic BidCoS packet received (My-CC1101, RSSI: -79 dBm): 1151A002FDCD99603C74044063F6280BEC00
08/21/18 19:26:45.918 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -83 dBm): 1151A002FDCD99603C74044063F6280BEC00
08/21/18 19:26:46.184 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0C52A641603C74FDCD99018B00
08/21/18 19:26:46.346 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1152A002FDCD99603C74049B4027E10B7000
08/21/18 19:26:46.376 HomeMatic BidCoS packet received (My-CC1101, RSSI: -78 dBm): 1152A002FDCD99603C74049B4027E10B7000
08/21/18 19:26:46.420 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -83 dBm): 1152A002FDCD99603C74049B4027E10B7000
08/21/18 19:26:47.005 HomeMatic BidCoS packet received (My-CC1101, RSSI: -86 dBm): 0C53A641603C74FDCD99018B00
08/21/18 19:26:47.036 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -94 dBm): 0C53A641603C74FDCD99018B00
08/21/18 19:26:47.338 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1153A002FDCD99603C7404F2DDFD4FA47400
08/21/18 19:26:47.368 HomeMatic BidCoS packet received (My-CC1101, RSSI: -78 dBm): 1153A002FDCD99603C7404F2DDFD4FA47400
08/21/18 19:26:47.406 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -81 dBm): 1153A002FDCD99603C7404F2DDFD4FA47400
08/21/18 19:26:48.152 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0C54A641603C74FDCD99018B00
08/21/18 19:26:48.190 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -91 dBm): 0C54A641603C74FDCD99018B00
08/21/18 19:26:48.328 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1154A002FDCD99603C74042AD7F23EB8A400
08/21/18 19:26:48.359 HomeMatic BidCoS packet received (My-CC1101, RSSI: -78 dBm): 1154A002FDCD99603C74042AD7F23EB8A400
08/21/18 19:26:48.396 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -83 dBm): 1154A002FDCD99603C74042AD7F23EB8A400
08/21/18 19:26:48.929 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:33580 accepted. Client number: 489607
08/21/18 19:26:48.930 RPC Server (Port 2001): Info: RPC server client id for client number 489607 is: 79346
08/21/18 19:26:48.931 RPC Server (Port 2001): Info: Client number 489607 is calling RPC method: getAllSystemVariables (1) Parameters:
08/21/18 19:26:49.520 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0C55A641603C74FDCD99018B00
08/21/18 19:26:49.551 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0C55A641603C74FDCD99018B00
08/21/18 19:26:49.815 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1155A002FDCD99603C74048F0507ED785700
08/21/18 19:26:49.845 HomeMatic BidCoS packet received (My-CC1101, RSSI: -78 dBm): 1155A002FDCD99603C74048F0507ED785700
08/21/18 19:26:49.883 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -83 dBm): 1155A002FDCD99603C74048F0507ED785700
08/21/18 19:26:51.051 HomeMatic BidCoS packet received (My-CC1101, RSSI: -85 dBm): 0C56A641603C74FDCD99018B00
08/21/18 19:26:51.088 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -88 dBm): 0C56A641603C74FDCD99018B00
08/21/18 19:26:51.302 Module HomeMatic BidCoS: CUNX "max-cube-1": Info: Sending (max-cube-1): 1156A002FDCD99603C7404325CC1B9E35600
08/21/18 19:26:51.332 HomeMatic BidCoS packet received (My-CC1101, RSSI: -78 dBm): 1156A002FDCD99603C7404325CC1B9E35600
08/21/18 19:26:51.369 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -83 dBm): 1156A002FDCD99603C7404325CC1B9E35600
08/21/18 19:26:52.834 HomeMatic BidCoS packet received (My-CC1101, RSSI: -76 dBm): 0FA186104DDF0D0000000AA9080B0000
08/21/18 19:26:52.871 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -72 dBm): 0FA186104DDF0D0000000AA9080B0000
08/21/18 19:26:52.943 HomeMatic BidCoS packet received (max-cube-1, RSSI: -59 dBm): 0FA186104DDF0D0000000AA9080B0000

sathya · August 21, 2018, 5:45pm

Die rote LED sagt: Der Handshake war nicht erfolgreich. Eigentlich sollte dann auch nichts an Home Assistant weitergegeben werden. In dem geposteten Logausschnitt sind auch keine Variablenänderungen sichtbar. Poste sonst noch einmal einen Abschnitt, welcher während der in Home Assistant angezeigten Änderung aufgezeichnet wurde.

m0wlheld · August 21, 2018, 5:47pm

Hier nochmal das Protokoll, nachdem ich Peer 33 auf das CC1101 Modul verschoben habe. RSSI ist jetzt natürlich schlechter (Etage dazwischen), aber die Lampe am Fensterkontakt leuchtet wieder grün.

Sieht das so aus, als ob der Max!Cube die Situation nicht verbessert, sondern verschlechtert hätte.

08/21/18 19:44:30.342 HomeMatic BidCoS packet received (My-CC1101, RSSI: -88 dBm): 0C78B641603C7452385C0192C8
08/21/18 19:44:30.342 Info: Ignoring broadcast packet from peer 33 to other peer, because AES handshakes are enabled for this peer.
08/21/18 19:44:30.379 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -101 dBm): 0C78B641603C7452385C0192C8
08/21/18 19:44:30.469 HomeMatic BidCoS packet received (My-CC1101, RSSI: -82 dBm): 0A78800252385C603C7400
08/21/18 19:44:30.500 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -69 dBm): 0A78800252385C603C7400
08/21/18 19:44:30.565 HomeMatic BidCoS packet received (max-cube-1, RSSI: -68 dBm): 0C78B641603C7452385C0192C8
08/21/18 19:44:30.565 HomeMatic BidCoS packet received (max-cube-1, RSSI: -48 dBm): 0A78800252385C603C7400
08/21/18 19:44:30.644 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -94 dBm): 0C79A641603C74FDCD990192C8
08/21/18 19:44:30.713 Module HomeMatic BidCoS: TI CC110X "My-CC1101": Info: Sending (My-CC1101): 1179A002FDCD99603C7404A781FAC11BEA00
08/21/18 19:44:30.779 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -99 dBm): 1179A002FDCD99603C7404A781FAC11BEA00
08/21/18 19:44:30.813 HomeMatic BidCoS packet received (max-cube-1, RSSI: -72 dBm): 0C79A641603C74FDCD990192C8
08/21/18 19:44:30.813 HomeMatic BidCoS packet received (max-cube-1, RSSI: -80 dBm): 1179A002FDCD99603C7404A781FAC11BEA00
08/21/18 19:44:30.868 Info: r-Frame is: 1979A603603C74FDCD995BE063FE0D905872D87AABCA6B9C8D9B
08/21/18 19:44:30.868 HomeMatic BidCoS packet received (My-CC1101, RSSI: -88 dBm): 0C79A641603C74FDCD990192C8
08/21/18 19:44:30.869 Module HomeMatic BidCoS: Info: LOWBAT on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0x00.
08/21/18 19:44:30.869 Module HomeMatic BidCoS: Info: STATE on channel 1 of HomeMatic BidCoS peer 33 with serial number OEQ1196738 was set to 0xC8.
08/21/18 19:44:30.968 Module HomeMatic BidCoS: TI CC110X "My-CC1101": Info: Sending (My-CC1101): 0E798002FDCD99603C7400A653A4CC
08/21/18 19:44:31.020 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -99 dBm): 0E798002FDCD99603C7400A653A4CC
08/21/18 19:44:31.061 HomeMatic BidCoS packet received (max-cube-1, RSSI: -70 dBm): 1979A603603C74FDCD995BE063FE0D905872D87AABCA6B9C8D9B
08/21/18 19:44:31.061 HomeMatic BidCoS packet received (max-cube-1, RSSI: -80 dBm): 0E798002FDCD99603C7400A653A4CC
08/21/18 19:44:34.479 HomeMatic BidCoS packet received (My-CC1101, RSSI: -87 dBm): 0F4986105D5D790000000AA8EC0E0000
08/21/18 19:44:34.515 HomeMatic BidCoS packet received (hm-cfg-lan-1, RSSI: -46 dBm): 0F4986105D5D790000000AA8EC0E0000
08/21/18 19:44:34.516 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x00EC.
08/21/18 19:44:34.516 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x0E.
08/21/18 19:44:34.516 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x00.
08/21/18 19:44:34.516 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x00.
08/21/18 19:44:34.516 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x00.
08/21/18 19:44:34.517 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x00.
08/21/18 19:44:34.517 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x2A.
08/21/18 19:44:34.517 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 4 with serial number OEQ0856164 was set to 0x00.
08/21/18 19:44:34.529 HomeMatic BidCoS packet received (max-cube-1, RSSI: -53 dBm): 0F4986105D5D790000000AA8EC0E0000

sathya · August 21, 2018, 5:49pm

Hier sieht es auch gut aus. Ich vermute mal, der MAX-Cube hat einfach Timingprobleme und deshalb klappen die Handshakes nicht. Das war beim CUNO auch schon der Fall. Mit einem Homegear-Gateway oder dem HM-CFG-LAN sollte es alternativ aber klappen.

m0wlheld · August 21, 2018, 5:51pm

Okay, danke für die Analyse. Dann werde ich den Max!Cube mal außer Betrieb nehmen, da bei allen anderen Peers außer 33 noch Roaming aktiv ist, sollten die automatisch umschwenken - richtig?

sathya · August 21, 2018, 5:54pm

Richtig. Wenn du den MAX-Cube ersetzt, berichte mal, ob es dann funktioniert. Nur die Sicherheitslücke muss ich noch irgendwie lösen.

m0wlheld · August 21, 2018, 6:38pm

Also, gerade (20:30h) war via Home Assistant kontrolliertes Jalousien-Schließen angesagt und nicht nur, dass alle gewünschten Jalousien reagierten, sie gingen auch mit deutlich weniger Latenz zu, quasi zeitgleich. Auch tauchten keine “Servicemeldungen” in der Homematic Softwre auf.