Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. BLE Adapter crasht Raspi 4 4GB - System tot

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    BLE Adapter crasht Raspi 4 4GB - System tot

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

      HI @AlCalzone ,

      ich komm mit einem neuen System nicht weiter.

      Kurzusammenfassung:

      BLE Adapter installiert, wenn ich Ihn starte läuft er kurz an. Ich inde hinterher auch in der Objektliste dass er was gefunden hat.
      Aber nach ungefär 5-10 sekunden, steigt die ssh Verbundung aus und ioBroker ist auch nicht mehr erreichbar.
      Wenn ich dabei das Logging (silly) beobachte, gibt es keinen erkennbaren Trigger. mi-flora an und aus, Adapter neu installiert auch kein Unterschied.

      Hier meine config und Installationsschritte, :

      Raspy 4 4GB, ioBroker neu aufgesetzt:

      Node.js
      v10.19.0
      NPM
      6.13.4
      JS controller Installiert: 2.2.9

      sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev libcap2-bin
      Paketlisten werden gelesen... Fertig
      Abhängigkeitsbaum wird aufgebaut.
      Statusinformationen werden eingelesen.... Fertig
      libcap2-bin ist schon die neueste Version (1:2.25-2).
      libudev-dev ist schon die neueste Version (241-7~deb10u3+rpi1).
      bluetooth ist schon die neueste Version (5.50-1+rpt1).
      bluez ist schon die neueste Version (5.50-1+rpt1).
      libbluetooth-dev ist schon die neueste Version (5.50-1+rpt1).
      0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
      
      
      sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)
      

      keine Fehlermeldung.

      Installationmeldungen:


      $ ./iobroker add ble --host ioBroker-hostBER
      NPM version: 6.13.4
      npm install iobroker.ble@0.10.1 --loglevel error --prefix "/opt/iobroker" (System call)
      prebuild-install
      info begin Prebuild-install version 5.3.3
      prebuild-install
      info looking for cached prebuild @ /home/iobroker/.npm/_prebuilds/4d8f16-usb-v1.6.2-node-v64-linux-arm.tar.gzprebuild-install
      http request GET https://github.com/tessel/node-usb/releases/download/v1.6.2/usb-v1.6.2-node-v64-linux-arm.tar.gz
      prebuild-install
      http 404 https://github.com/tessel/node-usb/releases/download/v1.6.2/usb-v1.6.2-node-v64-linux-arm.tar.gz
      prebuild-install
      WARN install No prebuilt binaries found (target=10.19.0 runtime=node arch=arm libc= platform=linux)
      In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/node_usb.cc:1:../node_modules/nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:../node_modules/nan/nan.h:2232:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type] , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete) ^
      In file included from ../src/node_usb.h:14, from ../src/node_usb.cc:1:../src/node_usb.cc: At global scope:/home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void ()(v8::Localv8::Object)’ to ‘node::addon_register_func’ {aka ‘void ()(v8::Localv8::Object, v8::Localv8::Value, void*)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^/home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^../src/node_usb.cc:95:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(usb_bindings, Initialize) ^
      ../src/node_usb.cc: In function ‘void handleHotplug(std::pair<libusb_device*, libusb_hotplug_event>)’:../src/node_usb.cc:151:58: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, const char*, int, v8::Localv8::Value)’ is deprecated [-Wdeprecated-declarations] Nan::MakeCallback(Nan::New(hotplugThis), "emit", 2, argv); ^In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/node_usb.cc:1:../node_modules/nan/nan.h:1001:46: note: declared here NAN_DEPRECATED inline v8::Localv8::Value MakeCallback( ^
      ~~~~~~~~~
      ../src/node_usb.cc:151:58: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, const char, int, v8::Localv8::Value)’ is deprecated [-Wdeprecated-declarations] Nan::MakeCallback(Nan::New(hotplugThis), "emit", 2, argv); ^In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/node_usb.cc:1:../node_modules/nan/nan.h:1001:46: note: declared here NAN_DEPRECATED inline v8::Localv8::Value MakeCallback( ^~~~~~~~~~~~
      In file included from ../src/node_usb.h:12, from ../src/node_usb.cc:1:/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P
      , typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:/home/iobroker/.cache/node-gyp/10.19.0/include/node/node_object_wrap.h:84:78: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type] reinterpret_cast<Callback>(callback), type); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:../node_modules/nan/nan_object_wrap.h:65:61: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
      In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/device.cc:1:../node_modules/nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker
      )’:../node_modules/nan/nan.h:2232:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type] , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete) ^
      ../src/device.cc: In member function ‘void Req::submit(Device*, v8::Localv8::Function, uv_work_cb, uv_work_cb)’:../src/device.cc:220:70: warning: cast between incompatible function types from ‘uv_work_cb’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type] uv_queue_work(uv_default_loop(), &req, backend, (uv_after_work_cb) after); ^~~~~
      ../src/device.cc: In static member function ‘static void Req::default_after(uv_work_t*)’:../src/device.cc:237:64: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value)’ is deprecated [-Wdeprecated-declarations] Nan::MakeCallback(device, Nan::New(baton->callback), 1, argv); ^In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/device.cc:1:../node_modules/nan/nan.h:959:46: note: declared here NAN_DEPRECATED inline v8::Localv8::Value MakeCallback( ^~../src/device.cc:237:64: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value*)’ is deprecated [-Wdeprecated-declarations] Nan::MakeCallback(device, Nan::New(baton->callback), 1, argv); ^In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/device.cc:1:../node_modules/nan/nan.h:959:46: note: declared here NAN_DEPRECATED inline v8::Localv8::Value MakeCallback( ^~
      In file included from ../src/node_usb.h:12, from ../src/device.cc:1:/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P
      , typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:/home/iobroker/.cache/node-gyp/10.19.0/include/node/node_object_wrap.h:84:78: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type] reinterpret_cast<Callback>(callback), type); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:../node_modules/nan/nan_object_wrap.h:65:61: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
      In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/transfer.cc:1:../node_modules/nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker
      )’:../node_modules/nan/nan.h:2232:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type] , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete) ^
      ../src/transfer.cc: In function ‘void handleCompletion(Transfer*)’:../src/transfer.cc:126:72: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value)’ is deprecated [-Wdeprecated-declarations] Nan::MakeCallback(self->handle(), Nan::New(self->v8callback), 3, argv); ^In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/transfer.cc:1:../node_modules/nan/nan.h:959:46: note: declared here NAN_DEPRECATED inline v8::Localv8::Value MakeCallback( ^~../src/transfer.cc:126:72: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value*)’ is deprecated [-Wdeprecated-declarations] Nan::MakeCallback(self->handle(), Nan::New(self->v8callback), 3, argv); ^In file included from ../src/helpers.h:3, from ../src/node_usb.h:21, from ../src/transfer.cc:1:../node_modules/nan/nan.h:959:46: note: declared here NAN_DEPRECATED inline v8::Localv8::Value MakeCallback( ^~
      In file included from ../src/node_usb.h:12, from ../src/transfer.cc:1:/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P
      , typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:/home/iobroker/.cache/node-gyp/10.19.0/include/node/node_object_wrap.h:84:78: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type] reinterpret_cast<Callback>(callback), type); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:../node_modules/nan/nan_object_wrap.h:65:61: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void ()(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
      In file included from ../src/BluetoothHciSocket.cpp:8:../../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker
      )’:../../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void ()(uv_work_t)’ {aka ‘void ()(uv_work_s)’} to ‘uv_after_work_cb’ {aka ‘void ()(uv_work_s, int)’} [-Wcast-function-type] , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete) ^
      In file included from /home/iobroker/.cache/node-gyp/10.19.0/include/node/node_buffer.h:25, from ../src/BluetoothHciSocket.cpp:7:../src/BluetoothHciSocket.cpp: At global scope:/home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void ()(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void ()(v8::Localv8::Object)’} to ‘node::addon_register_func’ {aka ‘void ()(v8::Localv8::Object, v8::Localv8::Value, void)’} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^/home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^../src/BluetoothHciSocket.cpp:578:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(binding, BluetoothHciSocket::Init); ^
      In file included from /home/iobroker/.cache/node-gyp/10.19.0/include/node/node.h:63, from /home/iobroker/.cache/node-gyp/10.19.0/include/node/node_buffer.h:25, from ../src/BluetoothHciSocket.cpp:7:/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfonode::ObjectWrap&)]’:/home/iobroker/.cache/node-gyp/10.19.0/include/node/node_object_wrap.h:84:78: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfonode::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfonode::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type] reinterpret_cast<Callback>(callback), type); ^
      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      /home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)]’:../../../nan/nan_object_wrap.h:65:61: required from here/home/iobroker/.cache/node-gyp/10.19.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfoNan::ObjectWrap::Callback’ {aka ‘void ()(const v8::WeakCallbackInfoNan::ObjectWrap&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
      host.ioBroker-hostBER install adapter ble
      upload [7] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/words.js words.js application/javascript
      upload [6] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/style.css style.css text/css
      upload [5] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/index_m.html index_m.html text/html
      upload [4] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/index.html index.html text/html
      upload [3] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/build/index.map build/index.map application/json
      upload [2] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/build/index.js.map build/index.js.map application/json
      upload [1] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/build/index.js build/index.js application/javascript
      upload [0] ble.admin /opt/iobroker/node_modules/iobroker.ble/admin/ble.png ble.png image/png
      host.ioBroker-hostBER object system.adapter.ble created/updated
      host.ioBroker-hostBER create instance ble
      host.ioBroker-hostBER object ble.0.options.allowNewDevices created
      host.ioBroker-hostBER object ble.0.options created
      host.ioBroker-hostBER object ble.0.info.driverState created
      host.ioBroker-hostBER object ble.0.info.connection created
      host.ioBroker-hostBER object ble.0.info created
      host.ioBroker-hostBER object system.adapter.ble.0.sigKill created
      host.ioBroker-hostBER object system.adapter.ble.0.eventLoopLag created
      host.ioBroker-hostBER object system.adapter.ble.0.outputCount created
      host.ioBroker-hostBER object system.adapter.ble.0.inputCount created
      host.ioBroker-hostBER object system.adapter.ble.0.uptime created
      host.ioBroker-hostBER object system.adapter.ble.0.memRss created
      host.ioBroker-hostBER object system.adapter.ble.0.memHeapTotal created
      host.ioBroker-hostBER object system.adapter.ble.0.memHeapUsed created
      host.ioBroker-hostBER object system.adapter.ble.0.cputime created
      host.ioBroker-hostBER object system.adapter.ble.0.cpu created
      host.ioBroker-hostBER object system.adapter.ble.0.compactMode created
      host.ioBroker-hostBER object system.adapter.ble.0.connected created
      host.ioBroker-hostBER object system.adapter.ble.0.alive created
      host.ioBroker-hostBER object system.adapter.ble.0 created
      process exited with code 0

      Nach Installation kommt die Konfigseite aber da steigt der Raspi aus

      Also Stromreset und nach Boot ist Adapter rot, und wird auch manuell über Admin deaktiviert.

      Log vom reboot:

      host.ioBroker-hostBER	2020-03-22 16:03:44.112	info	Do not restart adapter system.adapter.ble.0 because disabled or deleted
      host.ioBroker-hostBER	2020-03-22 16:03:44.111	error	instance system.adapter.ble.0 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
      ble.0	2020-03-22 16:03:43.571	warn	(1311) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
      ble.0	2020-03-22 16:03:43.514	error	(1311) adapter disabled
      rpi2.0	2020-03-22 16:03:40.215	error	(1251) No Value found for cpu_frequency
      

      Bei deaktivierten Adapter System stabil.

      hciconfig
      hci0:   Type: Primary  Bus: UART
              BD Address: DC:A6:32:3E:F2:CD  ACL MTU: 1021:8  SCO MTU: 64:1
              UP RUNNING
              RX bytes:778 acl:0 sco:0 events:48 errors:0
              TX bytes:1775 acl:0 sco:0 commands:48 errors:0
      
      

      In den BLE Einstellungen, also alles so belassen, bei plugins xiaomi eintragen.

      Adapter starten über ioBroker Admin. Nach c.a. 10 sek. ist der Raspi weg.

      Anbei noch die Logs von allem:
      iobroker.2020-03-22.log.htm

      Ich bin ratlos, irgendwie ist der ganze io Stack weg nach sec, weil ssh auch abraucht.

      Any idea ?

      LG

      Milo

      AlCalzone 1 Reply Last reply Reply Quote 0
      • AlCalzone
        AlCalzone Developer @mwp007 last edited by

        @mwp007 Kannst du mal die CPU- und RAM-Auslastung beobachten, wenn du den Adapter startest?

        1 Reply Last reply Reply Quote 0
        • M
          mwp007 last edited by

          Das ist das letzte Zucken bevor ssh weg ist.
          2020-03-22.png

          AlCalzone 1 Reply Last reply Reply Quote 0
          • AlCalzone
            AlCalzone Developer @mwp007 last edited by

            @mwp007 Sieht relativ entspannt aus. Ich weiß ehrlich gesagt, nicht was los ist.

            1 Reply Last reply Reply Quote 0
            • M
              mwp007 last edited by mwp007

              der adapter läuft ja auch an, Nach neustart und deaktivierung habe ich ne Objektliste:
              313bc230-fb3b-4790-b948-ce23101e9148-grafik.png

              hier nochmal das letzte Zucken aus Mem sicht.

              9026e240-d0a6-42ac-afba-096ca9d98962-grafik.png

              ich probier mal alle anderen adapter ausser web und admin auszuschalten

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

                @mwp007 Was hast du für ein Netzteil? der Pi4 ist da sehr empfindlich.
                Möglicherweise zieht der BT dann die Spannung runter

                1 Reply Last reply Reply Quote 0
                • M
                  mwp007 last edited by mwp007

                  Hab ein Original Raspi Netzteil. Ich zeih aber mal den USB Stick raus jetzt, die anderen Adapter hat nix gebracht. Hab auhc noch die StromPI PLatine, kann ich dann auch noch ran tackern

                  1 Reply Last reply Reply Quote 0
                  • M
                    mwp007 last edited by

                    Also USB Stick raus, alle anderen Adapter aus.
                    Funzt immer noch nicht.

                    Muss mal was essen, dann schau ich mal nach Voltage logging und StromPI

                    1 Reply Last reply Reply Quote 0
                    • M
                      mwp007 last edited by

                       vcgencmd get_throttled
                      throttled=0x0
                      
                      Homoran 1 Reply Last reply Reply Quote 0
                      • Homoran
                        Homoran Global Moderator Administrators @mwp007 last edited by

                        @mwp007 Aber warum?

                        1 Reply Last reply Reply Quote 0
                        • M
                          mwp007 last edited by mwp007

                          Warum was ?
                          0x0 heisst doch kein Bit gesetzt, alles in Ordnung, oder ?

                          0: under-voltage
                          1: arm frequency capped
                          2: currently throttled
                          16: under-voltage has occurred
                          17: arm frequency capped has occurred
                          18: throttling has occurred

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

                            @mwp007 Sorry ich dachte das war eine Fehlermeldung dass gedrosselt wurde

                            1 Reply Last reply Reply Quote 0
                            • M
                              mwp007 last edited by

                              @Homoran : aahh OK .. eben nicht 🙂

                              Also hab jetzt eine BT Dongle reingesteckt, und im BLE auf Adapter 1 gewechselt.

                              Jetzt läufts^^

                              Hardware Fehler im BT Chip aufn Raspi vielleicht?

                              AUf jden Fall, jetzt da dass läuft muss ich wohl gleich noch neues Topic aufmachen..

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

                                @mwp007 sagte in BLE Adapter crasht Raspi 4 4GB - System tot:

                                Hardware Fehler im BT Chip aufn Raspi vielleicht?

                                Möchlich, aber eher ist das "originale" Netzteil doch zu schwach und der "Dongle" zieht weniger Strom

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

                                  @Homoran hmm.. aber dann müsste er doch bei vcgencmd, was anderes als 0 anzeigen wenn undervoltage aufgetreten wär... ich mach noch den Zigbee mit dem 18dB Booster ran und ne SSD.
                                  Dongle und USB Stick sagen gehen zusammen bisher.

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mwp007 last edited by

                                    also der adpater hat auch jetzt nen crash gemacht auch über den Dongle.. hab noch ne zweite insanz installiert auf den internen, und dann waren beide instanze hin.
                                    da kam auch ein seltsames warning und im log war gut was los mit neustart des adapters

                                    (2669) Got terminate signal. Checking desired PID: 2737 vs own PID 2669
                                    

                                    aber ich bin ein bischen weiter :

                                    nachdem ich die zwei mi-flora sensoren und den einen mi temp & humidity sensor ausgemacht hab (battery off) und den BLE adapter neu installiert hab läuft es auch wieder über das interne BT.

                                    BLE Dapter frisch, kein Plugin aktiviert, keine Xiaomi sensoren aktiv: läuft stabil soweit

                                    Bis jetzt habe ich den Eindruck, als ob der adapter ein call stack overflow verursacht hat, wenn er einen von den sensoren nicht richtig lesen kann ( die waren im anderen Zimmer )

                                    AlCalzone 1 Reply Last reply Reply Quote 0
                                    • AlCalzone
                                      AlCalzone Developer @mwp007 last edited by

                                      @mwp007 sagte in BLE Adapter crasht Raspi 4 4GB - System tot:

                                      Bis jetzt habe ich den Eindruck, als ob der adapter ein call stack overflow verursacht hat, wenn er einen von den sensoren nicht richtig lesen kann

                                      Wenn das so ist, liegt das leider außerhalb meiner Macht, da der Bluetooth-Stack durch eine Abhängigkeit angesteuert wird 😞

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        mwp007 @AlCalzone last edited by mwp007

                                        @AlCalzone hej.. absolut nicht deine schuld !
                                        diese xiaomi dinger sind echt billig und schwer zu proggen.

                                        geht doch nur darum herauszufinden wie diese dinger zum laufen zu kriegen sind 😉

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mwp007 last edited by mwp007

                                          hat leider nix mit xioami zu tun..
                                          nachdem es ja lief über internes BT, war nach neustart wieder der freeze des systems da.

                                          hab jetzt also wieder alle xiaomi sensoren deaktiviert, objektliste gelöscht und wieder freeze

                                          werd langsam irre kann den fehler nicht eingrenzen
                                          nur wenn ich den adpater deaktivire läufts.

                                          sieht aber alles immer noch nach stack overflow im adapter aus

                                          gudn8t erstmal

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            mwp007 last edited by mwp007

                                            @AlCalzone kannst du bitte eine version bereitstellen die nicht nach der installation, sofort aktiv ist, obwohl sie nach der config fragt. da das system ziemlich direkt nach der installation abraucht, scheint das leider der fall zu sein.
                                            Ich bin mir auch nicht sicher ob die deinstalltion per admin die configs cleant. ist es beim deinstall per console anders?

                                            würde mir sehr bei der fehlereingrenzung helfen. Danke ! 🙂

                                            AlCalzone 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

                                            866
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            ble crash raspberry 4
                                            5
                                            41
                                            2659
                                            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