Navigation

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

    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

    Radar2 startet nicht

    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      LarryXXL @LarryXXL last edited by Homoran

      @larryxxl

      Radar 2 startet nicht.

      log

      host.iob-server
      2023-07-17 15:06:54.411	info	Restart adapter system.adapter.radar2.0 because enabled
      host.iob-server
      2023-07-17 15:06:54.411	error	instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      
      radar2.0
      2023-07-17 15:06:54.382	info	terminating
      
      radar2.0
      2023-07-17 15:06:53.933	info	debug: created State radar2.0.info.connection
      
      radar2.0
      2023-07-17 15:06:53.884	info	terminating
      
      radar2.0
      2023-07-17 15:06:53.884	info	terminating
      
      radar2.0
      2023-07-17 15:06:53.884	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      
      radar2.0
      2023-07-17 15:06:53.883	info	terminating
      
      radar2.0
      2023-07-17 15:06:53.883	info	Adapter disconnected and stopped with dostop(null) and callback(true)
      
      radar2.0
      2023-07-17 15:06:53.883	info	Unload adapter now with null
      
      radar2.0
      2023-07-17 15:06:53.878	error	Exception-Code: ENOENT: spawn ping ENOENT
      
      radar2.0
      2023-07-17 15:06:53.878	error	Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
      
      radar2.0
      2023-07-17 15:06:53.878	error	uncaught exception: spawn ping ENOENT
      
      radar2.0
      2023-07-17 15:06:53.877	warn	Uncaught Exception: spawn ping ENOENT
      
      radar2.0
      2023-07-17 15:06:53.862	info	Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B
      
      radar2.0
      2023-07-17 15:06:53.851	info	debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices!
      
      radar2.0
      2023-07-17 15:06:53.850	info	debug: radar2 set to scan every 30 seconds and printers every 720 minutes.
      
      radar2.0
      2023-07-17 15:06:53.776	info	Connected with '0.0.0.0' for DHCP Scan
      
      radar2.0
      2023-07-17 15:06:53.769	info	arp-scan will use the following interfaces: [ 'ens18' ]
      
      radar2.0
      2023-07-17 15:06:53.769	info	debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ]
      
      radar2.0
      2023-07-17 15:06:53.768	info	debug: use known BT list: [ '01:12:23:34:45:56' ]
      
      radar2.0
      2023-07-17 15:06:53.767	info	debug: radar2 set to flag items away if they are not seen for 3 minutes
      
      radar2.0
      2023-07-17 15:06:53.567	info	debug: started #3 hciconfig hci0 up
      
      radar2.0
      2023-07-17 15:06:53.448	info	debug: started #2 hciconfig hci0 down
      
      radar2.0
      2023-07-17 15:06:53.443	info	Will run hcitool-mode and not noble on device [ [Object] ]!
      
      radar2.0
      2023-07-17 15:06:53.425	info	debug: started #1 hcitool dev
      
      radar2.0
      2023-07-17 15:06:53.411	info	Will use l2Ping for BT scans.
      
      radar2.0
      2023-07-17 15:06:53.405	info	radar2 initialization started...
      
      radar2.0
      2023-07-17 15:06:53.404	info	debug: radar2 received 2 objects and 1 states, with config devices,scandelay,arp_scan_cmd,btadapterid,printerdelay,debug,knownIPs,knownBTs,external,delayaway,delayuwz,numuwz,hcionly,l2ponly,longuwz,suBT,suIP,lang,latitude,longitude,adapterConf,loglevel
      
      radar2.0
      2023-07-17 15:06:53.364	info	starting. Version 2.0.7 (non-npm: frankjoke/ioBroker.radar2) in /opt/iobroker/node_modules/iobroker.radar2, node: v18.16.1, js-controller: 5.0.8
      host.iob-server
      2023-07-17 15:06:52.579	info	instance system.adapter.radar2.0 started with pid 2469
      host.iob-server
      2023-07-17 13:06:22.554	info	Restart adapter system.adapter.radar2.0 because enabled
      host.iob-server
      2023-07-17 13:06:22.554	error	instance system.adapter.radar2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
      
      radar2.0
      2023-07-17 13:06:22.523	info	terminating
      
      radar2.0
      2023-07-17 13:06:22.069	info	debug: created State radar2.0.info.connection
      
      radar2.0
      2023-07-17 13:06:22.024	info	terminating
      
      radar2.0
      2023-07-17 13:06:22.023	info	terminating
      
      radar2.0
      2023-07-17 13:06:22.023	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
      
      radar2.0
      2023-07-17 13:06:22.023	info	terminating
      
      radar2.0
      2023-07-17 13:06:22.023	info	Adapter disconnected and stopped with dostop(null) and callback(true)
      
      radar2.0
      2023-07-17 13:06:22.022	info	Unload adapter now with null
      
      radar2.0
      2023-07-17 13:06:22.018	error	Exception-Code: ENOENT: spawn ping ENOENT
      
      radar2.0
      2023-07-17 13:06:22.018	error	Error: spawn ping ENOENT at ChildProcess._handle.onexit (node:internal/child_process:283:19) at onErrorNT (node:internal/child_process:476:16) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
      
      radar2.0
      2023-07-17 13:06:22.017	error	uncaught exception: spawn ping ENOENT
      
      radar2.0
      2023-07-17 13:06:22.017	warn	Uncaught Exception: spawn ping ENOENT
      
      radar2.0
      2023-07-17 13:06:22.002	info	Will try to scan BT devices: hci0 78:8A:86:1F:0B:8B
      
      radar2.0
      2023-07-17 13:06:21.991	info	debug: Will 'not save' unknown BT devices and will 'save' unknown IP devices!
      
      radar2.0
      2023-07-17 13:06:21.990	info	debug: radar2 set to scan every 30 seconds and printers every 720 minutes.
      
      radar2.0
      2023-07-17 13:06:21.918	info	Connected with '0.0.0.0' for DHCP Scan
      
      radar2.0
      2023-07-17 13:06:21.912	info	arp-scan will use the following interfaces: [ 'ens18' ]
      
      radar2.0
      2023-07-17 13:06:21.911	info	debug: use known IP list: [ '192.168.178.10', '192.168.178.10' ]
      
      radar2.0
      2023-07-17 13:06:21.911	info	debug: use known BT list: [ '01:12:23:34:45:56' ]
      
      radar2.0
      2023-07-17 13:06:21.910	info	debug: radar2 set to flag items away if they are not seen for 3 minutes
      
      radar2.0
      2023-07-17 13:06:21.723	info	debug: started #3 hciconfig hci0 up
      
      radar2.0
      2023-07-17 13:06:21.604	info	debug: started #2 hciconfig hci0 down
      
      radar2.0
      2023-07-17 13:06:21.600	info	Will run hcitool-mode and not noble on device [ [Object] ]!
      
      radar2.0
      2023-07-17 13:06:21.580	info	debug: started #1 hcitool dev
      
      radar2.0
      2023-07-17 13:06:21.566	info	Will use l2Ping for BT scans.
      
      radar2.0
      2023-07-17 13:06:21.560	info	radar2 initialization started...
      
      radar2.0
      2023-07-17 13:06:21.559	info	debug: radar2 received 2 objects and 1 states, with config devices,scandelay,arp_scan_cmd,btadapterid,printerdelay,debug,knownIPs,knownBTs,external,delayaway,delayuwz,numuwz,hcionly,l2ponly,longuwz,suBT,suIP,lang,latitude,longitude,adapterConf,loglevel
      
      radar2.0
      2023-07-17 13:06:21.512	info	starting. Version 2.0.7 (non-npm: frankjoke/ioBroker.radar2) in /opt/iobroker/node_modules/iobroker.radar2, node: v18.16.1, js-controller: 5.0.8
      
      radar2.0
      2023-07-17 13:06:21.426	debug	States connected to redis: 127.0.0.1:9000
      
      radar2.0
      2023-07-17 13:06:21.373	debug	States create User PubSub Client
      
      radar2.0
      2023-07-17 13:06:21.373	debug	States create System PubSub Client
      
      radar2.0
      2023-07-17 13:06:21.366	debug	Redis States: Use Redis connection: 127.0.0.1:9000
      
      radar2.0
      2023-07-17 13:06:21.351	debug	Objects connected to redis: 127.0.0.1:9001
      
      radar2.0
      2023-07-17 13:06:21.347	debug	Objects client initialize lua scripts
      
      radar2.0
      2023-07-17 13:06:21.329	debug	Objects create User PubSub Client
      
      radar2.0
      2023-07-17 13:06:21.328	debug	Objects create System PubSub Client
      
      radar2.0
      2023-07-17 13:06:21.327	debug	Objects client ready ... initialize now
      
      radar2.0
      2023-07-17 13:06:21.309	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001
      host.iob-server
      2023-07-17 13:06:20.735	info	instance system.adapter.radar2.0 started with pid 2434
      

      MOD-EDIT: Code in code-tags gesetzt!

      die adapter Hilfe habe ich schon ausprobiert.
      Fehler verschwindet einfach nicht

      grrfield 1 Reply Last reply Reply Quote 0
      • grrfield
        grrfield @LarryXXL last edited by

        @larryxxl Hast Du die Befehle unter https://github.com/iobroker-community-adapters/ioBroker.radar2#installation ausgeführt?

        L 1 Reply Last reply Reply Quote 0
        • L
          LarryXXL @grrfield last edited by

          @grrfield

          ja habe die Befehle schon ausgeführt. Denke das in IOBroker alles ok ist. Aber etwas unter Ubuntu fehlt oder falsch installiert ist.

          Es laufen alle anderen Adapter bis auf den Radar2.
          Auch Bluetooth ist ok unter Proxmox und einer VM. Habe hierfür allerdings verschiedene M2 Wifi adapter ausprobieren müssen. Intel war ein Problem AX201,210. Realtek funktioniert aber.

          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @LarryXXL last edited by Thomas Braun

            @larryxxl

            Zeitzone ist nicht richtig gesetzt, du hampelst als root herum.

            L 1 Reply Last reply Reply Quote 0
            • L
              LarryXXL @Thomas Braun last edited by

              @thomas-braun

              Kann es sein das man als User "Pi" mit Sudo mehr rumhampelt als als "root" ?
              Und wenn eine falsche Zeitzone dem Radar2 Adapter beim Starten permanent abstürzen lässt sollte ich vielleicht doch noch Lotto spielen.😇

              Thomas Braun 2 Replies Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @LarryXXL last edited by

                @larryxxl sagte in Radar2 startet nicht:

                Kann es sein das man als User "Pi" mit Sudo mehr rumhampelt als als "root" ?

                Nein.

                1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @LarryXXL last edited by

                  @larryxxl sagte in Radar2 startet nicht:

                  Und wenn eine falsche Zeitzone dem Radar2 Adapter beim Starten permanent abstürzen lässt sollte ich vielleicht doch noch Lotto spielen.

                  Ist halt ein Indikator dafür daß das System nicht senkrecht eingerichtet ist. Vor allem in Kombination mit dem root.

                  L 1 Reply Last reply Reply Quote 0
                  • L
                    LarryXXL @Thomas Braun last edited by

                    @thomas-braun

                    wo stelle ich die Zeitzone in IOBroker ein ?

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @LarryXXL last edited by

                      @larryxxl

                      Die Zeitzone in deinem OS ist falsch.

                      L 1 Reply Last reply Reply Quote 0
                      • L
                        LarryXXL @Thomas Braun last edited by Homoran

                        @thomas-braun

                        To restore this content, you can run the 'unminimize' command.
                        Last login: Mon Jul 17 14:26:06 2023 from 192.168.1.150
                        root@iob-server:~# su pi
                        pi@iob-server:/root$ sudo timedatectl set-timezone Europe/Berlin
                        [sudo] password for pi:
                        pi@iob-server:/root$ sudo timedatectl
                                       Local time: Tue 2023-07-18 20:36:07 CEST
                                   Universal time: Tue 2023-07-18 18:36:07 UTC
                                         RTC time: Tue 2023-07-18 18:36:07
                                        Time zone: Europe/Berlin (CEST, +0200)
                        System clock synchronized: yes
                                      NTP service: active
                                  RTC in local TZ: no
                        pi@iob-server:/root$
                        

                        MOD-EDIT: Code in code-tags gesetzt!

                        Das nächste Prolem war das wenn ich das aktuellen Beta Admin.adapter installiere iobroker gar nicht mehr startet. 6.6.0->6.6.1.

                        danach war ein Rollback nötig.

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @LarryXXL last edited by

                          @larryxxl sagte in Radar2 startet nicht:

                          Das nächste Prolem war das wenn ich das aktuellen Beta Admin.adapter installiere iobroker gar nicht mehr startet. 6.6.0->6.6.1.
                          danach war ein Rollback nötig.

                          Was soll ich sagen...
                          Hat es auf meinem System natürlich getan.

                          L 1 Reply Last reply Reply Quote 0
                          • L
                            LarryXXL @Thomas Braun last edited by

                            @thomas-braun

                            Ubuntu neu installiert. kein root. iobroker neu installiert. Adapter neu installiert und eingerichtet. Zigbee Backup eingespielt.

                            alles gebrauchten Adapter sind nun grün und laufen.
                            Blockly Scripte mussten teilweise korrigiert werden weil jetzt die empfohlende node Version benutzt wird.
                            Alles soweit ok.

                            Thomas Braun crunchip 2 Replies Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @LarryXXL last edited by

                              @larryxxl

                              Also 'kaum macht man es ordentlich/richtig, schon funktioniert es?'

                              1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @LarryXXL last edited by

                                @larryxxl sagte in Radar2 startet nicht:

                                Blockly Scripte mussten teilweise korrigiert werden weil jetzt die empfohlende node Version benutzt wird.

                                Verstehe ich aber nicht ganz den Zusammenhang

                                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

                                472
                                Online

                                32.1k
                                Users

                                80.7k
                                Topics

                                1.3m
                                Posts

                                4
                                15
                                637
                                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