CCU - Snapshotversand via Telegram bei Klingelsignalerkennung

User stellen ihre Haussteuerung vor

Moderator: Co-Administratoren

StephanBJ
Beiträge: 21
Registriert: 21.04.2019, 19:10
Hat sich bedankt: 2 Mal

Re: CCU - Snapshotversand via Telegram bei Klingelsignalerkennung

Beitrag von StephanBJ » 27.12.2020, 14:24

Hallo, bin jetzt erst wieder dazugekommen, mich darum zu kümmern.

im CuxD Fullsyslog steht:

Code: Alles auswählen

Dec 27 14:19:35 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
Dec 27 14:19:36 homematic-raspi local0.info ReGaHss: Info: start web processing, worker thread #0 {"HTTP-Listener"} [spawnNewProcess():httpListener.cpp:208]
Dec 27 14:19:36 homematic-raspi local0.info ReGaHss: Info: recvd 326 bytes by web server #1 [ThreadFunction():httpServer.cpp:797]
Dec 27 14:19:36 homematic-raspi local0.info ReGaHss: Info: IseSession GetSessionId from URL: /tclrega.exe [GetSessionId():iseSession.cpp:185]
Dec 27 14:19:36 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: start web processing, worker thread #0 {"HTTP-Listener"} [spawnNewProcess():httpListener.cpp:208]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: recvd 751 bytes by web server #1 [ThreadFunction():httpServer.cpp:797]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: IseSession GetSessionId from URL: /esp/[email protected]@&action=UpdateUI [GetSessionId():iseSession.cpp:185]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: start web processing, worker thread #0 {"HTTP-Listener"} [spawnNewProcess():httpListener.cpp:208]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: recvd 684 bytes by web server #1 [ThreadFunction():httpServer.cpp:797]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: IseSession GetSessionId from URL: /tclrega.exe [GetSessionId():iseSession.cpp:185]
Dec 27 14:19:37 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
Dec 27 14:19:40 homematic-raspi local0.info ReGaHss: Info: start web processing, worker thread #0 {"HTTP-Listener"} [spawnNewProcess():httpListener.cpp:208]
Dec 27 14:19:40 homematic-raspi local0.info ReGaHss: Info: recvd 751 bytes by web server #1 [ThreadFunction():httpServer.cpp:797]
Dec 27 14:19:40 homematic-raspi local0.info ReGaHss: Info: IseSession GetSessionId from URL: /esp/[email protected]@&action=UpdateUI [GetSessionId():iseSession.cpp:185]
Dec 27 14:19:40 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
Dec 27 14:19:42 homematic-raspi local0.info ReGaHss: Info: start web processing, worker thread #0 {"HTTP-Listener"} [spawnNewProcess():httpListener.cpp:208]
Dec 27 14:19:42 homematic-raspi local0.info ReGaHss: Info: recvd 326 bytes by web server #1 [ThreadFunction():httpServer.cpp:797]
Dec 27 14:19:42 homematic-raspi local0.info ReGaHss: Info: IseSession GetSessionId from URL: /tclrega.exe [GetSessionId():iseSession.cpp:185]
Dec 27 14:19:42 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
Dec 27 14:19:43 homematic-raspi local0.info ReGaHss: Info: start web processing, worker thread #0 {"HTTP-Listener"} [spawnNewProcess():httpListener.cpp:208]
Dec 27 14:19:43 homematic-raspi local0.info ReGaHss: Info: recvd 751 bytes by web server #1 [ThreadFunction():httpServer.cpp:797]
Dec 27 14:19:43 homematic-raspi local0.info ReGaHss: Info: IseSession GetSessionId from URL: /esp/[email protected]@&action=UpdateUI [GetSessionId():iseSession.cpp:185]
Dec 27 14:19:43 homematic-raspi local0.info ReGaHss: Info: http id #1 sends parsed file [ParseFileAndSendWebResponse():httpServer.cpp:2079]
In der CCU:

Code: Alles auswählen

Dec 27 14:21:00 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: 1 Accesspoints in Queue 
Dec 27 14:21:00 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 27 14:21:00 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 27 14:21:56 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:2098 
Dec 27 14:21:56 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-2] init finished 
Dec 27 14:21:56 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF 
Dec 27 14:21:56 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient HmIP-RF -> 263 device addresses will be added 


Gruß
Stephan

dtp
Beiträge: 9343
Registriert: 21.09.2012, 08:09
System: CCU
Wohnort: Stuttgart
Hat sich bedankt: 133 Mal
Danksagung erhalten: 289 Mal

Re: CCU - Snapshotversand via Telegram bei Klingelsignalerkennung

Beitrag von dtp » 01.01.2021, 17:51

StephanBJ hat geschrieben:
11.12.2020, 18:08
Kann mir jemand sagen wo der Fehler liegt?
Du darfst dir keinen Timer erzeugen. Du brauchst die Funktion Exec für den System-Gerätetyp.
2021-01-01 17-52-27.png
2021-01-01 17-52-27.png (13.41 KiB) 119 mal betrachtet
Wird häufig und gerne falsch gemacht.
CCU3 mit stets aktueller FW und den Addons "CUxD" und "Programmedrucken", ioBroker auf Synology DiskStation DS718+ im Docker-Container;
einige Projekte: zentrales Push-Nachrichten-Programm zPNP, DoorPi-Videotürsprechanlage, An- und Abwesenheitsdetektion per Haustürschloss, zentrales Programm zur Steuerung von Beschattungsgeräten zBSP.

StephanGJ
Beiträge: 1
Registriert: 26.06.2018, 12:45

Re: CCU - Snapshotversand via Telegram bei Klingelsignalerkennung

Beitrag von StephanGJ » 14.01.2021, 09:35

Ich werde es nachher mal probieren

Antworten

Zurück zu „Projektvorstellungen“