HM-MOD-RPI-PCB sendet nicht mehr, empfängt aber Daten

Deutsche Foren Fehler
#1

Hallo,

in den aktuellen Nightly-Builds kann ich über meinen HM-MOD-RPI-PCB (RPI3 mit Raspbian Jessie) keinen einzigen Aktor mehr schalten. Daten werden relativ problemlos empfangen aber jeder Versuch etwas zu senden scheitert mit diesen Meldungen:

01/25/18 17:13:06.764 RPC Server (Port 2001): Info: Connection from ::ffff:127.0.0.1:44150 accepted. Client number: 449
01/25/18 17:13:06.765 RPC Server (Port 2001): Info: RPC server client id for client number 449 is: 11
01/25/18 17:13:06.766 RPC Server (Port 2001): Info: Client number 449 is calling RPC method: setValue (2) Parameters:
(String) MEQ00000002:2
(String) STATE
(Boolean) 0
01/25/18 17:13:09.330 RPC Server (Port 2001): Info: Client number 449 is calling RPC method: ping (2) Parameters:
(String) homegear
01/25/18 17:13:09.746 HomeMatic BidCoS packet received (HM-MOD-RPI-PCB-1, RSSI: -30 dBm): 0F9C865E3DF23E0000002DF625012F84
01/25/18 17:13:09.747 Module HomeMatic BidCoS: Info: BOOT on channel 1 of HomeMatic BidCoS peer 20 with serial number MEQ0000000 was set to 0x00.
01/25/18 17:13:09.747 Module HomeMatic BidCoS: Info: ENERGY_COUNTER on channel 1 of HomeMatic BidCoS peer 20 with serial number MEQ0000000 was set to 0x2DF625.
01/25/18 17:13:09.747 Module HomeMatic BidCoS: Info: POWER on channel 1 of HomeMatic BidCoS peer 20 with serial number MEQ0000000 was set to 0x012F84.
01/25/18 17:13:09.776 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/25/18 17:13:09.776 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 44). Retrying...
01/25/18 17:13:11.867 HomeMatic BidCoS packet received (HM-MOD-RPI-PCB-1, RSSI: -56 dBm): 0F47861022E2400000000AA09A096002
01/25/18 17:13:11.868 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x009A.
01/25/18 17:13:11.868 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x09.
01/25/18 17:13:11.868 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x02.
01/25/18 17:13:11.869 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x00.
01/25/18 17:13:11.869 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x00.
01/25/18 17:13:11.869 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x02.
01/25/18 17:13:11.869 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x28.
01/25/18 17:13:11.869 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 25 with serial number KEQ0000001 was set to 0x60.
01/25/18 17:13:12.881 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/25/18 17:13:12.881 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 44). Retrying...
01/25/18 17:13:13.088 HomeMatic BidCoS packet received (HM-MOD-RPI-PCB-1, RSSI: -60 dBm): 0F9886102211310000000AA091093B18
01/25/18 17:13:13.090 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x0091.
01/25/18 17:13:13.090 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x09.
01/25/18 17:13:13.090 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x18.
01/25/18 17:13:13.090 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x00.
01/25/18 17:13:13.090 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x00.
01/25/18 17:13:13.090 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x18.
01/25/18 17:13:13.091 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x28.
01/25/18 17:13:13.091 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 24 with serial number KEQ0000002 was set to 0x3B.
01/25/18 17:13:14.411 HomeMatic BidCoS packet received (HM-MOD-RPI-PCB-1, RSSI: -68 dBm): 0D97A6103462EDFD66D506017000
01/25/18 17:13:14.412 Module HomeMatic BidCoS: Info: BRIGHTNESS on channel 1 of HomeMatic BidCoS peer 14 with serial number LEQ0000001 was set to 0x70.
01/25/18 17:13:15.987 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/25/18 17:13:15.987 Module HomeMatic BidCoS: Info: Queue is not finished (peer: 44). Retrying...
01/25/18 17:13:17.024 HomeMatic BidCoS packet received (HM-MOD-RPI-PCB-1, RSSI: -68 dBm): 0FE786102324000000000A506F0C0018
01/25/18 17:13:17.026 Module HomeMatic BidCoS: Info: ACTUAL_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x006F.
01/25/18 17:13:17.026 Module HomeMatic BidCoS: Info: BATTERY_STATE on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x0C.
01/25/18 17:13:17.026 Module HomeMatic BidCoS: Info: BOOST_STATE on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x18.
01/25/18 17:13:17.026 Module HomeMatic BidCoS: Info: CONTROL_MODE on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x00.
01/25/18 17:13:17.026 Module HomeMatic BidCoS: Info: FAULT_REPORTING on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x00.
01/25/18 17:13:17.027 Module HomeMatic BidCoS: Info: PARTY_START_TIME on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x18.
01/25/18 17:13:17.027 Module HomeMatic BidCoS: Info: SET_TEMPERATURE on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x14.
01/25/18 17:13:17.027 Module HomeMatic BidCoS: Info: VALVE_STATE on channel 4 of HomeMatic BidCoS peer 35 with serial number KEQ0000003 was set to 0x00.
01/25/18 17:13:19.092 Module HomeMatic BidCoS: Info: Setting peer to unreachable, because the queue processing was interrupted.
01/25/18 17:13:19.093 Info: Peer 44 is unreachable.
01/25/18 17:13:21.629 Info: Peer 44 is reachable again.

Ich habe jetzt auf den Nightly-Build vom 02.01.2018 zurückgesetzt und damit scheint alles wieder zu funktionieren.

Hat jemand ähnliche Probleme?

Danke,
Thorsten

Homegear: config_pending, kein neues Pairing möglich
(Gelöst) Pairing mit HM-MOD-RPI-PCB klappt nicht, Pakete werden aber empfangen (meine erste Installation)
(Gelöst) Pairing mit HM-MOD-RPI-PCB klappt nicht, Pakete werden aber empfangen (meine erste Installation)
#2

Moin,

habe genau das Gleiche Problem seitdem ich ein Update per Open Hab gemacht habe. Die Aktoren senden zwar Ihre Daten, aber reagieren nicht auf von mir gesendete Befehle.
Außerdem lassen sich die Geräte nicht mehr an oder ablernen.

Hardware: Pi3 mit HM-MOD-RPI-PCB
OpenHab Version: 2.2.0-1 (jessie)
Homegear Version: 0.7.14-1563

Gruß Alex

#3

Hallo,

habe das gleiche Problem…
Gestern Abend habe ich openhabian mit apt-get update und upgrade upgedatet und seitdem kommt keine Kommunikation mehr zustande.
Auch wenn ich im Homatic Konfigurator die Geräte steuern will kommt eine Fehlermeldung.

Ich weiss, warum ich manchmal keine Updates machen will…

Gruß Andy

#4

Hallo,

in der Tat hat sich da ein Fehler eingeschlichen :roll_eyes:. Im nächsten Nightly ist er gefixed. Für Raspbian Jessie in etwa zwei Stunden, für Raspbian Stretch in etwa 8 Stunden. Das wird auch zügig in der Stable-Version gefixed.

Viele Grüße

Sathya

2 Likes
#5

Blöde Frage @sathya , wenn ich die Nightly installiere, gibt es dann keine Probleme mit der Stable Version die ich drauf installiert habe bei openhabian?
Wenn es keine Probleme macht, kann ich dann paar Tage später die Stable installieren und es macht dann keine Probleme mit der davor installierten Nightly?

Sorry für die dummen Fragen…

#6

Hallo @AndyW,

es gibt keine dummen Fragen ;-). Nein, es gibt keine Probleme mit der Stable-Version. Du kannst auch ohne Weiteres wieder zurück zur Stable, sobald die Fixes dort enthalten sind. Zum Downgrade dann:

apt install <package-name>=<package-version-number>

Viele Grüße

Sathya