Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Visualisierung
    4. Vis kennt keine Homematic-Geräte

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Vis kennt keine Homematic-Geräte

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

      Neustart mache Ich heute abend. Bis später 🙂

      1 Reply Last reply Reply Quote 0
      • C
        Communicate last edited by

        So, Neustart durchgeführt.

        Jetzt kann ich weder das Admin noch das bis webinterdace mehr aufrufen. Per ssh komme ich aber ohne Probleme auf den raspi. Was kann ich tun!
        1917_sonos_ger_te_in_verbindung_mit_alexa_und_iobroker_steuern.docx

        1 Reply Last reply Reply Quote 0
        • Bluefox
          Bluefox last edited by

          @Communicate:

          So, Neustart durchgeführt.

          Jetzt kann ich weder das Admin noch das bis webinterdace mehr aufrufen. Per ssh komme ich aber ohne Probleme auf den raspi. Was kann ich tun! `
          Checken ob ioBroker überhaupt läuft:

          ps -A | grep io
          1 Reply Last reply Reply Quote 0
          • C
            Communicate last edited by

            Hi,

            das kommt daraus:

            pi@raspberrypi ~ $ ps -A | grep io
   17 ?        00:00:00 bioset
   20 ?        00:00:00 rpciod
   23 ?        00:00:00 nfsiod
   35 ?        00:00:00 DWC Notificatio
 2048 ?        00:00:52 io.js-controlle
 2191 ?        00:00:51 io.admin.0
 2309 ?        00:00:15 io.web.0
 2356 ?        00:01:49 io.hm-rega.0
 2357 ?        00:00:10 io.hm-rpc.0

            EDIT:

            Ein Versuch iobroker zu starten sagt folgendes:

            pi@raspberrypi /opt/iobroker $ sudo ./iobroker start
ioBroker controller daemon already running. PID: 2048
            1 Reply Last reply Reply Quote 0
            • C
              Communicate last edited by

              Update:

              Jetzt kann ich Admin wieder aufrufen, warum auch immer…

              So sieht jetzt das Log aus:

              hm-rega-0	2015-06-24 17:56:17	warn	Pending request for more than 54675000 ms
hm-rega-0	2015-06-24 17:56:16	warn	Pending request for more than 54650000 ms
hm-rega-0	2015-06-24 17:56:16	warn	Pending request for more than 54625000 ms
hm-rega-0	2015-06-24 17:56:15	warn	Pending request for more than 54600000 ms
hm-rega-0	2015-06-24 17:56:14	warn	Pending request for more than 54575000 ms
hm-rega-0	2015-06-24 17:56:14	warn	Pending request for more than 54550000 ms
hm-rega-0	2015-06-24 17:56:13	warn	Pending request for more than 54525000 ms
hm-rega-0	2015-06-24 17:56:13	warn	Pending request for more than 54500000 ms
hm-rega-0	2015-06-24 17:56:12	warn	Pending request for more than 54475000 ms
hm-rega-0	2015-06-24 17:56:11	warn	Pending request for more than 54450000 ms
hm-rpc-0	2015-06-24 17:56:11	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:20011","hm-rpc.0"]
hm-rpc-0	2015-06-24 17:56:11	info	xmlrpc server is trying to listen on 192.168.178.49:20011
hm-rega-0	2015-06-24 17:56:11	warn	Pending request for more than 54425000 ms
hm-rega-0	2015-06-24 17:56:10	warn	Pending request for more than 54400000 ms
hm-rpc-0	2015-06-24 17:56:10	info	starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.hm-rpc
hm-rega-0	2015-06-24 17:56:10	warn	Pending request for more than 54375000 ms
hm-rpc-0	2015-06-24 17:56:09	debug	statesDB connected
hm-rpc-0	2015-06-24 17:56:09	debug	objectDB connected
hm-rega-0	2015-06-24 17:56:09	warn	Pending request for more than 54350000 ms
hm-rega-0	2015-06-24 17:56:08	warn	Pending request for more than 54325000 ms
hm-rega-0	2015-06-24 17:56:08	warn	Pending request for more than 54300000 ms
hm-rega-0	2015-06-24 17:56:07	warn	Pending request for more than 54275000 ms
hm-rega-0	2015-06-24 17:56:06	warn	Pending request for more than 54250000 ms
hm-rega-0	2015-06-24 17:56:06	warn	Pending request for more than 54225000 ms
hm-rega-0	2015-06-24 17:56:05	warn	Pending request for more than 54200000 ms
hm-rega-0	2015-06-24 17:56:05	warn	Pending request for more than 54175000 ms
hm-rega-0	2015-06-24 17:56:04	warn	Pending request for more than 54150000 ms
hm-rega-0	2015-06-24 17:56:03	warn	Pending request for more than 54125000 ms
host-raspberrypi	2015-06-24 17:56:03	info	instance system.adapter.hm-rpc.0 started with pid 2459
host-raspberrypi	2015-06-24 17:56:03	info	object change system.adapter.hm-rpc.0
hm-rega-0	2015-06-24 17:56:03	warn	Pending request for more than 54100000 ms
host-raspberrypi	2015-06-24 17:51:05	info	instance system.adapter.hm-rpc.0 started with pid 2454
host-raspberrypi	2015-06-24 17:51:05	info	object change system.adapter.hm-rpc.0
hm-rega-0	2015-06-24 17:51:05	warn	Pending request for more than 42525000 ms
hm-rega-0	2015-06-24 17:51:05	warn	Pending request for more than 42500000 ms
hm-rega-0	2015-06-24 17:51:04	warn	Pending request for more than 42475000 ms
hm-rega-0	2015-06-24 17:51:03	warn	Pending request for more than 42450000 ms
hm-rega-0	2015-06-24 17:51:03	warn	Pending request for more than 42425000 ms
hm-rega-0	2015-06-24 17:51:02	warn	Pending request for more than 42400000 ms
hm-rega-0	2015-06-24 17:51:01	warn	Pending request for more than 42375000 ms
hm-rega-0	2015-06-24 17:51:01	warn	Pending request for more than 42350000 ms
hm-rega-0	2015-06-24 17:51:00	warn	Pending request for more than 42325000 ms
hm-rega-0	2015-06-24 17:50:59	warn	Pending request for more than 42300000 ms
hm-rega-0	2015-06-24 17:50:59	warn	Pending request for more than 42275000 ms
hm-rega-0	2015-06-24 17:50:58	warn	Pending request for more than 42250000 ms
hm-rega-0	2015-06-24 17:50:57	warn	Pending request for more than 42225000 ms
hm-rega-0	2015-06-24 17:50:57	warn	Pending request for more than 42200000 ms
hm-rega-0	2015-06-24 17:50:56	warn	Pending request for more than 42175000 ms
hm-rega-0	2015-06-24 17:50:55	warn	Pending request for more than 42150000 ms
hm-rega-0	2015-06-24 17:50:55	warn	Pending request for more than 42125000 ms
hm-rega-0	2015-06-24 17:50:54	warn	Pending request for more than 42100000 ms
hm-rpc-0	2015-06-24 17:50:53	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:2001",""]
host-raspberrypi	2015-06-24 17:50:53	info	stopInstance system.adapter.hm-rpc.0 killing pid 2357
host-raspberrypi	2015-06-24 17:50:53	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 17:50:53	info	object change system.adapter.hm-rpc.0
              1 Reply Last reply Reply Quote 0
              • Homoran
                Homoran Global Moderator Administrators last edited by

                @Communicate:

                Hi,

                das kommt daraus:

                pi@raspberrypi ~ $ ps -A | grep io
   17 ?        00:00:00 bioset
   20 ?        00:00:00 rpciod
   23 ?        00:00:00 nfsiod
   35 ?        00:00:00 DWC Notificatio
 2048 ?        00:00:52 io.js-controlle
 2191 ?        00:00:51 io.admin.0
 2309 ?        00:00:15 io.web.0
 2356 ?        00:01:49 io.hm-rega.0
 2357 ?        00:00:10 io.hm-rpc.0

                EDIT:

                Ein Versuch iobroker zu starten sagt folgendes:

                pi@raspberrypi /opt/iobroker $ sudo ./iobroker start
ioBroker controller daemon already running. PID: 2048
```` `

                Das ist klar; das wurde dir ja auch schon oben gesagt:

                 2048 ?        00:00:52 io.js-controlle

                somit läuft der controller, außerdem hm-rpc, hm-rega und der web-Adapter.

                Was hattest du da gemacht?

                hm-rpc-0   2015-06-24 17:50:53   info   xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:2001",""]
host-raspberrypi   2015-06-24 17:50:53   info   stopInstance system.adapter.hm-rpc.0 killing pid 2357
host-raspberrypi   2015-06-24 17:50:53   info   stopInstance system.adapter.hm-rpc.0
host-raspberrypi   2015-06-24 17:50:53   info   object change system.adapter.hm-rpc.0

                Am rpc-Adapter wurde etwas geändert,

                Gruß

                Rainer

                1 Reply Last reply Reply Quote 0
                • C
                  Communicate last edited by

                  ` > Was hattest du da gemacht?

                  CODE: ALLES AUSWÄHLEN

                  hm-rpc-0 2015-06-24 17:50:53 info xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:2001",""]

                  host-raspberrypi 2015-06-24 17:50:53 info stopInstance system.adapter.hm-rpc.0 killing pid 2357

                  host-raspberrypi 2015-06-24 17:50:53 info stopInstance system.adapter.hm-rpc.0

                  host-raspberrypi 2015-06-24 17:50:53 info object change system.adapter.hm-rpc.0

                  Am rpc-Adapter wurde etwas geändert, `

                  Den RPC Adapter einmal aus und dann wieder an gemacht…

                  Hier mal das log nach einem Neustart mit anschliessendem Start der RPC Instanz (aber ohne Init, CheckInit, etc.):

                  hm-rpc-0	2015-06-24 18:06:53	info	starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.hm-rpc
hm-rpc-0	2015-06-24 18:06:52	debug	statesDB connected
hm-rpc-0	2015-06-24 18:06:52	debug	objectDB connected
host-raspberrypi	2015-06-24 18:06:48	warn	instance system.adapter.hm-rpc.0 already running with pid 2412
host-raspberrypi	2015-06-24 18:06:47	info	instance system.adapter.hm-rpc.0 started with pid 2412
host-raspberrypi	2015-06-24 18:06:46	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:45	info	instance system.adapter.hm-rpc.0 terminated with code 143 ()
host-raspberrypi	2015-06-24 18:06:45	info	stopInstance system.adapter.hm-rpc.0 killing pid 2411
host-raspberrypi	2015-06-24 18:06:45	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:45	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:43	warn	instance system.adapter.hm-rpc.0 already running with pid 2411
host-raspberrypi	2015-06-24 18:06:40	info	instance system.adapter.hm-rpc.0 started with pid 2411
host-raspberrypi	2015-06-24 18:06:40	info	instance system.adapter.hm-rpc.0 terminated with code 143 ()
host-raspberrypi	2015-06-24 18:06:40	info	stopInstance system.adapter.hm-rpc.0 killing pid 2410
host-raspberrypi	2015-06-24 18:06:40	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:40	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:39	info	instance system.adapter.hm-rpc.0 started with pid 2410
host-raspberrypi	2015-06-24 18:06:39	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:38	info	instance system.adapter.hm-rpc.0 terminated with code 143 ()
host-raspberrypi	2015-06-24 18:06:38	info	stopInstance system.adapter.hm-rpc.0 killing pid 2409
host-raspberrypi	2015-06-24 18:06:38	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:38	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:06:36	info	instance system.adapter.hm-rpc.0 started with pid 2409
host-raspberrypi	2015-06-24 18:06:36	info	object change system.adapter.hm-rpc.0

                  Und dann hier das Log, nachdem ich Init? aktiviert habe:

                  hm-rpc-0	2015-06-24 18:09:10	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:2001","hm-rpc.0"]
hm-rpc-0	2015-06-24 18:09:10	info	xmlrpc server is trying to listen on 192.168.178.49:2001
hm-rpc-0	2015-06-24 18:09:09	info	starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.hm-rpc
hm-rpc-0	2015-06-24 18:09:08	debug	statesDB connected
hm-rpc-0	2015-06-24 18:09:08	debug	objectDB connected
host-raspberrypi	2015-06-24 18:09:02	warn	instance system.adapter.hm-rpc.0 already running with pid 2417
host-raspberrypi	2015-06-24 18:09:02	info	instance system.adapter.hm-rpc.0 started with pid 2417
host-raspberrypi	2015-06-24 18:09:02	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:09:00	info	stopInstance system.adapter.hm-rpc.0 killing pid 2412
host-raspberrypi	2015-06-24 18:09:00	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:09:00	info	object change system.adapter.hm-rpc.0
inMem	2015-06-24 18:08:52	debug	message *.logging system.adapter.admin.0.logging val=true, ack=true, ts=1435169332, from=system.adapter.admin.0, lc=1435169162

                  und hier nachdem ich Init aktiviert habe:

                  hm-rpc-0	2015-06-24 18:11:56	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:20011","hm-rpc.0"]
hm-rpc-0	2015-06-24 18:11:56	info	xmlrpc server is trying to listen on 192.168.178.49:20011
hm-rpc-0	2015-06-24 18:11:55	info	starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.hm-rpc
hm-rpc-0	2015-06-24 18:11:54	debug	statesDB connected
hm-rpc-0	2015-06-24 18:11:54	debug	objectDB connected
host-raspberrypi	2015-06-24 18:11:49	info	instance system.adapter.hm-rpc.0 started with pid 2427
host-raspberrypi	2015-06-24 18:10:55	info	instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
hm-rpc-0	2015-06-24 18:10:55	error	already running
hm-rpc-0	2015-06-24 18:10:54	debug	statesDB connected
hm-rpc-0	2015-06-24 18:10:54	debug	objectDB connected
host-raspberrypi	2015-06-24 18:10:48	info	instance system.adapter.hm-rpc.0 started with pid 2422
host-raspberrypi	2015-06-24 18:10:46	info	stopInstance system.adapter.hm-rpc.0 killing pid 2417
host-raspberrypi	2015-06-24 18:10:46	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:10:46	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:09:00	info	instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
inMem	2015-06-24 18:10:46	debug	message *.logging system.adapter.admin.0.logging val=true, ack=true, ts=1435169446, from=system.adapter.admin.0, lc=1435169162
hm-rpc-0	2015-06-24 18:10:46	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:2001",""]

                  Und hier nachdem ich "Initiiere Geräte neu" aktiviert habe:

                  hm-rpc-0	2015-06-24 18:13:49	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:200111","hm-rpc.0"]
hm-rpc-0	2015-06-24 18:13:49	info	xmlrpc server is trying to listen on 192.168.178.49:200111
hm-rpc-0	2015-06-24 18:13:48	info	starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.hm-rpc
hm-rpc-0	2015-06-24 18:13:47	debug	statesDB connected
hm-rpc-0	2015-06-24 18:13:47	debug	objectDB connected
host-raspberrypi	2015-06-24 18:13:41	info	instance system.adapter.hm-rpc.0 started with pid 2438
host-raspberrypi	2015-06-24 18:13:39	info	instance system.adapter.hm-rpc.0 terminated with code 143 ()
host-raspberrypi	2015-06-24 18:13:38	info	stopInstance system.adapter.hm-rpc.0 killing pid 2437
host-raspberrypi	2015-06-24 18:13:38	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:13:38	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:13:37	info	instance system.adapter.hm-rpc.0 started with pid 2437
host-raspberrypi	2015-06-24 18:13:37	info	object change system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:13:07	info	instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
hm-rpc-0	2015-06-24 18:13:07	error	already running
hm-rpc-0	2015-06-24 18:13:06	debug	statesDB connected
hm-rpc-0	2015-06-24 18:13:06	debug	objectDB connected
host-raspberrypi	2015-06-24 18:13:01	info	instance system.adapter.hm-rpc.0 started with pid 2432
inMem	2015-06-24 18:12:58	debug	message *.logging system.adapter.admin.0.logging val=true, ack=true, ts=1435169579, from=system.adapter.admin.0, lc=1435169162
inMem	2015-06-24 18:12:58	debug	message *.logging system.adapter.admin.0.logging val=true, ack=true, ts=1435169579, from=system.adapter.admin.0, lc=1435169162
hm-rpc-0	2015-06-24 18:12:58	info	xmlrpc -> 192.168.178.101:2001 init ["http://192.168.178.49:2001",""]
host-raspberrypi	2015-06-24 18:12:58	info	stopInstance system.adapter.hm-rpc.0 killing pid 2427
host-raspberrypi	2015-06-24 18:12:58	info	stopInstance system.adapter.hm-rpc.0
host-raspberrypi	2015-06-24 18:12:58	info	object change system.adapter.hm-rpc.0
inMem	2015-06-24 18:12:50	debug	message *.logging system.adapter.admin.0.logging val=true, ack=true, ts=1435169571, from=system.adapter.admin.0, lc=1435169162

                  ein ps -A | grep io ergibt:

                  ` > pi@raspberrypi ~ $ ps -A | grep io

                  17 ? 00:00:00 bioset

                  20 ? 00:00:00 rpciod

                  23 ? 00:00:00 nfsiod

                  35 ? 00:00:00 DWC Notificatio

                  2051 ? 00:00:32 io.js-controlle

                  2118 ? 00:00:35 io.admin.0

                  2252 ? 00:00:12 io.web.0

                  2363 ? 00:00:11 io.hm-rega.0

                  2417 ? 00:00:07 io.hm-rpc.0

                  2427 ? 00:00:06 io.hm-rpc.0

                  2438 ? 00:00:06 io.hm-rpc.0 `

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

                    Jetzt laufen drei rpc Instanzen und dier alte Fehler ist wieder das:

                    "http://192.168.178.49:20011"

                    Gruß

                    Rainer

                    1 Reply Last reply Reply Quote 0
                    • C
                      Communicate last edited by

                      Haltet mich für total bekloppt, aber nachdem ich die CCU2 neugestartet habe, geht es jetzt. Komisch :roll:

                      Einziger Fehler, der aber nicht so schlimm ist:

                      Wenn ich bei den Instanzen auf VIS klicke ruft er "undefined://192.168.178.49:8082/vis/edit.html auf statt http:// …

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

                        @Communicate:

                        Haltet mich für total bekloppt, aber nachdem ich die CCU2 neugestartet habe, geht es jetzt. Komisch `
                        Hoffentlich war es das, immerhin meldete sich iobroker, dass er seit zigtausend ms auf eine Reaktion der CCU wartet.

                        @Communicate:

                        Wenn ich bei den Instanzen auf VIS klicke ruft er "undefined://192.168.178.49:8082/vis/edit.html auf statt http:// … `
                        der bug ist bekannt.

                        Gruß

                        Rainer

                        1 Reply Last reply Reply Quote 0
                        • Y
                          ykuendig last edited by

                          Die 'pending requests' sind ein Problem, welches wir im Zusammenhang mit Tests des iobroker.occ Adapters festgestellt hatten. Das war auch dort ein Zeichen, dass die CCU zerschossen war. Hast Du auch occ installiert?

                          Das andere Problem sind die zum hängenden Instanzen. Ich habe das manchmal bei Javascript und versuche da noch die Zusammenhänge zu verstehen. Aber hilft nur entweder einzeln abschiessen mit kill oder reboot…
                          144_tradfri.txt

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          903
                          Online

                          31.7k
                          Users

                          79.7k
                          Topics

                          1.3m
                          Posts

                          6
                          44
                          5873
                          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