Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test js-controller v2.0.x (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

    Test js-controller v2.0.x (GitHub)

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

      ich habe die neueste Radar2-Version.
      Ich bekomme keine Unwetter-Warnungen, weil die im Admin
      angegebene GPS-Position nicht verarbeitet werden kann.

      No geo location data found configured in admin to calculate UWZ AREA ID or ID not valid!

      Gruß,
      Mathias

      apollon77 arteck 2 Replies Last reply Reply Quote 0
      • apollon77
        apollon77 @SBorg last edited by

        @SBorg ich dachte immer das das gethostinfo was mit DNS oder Netzwerk zu tun hat ...

        Also mach ich die Änderungen wegen Dashboard wieder rückgängig?! Mal nach der Fehlermeldung im Browser Konsole gesucht?

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

          @MathiasJ hm ... da ist jetzt die Frage ob diese GitHub Version kaputt ist oder es am Controller 2 liegt?! Müsste man auf nem 1.5.x mal Gegenchecken.

          M MathiasJ 2 Replies Last reply Reply Quote 0
          • M
            msauer @apollon77 last edited by

            @apollon77 said in [Aufruf] js-controller 2.0 Beta Test:

            hm ... da ist jetzt die Frage ob diese GitHub Version kaputt ist oder es am Controller 2 liegt?! Müsste man auf nem 1.5.x mal Gegenchecken.

            Wegen dem Problem habe sich ein Issue bei Radar2 aufgemacht..

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

              @apollon77
              Was willst Du mit der 1.5 gegenchecken?
              Vor dem Update lief es ja.
              Nach einem Reboot wurden zumindest mal alle BT-Geräte erkannt, sowohl unter noble, als auch hci only.
              Erinnert mich irgendwie an meine andere Testinstallation unter Node 12.x
              Da ging weder Radar2, noch BLE.
              Diese Installation läuft hingegen mit Node 10.x

              1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active @MathiasJ last edited by arteck

                @MathiasJ welches Program ?? verarbeitet die Unwetter Warnung ? dwd ?? oder was hast du da am laufen

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

                  Ich dachte, das wird auch von Radar übernommen, wenn Du den richtigen Standort im Admin angibst?
                  In der produktiven Installation bekomme ich eine Meldung von DWD, eine andere von Radar2.
                  Bei der Testinstallation bekomme ich keine Meldung, weil ich DWD deaktiviert habe.
                  Und Radar kann die GPS Position nicht verwerten

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

                    ... und beide Installationen haben die gleiche Radar Version?

                    MathiasJ 1 Reply Last reply Reply Quote 0
                    • E
                      e-i-k-e last edited by e-i-k-e

                      Haben soeben mein Multihost System auf 2.0.12 aktualisiert.
                      Bei mir läuft alles 👍

                      Mein Master spukt mir auch folgendes aus.

                      Unbenannt.JPG

                      anbei die log vom Master. iobroker.2019-09-27.log

                      apollon77 1 Reply Last reply Reply Quote 0
                      • apollon77
                        apollon77 @e-i-k-e last edited by apollon77

                        @e-i-k-e Jupp. Fox für diese Fehlanzeige bei redis/redis kommt heute Nacht denke ich. Muss ja meinem Release Rhythmus treu bleiben 😜

                        E 1 Reply Last reply Reply Quote 1
                        • E
                          e-i-k-e @apollon77 last edited by

                          @apollon77 So ist es 😜
                          Danke für deine Arbeit!

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

                            @apollon77
                            ja, haben sie. Radar2 1.2.0

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

                              @MathiasJ ok. Checke.

                              J MathiasJ 2 Replies Last reply Reply Quote 0
                              • J
                                Jan1 @apollon77 last edited by

                                @apollon77
                                mit der 2.0.12 viele Errors im Log bei einem Neustart und Dashboard von Node-Red und Qcontrol immer noch leer, sonst keine Probleme erkannt.

                                host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.417	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.416	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.415	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.414	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.413	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: (node:15413) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js proc
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: at TCP._handle.close (net.js:606:12)
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:82:20)
host.Beelink	2019-09-28 08:23:07.412	error	Caught by controller[1]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:115:25)
host.Beelink	2019-09-28 08:23:07.411	error	Caught by controller[1]: (node:15413) UnhandledPromiseRejectionWarning: Error: Connection is closed.

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

                                  @apollon77
                                  vielleicht is es ja weg, Du hast soweit ich mich erinnern kann, heute Nacht neu released.
                                  ich habe aber die Version von vorgestern noch drauf.

                                  apollon77 2 Replies Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 @MathiasJ last edited by

                                    @MathiasJ ich habe letzte Nacht nix gemacht 😉 war zu müde.

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

                                      @Jan1 Qontrol aktualisiert? Musst du. Mach mal. Dann sollte das wieder tun.

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

                                        Also auf meiner check Liste für heute steht:

                                        • nochmal die redis Promise Warnungen ansehen
                                        • Radar2 Fehler
                                        • iobroker Status bei redis/redis
                                        • node-red wegen Dashboard schauen (mal installieren und sehen ob’s bei mir tut)
                                        • ggf iot schauen mit Google devices. Da gabs auch einen fehlerbericht.

                                        Fehlt was?

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

                                          @apollon77
                                          alles aktuell, hier mal ein Bild, nicht dass wir aneinander vorbei reden
                                          58c30868-bf72-4157-8d17-adfb1fbb9646-grafik.png

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

                                            Also node-red:

                                            • frisch 1.10.1 installiert
                                            • dashbard tut
                                            • Aufruf als eigener ioBroker "tab" und via link tut auch

                                            Wenn es bei dir als tab nicht tut: Irgendwie master/slave? Was ist dann wo? Steht was in Browser Konsole?

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            897
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller
                                            48
                                            1047
                                            253324
                                            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