Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Seit update keine Zustandsänderungen der z.B. Fensterkontakte

    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

    Seit update keine Zustandsänderungen der z.B. Fensterkontakte

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

      Hi ist denn der Fehler hm-rpc oder node_modules?

      Soll ich das so ausführen?

      cd /opt/iobroker

      npm install iobroker.hm-rpc –production

      iobroker upload hm-rpc

      ./iobroker restart

      1 Reply Last reply Reply Quote 0
      • A
        audioconcept last edited by

        Könnte ihr mir bitte noch mal weiterhelfen?

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

          Wie ist denn jetzt der aktuelle Status?

          Meine letzte Frage war:
          @Homoran:

          Sind ALLE Adapter und auch der js-controller auf dem neuesten Stand? `
          Leider bekam ich nur die folgende Antwort:
          @audioconcept:

          ja … habe alle Adapter im Adminmodul aktualisiert. `
          Da kann ich mir jetzt etwas bei aussuchen, oder?

          Dann kommt:
          @audioconcept:

          der js controller muss ich den anders auf dem neuesten Stand bringen? `
          und weiter Informationen, die ich nicht der aktuellen Lage zuordnen konnte.

          Könnten aber ursächlich sein.

          Also nochmal:

          Was ist jetzt der Status?

          • Fehlermeldungen im Log??

          Gruß

          Rainer

          1 Reply Last reply Reply Quote 0
          • A
            audioconcept last edited by

            Hallo Rainer

            Ich hatte Jessie neu installiert auf dem Pi. Habe es nach der Anleitung auf der IOBROKER Seite gemacht. Danach habe ich letzte Sicherungsdatei eingespielt.

            Auf der Admin-Adapterseite habe ich alle Aktualisierungen ausgeführt.

            ist der js-controller dann nicht automatisch auf den neuesten Stand?

            Muss ich es dann so installieren?:
            ` > cd /opt/iobroker

            iobroker stop

            npm install iobroker.js-controller –production

            iobroker start `

            Die Logmeldung ist noch die im ersten Beitrag.

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

              @audioconcept:

              ist der js-controller dann nicht automatisch auf den neuesten Stand? `
              Nein, das update dazu findest du unter dem Reiter "Hosts"

              @audioconcept:

              Muss ich es dann so installieren?:

              cd /opt/iobroker
iobroker stop
npm install iobroker.js-controller --production
iobroker start
```` `

              ja!

              Gruß

              Rainer

              1 Reply Last reply Reply Quote 0
              • A
                audioconcept last edited by

                Hi Rainer

                sorry ja unter Host ist der js controller auch auf dem neuesten Stand 0.9.0. Hatte ich auch alles gemacht.

                Was kann ich noch machen?

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

                  Bitte folgendes alles auf der konsole ausführen und Fehlermeldungen sofort posten (cut and paste in code-tags)

                  zuerst einmal überprüfen, ob alles auf dem neuesten Stand ist.

                  cd /opt/iobroker
iobroker update

                  Sollte da hinter einem Adapter "updateable" stehen bitte diesen updaten, aber erst:

                  Da es ja immer sein kann, dass eine Datei beim Download korrupt ist, und damit diese auch wieder neu heruntergeladen wird, mache bitte als erstes:

                  cd /opt/iobroker
npm cache clean

                  Dann ggf. noch zu aktualisierende Adapter aktualisieren.

                  Da der Fehler anscheinend etwas mit dem hm-rpc zu tun hat würde ich jetzt erst einmal den neu installieren.

                  cd /opt/iobroker
iobroker stop
npm install iobroker.hm-rpc --production
iobroker upload hm-rpc
iobroker start

                  Und dann mal sehen, ob es jetzt wieder läuft.

                  Gruß

                  Rainer

                  1 Reply Last reply Reply Quote 0
                  • A
                    audioconcept last edited by

                    ok Danke versuche ich morgen sofort.

                    Gesendet von meinem STV100-4 mit Tapatalk

                    1 Reply Last reply Reply Quote 0
                    • A
                      audioconcept last edited by

                      Hi hab alles jetzt so gemacht.

                      Geht aber noch immer nicht.

                      Im log steht immer noch:

                      Drücke Strg+A und danach Strg+C, um den Inhalt in die Zwischenablage zu kopieren. Klicke irgendwo, um das Fenster zu schliessen.
raspberrypi	2016-07-04 20:27:47.231	info	host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
raspberrypi	2016-07-04 20:27:47.230	error	host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc.0	2016-07-04 20:27:47.133	info	hm-rpc.0 Disconnected
hm-rpc.0	2016-07-04 20:27:46.932	info	hm-rpc.0 binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
hm-rpc.0	2016-07-04 20:27:46.932	error	TypeError: Cannot read property '2' of undefined at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48) at Socket.(/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20)
hm-rpc.0	2016-07-04 20:27:46.930	error	uncaught exception: Cannot read property '2' of undefined
hm-rpc.0	2016-07-04 20:26:04.552	info	hm-rpc.0 Connected
hm-rpc.0	2016-07-04 20:26:03.236	info	hm-rpc.0 binrpc -> 143 devices
hm-rpc.0	2016-07-04 20:26:02.859	info	hm-rpc.0 binrpc <- listDevices ['hm-rpc.0']
hm-rpc.0	2016-07-04 20:26:02.596	info	hm-rpc.0 binrpc client is trying to connect to 192.168.2.102:2001 with ['xmlrpc_bin://192.168.2.138:2001','hm-rpc.0']
hm-rpc.0	2016-07-04 20:26:02.593	info	hm-rpc.0 binrpc server is trying to listen on 192.168.2.138:2001
hm-rpc.0	2016-07-04 20:26:02.182	info	hm-rpc.0 starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.hm-rpc
raspberrypi	2016-07-04 20:25:59.522	info	host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 2009
raspberrypi	2016-07-04 20:25:29.511	info	host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
raspberrypi	2016-07-04 20:25:29.510	error	host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc.0	2016-07-04 20:24:44.565	info	hm-rpc.0 Connected
hm-rpc.0	2016-07-04 20:24:43.252	info	hm-rpc.0 binrpc -> 143 devices
hm-rpc.0	2016-07-04 20:24:42.843	info	hm-rpc.0 binrpc <- listDevices ['hm-rpc.0']
hm-rpc.0	2016-07-04 20:24:42.582	info	hm-rpc.0 binrpc client is trying to connect to 192.168.2.102:2001 with ['xmlrpc_bin://192.168.2.138:2001','hm-rpc.0']
hm-rpc.0	2016-07-04 20:24:42.579	info	hm-rpc.0 binrpc server is trying to listen on 192.168.2.138:2001
hm-rpc.0	2016-07-04 20:24:42.172	info	hm-rpc.0 starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.hm-rpc
raspberrypi	2016-07-04 20:24:39.539	info	host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 1838
raspberrypi	2016-07-04 20:24:09.519	info	host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
raspberrypi	2016-07-04 20:24:09.517	error	host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc.0	2016-07-04 20:24:09.458	info	hm-rpc.0 Disconnected
hm-rpc.0	2016-07-04 20:24:09.457	info	hm-rpc.0 binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
hm-rpc.0	2016-07-04 20:24:09.457	error	TypeError: Cannot read property '2' of undefined at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48) at Socket.(/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20)
hm-rpc.0	2016-07-04 20:24:09.453	error	uncaught exception: Cannot read property '2' of undefined
hm-rpc.0	2016-07-04 20:24:09.221	info	hm-rpc.0 binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
hm-rpc.0	2016-07-04 20:24:09.220	error	TypeError: Cannot read property '2' of undefined at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48) at Socket.(/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20)
hm-rpc.0	2016-07-04 20:24:09.219	error	uncaught exception: Cannot read property '2' of undefined
hm-rpc.0	2016-07-04 20:24:08.978	info	hm-rpc.0 Connected
hm-rpc.0	2016-07-04 20:24:07.646	info	hm-rpc.0 binrpc -> 143 devices
hm-rpc.0	2016-07-04 20:24:07.240	info	hm-rpc.0 binrpc <- listDevices ['hm-rpc.0']
hm-rpc.0	2016-07-04 20:24:06.968	info	hm-rpc.0 binrpc client is trying to connect to 192.168.2.102:2001 with ['xmlrpc_bin://192.168.2.138:2001','hm-rpc.0']
hm-rpc.0	2016-07-04 20:24:06.965	info	hm-rpc.0 binrpc server is trying to listen on 192.168.2.138:2001
hm-rpc.0	2016-07-04 20:24:06.567	info	hm-rpc.0 starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.hm-rpc
raspberrypi	2016-07-04 20:24:05.831	info	host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 1748
raspberrypi	2016-07-04 20:23:33.657	info	host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
raspberrypi	2016-07-04 20:23:33.656	error	host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc.0	2016-07-04 20:23:33.575	info	hm-rpc.0 Disconnected
hm-rpc.0	2016-07-04 20:23:33.575	info	hm-rpc.0 binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
hm-rpc.0	2016-07-04 20:23:33.575	error	TypeError: Cannot read property '2' of undefined at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48) at Socket.(/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20)
hm-rpc.0	2016-07-04 20:23:33.574	error	uncaught exception: Cannot read property '2' of undefined
hm-rpc.0	2016-07-04 20:23:33.405	info	hm-rpc.0 binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
hm-rpc.0	2016-07-04 20:23:33.404	error	TypeError: Cannot read property '2' of undefined at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48) at Socket.(/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20)
hm-rpc.0	2016-07-04 20:23:33.402	error	uncaught exception: Cannot read property '2' of undefined
hm-rpc.0	2016-07-04 20:23:33.311	info	hm-rpc.0 Connected
hm-rpc.0	2016-07-04 20:23:31.925	info	hm-rpc.0 binrpc -> 143 devices
hm-rpc.0	2016-07-04 20:23:31.542	info	hm-rpc.0 binrpc <- listDevices ['hm-rpc.0']
hm-rpc.0	2016-07-04 20:23:31.278	info	hm-rpc.0 binrpc client is trying to connect to 192.168.2.102:2001 with ['xmlrpc_bin://192.168.2.138:2001','hm-rpc.0']
hm-rpc.0	2016-07-04 20:23:31.275	info	hm-rpc.0 binrpc server is trying to listen on 192.168.2.138:2001
hm-rpc.0	2016-07-04 20:23:30.856	info	hm-rpc.0 starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.hm-rpc
raspberrypi	2016-07-04 20:23:28.984	info	host.raspberrypi instance system.adapter.hm-rpc.0 started with pid 1739
raspberrypi	2016-07-04 20:22:57.953	info	host.raspberrypi Restart adapter system.adapter.hm-rpc.0 because enabled
raspberrypi	2016-07-04 20:22:57.952	error	host.raspberrypi instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc.0	2016-07-04 20:22:57.874	info	hm-rpc.0 Disconnected
hm-rpc.0	2016-07-04 20:22:57.682	info	hm-rpc.0 binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
hm-rpc.0	2016-07-04 20:22:57.681	error	TypeError: Cannot read property '2' of undefined at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48) at Socket.(/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20)
hm-rpc.0	2016-07-04 20:22:57.678	error	uncaught exception: Cannot read property '2' of undefined
hm-rpc-0	2016-07-04 20:21:55.938	info	Connected
hm-rpc-0	2016-07-04 20:21:54.359	info	binrpc -> 143 devices
hm-rpc-0	2016-07-04 20:21:54.320	info	binrpc <- listDevices ['hm-rpc.0']
hm-rpc-0	2016-07-04 20:21:54.038	info	binrpc client is trying to connect to 192.168.2.102:2001 with ['xmlrpc_bin://192.168.2.138:2001','hm-rpc.0']
hm-rpc-0	2016-07-04 20:21:54.031	info	binrpc server is trying to listen on 192.168.2.138:2001
hm-rpc-0	2016-07-04 20:21:53.458	info	starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.hm-rpc
host-raspberrypi	2016-07-04 20:21:50.909	info	instance system.adapter.hm-rpc.0 started with pid 1651
host-raspberrypi	2016-07-04 20:21:20.887	info	Restart adapter system.adapter.hm-rpc.0 because enabled
host-raspberrypi	2016-07-04 20:21:20.886	error	instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc-0	2016-07-04 20:21:20.842	info	terminating
hm-rpc-0	2016-07-04 20:21:20.801	info	Disconnected
hm-rpc-0	2016-07-04 20:21:20.685	info	binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
TypeError:	2016-07-04 20:21:20.680	error	at TCP.onread (net.js:531:20)
TypeError:	2016-07-04 20:21:20.680	error	at Socket.Readable.push (_stream_readable.js:111:10)
TypeError:	2016-07-04 20:21:20.680	error	at readableAddChunk (_stream_readable.js:153:18)
TypeError:	2016-07-04 20:21:20.680	error	at Socket.emit (events.js:169:7)
TypeError:	2016-07-04 20:21:20.680	error	at emitOne (events.js:77:13)
TypeError:	2016-07-04 20:21:20.680	error	at Socket. (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22)
TypeError:	2016-07-04 20:21:20.680	error	at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48)
TypeError:	2016-07-04 20:21:20.680	error	Cannot read property '2' of undefined
uncaught	2016-07-04 20:21:20.664	error	exception: Cannot read property '2' of undefined
hm-rpc-0	2016-07-04 20:20:46.258	info	Connected
hm-rpc-0	2016-07-04 20:20:44.616	info	binrpc -> 143 devices
hm-rpc-0	2016-07-04 20:20:44.576	info	binrpc <- listDevices ['hm-rpc.0']
hm-rpc-0	2016-07-04 20:20:44.299	info	binrpc client is trying to connect to 192.168.2.102:2001 with ['xmlrpc_bin://192.168.2.138:2001','hm-rpc.0']
hm-rpc-0	2016-07-04 20:20:44.293	info	binrpc server is trying to listen on 192.168.2.138:2001
hm-rpc-0	2016-07-04 20:20:43.752	info	starting. Version 1.3.1 in /opt/iobroker/node_modules/iobroker.hm-rpc
host-raspberrypi	2016-07-04 20:20:41.198	info	instance system.adapter.hm-rpc.0 started with pid 1630
host-raspberrypi	2016-07-04 20:20:11.176	info	Restart adapter system.adapter.hm-rpc.0 because enabled
host-raspberrypi	2016-07-04 20:20:11.175	error	instance system.adapter.hm-rpc.0 terminated with code 0 (OK)
hm-rpc-0	2016-07-04 20:20:11.139	info	terminating
hm-rpc-0	2016-07-04 20:20:11.095	info	Disconnected
hm-rpc-0	2016-07-04 20:20:11.075	info	binrpc -> 192.168.2.102:2001 init ['xmlrpc_bin://192.168.2.138:2001','']
TypeError:	2016-07-04 20:20:11.068	error	at TCP.onread (net.js:531:20)
TypeError:	2016-07-04 20:20:11.068	error	at Socket.Readable.push (_stream_readable.js:111:10)
TypeError:	2016-07-04 20:20:11.068	error	at readableAddChunk (_stream_readable.js:153:18)
TypeError:	2016-07-04 20:20:11.068	error	at Socket.emit (events.js:169:7)
TypeError:	2016-07-04 20:20:11.068	error	at emitOne (events.js:77:13)
TypeError:	2016-07-04 20:20:11.068	error	at Socket. (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:55:22)
TypeError:	2016-07-04 20:20:11.068	error	at handleCall (/opt/iobroker/node_modules/iobroker.hm-rpc/node_modules/binrpc/lib/server.js:72:48)
TypeError:	2016-07-04 20:20:11.068	error	Cannot read property '2' of undefined
uncaught	2016-07-04 20:20:11.047	error	exception: Cannot read property '2' of undefined
                      1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators last edited by

                        Stimmen die Konfigurationen von hm-rpc und hm-rega noch?

                        Irgendetwas scheint der hm-rpc einzulesen, mit dem er aber nicht klar kommt.

                        Gruß

                        Rainer

                        1 Reply Last reply Reply Quote 0
                        • A
                          audioconcept last edited by

                          Hallo sollte eigentlich stimmen.

                          filename="IMG_20160630_1708479.jpg" index="0">~~ filename="IMG_20160630_1708199.jpg" index="1">~~ filename="IMG_20160630_1708171.jpg" index="2">~~

                          Gesendet von meinem STV100-4 mit Tapatalk

                          1 Reply Last reply Reply Quote 0
                          • A
                            audioconcept last edited by

                            Es waren keine Updates mehr offen (nur zwei Wetterupdates).

                            Hast du noch eine Idee?

                            Gesendet von meinem STV100-4 mit Tapatalk

                            1 Reply Last reply Reply Quote 0
                            • A
                              audioconcept last edited by

                              HI

                              aus irgend einen Grund war im RPC Adapter BIN-RPC anstatt XML-RPC eingestellt. Jetzt geht es wieder.

                              Danke euch.

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

                              Support us

                              ioBroker
                              Community Adapters
                              Donate
                              FAQ Cloud / IOT
                              HowTo: Node.js-Update
                              HowTo: Backup/Restore
                              Downloads
                              BLOG

                              942
                              Online

                              31.9k
                              Users

                              80.3k
                              Topics

                              1.3m
                              Posts

                              3
                              18
                              1721
                              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