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.
    • SBorg
      SBorg Forum Testing Most Active @apollon77 last edited by

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

      @SBorg ja versions increase wollte die IDE noch einen klick aber anderes fenster war davor ... hihi ... jetzt auch fixed

      😀

      Bisheriges Fazit: lüppt, etliche Adapter brauchen aber ein Update:

      (10881) State "upnp.0.FRITZ!Box_7490_(UI).l2tpv3.l2tpv3.GetInfo.sid" has no existing object, this might lead to an error in future versions

      Youtube + Enigma steigen per Exception kpl. aus, sind ohne Update so nicht mehr nutzbar.
      Bspw: Youtube ( @haus-automatisierung ) :

      (17541) Error: The id "channels.HausAutomatisierungCom.video.0." is invalid. Ids are not allowed to end in "."

      Ich denke mal [--y] ist für *unattended" (habe nix mehr zum ausprobieren)? Pauschal finde ich es mittels der jetzt erfolgenden [yes/no] Abfrage besser, bin aber eh faul...:

      iobroker upgrade --y
      SBorg 1 Reply Last reply Reply Quote 0
      • J
        Jan1 last edited by

        Der Enigma2 Adapter läuft mit der Version nicht mehr:

        2021-01-09 13:18:47.837 - info: host.Beelink "system.adapter.enigma2.0" disabled
2021-01-09 13:19:03.296 - info: host.Beelink "system.adapter.enigma2.0" enabled
2021-01-09 13:19:03.363 - info: host.Beelink instance system.adapter.enigma2.0 started with pid 1556694
2021-01-09 13:19:05.000 - info: enigma2.0 (1556694) starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.enigma2, node: v14.15.4, js-controller: 3.2.3
2021-01-09 13:19:05.031 - info: enigma2.0 (1556694) starting Polling every 5000 ms
2021-01-09 13:19:05.075 - error: enigma2.0 (1556694) 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:19:05.076 - error: enigma2.0 (1556694) unhandled promise rejection: Not exists
2021-01-09 13:19:05.079 - error: enigma2.0 (1556694) Error: Not exists
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
at processImmediate (internal/timers.js:463:21)
2021-01-09 13:19:05.079 - error: enigma2.0 (1556694) Not exists
2021-01-09 13:19:05.093 - error: enigma2.0 (1556694) 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:19:05.093 - error: enigma2.0 (1556694) unhandled promise rejection: Not exists
2021-01-09 13:19:05.094 - error: enigma2.0 (1556694) Error: Not exists
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
at processImmediate (internal/timers.js:463:21)
2021-01-09 13:19:05.094 - error: enigma2.0 (1556694) Not exists
2021-01-09 13:19:05.104 - error: enigma2.0 (1556694) 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:19:05.105 - error: enigma2.0 (1556694) unhandled promise rejection: Not exists
2021-01-09 13:19:05.105 - error: enigma2.0 (1556694) Error: Not exists
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
at processImmediate (internal/timers.js:463:21)
2021-01-09 13:19:05.105 - error: enigma2.0 (1556694) Not exists
2021-01-09 13:19:05.106 - error: enigma2.0 (1556694) 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:19:05.107 - error: enigma2.0 (1556694) unhandled promise rejection: Not exists
2021-01-09 13:19:05.107 - error: enigma2.0 (1556694) Error: Not exists
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
at processImmediate (internal/timers.js:463:21)
2021-01-09 13:19:05.108 - error: enigma2.0 (1556694) Not exists
2021-01-09 13:19:05.109 - error: enigma2.0 (1556694) 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:19:05.109 - error: enigma2.0 (1556694) unhandled promise rejection: Not exists
2021-01-09 13:19:05.109 - error: enigma2.0 (1556694) Error: Not exists
at Object.maybeCallbackWithError (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2270:17)
at Immediate. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3010:38)
at processImmediate (internal/timers.js:463:21)
2021-01-09 13:19:05.110 - error: enigma2.0 (1556694) Not exists
2021-01-09 13:19:05.619 - info: enigma2.0 (1556694) terminating
2021-01-09 13:19:05.621 - warn: enigma2.0 (1556694) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-01-09 13:19:06.260 - error: host.Beelink instance system.adapter.enigma2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-01-09 13:19:06.262 - info: host.Beelink Restart adapter system.adapter.enigma2.0 because enabled

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

          @Jan1 richtig, genauso wenig wie der mihome-vacuum, Issues hab ich schon angelegt.

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

            @ilovegym
            Ist das die selbe Ursache und muss das im Adapter gefixt werden, oder im JS-Controller?

            Ich habs zur Sicherheit auch gleich noch im Adapter Thread gepostet.

            apollon77 1 Reply Last reply Reply Quote 0
            • SBorg
              SBorg Forum Testing Most Active @SBorg last edited by

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

              Youtube + Enigma steigen per Exception kpl. aus, sind ohne Update so nicht mehr nutzbar.

              +weitere kommen durch den JS-Controller, müssen aber im jeweiligen Adapter gefixt werden 😉

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

                @apollon77
                smartmeter Adapter gibt ne Warnung:
                smartmeter.0 2021-01-09 13:35:48.320 warn (2581) State "smartmeter.0.1-0:1_8_0__255.rawvalue" has no existing object, this might lead to an error in future versions

                Ansonsten ist es jetzt mit 3.2.3 sehr ruhig... 🙂

                apollon77 1 Reply Last reply Reply Quote 0
                • 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
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            854
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

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