Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Beta Test js-controller 3.2.x auf GitHub

    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

    Beta Test js-controller 3.2.x auf GitHub

    This topic has been deleted. Only users with topic management privileges can see it.
    • Rob_in
      Rob_in @apollon77 last edited by

      Problem with chromecast adapter. Debug output:

      2021-01-09 13:36:54.062  - error: chromecast.0 (32660) Not exists
        ioredis:redis write command[10.1.1.30:9000 (chromecast.0 (32660))]: 0 -> publish('messagebox.system.host.pg.mh,{"command":"addNotification","message":{"scope":"system","category":null,"message":"Not exists","instance":"chromecast.0"},"from":"system.adapter.chromecast.0","callback": ... <REDACTED full-length="351">') +12ms
      2021-01-09 13:36:54.065  - error: chromecast.0 (32660) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2021-01-09 13:36:54.067  - error: chromecast.0 (32660) unhandled promise rejection: Not exists
      2021-01-09 13:36:54.069  - error: chromecast.0 (32660) Error: Not exists
          at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
          at Immediate.adapterObjects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
          at runCallback (timers.js:706:11)
          at tryOnImmediate (timers.js:676:5)
          at processImmediate (timers.js:658:5)
      2021-01-09 13:36:54.070  - error: chromecast.0 (32660) Not exists
        ioredis:redis write command[10.1.1.30:9000 (chromecast.0 (32660))]: 0 -> publish('messagebox.system.host.pg.mh,{"command":"addNotification","message":{"scope":"system","category":null,"message":"Not exists","instance":"chromecast.0"},"from":"system.adapter.chromecast.0","callback": ... <REDACTED full-length="351">') +8ms
      2021-01-09 13:36:54.073  - error: chromecast.0 (32660) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
      2021-01-09 13:36:54.075  - error: chromecast.0 (32660) unhandled promise rejection: Not exists
      2021-01-09 13:36:54.077  - error: chromecast.0 (32660) Error: Not exists
          at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
          at Immediate.adapterObjects.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
          at runCallback (timers.js:706:11)
          at tryOnImmediate (timers.js:676:5)
          at processImmediate (timers.js:658:5)
      2021-01-09 13:36:54.078  - error: chromecast.0 (32660) Not exists
      
      apollon77 1 Reply Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators last edited by Homoran

        @apollon77
        ich weiß nicht, ob dies hier mit der controller-Version zusammenhängt.

        Ich hatte auf der Testinstallation den sony-bravia Adapter installiert und wollte ihn wieder löschen:

        $ ./iobroker del sony-bravia
        Delete adapter "sony-bravia"
        host.ioBroker-rock64 Counted 1 meta of sony-bravia
        host.ioBroker-rock64 Counted 1 adapter for sony-bravia
        host.ioBroker-rock64 Counted 2 states (system.adapter.sony-bravia.*) from states
        ERROR: Cannot delete sony-bravia.admin files folder: ReplyError: Error ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/iobroker-data/files/sony-bravia.admin'
        ERROR: Cannot delete sony-bravia.admin files folder: ReplyError: Error ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/iobroker-data/files/sony-bravia.admin'
        host.ioBroker-rock64 object sony-bravia.admin deleted
        host.ioBroker-rock64 Deleting 2 object(s).
        host.ioBroker-rock64 Deleting 2 state(s).
        npm uninstall iobroker.sony-bravia --loglevel error --prefix "/opt/iobroker" (System call)
        

        Habe das monierte Verzeichnis geleert, da war noch _data.json drin, danach klappte es immer noch nicht.
        Erneut installiert und wieder das oben gezeigte

        EDIT:

        Muss an der Version liegen!
        bei hm-rpc das gleiche beim Löschen des Adapters:

        $ ./iobroker del hm-rpc
        Delete adapter "hm-rpc"
        host.ioBroker-rock64 Counted 1 instances of hm-rpc
        host.ioBroker-rock64 Counted 3 meta of hm-rpc
        host.ioBroker-rock64 Counted 1 adapter for hm-rpc
        host.ioBroker-rock64 Counted 116 devices of hm-rpc
        host.ioBroker-rock64 Counted 516 channels of hm-rpc
        host.ioBroker-rock64 Counted 2445 states of hm-rpc
        host.ioBroker-rock64 Counted 15 states of system.adapter.hm-rpc
        host.ioBroker-rock64 Counted 2438 states (io.hm-rpc.*) from states
        host.ioBroker-rock64 Counted 15 states (system.adapter.hm-rpc.*) from states
        host.ioBroker-rock64 Counted 1 objects of hm-rpc
        ERROR: Cannot delete hm-rpc.admin files folder: ReplyError: Error ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/iobroker-data/files/hm-rpc.admin'
        ERROR: Cannot delete hm-rpc.admin files folder: ReplyError: Error ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/iobroker-data/files/hm-rpc.admin'
        host.ioBroker-rock64 object hm-rpc.admin deleted
        host.ioBroker-rock64 Deleting 3098 object(s). Be patient...
        host.ioBroker-rock64: Only 3000 objects left to be deleted.
        host.ioBroker-rock64: Only 2800 objects left to be deleted.
        host.ioBroker-rock64: Only 2600 objects left to be deleted.
        host.ioBroker-rock64: Only 2400 objects left to be deleted.
        host.ioBroker-rock64: Only 2200 objects left to be deleted.
        

        EDIT2:
        jetzt sind sie auf einmal beide weg 😱

        apollon77 1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @Jan1 last edited by

          @Jan1 Wir werden den Fall hier im controller fixen. am Ende versuchen die Adapter ein Objekt zu löschen was es nicht gibt ... wir werden den Fehler als "aktion erfolgreich" behandeln, Fix kommt nachher

          1 Reply Last reply Reply Quote 1
          • apollon77
            apollon77 @Neuschwansteini last edited by

            @ilovegym Butte auch Issue anlegen

            Neuschwansteini 1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 @Rob_in last edited by

              @Rob_in siehe Post eben ... Fix kommt nachher noch

              Rob_in 1 Reply Last reply Reply Quote 0
              • Rob_in
                Rob_in @apollon77 last edited by

                @apollon77 Indeed, the chromecast issue is correct by this commit: https://github.com/ioBroker/ioBroker.js-controller/pull/1167/commits/8e43c640e5f6d06966becda582a7ffba6ed169bc

                🙂

                foxriver76 created this issue in ioBroker/ioBroker.js-controller

                closed do not return an error if object does not exist on delForeignObject/d… #1167

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

                  @Homoran schaue ich mir an

                  1 Reply Last reply Reply Quote 0
                  • Neuschwansteini
                    Neuschwansteini @apollon77 last edited by

                    @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

                    @ilovegym Butte auch Issue anlegen

                    https://github.com/Apollon77/ioBroker.smartmeter/issues/179

                    Ilovegym66 created this issue in Apollon77/ioBroker.smartmeter

                    closed js-cotntroller 3.2.3 warnings #179

                    1 Reply Last reply Reply Quote 0
                    • apollon77
                      apollon77 @Rob_in last edited by

                      @Rob_in Exakt, war gherade einkaufen und dann ne USV tauschen und jetzt sortiere ich alles und bereite update vor 🙂
                      Noch eeeeeetwas Geduld

                      1 Reply Last reply Reply Quote 2
                      • apollon77
                        apollon77 last edited by

                        So, liebe Freunde der gepflegten Controler Tests 🙂

                        Github ist nun mit der 3.2.4 ausgestattet die alles bisher berichtete behandelt.

                        • die "Not exists" Fehler in einigen Adaptern wenn diese nicht existente Objekte gelöscht haben sollten weg sein
                        • Lets encrypt wurde nochmal ein bissl getuned (hat das schonmal jemand gecheckt? ;-))
                        • der Adapter löschen File Fehler von @Homoran sollte auch weg sein

                        Have fun

                        Ingo

                        Neuschwansteini Homoran UncleSam peterbaumert 4 Replies Last reply Reply Quote 0
                        • Neuschwansteini
                          Neuschwansteini @apollon77 last edited by

                          @apollon77 Super, vielen vielen Dank fürs schnelle fixen, das Teil läuft hier jetzt produktiv und darf sich mal austoben.. 🙂

                          Enigma, Mihome-Vacuum, etc.. keine Fehler mehr.

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

                            @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

                            der Adapter löschen File Fehler von @Homoran sollte auch weg sein

                            Jepp!

                            $ ./iobroker del hm-rpc
                            Delete adapter "hm-rpc"
                            host.ioBroker-rock64 Counted 3 meta of hm-rpc
                            host.ioBroker-rock64 Counted 1 adapter for hm-rpc
                            host.ioBroker-rock64 file hm-rpc.admin deleted
                            host.ioBroker-rock64 object hm-rpc.admin deleted
                            host.ioBroker-rock64 Deleting 4 object(s).
                            npm uninstall iobroker.hm-rpc --loglevel error --prefix "/opt/iobroker" (System call)
                            process exited with code 0
                            

                            Danke!

                            1 Reply Last reply Reply Quote 1
                            • J
                              Jan1 last edited by

                              Eine Warnung habe ich noch:

                              alexa2.0	2021-01-09 18:37:33.810	warn	(2002421) State "alexa2.0.Echo-Devices.G070L80672670J9K.Player.muted" has no existing object, this might lead to an error in future versions
                              alexa2.0	2021-01-09 18:37:33.808	warn	(2002421) State "alexa2.0.Echo-Devices.G070L80672670J9K.Player.volume" has no existing object, this might lead to an error in future versions
                              
                              apollon77 Homoran 2 Replies Last reply Reply Quote 0
                              • apollon77
                                apollon77 @Jan1 last edited by

                                @Jan1 —> Adapter issue anlegen (bzw das gibts schon)

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

                                  @Jan1 sagte in Beta Test js-controller 3.2.x auf GitHub:

                                  Eine Warnung habe ich noch:

                                  so was hab ich reichlich:

                                  hm-rpc.0	2021-01-09 18:48:51.753	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:35","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.695	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:34","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.630	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:33","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.537	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:32","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.467	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:31","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.407	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:30","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.340	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:29","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.277	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:28","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.218	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:27","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.159	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:26","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.101	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:25","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:51.042	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:24","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.982	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:23","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.894	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:22","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.824	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:21","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.764	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:20","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.704	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:19","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.644	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:18","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.586	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:17","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.528	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:16","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.469	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:15","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.411	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:14","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:50.300	warn	(10641) State "hm-rpc.0.LTK0124195.2.FREQUENCY" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:50.298	warn	(10641) State "hm-rpc.0.LTK0124195.2.VOLTAGE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:50.296	warn	(10641) State "hm-rpc.0.LTK0124195.2.CURRENT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:50.287	warn	(10641) State "hm-rpc.0.LTK0124195.2.POWER" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:50.286	warn	(10641) State "hm-rpc.0.LTK0124195.2.ENERGY_COUNTER" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:50.284	warn	(10641) State "hm-rpc.0.LTK0124195.2.BOOT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:50.234	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:13","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.813	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:12","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.747	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:11","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.689	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:10","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.630	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:9","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.571	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:8","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.512	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:7","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.453	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:6","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.393	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:5","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.333	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:4","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.263	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:3","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.203	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:2","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.140	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:1","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:49.072	warn	(10641) State "hm-rpc.0.NEQ0633493.1.STATE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:49.070	warn	(10641) State "hm-rpc.0.NEQ0633493.1.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:49.032	warn	(10641) State "hm-rpc.0.NEQ0633493.1.ERROR" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:48.133	info	(10641) xmlrpc -> getParamsetDescription ["BidCoS-RF:0","VALUES"]
                                  hm-rpc.0	2021-01-09 18:48:44.849	warn	(10641) State "hm-rpc.0.BidCoS-RF.50.PRESS_LONG" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.508	warn	(10641) State "hm-rpc.0.JEQ0140901.1.BRIGHTNESS" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.482	warn	(10641) State "hm-rpc.0.JEQ0140901.1.SUNSHINEDURATION" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.481	warn	(10641) State "hm-rpc.0.JEQ0140901.1.WIND_DIRECTION_RANGE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.479	warn	(10641) State "hm-rpc.0.JEQ0140901.1.WIND_DIRECTION" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.478	warn	(10641) State "hm-rpc.0.JEQ0140901.1.WIND_SPEED" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.476	warn	(10641) State "hm-rpc.0.JEQ0140901.1.RAIN_COUNTER" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.475	warn	(10641) State "hm-rpc.0.JEQ0140901.1.RAINING" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.473	warn	(10641) State "hm-rpc.0.JEQ0140901.1.HUMIDITY" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:44.466	warn	(10641) State "hm-rpc.0.JEQ0140901.1.TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.685	warn	(10641) State "hm-rpc.0.LTK0129844.2.SET_TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.666	warn	(10641) State "hm-rpc.0.LTK0129844.2.ACTUAL_HUMIDITY" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.664	warn	(10641) State "hm-rpc.0.LTK0129844.2.ACTUAL_TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.646	warn	(10641) State "hm-rpc.0.NEQ0532734.5.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.645	warn	(10641) State "hm-rpc.0.NEQ0532734.4.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.643	warn	(10641) State "hm-rpc.0.NEQ0532734.3.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.642	warn	(10641) State "hm-rpc.0.NEQ0532734.2.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.640	warn	(10641) State "hm-rpc.0.NEQ0532734.1.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.639	warn	(10641) State "hm-rpc.0.NEQ0532734.0.LOWBAT" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.637	warn	(10641) State "hm-rpc.0.NEQ0532734.4.TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.635	warn	(10641) State "hm-rpc.0.NEQ0532734.3.TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.633	warn	(10641) State "hm-rpc.0.NEQ0532734.2.TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  hm-rpc.0	2021-01-09 18:48:43.621	warn	(10641) State "hm-rpc.0.NEQ0532734.1.TEMPERATURE" has no existing object, this might lead to an error in future versions
                                  

                                  Issue bei hm-rpc?

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    Jan1 @apollon77 last edited by

                                    @apollon77
                                    Dann ist ja schon alles in die Wege geleitet und der Rest verhält sich bei mir bis jetzt sehr unauffällig. Mal wieder top Arbeit 👍

                                    1 Reply Last reply Reply Quote 0
                                    • UncleSam
                                      UncleSam Developer @apollon77 last edited by

                                      @apollon77 sagte in Beta Test js-controller 3.2.x auf GitHub:

                                      Lets encrypt wurde nochmal ein bissl getuned (hat das schonmal jemand gecheckt? ;-))

                                      Wäre es sinnvoll hier im Forumin in alle LE Themen der letzten vier Monate einen Beitrag zu machen, dass das getestet werden könnte? Von den Kern-Leuten verwenden das wohl die wenigsten, da die meisten auf die Cloud setzen

                                      apollon77 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @UncleSam last edited by

                                        @UncleSam super Idee. Mag jemand das mal übernehmen? Aber halt betonen das noch frühes stadium nichtsesshaftem jemand unwissentlich seien Live system schrottet.

                                        UncleSam 1 Reply Last reply Reply Quote 0
                                        • UncleSam
                                          UncleSam Developer @apollon77 last edited by UncleSam

                                          @apollon77 ich mache das... Wenn ich die Themen finde...

                                          Edit: Nachtrag: habe es in 5 Themen, die seit Mai erstellt wurden, erwähnt. Hoffen wir, dass sich jemand meldet.

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

                                            @UncleSam @apollon77

                                            Auch hier weiß ich nicht, ob es am controller liegt, aber ich bekomme keine Verbindung zur Homematic bei HmIP

                                            2021-01-09 20:03:37.197 - info: host.ioBroker-rock64 instance system.adapter.hm-rpc.1 started with pid 10896
                                            2021-01-09 20:03:40.061 - info: hm-rpc.1 (10896) starting. Version 1.14.24 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v12.20.1, js-controller: 3.2.4
                                            2021-01-09 20:03:40.256 - info: hm-rpc.1 (10896) xmlrpc server is trying to listen on 192.168.138.168:2010
                                            2021-01-09 20:03:40.258 - info: hm-rpc.1 (10896) xmlrpc client is trying to connect to 192.168.123.52:2010/ with ["http://192.168.138.168:2010","hm-rpc.1"]
                                            2021-01-09 20:03:58.396 - warn: hm-rpc.0 (10658) State "hm-rpc.0.CENTRAL.PONG" has no existing object, this might lead to an error in future versions
                                            :
                                            :
                                            :
                                            hm-rpc.1	2021-01-09 20:05:51.215	error	(10896) init error: Error: connect ETIMEDOUT 192.168.123.52:2010
                                            

                                            Einstellung ist identisch, wie bisher

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            840
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            25
                                            287
                                            32846
                                            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