Keine kommunikation mit Wired Komponenten

Einrichtung, Nutzung und Hilfe zu RaspberryMatic (OCCU auf Raspberry Pi)

Moderatoren: jmaus, Co-Administratoren

Micha578
Beiträge: 45
Registriert: 28.08.2010, 23:31

Keine kommunikation mit Wired Komponenten

Beitrag von Micha578 » 04.11.2017, 19:05

Hallo in die Runde...

Ich habe heute ein Raspberry Pi3 mit Funkmodul und Wired Lan Gateway in Betrieb genommen. Nach anfänglichen Problemen weil der Aufkleber mit der Seriennummer auf dem Lan Gateway nicht dran war, hab ich das über das Netfindertool gefunden und in der Administration stand auch endlich "verbunden" beim Gateway.

Leider ist aber trotzdem keine Komunikation mit den Wired Komponenten möglich.

Das Backup kam von einer CCU1. Das Einspielen hatte Problemlos geklappt, in der WebUI sind auch alle Einstellungen für Räume usw. vorhanden. Nur ansteuern lässt sich nichts.

Hat da jemand einen Tip für mich wo ich ansetzen könnte?

Zur Info: Wenn ich die CCU1 wieder an den Bus hänge läuft wieder alles normal. Mit Funkkomponenten kann ich nichts testen weil ich keine habe, das ganze Haus ist nur mit Wired Geräten ausgestattet.

Benutzeravatar
anli
Beiträge: 4326
Registriert: 10.06.2009, 14:01
Wohnort: 20 Min. nördlich von Hannover und bei Bremen
Hat sich bedankt: 1 Mal
Danksagung erhalten: 23 Mal
Kontaktdaten:

Re: Keine kommunikation mit Wired Komponenten

Beitrag von anli » 05.11.2017, 12:00

Guten morgen!

Bitte in der Systemsteuerung -> Zentralenwartung Bidcos-Wired auf "alles loggen" stellen, dem RPi neu starten und dann das Log hier in Code-Tags posten. Dann kann man evtl. sehen wo der Hase im Pfeffer liegt.

Die Verkabelung hast Du schon kontrolliert (A/B evtl. vertauscht)? Wie ist der BUS aufgebaut? Ein "Abschlusswiderstand" ist verbaut?
Herzliche Grüße, anli

Alle Angaben ohne Gewähr und Haftung meinerseits. Verwendung der von mir zur Verfügung gestellten Downloads auf eigene Gefahr. Ich bitte um Verständnis, dass ich aus zeitlichen Gründen keine unaufgeforderte Hilfestellung per PN/Mail geben kann. Bitte allgemeine Fragen ins Forum stellen, hier können viele fähige User viel schneller helfen.

Homematic-Manager v2: einfaches Tool zum Erstellen von Direktverknüpfungen und Bearbeiten von Gerätenamen, -parametern etc. für Homematic und HomematicIP (Alternative diesbzgl. zur WebUI)

Einsteiger-Hilfeerweiterter Skript-Parser

Micha578
Beiträge: 45
Registriert: 28.08.2010, 23:31

Re: Keine kommunikation mit Wired Komponenten

Beitrag von Micha578 » 05.11.2017, 12:09

Hi und danke für Deine Rückmeldung.

Ein Abschlusswiderstand ist verbaut (der mit Überspannungsschutz), funktioniert ja auch mit der CCU1.

Wenn ich morgen vom Dienst zurück bin stelle ich das mal um und gucke nach.

Wenn ich ihn finde, tausche ich den Abschlusswiderstand mal aus, denn von Zeit zu Zeit hatte die CCU1 auch mal "Kommunikation gestört" angezeigt. Nicht, daß das neue System da anfälliger ist...

Familienvater
Beiträge: 7151
Registriert: 31.12.2006, 15:18
System: Alternative CCU (auf Basis OCCU)
Wohnort: Rhein-Main
Danksagung erhalten: 34 Mal

Re: Keine kommunikation mit Wired Komponenten

Beitrag von Familienvater » 05.11.2017, 12:18

Hi,

das wired-Lan-Gateway bzw. auch die Zentrale erzeugt keine Kommunikation gestört Meldungen für Wired-Geräte, das ist ein Luxus, den nur die CCU1 hatte...
Probleme die in die Richtung gehen, muss man sich leider selber aus dem Syslog raussuchen.

Der Familienvater

Daimler
Beiträge: 9115
Registriert: 17.11.2012, 10:47
System: Alternative CCU (auf Basis OCCU)
Wohnort: Köln
Hat sich bedankt: 37 Mal
Danksagung erhalten: 283 Mal

Re: Keine kommunikation mit Wired Komponenten

Beitrag von Daimler » 05.11.2017, 12:37

Hi,

du hast den RMatic aber nach der Einrichtung des RS-Gateways neu gebootet?
Werden die Geräte nach dem Neustart unter Status --> Geräte angezeigt?

Zum HMW-Sys-OP-DR:
So einer hat mir auch einmal mein RS-Gateway zerschossen - und ja: es war alles korrekt angeschlossen!
Gleiche Symptome:
Alle W-Geräte ließen sich ohne Servicemeldung in der WebUI umschalten - nur auf dem Bus / an den Geräten tat sich nix.
Gruß Günter

pivccx mit 3.xx in Produktiv und Testsystem mit HM-, HM-W, HMIP- und HMIP-W Geräten, HPCx Studio 4.1,
L-Gateways, RS-L-Gateways, HAP, Drap, FHZ200x, vereinzelt noch FS2x-Komponenten.
HM / HM-IP: Zur Zeit knapp 300 Komponenten mit ??? Kanälen .

Ich übernehme für alle von mir gegebenen Hinweise, Tipps und Links keine Haftung! Das Befolgen meiner Tipps ist nur für Fachkundige gedacht und erfolgt auf eigene Gefahr!

Benutzeravatar
robbi77
Beiträge: 13860
Registriert: 19.01.2011, 19:15
System: CCU
Wohnort: Landau
Hat sich bedankt: 182 Mal
Danksagung erhalten: 739 Mal

Re: Keine kommunikation mit Wired Komponenten

Beitrag von robbi77 » 05.11.2017, 12:40

@Familienvater
Das verstehe ich jetzt nicht. Was meinst du genau damit?
Gibt es bei wired Geräten an einer CCU2 gar keine „gestört Meldungen“, auch wenn ein Gerät nicht erreichbar ist?
Dann wäre ja meine CCU2 defekt, weil ich hatte schon „gestört Meldungen“.


Gruß
Roberto
Bei Risiken und Nebenwirkungen fragen Sie den Elektriker Ihres geringsten Mißtrauens!
http://www.eq-3.de/service/downloads.html
Tips und Tricks für Anfänger: viewtopic.php?t=22801
Programmlogik: viewtopic.php?f=31&t=4251
Webui-Handbuch: https://www.eq-3.de/downloads/download/ ... h_eQ-3.pdf
Script und Linksammlung: viewtopic.php?f=26&t=27907
Troll des Forums ...

Benutzeravatar
anli
Beiträge: 4326
Registriert: 10.06.2009, 14:01
Wohnort: 20 Min. nördlich von Hannover und bei Bremen
Hat sich bedankt: 1 Mal
Danksagung erhalten: 23 Mal
Kontaktdaten:

Re: Keine kommunikation mit Wired Komponenten

Beitrag von anli » 05.11.2017, 12:42

Was man noch machen kann ist natürlich, die Komplexität zu reduzieren - erstmal nur den Widerstand und ein Wired-Gerät anschließen und schauen, ob es dann funktioniert. Wenn ja, dann solange Wired-Geräte hinzunehmen, bis es nicht mehr geht, dann hat man den Schuldigen gefunden. Wenn man viele Wired-Geräte hat, kann man es auch mit der "Halb-Methode" machen - erst die eine Hälfte der Wired-Geräte testen, wenn die funktioniert, die andere. Wenn die nicht geht ist das problematische Gerät in der Hälfte. Dann diese Hälfte wieder teilen und das Spiel beginnt von vorn. Solange, bis nur noch ein Gerät übrig ist :mrgreen:
Herzliche Grüße, anli

Alle Angaben ohne Gewähr und Haftung meinerseits. Verwendung der von mir zur Verfügung gestellten Downloads auf eigene Gefahr. Ich bitte um Verständnis, dass ich aus zeitlichen Gründen keine unaufgeforderte Hilfestellung per PN/Mail geben kann. Bitte allgemeine Fragen ins Forum stellen, hier können viele fähige User viel schneller helfen.

Homematic-Manager v2: einfaches Tool zum Erstellen von Direktverknüpfungen und Bearbeiten von Gerätenamen, -parametern etc. für Homematic und HomematicIP (Alternative diesbzgl. zur WebUI)

Einsteiger-Hilfeerweiterter Skript-Parser

Familienvater
Beiträge: 7151
Registriert: 31.12.2006, 15:18
System: Alternative CCU (auf Basis OCCU)
Wohnort: Rhein-Main
Danksagung erhalten: 34 Mal

Re: Keine kommunikation mit Wired Komponenten

Beitrag von Familienvater » 05.11.2017, 13:31

Hi,
robbi77 hat geschrieben: Gibt es bei wired Geräten an einer CCU2 gar keine „gestört Meldungen“, auch wenn ein Gerät nicht erreichbar ist?
Dann wäre ja meine CCU2 defekt, weil ich hatte schon „gestört Meldungen“.
schön, ich habe es nicht geschafft, der CCU2 Servicemeldungen abzutrotzen, wenn man z.B. nur A oder B trennt (bei der einen Ader funktioniert die Kommunikation Gateway->Aktor, im anderen Fall nur Aktor->Zentrale). Auch wenn das Gateway nicht verbunden ist, oder das Netzwerk "unzuverlässig" ist, gibt es nur entsprechende Hinweise im Syslog, nicht als Servicemeldung.

Ich habe das aber auch an EQ3 gemeldet, aber wenn überhaupt gab es nur den Autoresponder mit der Ticketnummer. Immerhin hat es EQ3 geschafft, den wired-Sysloglevel-Bug bei einem Neustart in einer der letzten FW-Versionen zu fixen, es scheinen also Leute auf der anderen Seite bei EQ3 zu sitzen, die wenn man es Ihnen mit vielen Screenshots erklärt, das Problem fixen konnten (auch wenn erstmal gar kein Fehler vorhanden sein soll, würde ja alles funktionieren).

Der Familienvater

Benutzeravatar
robbi77
Beiträge: 13860
Registriert: 19.01.2011, 19:15
System: CCU
Wohnort: Landau
Hat sich bedankt: 182 Mal
Danksagung erhalten: 739 Mal

Keine kommunikation mit Wired Komponenten

Beitrag von robbi77 » 05.11.2017, 14:04

OK. Ich hatte letztens reihenweise Kommstörungen, warum keine Ahnung. Die trudelten alle per Push ein als ich auf Arbeit war. Wollte ich per App (PC) ein Licht schalten kam postwendend eine Kommstörung.
Wie gesagt bin dem „Fehler“ nicht weiter nachgegangen, abends ging wieder alles.
Schiebe es auf die Bauarbeiten in unserer Straße, Erneuerung der Stromleitung, es hatte wohl eine Phase erwischt .... und vermute genau die mit dem Netzteil.


Gruß
Roberto
Bei Risiken und Nebenwirkungen fragen Sie den Elektriker Ihres geringsten Mißtrauens!
http://www.eq-3.de/service/downloads.html
Tips und Tricks für Anfänger: viewtopic.php?t=22801
Programmlogik: viewtopic.php?f=31&t=4251
Webui-Handbuch: https://www.eq-3.de/downloads/download/ ... h_eQ-3.pdf
Script und Linksammlung: viewtopic.php?f=26&t=27907
Troll des Forums ...

Micha578
Beiträge: 45
Registriert: 28.08.2010, 23:31

Re: Keine kommunikation mit Wired Komponenten

Beitrag von Micha578 » 06.11.2017, 11:53

Hallo,
so sieht der error log aus:

Code: Alles auswählen

Nov  6 11:46:23 homematic-raspi daemon.notice ntpdate[423]: step time server 81.14.202.21 offset 1509965147.723786 sec
Nov  6 11:46:23 homematic-raspi daemon.notice ntpd[425]: ntpd 4.2.8p10@1.3728-o Sat Oct 21 22:47:26 UTC 2017 (1): Starting
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[425]: Command line: /usr/sbin/ntpd -g ntp.homematic.com
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: proto: precision = 0.990 usec (-20)
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listen and drop on 0 v6wildcard [::]:123
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listen normally on 2 lo 127.0.0.1:123
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listen normally on 3 eth0 192.168.178.112:123
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listen normally on 4 lo [::1]:123
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listen normally on 5 eth0 [fe80::ba27:ebff:feda:557f%2]:123
Nov  6 11:46:23 homematic-raspi daemon.info ntpd[427]: Listening on routing socket on fd #22 for interface updates
Nov  6 11:46:23 homematic-raspi daemon.err xinetd[454]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Nov  6 11:46:23 homematic-raspi daemon.crit xinetd[454]: 454 {init_services} no services. Exiting...
Nov  6 11:46:24 homematic-raspi user.info root: Updating RF Lan Gateway Coprocessor Firmware
Nov  6 11:46:24 homematic-raspi user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Nov  6 11:46:24 homematic-raspi user.info root: Updating RF Lan Gateway Firmware
Nov  6 11:46:24 homematic-raspi user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Nov  6 11:46:24 homematic-raspi user.info root: Updating Wired Lan Gateway Firmware
Nov  6 11:46:24 homematic-raspi user.info update-lgw-firmware: LAN Gateway Firmware Update...
Nov  6 11:46:24 homematic-raspi user.info update-lgw-firmware: Gateway LEQ0637514
Nov  6 11:46:26 homematic-raspi user.info update-lgw-firmware: Gateway type is eQ3-HMW-LGW-App
Nov  6 11:46:26 homematic-raspi user.info update-lgw-firmware: Available Firmware Version:   1.0.5
Nov  6 11:46:26 homematic-raspi user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.0.5
Nov  6 11:46:26 homematic-raspi user.info update-lgw-firmware: Firmware is up to date
Nov  6 11:46:29 homematic-raspi daemon.info snmpd[550]: Created directory: /var/lib/snmp
Nov  6 11:46:29 homematic-raspi daemon.info snmpd[550]: Created directory: /var/lib/snmp/cert_indexes
Nov  6 11:46:29 homematic-raspi daemon.info snmpd[550]: Created directory: /var/lib/snmp/mib_indexes
Nov  6 11:46:29 homematic-raspi daemon.info snmpd[550]: Turning on AgentX master support.
Nov  6 11:46:29 homematic-raspi daemon.info snmpd[552]: NET-SNMP version 5.7.3
Nov  6 11:46:30 homematic-raspi user.info kernel: [   42.369129] eq3loop: created slave ttyS0
Nov  6 11:46:30 homematic-raspi user.info kernel: [   42.370427] eq3loop: created slave mmd_bidcos
Nov  6 11:46:34 homematic-raspi user.info kernel: [   46.585909] eq3loop: eq3loop_open_slave() mmd_bidcos
Nov  6 11:46:48 homematic-raspi cron.err crond[209]: time disparity of 25166086 minutes detected
Nov  6 11:46:55 homematic-raspi user.info kernel: [   67.887078] eq3loop: eq3loop_open_slave() ttyS0
Nov  6 11:46:55 homematic-raspi user.info kernel: [   67.887326] eq3loop: eq3loop_close_slave() ttyS0
Nov  6 11:46:55 homematic-raspi user.info kernel: [   67.905146] eq3loop: eq3loop_open_slave() ttyS0
Nov  6 11:46:55 homematic-raspi user.info kernel: [   67.905333] eq3loop: eq3loop_close_slave() ttyS0
Nov  6 11:46:55 homematic-raspi user.info kernel: [   67.933360] eq3loop: eq3loop_open_slave() ttyS0
Nov  6 11:46:55 homematic-raspi user.notice kernel: [   67.937394] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x5459
Nov  6 11:46:55 homematic-raspi user.notice kernel: [   67.937415] eq3loop: eq3loop_ioctl_slave() ttyS0: unhandled ioctl 0x545D
Nov  6 11:47:08 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:08 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:08 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:08 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:09 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:10 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:10 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:10 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:10 homematic-raspi user.info kernel: [   82.819802] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
Nov  6 11:47:10 homematic-raspi user.info kernel: [   82.885535] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
Nov  6 11:47:10 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:11 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:11 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:11 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:11 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:11 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:11 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:11 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:11 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:11 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:11 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:11 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:11 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:11 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:12 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:12 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:12 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:12 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:13 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:14 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:14 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:14 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:14 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:14 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:14 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:14 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:14 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:14 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:14 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:14 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:14 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:14 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:15 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:15 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:15 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:15 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:16 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:16 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:16 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:16 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:17 homematic-raspi local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [iseXmlRpc.h:281]
Nov  6 11:47:17 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","1009"} result= nil [iseXmlRpc.cpp:2612]
Nov  6 11:47:17 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [iseXmlRpc.cpp:1204]
Nov  6 11:47:17 homematic-raspi local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=System [iseRTHss.cpp:163]
Nov  6 11:47:17 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:18 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:18 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:18 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:18 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"FEQ0045930:16","STATE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:18 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Nov  6 11:47:18 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Nov  6 11:47:18 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:18 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:19 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:19 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:19 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:19 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:19 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:17","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:19 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:19 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:17 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:20 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:20 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:20 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:20 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=LEVEL failed getting physical value.
Nov  6 11:47:20 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"HEQ0482880:3","LEVEL"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:20 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Nov  6 11:47:20 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [iseDOMdpHSS.cpp:130]
Nov  6 11:47:21 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:22 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:22 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:22 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:22 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:22 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:22 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:16","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:22 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:22 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:16 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:22 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:23 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:23 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:23 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =getValue Params = {"HEQ0241105:17","STATE"} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:23 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1432]
Nov  6 11:47:23 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [iseDOMdpHSS.cpp:130]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:13","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:13 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:23 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:23 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:14","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:14 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:23 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:23 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:19","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:23 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:19 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:23 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:24 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:24 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:24 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:24 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0046001:15","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:24 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:24 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0046001:15 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:25 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:25 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:25 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:25 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:26 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:27 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:27 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:27 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:27 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0046001:17","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:27 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:27 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0046001:17 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:27 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:28 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:28 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:28 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:28 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:15","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:28 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:28 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:15 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:28 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:29 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:29 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:29 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:30 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:30 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:30 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:30 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:30 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0045930:17","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:30 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:30 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0045930:17 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:31 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:32 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:32 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:32 homematic-raspi user.err hs485d: HSSParameter::SetValue() false Put failed
Nov  6 11:47:32 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"FEQ0046001:18","STATE",false} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:32 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:32 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = FEQ0046001:18 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:32 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:33 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:33 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:33 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:33 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:34 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:34 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:34 homematic-raspi user.err hs485d: HSSParameter::SetValue() 1.000000 Put failed
Nov  6 11:47:34 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"HEQ0483022:3","LEVEL",1.000000} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:34 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:34 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = HEQ0483022:3 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:35 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:35 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:35 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:35 homematic-raspi user.err hs485d: HSSParameter::SetValue() 1.000000 Put failed
Nov  6 11:47:35 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"HEQ0482964:3","LEVEL",1.000000} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:35 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:35 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = HEQ0482964:3 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:36 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:36 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:36 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:36 homematic-raspi user.err hs485d: HSSParameter::SetValue() 1.000000 Put failed
Nov  6 11:47:36 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"HEQ0482944:3","LEVEL",1.000000} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:36 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:36 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = HEQ0482944:3 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:37 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:38 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:38 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::PutData SendMessage() failed
Nov  6 11:47:38 homematic-raspi user.err hs485d: HSSParameter::SetValue() 1.000000 Put failed
Nov  6 11:47:38 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute result isFault; method =setValue Params = {"HEQ0482959:3","LEVEL",1.000000} result= [faultCode:-1,faultString:"Failure"] [iseXmlRpc.cpp:2618]
Nov  6 11:47:38 homematic-raspi local0.err ReGaHss: Error: IseXmlRpc::CallSetValue: CallXmlrpcMethod failed [iseXmlRpc.cpp:1502]
Nov  6 11:47:38 homematic-raspi local0.err ReGaHss: Error: IseHssDP::WriteValue: CallSetValue failed; address = HEQ0482959:3 [iseDOMdpHSS.cpp:77]
Nov  6 11:47:39 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:39 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:39 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:39 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:40 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:40 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:40 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:40 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:40 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:40 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:40 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:40 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:40 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:40 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:40 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:40 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:40 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:40 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:41 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:42 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:42 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:42 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:43 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:43 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:43 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:43 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:43 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:43 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:43 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:43 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:43 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:43 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:43 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:43 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:43 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:43 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:44 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:44 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:44 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:44 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:45 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:46 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:46 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:46 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:46 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:47 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:47 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:47 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:48 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:48 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:48 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:48 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:49 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:50 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:50 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:50 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:50 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:51 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:51 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:51 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:52 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:52 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:52 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:52 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:53 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:54 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:54 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:54 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:54 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:55 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:55 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:55 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Nov  6 11:47:56 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:56 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:56 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:56 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:57 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:58 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:58 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:58 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:47:58 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:59 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:47:59 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:47:59 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:00 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:48:00 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:48:00 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:00 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:00 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:00 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:00 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:00 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:00 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:00 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:00 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:00 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:00 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:00 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:01 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:48:02 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:48:02 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:02 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:02 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:48:03 homematic-raspi user.err hs485d: LGW_RPL_ANSWER ERROR - request was 53
Nov  6 11:48:03 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:03 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:03 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:03 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:03 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:03 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:03 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:03 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:03 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:03 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.
Nov  6 11:48:03 homematic-raspi user.err hs485d: HS485PhysicalDataInterfaceCommand::GetData SendMessage failed for LEVEL_GET
Nov  6 11:48:03 homematic-raspi user.err hs485d: HSSParameter::GetValue() id=STATE failed getting physical value.

Antworten

Zurück zu „RaspberryMatic“