Erfahrungen mit RaspberryMatic 2.31.25.20180324

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

Moderatoren: jmaus, Co-Administratoren

Xfiles_de
Beiträge: 160
Registriert: 27.07.2016, 06:10
Hat sich bedankt: 2 Mal

Re: Erfahrungen mit RaspberryMatic 2.31.25.20180324

Beitrag von Xfiles_de » 23.04.2018, 13:55

Danke dir .
Habe es mir durch . Sehr interessant .
Und freue mich auf deine zukünftige Updates .

Eine kleine frage hätte ich noch :
Muss für der neue Funkmodul zwingend Raspberry Pi 3 sein ? Oder geht auch Raspberry Pi 2 Modell B sein ?



Gesendet mit Tapatalk

Benutzeravatar
jmaus
Beiträge: 9819
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 459 Mal
Danksagung erhalten: 1856 Mal
Kontaktdaten:

Re: Erfahrungen mit RaspberryMatic 2.31.25.20180324

Beitrag von jmaus » 23.04.2018, 14:17

Xfiles_de hat geschrieben: Muss für der neue Funkmodul zwingend Raspberry Pi 3 sein ? Oder geht auch Raspberry Pi 2 Modell B sein ?
Das wird auch mit einem RaspberryPi2 gehen und auch mit einem Pi Zero W oder mit einer Adapter Platine sogar an den alten RaspberryPi-Modellen die keine 40 Pin-Leiste haben.
RaspberryMatic 3.75.6.20240316 @ ProxmoxVE – ~200 Hm-RF/HmIP-RF/HmIPW Geräte + ioBroker + HomeAssistant – GitHub / Sponsors / PayPal / ☕️

Xfiles_de
Beiträge: 160
Registriert: 27.07.2016, 06:10
Hat sich bedankt: 2 Mal

Re: Erfahrungen mit RaspberryMatic 2.31.25.20180324

Beitrag von Xfiles_de » 23.04.2018, 14:40

Danke .

Da ich mit meinen Funkmodul der ersten Generation und deinen Raspberrymatic super zufrieden bin , sehe ich kein Handlungsbedarf :)

Gesendet mit Tapatalk

stylewalker
Beiträge: 13
Registriert: 20.01.2018, 23:49

Re: Erfahrungen mit RaspberryMatic 2.31.25.20180324

Beitrag von stylewalker » 23.04.2018, 22:11

jmaus hat geschrieben:
klana hat geschrieben: aus PocktControl:
Also das funktioniert nicht:
system.Exec("wget -q -O /dev/null '--post-data=" # msg # "' " # url # " &");

das schon:
system.Exec("wget -q -O /dev/null '--post-data=" # msg # "' " # url);
Was heisst hier „funktioniert nicht“? Im sinne von es kommt keine push meldung an oder im sinne von es kommt eine push meldung an aber im logfile finden sich diese mutex fehler?
Hallo Jens,

bei mir habe ich die gleiche Fehlermeldung beobachtet, nur dadurch bin ich auf diesen Post gestoßen. Die Auswirkungen waren jedoch etwas gravierender: Nach einer Menge an Push-Mitteilungen hat die CCU reproduzierbar blockiert, in dem Sinne, dass keine Ereignisse mehr verarbeitet wurden. Über ein Programm wurde bei mir eine Variable gesetzt, welches ein anderes Programm hätte triggern sollen. Dies ist dann nicht mehr erfolgt, nur ein Neustart hat Abhilfe geschaffen.

Ich habe das ganze dann im Log versucht nachzuvollziehen / zu separieren. Hier ein erfolgreiches Triggern zwischen den Programmen (inkl. mtxStaticIseEsp-Fehler):

Code: Alles auswählen

homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: called Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)' with valNew = '1' ; oidTrigger = 5256 [iseDOMPrg.cpp:478]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_CHANGE is set, trigger dp exists  [iseCondition.cpp:524]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 1 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseCondition.cpp:1112]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_TRUE is set. [iseCondition.cpp:1117]
homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [httpServer.cpp:2022]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_ONLY is set, condition = 1 [iseCondition.cpp:484]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 0 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 0 [iseCondition.cpp:1074]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 0 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:227]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:232]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, condition result = 0 [iseRule.cpp:235]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_CHANGE is set, trigger dp exists  [iseCondition.cpp:524]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 1 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseCondition.cpp:1112]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_TRUE is set. [iseCondition.cpp:1117]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_ONLY is set, condition = 1 [iseCondition.cpp:484]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 0 valR1 = 0 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:227]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:232]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, condition result = 1 [iseRule.cpp:235]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: sr = 7964, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:256]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: sr = 7964, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:261]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: Rule evaluated state is TRUE by Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)'; Destination ID = 7965 [iseDOMPrg.cpp:501]
homematic-raspi local0.info ReGaHss: Info: IseDOMPrg::SetState: Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)', rule's trigger flags = 4 [iseDOMPrg.cpp:515]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: execute Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)'; Destination ID = 7965 [iseDOMPrg.cpp:611]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: start execute Destination within the trigger delay 0 [iseDOMPrg.cpp:615]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::Add: added element - id= 5359; oid= 5359; val= 1; time= 0 [iseRTScheduler.cpp:369]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: pDest->ExecuteDestination succeeded from Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)' with valNew = '1' [iseDOMPrg.cpp:625]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::ExecuteWriteJob: try to call set state - DP id = 5359 value = 1 [iseRTScheduler.cpp:629]
homematic-raspi local0.debug ReGaHss: Verbose: EventThread::ThreadFunction: wait max timeout = 240000 [iseRTEvent.cpp:69]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::ExecuteWriteJob: set state - DP id = 5359 [iseRTScheduler.cpp:634]
homematic-raspi local0.debug ReGaHss: Verbose: EventThread::ThreadFunction: wait max timeout = 240000 [iseRTEvent.cpp:69]
homematic-raspi local0.debug ReGaHss: Verbose: SchedulerRT::Execute -> ExecuteWriteJob: oid = 5359; ticks = 1 [iseRTScheduler.cpp:591]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: called Program ID = 5766 'Watchdog (Huellenschutz Benachrichtigung)' with valNew = '1' ; oidTrigger = 5359 [iseDOMPrg.cpp:478]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::ThreadFunction(): wait for event ms= 4294967295 [iseRTScheduler.cpp:481]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_CHANGE is set, trigger dp exists  [iseCondition.cpp:524]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 1 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseCondition.cpp:1112]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_TRUE is set. [iseCondition.cpp:1117]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_ONLY is set, condition = 1 [iseCondition.cpp:484]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = DP_VALUE_IN_RANGE, condition valL = 0 valR1 = 0 valR2 = 0 [iseCondition.cpp:370]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:227]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:232]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, condition result = 1 [iseRule.cpp:235]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: Rule evaluated state is TRUE by Program ID = 5766 'Watchdog (Huellenschutz Benachrichtigung)'; Destination ID = 5768 [iseDOMPrg.cpp:501]
homematic-raspi local0.info ReGaHss: Info: IseDOMPrg::SetState: Program ID = 5766 'Watchdog (Huellenschutz Benachrichtigung)', rule's trigger flags = 4 [iseDOMPrg.cpp:515]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: execute Program ID = 5766 'Watchdog (Huellenschutz Benachrichtigung)'; Destination ID = 5768 [iseDOMPrg.cpp:611]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: start execute Destination within the trigger delay 0 [iseDOMPrg.cpp:615]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::Add: added element - id= 4806; oid= 4806; val= H�llenschutz aktiviert; time= 0 [iseRTScheduler.cpp:369]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: pDest->ExecuteDestination succeeded from Program ID = 5766 'Watchdog (Huellenschutz Benachrichtigung)' with valNew = '1' [iseDOMPrg.cpp:625]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::ExecuteWriteJob: try to call set state - DP id = 4806 value = H�llenschutz aktiviert [iseRTScheduler.cpp:629]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::ExecuteWriteJob: set state - DP id = 4806 [iseRTScheduler.cpp:634]
homematic-raspi local0.debug ReGaHss: Verbose: SchedulerRT::Execute -> ExecuteWriteJob: oid = 4806; ticks = 1 [iseRTScheduler.cpp:591]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: called Program ID = 4807 'Push Script for pocket control' with valNew = 'H�llenschutz aktiviert' ; oidTrigger = 4806 [iseDOMPrg.cpp:478]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::ThreadFunction(): wait for event ms= 4294967295 [iseRTScheduler.cpp:481]
homematic-raspi local0.debug ReGaHss: Verbose: EventThread::ThreadFunction: wait max timeout = 240000 [iseRTEvent.cpp:69]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_UPDATE is set, trigger dp exists  [iseCondition.cpp:500]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_UPDATE is set, condition = 1 [iseCondition.cpp:506]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = DP_VALUE_IN_RANGE_FROM_TO, condition valL = H�llenschutz aktiviert valR1 =  valR2 =  [iseCondition.cpp:355]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_TRUE is set. [iseCondition.cpp:1117]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, condition result = 0 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:232]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, condition result = 0 [iseRule.cpp:235]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: Rule evaluated state is TRUE by Program ID = 4807 'Push Script for pocket control'; Destination ID = 4818 [iseDOMPrg.cpp:501]
homematic-raspi local0.info ReGaHss: Info: IseDOMPrg::SetState: Program ID = 4807 'Push Script for pocket control', rule's trigger flags = 6 [iseDOMPrg.cpp:515]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: execute Program ID = 4807 'Push Script for pocket control'; Destination ID = 4818 [iseDOMPrg.cpp:611]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: start execute Destination within the trigger delay 0 [iseDOMPrg.cpp:615]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::Add: added script element - id= 4818; time= 0 [iseRTScheduler.cpp:343]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: pDest->ExecuteDestination succeeded from Program ID = 4807 'Push Script for pocket control' with valNew = 'H�llenschutz aktiviert' [iseDOMPrg.cpp:625]
homematic-raspi local0.err ReGaHss: Error: Failed to close mutex 'mtxStaticIseEsp'! [iseSysLx.cpp:123]
homematic-raspi local0.info ReGaHss: Info: IsePersist::ExecProcess = 'wget -q -O /dev/null '--post-data=ccuid=XXX&push=H�llenschutz%20aktiviert%20' http://push.pocket-control.com:9325 &' returned 0 [iseDOMpersist.cpp:384]
Nach mehrmaligen Aufrufen, erfolgte irgendwann die Blockade. Das zugehörige Log zeigte nur noch das Auslösen des ersten Programms, das Folgeprogramm wurde nicht mehr getriggert:

Code: Alles auswählen

homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: called Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)' with valNew = '1' ; oidTrigger = 5256 [iseDOMPrg.cpp:478]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_CHANGE is set, trigger dp exists  [iseCondition.cpp:524]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 1 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseCondition.cpp:1112]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_TRUE is set. [iseCondition.cpp:1117]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_ONLY is set, condition = 1 [iseCondition.cpp:484]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 0 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 0 [iseCondition.cpp:1074]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 0 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:227]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:232]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, condition result = 0 [iseRule.cpp:235]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_CHANGE is set, trigger dp exists  [iseCondition.cpp:524]
homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [httpServer.cpp:2022]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 1 valR1 = 1 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseCondition.cpp:1112]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, CONDITION_TRIGGER_TRUE is set. [iseCondition.cpp:1117]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 0, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: DP_VALUE_CHECK_ONLY is set, condition = 1 [iseCondition.cpp:484]
homematic-raspi local0.debug ReGaHss: Verbose: IseSingleCondition::Evaluate: type = 1, condition valL = 0 valR1 = 0 [iseCondition.cpp:388]
homematic-raspi local0.debug ReGaHss: Verbose: IseCondition::Evaluate: sc = 1, condition result = 1 [iseCondition.cpp:1119]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:227]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:232]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: c = 0, condition result = 1 [iseRule.cpp:235]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: sr = 7964, CONDITION_TRIGGER_EXECUTE is reset. [iseRule.cpp:256]
homematic-raspi local0.debug ReGaHss: Verbose: EventThread::ThreadFunction: wait max timeout = 240000 [iseRTEvent.cpp:69]
homematic-raspi local0.debug ReGaHss: Verbose: IseRule::Evaluate: sr = 7964, CONDITION_TRIGGER_TRUE is set. [iseRule.cpp:261]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::SetState: Rule evaluated state is TRUE by Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)'; Destination ID = 7965 [iseDOMPrg.cpp:501]
homematic-raspi local0.info ReGaHss: Info: IseDOMPrg::SetState: Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)', rule's trigger flags = 4 [iseDOMPrg.cpp:515]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: execute Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)'; Destination ID = 7965 [iseDOMPrg.cpp:611]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: start execute Destination within the trigger delay 0 [iseDOMPrg.cpp:615]
homematic-raspi local0.info ReGaHss: Info: SchedulerRT::Add: added element - id= 5359; oid= 5359; val= 1; time= 0 [iseRTScheduler.cpp:369]
homematic-raspi local0.debug ReGaHss: Verbose: IseDOMPrg::Execute: pDest->ExecuteDestination succeeded from Program ID = 5686 'Funktion (Huellenschutz per Variable aktivieren)' with valNew = '1' [iseDOMPrg.cpp:625]
Über die Fehlermeldung bin ich schließlich auf diesen Post gestoßen. Nach entfernen des "&" hatte ich keine Probleme mehr und der Fehler ist nicht mehr aufgetreten. Aktuell sieht mein PocketControl-Script also wie folgt aus:

Code: Alles auswählen

!Version2
string mg = dom.GetObject(ID_SYSTEM_VARIABLES).Get("pocketControlPushMessage").Value();
string ccuid = dom.GetObject(ID_SYSTEM_VARIABLES).Get("pushCCUID").Value();
string msg="";
string part;
foreach(part, mg.Split(" ")) {
  msg = msg # part # '%20';
}
if (msg != "" && ccuid != "") {
  var url = "http://push.pocket-control.com:9325";
  msg = "ccuid=" # ccuid # "&push=" # msg;
  string stdout;
  string stderr;
  system.Exec("wget -q -O /dev/null '--post-data=" # msg  # "' " # url);
}
Gibt es schon ein Ticket auf Github (konnte keins finden)? Soll ich eins eröffnen?

Grüße,

Marvin

MathiasZ

Re: Erfahrungen mit RaspberryMatic 2.31.25.20180324

Beitrag von MathiasZ » 24.04.2018, 22:33

Das neue Funkmodul steht auf meiner Merkliste ganz oben.
Wenn es dann lieferbar ist, werde ich auch den Raspberry PI 3B+ in Betrieb nehmen.
Sind Gerätegruppen bei HMIP-Geräten geplant?
Ich soll eine kpl. Neuinstallation ausschliesslich mit HMIP-Geräte machen.
Das heisst, Heizung und Verschluss.
Licht evtl Philips HUE.
Gruß, Mathias

Gesendet von meinem SM-N915FY mit Tapatalk

Benutzeravatar
jmaus
Beiträge: 9819
Registriert: 17.02.2015, 14:45
System: Alternative CCU (auf Basis OCCU)
Wohnort: Dresden
Hat sich bedankt: 459 Mal
Danksagung erhalten: 1856 Mal
Kontaktdaten:

Re: Erfahrungen mit RaspberryMatic 2.31.25.20180324

Beitrag von jmaus » 28.04.2018, 12:05

Hier geht es weiter mit dem Erfahrungen-Beitrag für die soeben neu releaste Version 2.31.25.20180428:

viewtopic.php?f=65&t=43425#p433199

Viel Spass!
RaspberryMatic 3.75.6.20240316 @ ProxmoxVE – ~200 Hm-RF/HmIP-RF/HmIPW Geräte + ioBroker + HomeAssistant – GitHub / Sponsors / PayPal / ☕️

Gesperrt

Zurück zu „RaspberryMatic“