Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. CCU3 unreachable

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    CCU3 unreachable

    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Aidan last edited by

      Hallo zusammen,
      ich habe am Wochenende meinen Raspi geupdatet.
      Adapter + IObroker und System.
      Seit dem bekomme ich die Fehlermeldung:
      hm-rpc.2
      28255 2022-05-04 15:42:54.411 error Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

      hm-rpc.1
      28249 2022-05-04 15:42:54.411 error Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

      hm-rega.0
      925 2022-05-04 15:42:26.643 error CCU 192.168.178.51 unreachable

      hm-rpc.2
      4896 2022-05-04 15:42:15.207 error Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

      hm-rpc.1
      4903 2022-05-04 15:42:15.203 error Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

      hm-rega.0
      925 2022-05-04 15:41:53.523 error CCU 192.168.178.51 unreachable

      Das komische ist, dass z.B meine Astroschaltung abends anschaltet, aber um 23 Uhr nicht wieder aus.
      Im Board hatte ich gesucht und die CCU3 Firewall auf Vollzugriff gestellt. Dies bringt mir keine Besserung.

      Kennt jemand das Problem oder hat Lust es mit mir zu lösen?

      Homoran paul53 2 Replies Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @Aidan last edited by

        @aidan sagte in CCU3 unreachable:

        ich habe am Wochenende meinen Raspi geupdatet.

        welchen?
        Den für pihole?

        oder den für piVCCU/Raspberrymatic?

        A 1 Reply Last reply Reply Quote 0
        • A
          Aidan @Homoran last edited by

          @homoran: Bin mir nicht ganz sicher was du meinst.
          Ich habe nur einen Raspberry 4 mit Raspberry OS

          Homoran 1 Reply Last reply Reply Quote 0
          • paul53
            paul53 @Aidan last edited by

            @aidan sagte: CCU 192.168.178.51 unreachable

            Funktioniert vom RasPi ?

            ping 192.168.178.51
            A 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @Aidan last edited by

              @aidan sagte in CCU3 unreachable:

              Bin mir nicht ganz sicher was du meinst.

              ging mir genauso 😉

              aber die Fehler könnten auch bei Änderungen nach einem Update von CCU/RaspberryMatic o.ä. passiert sein

              A 1 Reply Last reply Reply Quote 0
              • A
                Aidan @paul53 last edited by Aidan

                @paul53 ja das geht vom Win Rechner
                Ping wird ausgeführt für 192.168.178.51 mit 32 Bytes Daten:
                Antwort von 192.168.178.51: Bytes=32 Zeit=5ms TTL=64
                Antwort von 192.168.178.51: Bytes=32 Zeit=1ms TTL=64
                Antwort von 192.168.178.51: Bytes=32 Zeit=1ms TTL=64
                Antwort von 192.168.178.51: Bytes=32 Zeit=2ms TTL=64

                Ping-Statistik für 192.168.178.51:
                Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
                (0% Verlust),
                Ca. Zeitangaben in Millisek.:
                Minimum = 1ms, Maximum = 5ms, Mittelwert = 2ms

                Hier vom Raspberry ( hört nur nicht auf zu pingen) -)


                64 bytes from 192.168.178.51: icmp_seq=17 ttl=64 time=2.40 ms
                64 bytes from 192.168.178.51: icmp_seq=18 ttl=64 time=1.85 ms
                64 bytes from 192.168.178.51: icmp_seq=19 ttl=64 time=1.36 ms
                64 bytes from 192.168.178.51: icmp_seq=20 ttl=64 time=1.62 ms
                64 bytes from 192.168.178.51: icmp_seq=21 ttl=64 time=1.33 ms
                64 bytes from 192.168.178.51: icmp_seq=22 ttl=64 time=1.53 ms
                64 bytes from 192.168.178.51: icmp_seq=23 ttl=64 time=1.60 ms

                1 Reply Last reply Reply Quote 0
                • A
                  Aidan @Homoran last edited by

                  @homoran da gab es auch eine neue Version aktuell ist die aktuelle Firmwareversion: 3.63.8 auf der CCU3 installiert

                  A 1 Reply Last reply Reply Quote 0
                  • A
                    Aidan @Aidan last edited by

                    @aidan said in CCU3 unreachable:

                    @homoran da gab es auch eine neue Version aktuell ist die aktuelle Firmwareversion: 3.63.8 auf der CCU3 installiert

                    Nachtrag:
                    Ich habe mal die Firmware 3,61.7 und das Backup installiert.
                    gerade zeigt mir die Log keinen Fehler mehr an.
                    Ich werde den morgigen Tag einmal abwarten ob sich neue Abgründe auftun-)
                    Ich werde berichten.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      Aidan @Aidan last edited by

                      ok, das war es nicht


                      hm-rega.0
                      14331 2022-05-04 20:01:35.284 error CCU 192.168.178.51 unreachable

                      hm-rega.0
                      14331 2022-05-04 20:01:35.283 error post request error: connect EHOSTUNREACH 192.168.178.51:8181

                      hm-rpc.2
                      21351 2022-05-04 20:01:30.414 error Ping error [raspberrypi:hm-rpc.2:ed6329769c4ff5518f4841af0f435448]: connect EHOSTUNREACH 192.168.178.51:2010

                      Homoran 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @Aidan last edited by

                        @aidan dann einmal ccu neustarten und bei erneutem Fehler dort mal im syslog nachsehen.

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          Aidan @Homoran last edited by

                          @homoran Moin, das scheint ein sporadischer Fehler zu sein. Ich hatte gestern, nach meinem letzten Post die CCU und Raspi neu gestartet. Heute Morgen war noch kein Fehler vorhanden.

                          Homoran 1 Reply Last reply Reply Quote 0
                          • Homoran
                            Homoran Global Moderator Administrators @Aidan last edited by

                            @aidan sagte in CCU3 unreachable:

                            das scheint ein sporadischer Fehler zu sein

                            kommt darauf an wie du das definierst.

                            Möglicherweise hat sich etwas auf der CCU verbogen und ioBroker kommt nicht mehr drauf.
                            Da wäre es interessant die Ursache davon im CCU-Log zu finden.

                            A 1 Reply Last reply Reply Quote 0
                            • A
                              Aidan @Homoran last edited by

                              @homoran : Jopp, bis jetzt kein weiterer Fehler. Wenn er wieder auftreten sollte, poste ich die Log-File der CCU.

                              A 1 Reply Last reply Reply Quote 0
                              • A
                                Aidan @Aidan last edited by

                                heute war es dann wieder soweit:

                                syslog

                                
1
PID
Zeit
error
Nachricht

hm-rega.0
14423	2022-05-31 16:40:16.447	error	CCU 192.168.178.51 unreachable

hm-rpc.2
3588	2022-05-31 16:40:04.282	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
3595	2022-05-31 16:40:04.282	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rega.0
14423	2022-05-31 16:39:46.439	error	CCU 192.168.178.51 unreachable

hm-rpc.1
3595	2022-05-31 16:39:34.294	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
3588	2022-05-31 16:39:34.294	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:39:13.320	error	CCU 192.168.178.51 unreachable

hm-rpc.1
3342	2022-05-31 16:38:56.362	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
3350	2022-05-31 16:38:56.362	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:38:40.200	error	CCU 192.168.178.51 unreachable

hm-rpc.1
3342	2022-05-31 16:38:26.373	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
3350	2022-05-31 16:38:26.373	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:38:07.080	error	CCU 192.168.178.51 unreachable

hm-rpc.1
3169	2022-05-31 16:37:48.603	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
3160	2022-05-31 16:37:48.603	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:37:33.960	error	CCU 192.168.178.51 unreachable

hm-rpc.2
3160	2022-05-31 16:37:18.615	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
3169	2022-05-31 16:37:18.615	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rega.0
14423	2022-05-31 16:37:00.840	error	CCU 192.168.178.51 unreachable

hm-rpc.1
2975	2022-05-31 16:36:40.681	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
2981	2022-05-31 16:36:40.681	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:36:27.720	error	CCU 192.168.178.51 unreachable

hm-rpc.1
2975	2022-05-31 16:36:10.693	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
2981	2022-05-31 16:36:10.692	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:35:54.600	error	CCU 192.168.178.51 unreachable

hm-rpc.1
12700	2022-05-31 16:35:32.680	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
12709	2022-05-31 16:35:32.680	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
14423	2022-05-31 16:35:21.480	error	CCU 192.168.178.51 unreachable

hm-rpc.2
12709	2022-05-31 16:35:02.680	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
12700	2022-05-31 16:35:02.680	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rega.0
14423	2022-05-31 16:34:48.360	error	CCU 192.168.178.51 unreachable

hm-rpc.2
12709	2022-05-31 16:34:29.494	error	Ping error [raspberrypi:hm-rpc.2:abe1359247c4adc29db79c86707719c5]: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
12700	2022-05-31 16:34:29.494	error	Ping error [raspberrypi:hm-rpc.1:eb2c958ba10c08de91b48fb6a857c852]: connect EHOSTUNREACH 192.168.178.51:2001

hm-rega.0
14423	2022-05-31 16:34:15.255	error	CCU 192.168.178.51 unreachable

hm-rega.0
14423	2022-05-31 16:34:15.240	error	post request error: connect EHOSTUNREACH 192.168.178.51:8181

                                Danach ist alles wie vorher, als ob nichts gewesen wäre.

                                Die Log von der CCU3 ist leer, habe allerdings nur folgende Haken gesetzt:
                                a6cac3e2-86bf-4063-9255-435d415bff79-image.png
                                bae76600-874c-4124-8cab-bb743989ffe6-image.png

                                Die verbundenen Geräte logge ich nicht mit.

                                A 1 Reply Last reply Reply Quote 0
                                • A
                                  Aidan @Aidan last edited by

                                  Und ein weiteres Mal

                                  Systemlog: syslog

                                  
hm-rpc.1
26121	2022-06-02 06:41:23.635	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rpc.2
26142	2022-06-02 06:41:23.634	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rega.0
766	2022-06-02 06:41:09.228	error	CCU 192.168.178.51 unreachable

hm-rpc.2
1818	2022-06-02 06:40:49.309	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
1803	2022-06-02 06:40:46.189	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rega.0
766	2022-06-02 06:40:36.120	error	CCU 192.168.178.51 unreachable

hm-rpc.2
1818	2022-06-02 06:40:19.308	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
1803	2022-06-02 06:40:16.188	error	Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001

hm-rega.0
766	2022-06-02 06:40:02.920	error	CCU 192.168.178.51 unreachable

hm-rega.0
766	2022-06-02 06:40:02.919	error	post request error: connect EHOSTUNREACH 192.168.178.51:8181

hm-rpc.2
1818	2022-06-02 06:39:46.274	error	Ping error [raspberrypi:hm-rpc.2:235f817ee7508a7fbc04c50e7a9e9b14]: connect EHOSTUNREACH 192.168.178.51:2010

hm-rpc.1
1803	2022-06-02 06:39:43.080	error	Ping error [raspberrypi:hm-rpc.1:062653ddb00e4a91c7a81c648f6cfffa]: connect EHOSTUNREACH 192.168.178.51:2001

                                  CCU3 Log leer, passt meine Einstellung um einen möglichen Fehler zu loggen?

                                  Fritzbox: alles schön!

                                  
Alle
02.06.22
06:57:58
Anmeldung an der FRITZ!Box-Benutzeroberfläche von IP-Adresse 
01.06.22
11:40:05
IPv6-Präfix wurde erfolgreich aktualisiert. Neues Präfix: 
01.06.22
08:19:21
Anmeldung an der FRITZ!Box-Benutzeroberfläche von IP-Adresse 
01.06.22

                                  Irgendjemand eine Idee?

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    Aidan @Aidan last edited by

                                    Ein paar mehr Infos Log Iobroker

                                    2022-06-02 06:35:13.052 - info: javascript.0 (706) script.js.common.Windrichtung: SW
2022-06-02 06:38:01.341 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:38:01.342 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:39:15.172 - warn: daikin-cloud.0 (1305) d421e0fa-5181-46d2-a29b-480607735929: Error on device update (1): outgoing request timed out after 10000ms
2022-06-02 06:39:15.398 - warn: daikin-cloud.0 (1305) e4a3a2ad-8e6d-42ec-8a35-44c7f47c96b9: Error on device update (1): outgoing request timed out after 10000ms
2022-06-02 06:39:15.629 - warn: daikin-cloud.0 (1305) 47fdf1b9-7224-440a-8b06-80727e9dff25: Error on device update (1): outgoing request timed out after 10000ms
2022-06-02 06:39:15.723 - warn: daikin-cloud.0 (1305) 95ad2a30-7564-4599-987c-8410930ca442: Error on device update (1): outgoing request timed out after 10000ms
2022-06-02 06:39:25.140 - warn: hm-rega.0 (766) Script "!# pollingInv.fn 0.2 !# !# Dieses Script gibt die Systemvariablen (inklusive uns" ignored, because still pending.
2022-06-02 06:39:25.153 - warn: hm-rega.0 (766) Script "!# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin" ignored, because still pending.
2022-06-02 06:39:43.080 - error: hm-rpc.1 (1803) Ping error [raspberrypi:hm-rpc.1:062653ddb00e4a91c7a81c648f6cfffa]: connect EHOSTUNREACH 192.168.178.51:2001
2022-06-02 06:39:43.099 - info: hm-rpc.1 (1803) Disconnected
2022-06-02 06:39:46.274 - error: hm-rpc.2 (1818) Ping error [raspberrypi:hm-rpc.2:235f817ee7508a7fbc04c50e7a9e9b14]: connect EHOSTUNREACH 192.168.178.51:2010
2022-06-02 06:39:46.286 - info: hm-rpc.2 (1818) Disconnected
2022-06-02 06:39:55.139 - warn: hm-rega.0 (766) Script "!# pollingInv.fn 0.2 !# !# Dieses Script gibt die Systemvariablen (inklusive uns" ignored, because still pending.
2022-06-02 06:39:55.140 - warn: hm-rega.0 (766) Script "!# programs.fn 1.3 !# Dieses Script gibt eine Liste der Programme als JSON Strin" ignored, because still pending.
2022-06-02 06:40:02.919 - error: hm-rega.0 (766) post request error: connect EHOSTUNREACH 192.168.178.51:8181
2022-06-02 06:40:02.920 - error: hm-rega.0 (766) CCU 192.168.178.51 unreachable
2022-06-02 06:40:16.188 - error: hm-rpc.1 (1803) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001
2022-06-02 06:40:19.308 - error: hm-rpc.2 (1818) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010
2022-06-02 06:40:25.177 - warn: daikin-cloud.0 (1305) d421e0fa-5181-46d2-a29b-480607735929: Error on device update (2): outgoing request timed out after 10000ms
2022-06-02 06:40:25.402 - warn: daikin-cloud.0 (1305) e4a3a2ad-8e6d-42ec-8a35-44c7f47c96b9: Error on device update (2): outgoing request timed out after 10000ms
2022-06-02 06:40:25.633 - warn: daikin-cloud.0 (1305) 47fdf1b9-7224-440a-8b06-80727e9dff25: Error on device update (2): outgoing request timed out after 10000ms
2022-06-02 06:40:25.728 - warn: daikin-cloud.0 (1305) 95ad2a30-7564-4599-987c-8410930ca442: Error on device update (2): outgoing request timed out after 10000ms
2022-06-02 06:40:36.120 - error: hm-rega.0 (766) CCU 192.168.178.51 unreachable
2022-06-02 06:40:46.189 - error: hm-rpc.1 (1803) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001
2022-06-02 06:40:46.192 - info: hm-rpc.1 (1803) xmlrpc -> 192.168.178.51:2001/ init ["http://192.168.178.46:2001",""]
2022-06-02 06:40:47.199 - info: hm-rpc.1 (1803) terminating
2022-06-02 06:40:47.200 - info: hm-rpc.1 (1803) Terminated (NO_ERROR): Without reason
2022-06-02 06:40:47.905 - info: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR)
2022-06-02 06:40:47.906 - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled
2022-06-02 06:40:49.309 - error: hm-rpc.2 (1818) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010
2022-06-02 06:40:49.313 - info: hm-rpc.2 (1818) xmlrpc -> 192.168.178.51:2010/ init ["http://192.168.178.46:2010",""]
2022-06-02 06:40:50.321 - info: hm-rpc.2 (1818) terminating
2022-06-02 06:40:50.323 - info: hm-rpc.2 (1818) Terminated (NO_ERROR): Without reason
2022-06-02 06:40:50.976 - info: host.raspberrypi instance system.adapter.hm-rpc.2 terminated with code 0 (NO_ERROR)
2022-06-02 06:40:50.977 - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.2 because enabled
2022-06-02 06:41:09.228 - error: hm-rega.0 (766) CCU 192.168.178.51 unreachable
2022-06-02 06:41:18.075 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 26121
2022-06-02 06:41:20.277 - info: hm-rpc.1 (26121) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.20.0, js-controller: 4.0.23
2022-06-02 06:41:20.471 - info: hm-rpc.1 (26121) xmlrpc server is trying to listen on 192.168.178.46:2001
2022-06-02 06:41:20.472 - info: hm-rpc.1 (26121) xmlrpc client is trying to connect to 192.168.178.51:2001/ with ["http://192.168.178.46:2001","raspberrypi:hm-rpc.1:0552f675f20b987054b827e65032c127"]
2022-06-02 06:41:21.073 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 26142
2022-06-02 06:41:23.239 - info: hm-rpc.2 (26142) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.20.0, js-controller: 4.0.23
2022-06-02 06:41:23.494 - info: hm-rpc.2 (26142) xmlrpc server is trying to listen on 192.168.178.46:2010
2022-06-02 06:41:23.495 - info: hm-rpc.2 (26142) xmlrpc client is trying to connect to 192.168.178.51:2010/ with ["http://192.168.178.46:2010","raspberrypi:hm-rpc.2:82a5faaa91f28255d655c231561ce10b"]
2022-06-02 06:41:23.634 - error: hm-rpc.2 (26142) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2010
2022-06-02 06:41:23.635 - error: hm-rpc.1 (26121) Init not possible, going to stop: connect EHOSTUNREACH 192.168.178.51:2001
2022-06-02 06:41:30.904 - info: hm-rpc.2 (26142) Connected
2022-06-02 06:41:35.182 - warn: daikin-cloud.0 (1305) d421e0fa-5181-46d2-a29b-480607735929: Error on device update (3): outgoing request timed out after 10000ms
2022-06-02 06:41:39.277 - info: hm-rega.0 (766) ReGaHSS 192.168.178.51 up
2022-06-02 06:41:39.298 - info: hm-rega.0 (766) time difference local-ccu 0s
2022-06-02 06:41:40.134 - info: hm-rega.0 (766) request state values
2022-06-02 06:41:41.953 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:41:41.953 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:41:42.315 - info: hm-rega.0 (766) Updated all datapoints
2022-06-02 06:41:42.329 - info: hm-rega.0 (766) got 33 variables
2022-06-02 06:41:42.452 - info: hm-rega.0 (766) added/updated 33 variables
2022-06-02 06:41:42.452 - info: hm-rega.0 (766) deleted 0 variables
2022-06-02 06:41:42.465 - info: hm-rega.0 (766) got 3 programs
2022-06-02 06:41:42.478 - info: hm-rega.0 (766) added/updated 3 programs
2022-06-02 06:41:42.478 - info: hm-rega.0 (766) deleted 0 programs
2022-06-02 06:41:42.497 - info: hm-rega.0 (766) update rooms to enum.rooms
2022-06-02 06:41:42.654 - info: hm-rega.0 (766) update functions to enum.functions
2022-06-02 06:41:42.814 - info: hm-rega.0 (766) update favorites to enum.favorites
2022-06-02 06:41:50.519 - info: hm-rpc.1 (26121) xmlrpc <- system.listMethods ["raspberrypi:hm-rpc.1:0552f675f20b987054b827e65032c127"]
2022-06-02 06:41:50.532 - info: hm-rpc.1 (26121) xmlrpc <- listDevices ["raspberrypi:hm-rpc.1:0552f675f20b987054b827e65032c127"]
2022-06-02 06:41:50.647 - info: hm-rpc.1 (26121) xmlrpc -> 110 devices
2022-06-02 06:41:50.706 - info: hm-rpc.1 (26121) Connected
2022-06-02 06:41:53.636 - info: hm-rpc.2 (26142) xmlrpc -> 192.168.178.51:2010/ init ["http://192.168.178.46:2010",""]
2022-06-02 06:41:53.637 - info: hm-rpc.1 (26121) xmlrpc -> 192.168.178.51:2001/ init ["http://192.168.178.46:2001",""]
2022-06-02 06:41:53.655 - info: hm-rpc.1 (26121) Disconnected
2022-06-02 06:41:53.666 - info: hm-rpc.1 (26121) terminating
2022-06-02 06:41:53.669 - info: hm-rpc.1 (26121) Terminated (NO_ERROR): Without reason
2022-06-02 06:41:53.709 - info: hm-rpc.2 (26142) Disconnected
2022-06-02 06:41:53.718 - info: hm-rpc.2 (26142) terminating
2022-06-02 06:41:53.721 - info: hm-rpc.2 (26142) Terminated (NO_ERROR): Without reason
2022-06-02 06:41:54.330 - info: host.raspberrypi instance system.adapter.hm-rpc.1 terminated with code 0 (NO_ERROR)
2022-06-02 06:41:54.331 - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.1 because enabled
2022-06-02 06:41:54.473 - info: host.raspberrypi instance system.adapter.hm-rpc.2 terminated with code 0 (NO_ERROR)
2022-06-02 06:41:54.475 - info: host.raspberrypi Restart adapter system.adapter.hm-rpc.2 because enabled
2022-06-02 06:42:24.600 - info: host.raspberrypi instance system.adapter.hm-rpc.1 started with pid 26287
2022-06-02 06:42:24.716 - info: host.raspberrypi instance system.adapter.hm-rpc.2 started with pid 26294
2022-06-02 06:42:27.103 - info: hm-rpc.1 (26287) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.20.0, js-controller: 4.0.23
2022-06-02 06:42:27.169 - info: hm-rpc.2 (26294) starting. Version 1.15.12 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.20.0, js-controller: 4.0.23
2022-06-02 06:42:27.334 - info: hm-rpc.1 (26287) xmlrpc server is trying to listen on 192.168.178.46:2001
2022-06-02 06:42:27.335 - info: hm-rpc.1 (26287) xmlrpc client is trying to connect to 192.168.178.51:2001/ with ["http://192.168.178.46:2001","raspberrypi:hm-rpc.1:5fc32bb5b4edd9186d7ab75520a98522"]
2022-06-02 06:42:27.379 - info: hm-rpc.1 (26287) xmlrpc <- system.listMethods ["raspberrypi:hm-rpc.1:5fc32bb5b4edd9186d7ab75520a98522"]
2022-06-02 06:42:27.391 - info: hm-rpc.1 (26287) xmlrpc <- listDevices ["raspberrypi:hm-rpc.1:5fc32bb5b4edd9186d7ab75520a98522"]
2022-06-02 06:42:27.422 - info: hm-rpc.2 (26294) xmlrpc server is trying to listen on 192.168.178.46:2010
2022-06-02 06:42:27.423 - info: hm-rpc.2 (26294) xmlrpc client is trying to connect to 192.168.178.51:2010/ with ["http://192.168.178.46:2010","raspberrypi:hm-rpc.2:9aae80f8693c08e066a472b917ffe8ea"]
2022-06-02 06:42:27.454 - info: hm-rpc.1 (26287) xmlrpc -> 110 devices
2022-06-02 06:42:27.471 - info: hm-rpc.2 (26294) Connected
2022-06-02 06:42:27.508 - info: hm-rpc.2 (26294) xmlrpc <- listDevices ["raspberrypi:hm-rpc.2:9aae80f8693c08e066a472b917ffe8ea"]
2022-06-02 06:42:27.517 - info: hm-rpc.1 (26287) Connected
2022-06-02 06:42:27.666 - info: hm-rpc.2 (26294) xmlrpc -> 0 devices
2022-06-02 06:42:28.866 - info: web.0 (1560) <== Disconnect system.user.admin from ::ffff:192.168.178.67 vis.0
2022-06-02 06:42:28.976 - info: hm-rpc.2 (26294) xmlrpc <- newDevices 276
2022-06-02 06:42:29.116 - info: hm-rpc.2 (26294) new HMIP devices/channels after filter: 0
2022-06-02 06:42:54.637 - info: javascript.0 (706) script.js.common.Windrichtung: SW
2022-06-02 06:42:54.638 - info: javascript.0 (706) script.js.common.Windrichtung: SW
2022-06-02 06:44:59.658 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:44:59.658 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:47:54.047 - info: javascript.0 (706) script.js.common.Windrichtung: W
2022-06-02 06:47:54.048 - info: javascript.0 (706) script.js.common.Windrichtung: W
2022-06-02 06:50:34.311 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:50:34.311 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:53:00.101 - info: javascript.0 (706) script.js.common.Windrichtung: NNO
2022-06-02 06:53:00.102 - info: javascript.0 (706) script.js.common.Windrichtung: NNO
2022-06-02 06:55:11.270 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:55:11.271 - info: javascript.0 (706) script.js.common.Windrichtung: WSW
2022-06-02 06:58:12.307 - info: javascript.0 (706) script.js.common.Windrichtung: SW
2022-06-02 06:58:12.308 - info: javascript.0 (706) script.js.common.Windrichtung: SW
2022-06-02 07:00:00.179 - info: host.raspberrypi instance system.adapter.tvspielfilm.0 started with pid 30701
2022-06-02 07:00:09.116 - info: host.raspberrypi instance system.adapter.ical.0 started with pid 30748
2022-06-02 07:00:13.431 - info: tvspielfilm.0 (30701) starting. Version 2.0.4 in /opt/iobroker/node_modules/iobroker.tvspielfilm, node: v12.20.0, js-controller: 4.0.23
2022-06-02 07:00:13.976 - info: ical.0 (30748) starting. Version 1.12.1 in /opt/iobroker/node_modules/iobroker.ical, node: v12.20.0, js-controller: 4.0.23
2022-06-02 07:00:15.447 - info: ical.0 (30748) processing URL: Mülltonnen https://calendar.google.com/calendar/ical/rj5a8dudqb86vj1lgp762upbco%40group.calendar.google.com/private-1a9c66362074c3e0500adb82cf90eb97/basic.ics
2022-06-02 07:00:15.590 - info: tvspielfilm.0 (30701) objects written
2022-06-02 07:00:20.794 - info: ical.0 (30748) Terminated (NO_ERROR): Without reason
2022-06-02 07:00:21.326 - info: host.raspberrypi instance system.adapter.ical.0 terminated with code 0 (NO_ERROR)
2022-06-02 07:00:26.105 - info: tvspielfilm.0 (30701) Terminated (NO_ERROR): Without reason
2022-06-02 07:00:26.642 - info: host.raspberrypi instance system.adapter.tvspielfilm.0 terminated with code 0 (NO_ERROR)
                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post

                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    826
                                    Online

                                    31.7k
                                    Users

                                    79.9k
                                    Topics

                                    1.3m
                                    Posts

                                    3
                                    16
                                    830
                                    Loading More Posts
                                    • Oldest to Newest
                                    • Newest to Oldest
                                    • Most Votes
                                    Reply
                                    • Reply as topic
                                    Log in to reply
                                    Community
                                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                    The ioBroker Community 2014-2023
                                    logo