Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Homematic Taster funktionieren nicht mehr

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    Homematic Taster funktionieren nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • X
      xfirf last edited by Homoran

      Hallo,
      ich habe vor etwa vier Wochen einen Homematic IP 6-Fach Wandtaster in Betrieb genommen. Vorher hatte ich schon zwei Homematic 2-Fach Wandtaster für meine Küche in Betrieb. Diese steuern per blockly einen Shelly.

      Seit ich den IP-Taster eingebunden habe - über eine eigene RPC-Instanz - funktionieren die alten 2-Fach Taster nur noch nach einem Neustart des iobroker für ein paar Tastendrücke. Danach funktionieren sie nicht mehr. Der IP-Taster funktioniert die ganze Zeit weiter, ohne Probleme.

      Ich habe keine Ahnung wieso und was ich dagegen machen könnte. Folgende Fehlermeldungen habe ich im Log:

      hm-rpc.2
      	2023-07-26 08:46:33.331	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 08:46:33.322	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 08:46:03.323	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 08:45:33.306	error	Ping error [iobrokerpi:hm-rpc.2:e8ca588bf13c3b90d24c05ddb25faa9c]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 07:37:29.357	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 07:37:29.334	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 07:36:59.335	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 07:36:29.309	error	Ping error [iobrokerpi:hm-rpc.2:692db1ed1975906effe461001ae452f5]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 06:28:25.322	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 06:28:25.302	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 06:27:55.303	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 06:27:25.278	error	Ping error [iobrokerpi:hm-rpc.2:ff1d1ed3a373ccebd7f736e1a41363b7]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.1
      	2023-07-26 06:27:04.165	error	Cannot call init: [http://192.168.178.120:2001, ""] Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:26:34.153	error	Init not possible, going to stop: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:26:04.141	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:24:16.134	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:22:44.424	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:21:02.138	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:19:02.423	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:17:13.500	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.1
      	2023-07-26 06:15:37.382	error	Ping error [iobrokerpi:hm-rpc.1:4a2aed73c3bbe0ce6e7dd909f7abaa2e]: Unknown XML-RPC tag 'TITLE'
      hm-rpc.2
      	2023-07-26 05:19:21.265	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 05:19:21.248	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 05:18:51.248	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 05:18:21.235	error	Ping error [iobrokerpi:hm-rpc.2:c35bc142292b973e213edda6d639b080]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 05:16:40.670	error	Ping error [iobrokerpi:hm-rpc.2:c35bc142292b973e213edda6d639b080]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 04:08:36.708	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 04:08:36.693	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 04:08:06.694	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 04:07:36.671	error	Ping error [iobrokerpi:hm-rpc.2:28098558cd24da7ceb86f7073cc2c760]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 02:59:32.741	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 02:59:32.726	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 02:59:02.726	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 02:58:32.712	error	Ping error [iobrokerpi:hm-rpc.2:eff1a08fd33bbfbb506ee61bbd79957f]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 01:50:28.640	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 01:50:28.624	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 01:49:58.624	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 01:49:28.601	error	Ping error [iobrokerpi:hm-rpc.2:4c8b966d526beb294b65a6564605ba7d]: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 00:41:24.640	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 00:41:24.624	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
      hm-rpc.2
      	2023-07-26 00:40:54.622	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char: 
      

      MOD-EDIT: Code in code-tags gesetzt!

      hm-rpc.1 ist die Instanz für rpc (die alten Taster)
      hm-rpc.2 ist die Instanz für die IP-Geräte

      iobroker 6.3.5
      JS-Controller ist auf 4.0.24
      Node 18.16.0

      Habt ihr eine Idee wie ich das besser debuggen kann oder sogar direkt was das Problem sein könnte?

      sigi234 Homoran 2 Replies Last reply Reply Quote 0
      • sigi234
        sigi234 Forum Testing Most Active @xfirf last edited by sigi234

        @xfirf

        Sentry für die betroffenen Instanzen deaktivieren.
        https://forum.iobroker.net/topic/66930/probleme-mit-homematic-rpc?_=1690359389851

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

          @xfirf sollze das helfen, bitte trotzdem zusätzlich die Ausgabe von iob diag in code-tags gesetzt posten.

          X 1 Reply Last reply Reply Quote 0
          • X
            xfirf @Homoran last edited by xfirf

            Danke für die antworten. Ob es klappt melde ich später zurück wenn ich daheim bin. iob diag output:

            ======================= SUMMARY =======================
            		     v.2023-04-16
            
            
            Operatingsystem: 	Raspbian GNU/Linux 10 (buster)
            Kernel: 		5.10.103-v8+
            Installation: 		Native
            Timezone: 		Europe/Berlin (CEST, +0200)
            User-ID: 		1000
            X-Server: 		false
            Boot Target: 		multi-user.target
            
            Pending OS-Updates: 	35
            Pending iob updates: 	0
            
            Nodejs-Installation: 	/usr/bin/nodejs 	v18.16.0
            			/usr/bin/node 		v18.16.0
            			/usr/bin/npm 		9.5.1
            			/usr/bin/npx 		9.5.1
            
            Recommended versions are nodejs 18.x.y and npm 9.x.y
            Your nodejs installation is correct
            
            MEMORY: 
                          total        used        free      shared  buff/cache   available
            Mem:           3.7G        1.0G        663M         29M        2.1G        2.6G
            Swap:           99M        2.0M         97M
            Total:         3.8G        1.0G        761M
            
            Active iob-Instances: 	21
            Active repo(s): stable
            
            ioBroker Core: 		js-controller 		4.0.24
            			admin 			6.3.5
            
            ioBroker Status: 	iobroker is running on this host.
            
            
            Objects type: jsonl
            States  type: redis
            
            Status admin and web instance:
            + system.adapter.admin.0                  : admin                 : iobrokerpi                               -  enabled, port: 8081, bind: 192.168.178.120, run as: admin
            + system.adapter.web.0                    : web                   : iobrokerpi                               -  enabled, port: 8082, bind: 0.0.0.0, run as: admin
            
            Objects: 		5698
            States: 		5429
            
            Size of iob-Database:
            
            15M	/opt/iobroker/iobroker-data/objects.jsonl
            7.7M	/opt/iobroker/iobroker-data/objects.json.migrated
            7.7M	/opt/iobroker/iobroker-data/objects.json.bak.migrated
            28K	/opt/iobroker/iobroker-data/objects.json.bak2
            16K	/opt/iobroker/iobroker-data/objects.json.old
            884K	/opt/iobroker/iobroker-data/states.json.old
            884K	/opt/iobroker/iobroker-data/states.json
            
            
            
            =================== END OF SUMMARY ====================
            
            Homoran 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @xfirf last edited by Homoran

              @xfirf sagte in Homematic Taster funktionieren nicht mehr:

              ioBroker Core: js-controller 4.0.24
              Nodejs-Installation: /usr/bin/nodejs v18.16.0

              falls das abschalten von sentry in der Instanz nutzt, hier ^ die Info für @fastfoot

              X 1 Reply Last reply Reply Quote 0
              • X
                xfirf @Homoran last edited by

                @homoran
                Es funktioniert jetzt, allerdings habe ich immer noch folgende Fehler im log stehen:

                hm-rpc.2
                	2023-07-26 20:57:39.555	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 20:57:39.543	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 20:57:09.545	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 20:56:39.527	error	Ping error [iobrokerpi:hm-rpc.2:b12b0e95ec5c8d0c1cfdc4d5749e534e]: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 19:48:35.667	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 19:48:35.638	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 19:48:05.649	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 19:47:35.621	error	Ping error [iobrokerpi:hm-rpc.2:d754e2c1585d75da04bc93440ccaff87]: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 18:39:31.800	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 18:39:31.789	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 18:39:01.789	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 18:38:31.775	error	Ping error [iobrokerpi:hm-rpc.2:cb4bcfd9c76793a3f5ed508d68f09b61]: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 17:30:27.638	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 17:30:27.621	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 17:29:57.622	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 17:29:27.596	error	Ping error [iobrokerpi:hm-rpc.2:c102171bff2471fbad875a8c8ef8be39]: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 16:21:23.700	error	Cannot call init: [http://192.168.178.120:2010, ""] Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 16:21:23.688	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 16:20:53.687	error	Init not possible, going to stop: Unexpected endLine: 0Column: 0Char:
                hm-rpc.2
                	2023-07-26 16:20:23.672	error	Ping error [iobrokerpi:hm-rpc.2:176da44cac0fa29a10e02bc6a7d915a9]: Unexpected endLine: 0Column: 0Char: 
                
                sigi234 1 Reply Last reply Reply Quote 0
                • sigi234
                  sigi234 Forum Testing Most Active @xfirf last edited by

                  @xfirf
                  Bei Rpc2 auch Sentry deaktiviert?

                  X 1 Reply Last reply Reply Quote 0
                  • X
                    xfirf @sigi234 last edited by

                    @sigi234 Ah jetzt verstehe ich. Ich hatte Sentry für den Admin-Adapter deaktivert. Dachte das wäre dann für "alles". Habs jetzt bei den homematic-RPC-Instanzen gemacht.
                    Danke.

                    1 Reply Last reply Reply Quote 0
                    • T
                      ticaki Developer last edited by

                      Gibt gerade soviele Topics zu diesem Thema, daher schreib ichs hier rein.

                      Hatte gerade wieder einen disconnect, nichts reagierte mehr, restart von hm-rpc brachte nichts (sentry dort deaktiviert) restart von hm-rega brachte die Funktionalität zurück. Dort habe ich jetzt ebenfalls sentry deaktiviert.

                      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

                      840
                      Online

                      32.1k
                      Users

                      80.7k
                      Topics

                      1.3m
                      Posts

                      4
                      9
                      503
                      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