Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter EnOcean v0.8.x

    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 Adapter EnOcean v0.8.x

    This topic has been deleted. Only users with topic management privileges can see it.
    • Jey Cee
      Jey Cee Developer @JuFu last edited by

      @jufu also dann nochmal von vorn, Log level der Instanz auf debug stellen (siehe screenshot). Dann bitte einmal die Adapterkonfiguration öffnen nachdem der Adapter gestartet ist. Anschließend das Log als TEXT in code Tags hier Posten.
      Loglevel_aendern.png

      J 2 Replies Last reply Reply Quote 0
      • J
        JuFu @Jey Cee last edited by

        @jey-cee die Instanz in den Debug Modus setzen hatte ich gemachtsetting1.JPG
        Wie ich jedoch das 'Log als TEXT in code Tags' hier poste ist mir nicht klar.
        Hab das Log heruntergeladen und dann den Text kopiert, aber wie weiter?

        Wie schon erwähnt - blutiger Anfänger ... 🤷‍♂️

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

          @Jey-Cee hat etwas gedauert aber ich meine jetzt herausgefunden zu haben wie das mit dem 'Log als TEXT in code Tags' gemeint ist.

          2022-10-28 10:12:29.334 - error: host.ioBroker-slave0 Caught by controller[0]: <--- Last few GCs --->
          2022-10-28 10:12:29.335 - error: host.ioBroker-slave0 Caught by controller[0]: [64493:0x28578880] 302347 ms: Scavenge 452.1 (463.0) -> 450.6 (463.0) MB, 3.6 / 0.0 ms (average mu = 0.243, current mu = 0.206) task
          2022-10-28 10:12:29.336 - error: host.ioBroker-slave0 Caught by controller[0]: [64493:0x28578880] 302427 ms: Scavenge 452.1 (463.0) -> 450.6 (463.3) MB, 3.8 / 0.0 ms (average mu = 0.243, current mu = 0.206) task
          2022-10-28 10:12:29.336 - error: host.ioBroker-slave0 Caught by controller[0]: [64493:0x28578880] 302507 ms: Scavenge 452.2 (463.3) -> 450.7 (463.3) MB, 3.6 / 0.0 ms (average mu = 0.243, current mu = 0.206) task
          2022-10-28 10:12:29.337 - error: host.ioBroker-slave0 Caught by controller[0]: <--- JS stacktrace --->
          2022-10-28 10:12:29.337 - error: host.ioBroker-slave0 Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
          2022-10-28 10:12:29.337 - error: host.ioBroker-slave0 Caught by controller[1]: 1: 0xafdf9c node::Abort() [io.enocean.0]
          2022-10-28 10:12:29.338 - error: host.ioBroker-slave0 Caught by controller[1]: 2: 0xa21604 void node::FPrintF<>(_IO_FILE*, char const*) [io.enocean.0]
          2022-10-28 10:12:29.338 - error: host.ioBroker-slave0 Caught by controller[2]: 3: 0xcd0368 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [io.enocean.0]
          2022-10-28 10:12:29.338 - error: host.ioBroker-slave0 Caught by controller[2]: 4: 0xcd0538 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [io.enocean.0]
          2022-10-28 10:12:29.339 - error: host.ioBroker-slave0 Caught by controller[2]: 5: 0xe8c23c [io.enocean.0]
          2022-10-28 10:12:29.339 - error: host.ioBroker-slave0 Caught by controller[3]: 6: 0xe8ccc4 [io.enocean.0]
          2022-10-28 10:12:29.340 - error: host.ioBroker-slave0 Caught by controller[3]: 7: 0xe9b10c [io.enocean.0]
          2022-10-28 10:12:29.340 - error: host.ioBroker-slave0 Caught by controller[3]: 8: 0xe9b92c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [io.enocean.0]
          2022-10-28 10:12:29.340 - error: host.ioBroker-slave0 Caught by controller[3]: 9: 0xe9c978 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [io.enocean.0]
          2022-10-28 10:12:29.341 - error: host.ioBroker-slave0 Caught by controller[4]: 10: 0xea005c v8::internal::IncrementalMarkingJob::Task::RunInternal() [io.enocean.0]
          2022-10-28 10:12:29.341 - error: host.ioBroker-slave0 Caught by controller[4]: 11: 0xd9a550 non-virtual thunk to v8::internal::CancelableTask::Run() [io.enocean.0]
          2022-10-28 10:12:29.341 - error: host.ioBroker-slave0 Caught by controller[5]: 12: 0xb62eac [io.enocean.0]
          2022-10-28 10:12:29.342 - error: host.ioBroker-slave0 Caught by controller[5]: 13: 0xb66450 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [io.enocean.0]
          2022-10-28 10:12:29.342 - error: host.ioBroker-slave0 Caught by controller[6]: 14: 0x14f92d4 [io.enocean.0]
          2022-10-28 10:12:29.342 - error: host.ioBroker-slave0 Caught by controller[7]: 15: 0x150b338 [io.enocean.0]
          2022-10-28 10:12:29.343 - error: host.ioBroker-slave0 Caught by controller[8]: 16: 0x14f9d10 uv_run [io.enocean.0]
          2022-10-28 10:12:29.343 - error: host.ioBroker-slave0 Caught by controller[8]: 17: 0xa4a0ac node::SpinEventLoop(node::Environment*) [io.enocean.0]
          2022-10-28 10:12:29.343 - error: host.ioBroker-slave0 Caught by controller[8]: 18: 0xb3ab58 node::NodeMainInstance::Run() [io.enocean.0]
          2022-10-28 10:12:29.344 - error: host.ioBroker-slave0 Caught by controller[8]: 19: 0xac83d0 node::Start(int, char**) [io.enocean.0]
          2022-10-28 10:12:29.344 - error: host.ioBroker-slave0 Caught by controller[8]: 20: 0x7fba82fe18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
          2022-10-28 10:12:29.345 - error: host.ioBroker-slave0 Caught by controller[9]: 21: 0xa48724 [io.enocean.0]
          2022-10-28 10:12:29.345 - warn: host.ioBroker-slave0 instance system.adapter.enocean.0 terminated due to SIGABRT
          2022-10-28 10:12:29.346 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 terminated with code NaN ()
          2022-10-28 10:12:29.346 - info: host.ioBroker-slave0 Restart adapter system.adapter.enocean.0 because enabled
          2022-10-28 10:12:59.497 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 started with pid 64717
          2022-10-28 10:13:02.159 - debug: enocean.0 (64717) Redis Objects: Use Redis connection: 192.168.115.6:9001
          2022-10-28 10:13:02.232 - debug: enocean.0 (64717) Objects client ready ... initialize now
          2022-10-28 10:13:02.239 - debug: enocean.0 (64717) Objects create System PubSub Client
          2022-10-28 10:13:02.242 - debug: enocean.0 (64717) Objects create User PubSub Client
          2022-10-28 10:13:02.305 - debug: enocean.0 (64717) Objects client initialize lua scripts
          2022-10-28 10:13:02.326 - debug: enocean.0 (64717) Objects connected to redis: 192.168.115.6:9001
          2022-10-28 10:13:02.377 - debug: enocean.0 (64717) Redis States: Use Redis connection: 192.168.115.6:9000
          2022-10-28 10:13:02.446 - debug: enocean.0 (64717) States create System PubSub Client
          2022-10-28 10:13:02.450 - debug: enocean.0 (64717) States create User PubSub Client
          2022-10-28 10:13:02.541 - debug: enocean.0 (64717) States connected to redis: 192.168.115.6:9000
          2022-10-28 10:13:03.138 - info: enocean.0 (64717) starting. Version 0.8.3 in /opt/iobroker/node_modules/iobroker.enocean, node: v16.18.0, js-controller: 4.0.23
          2022-10-28 10:13:05.167 - error: enocean.0 (64717) Timeout for response: Get version information
          2022-10-28 10:13:06.670 - error: enocean.0 (64717) Timeout for response: Get repeater mode and level
          2022-10-28 10:13:08.173 - error: enocean.0 (64717) Timeout for response: Get frequency
          2022-10-28 10:13:09.676 - error: enocean.0 (64717) Timeout for response: Get base ID
          2022-10-28 10:13:11.179 - error: enocean.0 (64717) Timeout for response: Read learnd devices
          2022-10-28 10:13:11.181 - info: enocean.0 (64717) {"AppVersion":"undefined.undefined.undefined.undefined","ApiVersion":"undefined.undefined.undefined.undefined"}
          
          
          1 Reply Last reply Reply Quote 0
          • J
            JuFu @Jey Cee last edited by

            @jey-cee hattest Du Gelegenheit Dir das Log mal anzusehen?

            Jey Cee 1 Reply Last reply Reply Quote 0
            • Jey Cee
              Jey Cee Developer @JuFu last edited by

              @jufu ja, da ist nicht drin was ich erwartet habe. Entweder das ist kein Vollständiges Log, du hast die Einstellungen nicht aufgerufen oder der Adapter lief dabei nicht.

              J J 2 Replies Last reply Reply Quote 0
              • J
                Jaaannis @Jey Cee last edited by Jaaannis

                Hallo,

                bin umgestiegen vom USB300 auf daas USB-FAM ESP3 Gateway.
                Leider klappt der Umzug nicht ganz Reibungslos.
                Ich habe die neue Gateway ID mit passenden Endungen im PCT14 in den FSR14-4 sowie unter objects im iobroker eingetragen.
                Laut log versendet der FAM-USB auch brav, leider kommt wohl nichts im FSR an durch den FAM14...
                Hat jemand eine Idee?

                Edit: Nach großem rumprobieren:
                PCT14 hat die Änderungen wiederholt nicht vollständig übernommen.
                Immer nochmal kontrollieren ob wirklich alle Kanäle übernommen worden sind.
                Bei mir hat es jetzt drei mal "Senden an das Gerät" gebraucht um alle 8 Kanäle (2xFSR14x4) zu übertragen (PCT14 V8.9)

                Problem gelöst 🙂

                Jey Cee 1 Reply Last reply Reply Quote 0
                • Jey Cee
                  Jey Cee Developer @Jaaannis last edited by

                  @jaaannis hast du die Instanz gelöscht und neu angelegt?

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    Jaaannis @Jey Cee last edited by

                    @jey-cee
                    nein, nur die Sende ID im obejct data jeweils geändert. Klappt jetzt einwandfrei 🙂

                    1 Reply Last reply Reply Quote 0
                    • J
                      JuFu @Jey Cee last edited by

                      @jey-cee Dann hier ein weiterer Versuch:
                      Der USB300 ist am RasperberryPi (Model 3B v1.2) eingesteckt welcher als ioBroker-slave0 am ioBroker-Master Lenovo Thinkcentre M710q, Intel, Debian11) online ist.
                      Das Log des slave0 ist gelöscht, die Instanz EnOcean v0.8.3 auf dem slave0 ist gestoppt, das Log level ist debug.
                      Ich starte die Instanz EnOcean und bekomme ein 'Connected to Host', 'Heartbeat' aber kein 'Connected to device or service'.
                      Ich öffne die settings und selekte Gateway USB300 (stand schon da). Für Serial port steht bereits /dev/ttyAMA0.
                      Ich öffne Serial port, kann dort aber nur /dev/ttyAMA0 auswählen.
                      Ich schließe die Instanz Settings und gehe zu Logs.
                      Nachfolgend das komplette Log:

                      2022-10-30 10:18:44.491 - warn: host.ioBroker-slave0 "system.host.ioBroker-slave3" is offline
                      2022-10-30 10:21:48.033 - info: host.ioBroker-slave0 "system.adapter.enocean.0" enabled
                      2022-10-30 10:21:48.196 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 started with pid 173550
                      2022-10-30 10:21:50.809 - debug: enocean.0 (173550) Redis Objects: Use Redis connection: 192.168.115.6:9001
                      2022-10-30 10:21:50.893 - debug: enocean.0 (173550) Objects client ready ... initialize now
                      2022-10-30 10:21:50.948 - debug: enocean.0 (173550) Objects create System PubSub Client
                      2022-10-30 10:21:50.951 - debug: enocean.0 (173550) Objects create User PubSub Client
                      2022-10-30 10:21:51.026 - debug: enocean.0 (173550) Objects client initialize lua scripts
                      2022-10-30 10:21:51.056 - debug: enocean.0 (173550) Objects connected to redis: 192.168.115.6:9001
                      2022-10-30 10:21:51.112 - debug: enocean.0 (173550) Redis States: Use Redis connection: 192.168.115.6:9000
                      2022-10-30 10:21:51.192 - debug: enocean.0 (173550) States create System PubSub Client
                      2022-10-30 10:21:51.196 - debug: enocean.0 (173550) States create User PubSub Client
                      2022-10-30 10:21:51.285 - debug: enocean.0 (173550) States connected to redis: 192.168.115.6:9000
                      2022-10-30 10:21:52.082 - info: enocean.0 (173550) starting. Version 0.8.3 in /opt/iobroker/node_modules/iobroker.enocean, node: v16.18.0, js-controller: 4.0.23
                      2022-10-30 10:21:54.111 - error: enocean.0 (173550) Timeout for response: Get version information
                      2022-10-30 10:21:55.614 - error: enocean.0 (173550) Timeout for response: Get repeater mode and level
                      2022-10-30 10:21:57.117 - error: enocean.0 (173550) Timeout for response: Get frequency
                      2022-10-30 10:21:58.620 - error: enocean.0 (173550) Timeout for response: Get base ID
                      2022-10-30 10:22:00.122 - error: enocean.0 (173550) Timeout for response: Read learnd devices
                      2022-10-30 10:22:00.124 - info: enocean.0 (173550) {"AppVersion":"undefined.undefined.undefined.undefined","ApiVersion":"undefined.undefined.undefined.undefined"}
                      2022-10-30 10:23:04.631 - info: enocean.0 (173550) ["/dev/ttyAMA0","/dev/ttyUSB0","/dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300_DD_FT6XA94C-if00-port0"]
                      

                      Was sollte ich als nächstes probieren?

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

                        @jufu ein paar Minuten später kommen weitere Log Meldungen die wohl auch mit dem EnOcean Adapter zu tun haben (?)
                        Hier nochmals das komplette Log

                        2022-10-30 10:18:44.491 - warn: host.ioBroker-slave0 "system.host.ioBroker-slave3" is offline
                        2022-10-30 10:21:48.033 - info: host.ioBroker-slave0 "system.adapter.enocean.0" enabled
                        2022-10-30 10:21:48.196 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 started with pid 173550
                        2022-10-30 10:21:50.809 - debug: enocean.0 (173550) Redis Objects: Use Redis connection: 192.168.115.6:9001
                        2022-10-30 10:21:50.893 - debug: enocean.0 (173550) Objects client ready ... initialize now
                        2022-10-30 10:21:50.948 - debug: enocean.0 (173550) Objects create System PubSub Client
                        2022-10-30 10:21:50.951 - debug: enocean.0 (173550) Objects create User PubSub Client
                        2022-10-30 10:21:51.026 - debug: enocean.0 (173550) Objects client initialize lua scripts
                        2022-10-30 10:21:51.056 - debug: enocean.0 (173550) Objects connected to redis: 192.168.115.6:9001
                        2022-10-30 10:21:51.112 - debug: enocean.0 (173550) Redis States: Use Redis connection: 192.168.115.6:9000
                        2022-10-30 10:21:51.192 - debug: enocean.0 (173550) States create System PubSub Client
                        2022-10-30 10:21:51.196 - debug: enocean.0 (173550) States create User PubSub Client
                        2022-10-30 10:21:51.285 - debug: enocean.0 (173550) States connected to redis: 192.168.115.6:9000
                        2022-10-30 10:21:52.082 - info: enocean.0 (173550) starting. Version 0.8.3 in /opt/iobroker/node_modules/iobroker.enocean, node: v16.18.0, js-controller: 4.0.23
                        2022-10-30 10:21:54.111 - error: enocean.0 (173550) Timeout for response: Get version information
                        2022-10-30 10:21:55.614 - error: enocean.0 (173550) Timeout for response: Get repeater mode and level
                        2022-10-30 10:21:57.117 - error: enocean.0 (173550) Timeout for response: Get frequency
                        2022-10-30 10:21:58.620 - error: enocean.0 (173550) Timeout for response: Get base ID
                        2022-10-30 10:22:00.122 - error: enocean.0 (173550) Timeout for response: Read learnd devices
                        2022-10-30 10:22:00.124 - info: enocean.0 (173550) {"AppVersion":"undefined.undefined.undefined.undefined","ApiVersion":"undefined.undefined.undefined.undefined"}
                        2022-10-30 10:23:04.631 - info: enocean.0 (173550) ["/dev/ttyAMA0","/dev/ttyUSB0","/dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300_DD_FT6XA94C-if00-port0"]
                        2022-10-30 10:26:53.571 - error: host.ioBroker-slave0 Caught by controller[0]: <--- Last few GCs --->
                        2022-10-30 10:26:53.573 - error: host.ioBroker-slave0 Caught by controller[0]: [173550:0x237d6880] 302520 ms: Scavenge 452.0 (463.0) -> 450.6 (463.0) MB, 6.9 / 0.0 ms (average mu = 0.223, current mu = 0.171) task
                        2022-10-30 10:26:53.574 - error: host.ioBroker-slave0 Caught by controller[0]: [173550:0x237d6880] 302573 ms: Scavenge 452.1 (463.0) -> 450.6 (463.3) MB, 7.7 / 0.0 ms (average mu = 0.223, current mu = 0.171) task
                        2022-10-30 10:26:53.574 - error: host.ioBroker-slave0 Caught by controller[0]: [173550:0x237d6880] 302640 ms: Scavenge 452.2 (463.3) -> 450.7 (463.3) MB, 4.6 / 0.0 ms (average mu = 0.223, current mu = 0.171) task
                        2022-10-30 10:26:53.575 - error: host.ioBroker-slave0 Caught by controller[1]: <--- JS stacktrace --->
                        2022-10-30 10:26:53.575 - error: host.ioBroker-slave0 Caught by controller[1]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                        2022-10-30 10:26:53.576 - error: host.ioBroker-slave0 Caught by controller[2]: 1: 0xafdf9c node::Abort() [io.enocean.0]
                        2022-10-30 10:26:53.576 - error: host.ioBroker-slave0 Caught by controller[3]: 2: 0xa21604 void node::FPrintF<>(_IO_FILE*, char const*) [io.enocean.0]
                        2022-10-30 10:26:53.577 - error: host.ioBroker-slave0 Caught by controller[4]: 3: 0xcd0368 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [io.enocean.0]
                        2022-10-30 10:26:53.578 - error: host.ioBroker-slave0 Caught by controller[5]: 4: 0xcd0538 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [io.enocean.0]
                        2022-10-30 10:26:53.578 - error: host.ioBroker-slave0 Caught by controller[6]: 5: 0xe8c23c [io.enocean.0]
                        2022-10-30 10:26:53.579 - error: host.ioBroker-slave0 Caught by controller[7]: 6: 0xe8ccc4 [io.enocean.0]
                        2022-10-30 10:26:53.580 - error: host.ioBroker-slave0 Caught by controller[8]: 7: 0xe9b10c [io.enocean.0]
                        2022-10-30 10:26:53.582 - error: host.ioBroker-slave0 Caught by controller[9]: 8: 0xe9b92c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [io.enocean.0]
                        2022-10-30 10:26:53.583 - error: host.ioBroker-slave0 Caught by controller[10]: 9: 0xe9c978 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [io.enocean.0]
                        2022-10-30 10:26:53.583 - error: host.ioBroker-slave0 Caught by controller[11]: 10: 0xea005c v8::internal::IncrementalMarkingJob::Task::RunInternal() [io.enocean.0]
                        2022-10-30 10:26:53.584 - error: host.ioBroker-slave0 Caught by controller[12]: 11: 0xd9a550 non-virtual thunk to v8::internal::CancelableTask::Run() [io.enocean.0]
                        2022-10-30 10:26:53.584 - error: host.ioBroker-slave0 Caught by controller[13]: 12: 0xb62eac [io.enocean.0]
                        2022-10-30 10:26:53.585 - error: host.ioBroker-slave0 Caught by controller[14]: 13: 0xb66450 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [io.enocean.0]
                        2022-10-30 10:26:53.586 - error: host.ioBroker-slave0 Caught by controller[15]: 14: 0x14f92d4 [io.enocean.0]
                        2022-10-30 10:26:53.586 - error: host.ioBroker-slave0 Caught by controller[16]: 15: 0x150b338 [io.enocean.0]
                        2022-10-30 10:26:53.587 - error: host.ioBroker-slave0 Caught by controller[17]: 16: 0x14f9d10 uv_run [io.enocean.0]
                        2022-10-30 10:26:53.587 - error: host.ioBroker-slave0 Caught by controller[18]: 17: 0xa4a0ac node::SpinEventLoop(node::Environment*) [io.enocean.0]
                        2022-10-30 10:26:53.588 - error: host.ioBroker-slave0 Caught by controller[19]: 18: 0xb3ab58 node::NodeMainInstance::Run() [io.enocean.0]
                        2022-10-30 10:26:53.588 - error: host.ioBroker-slave0 Caught by controller[20]: 19: 0xac83d0 node::Start(int, char**) [io.enocean.0]
                        2022-10-30 10:26:53.589 - error: host.ioBroker-slave0 Caught by controller[20]: 20: 0x7f9536ee18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
                        2022-10-30 10:26:53.589 - error: host.ioBroker-slave0 Caught by controller[21]: 21: 0xa48724 [io.enocean.0]
                        2022-10-30 10:26:53.590 - warn: host.ioBroker-slave0 instance system.adapter.enocean.0 terminated due to SIGABRT
                        2022-10-30 10:26:53.591 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 terminated with code NaN ()
                        2022-10-30 10:26:53.592 - info: host.ioBroker-slave0 Restart adapter system.adapter.enocean.0 because enabled
                        2022-10-30 10:27:23.719 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 started with pid 173788
                        2022-10-30 10:27:26.326 - debug: enocean.0 (173788) Redis Objects: Use Redis connection: 192.168.115.6:9001
                        2022-10-30 10:27:26.403 - debug: enocean.0 (173788) Objects client ready ... initialize now
                        2022-10-30 10:27:26.412 - debug: enocean.0 (173788) Objects create System PubSub Client
                        2022-10-30 10:27:26.414 - debug: enocean.0 (173788) Objects create User PubSub Client
                        2022-10-30 10:27:26.493 - debug: enocean.0 (173788) Objects client initialize lua scripts
                        2022-10-30 10:27:26.521 - debug: enocean.0 (173788) Objects connected to redis: 192.168.115.6:9001
                        2022-10-30 10:27:26.582 - debug: enocean.0 (173788) Redis States: Use Redis connection: 192.168.115.6:9000
                        2022-10-30 10:27:26.662 - debug: enocean.0 (173788) States create System PubSub Client
                        2022-10-30 10:27:26.666 - debug: enocean.0 (173788) States create User PubSub Client
                        2022-10-30 10:27:26.753 - debug: enocean.0 (173788) States connected to redis: 192.168.115.6:9000
                        2022-10-30 10:27:27.549 - info: enocean.0 (173788) starting. Version 0.8.3 in /opt/iobroker/node_modules/iobroker.enocean, node: v16.18.0, js-controller: 4.0.23
                        2022-10-30 10:27:29.571 - error: enocean.0 (173788) Timeout for response: Get version information
                        2022-10-30 10:27:31.082 - error: enocean.0 (173788) Timeout for response: Get repeater mode and level
                        2022-10-30 10:27:32.584 - error: enocean.0 (173788) Timeout for response: Get frequency
                        2022-10-30 10:27:34.087 - error: enocean.0 (173788) Timeout for response: Get base ID
                        2022-10-30 10:27:35.590 - error: enocean.0 (173788) Timeout for response: Read learnd devices
                        2022-10-30 10:27:35.592 - info: enocean.0 (173788) {"AppVersion":"undefined.undefined.undefined.undefined","ApiVersion":"undefined.undefined.undefined.undefined"}
                        2022-10-30 10:32:23.258 - error: host.ioBroker-slave0 Caught by controller[0]: <--- Last few GCs --->
                        2022-10-30 10:32:23.260 - error: host.ioBroker-slave0 Caught by controller[0]: [173788:0x31445880] 294550 ms: Scavenge 452.1 (463.3) -> 450.6 (463.3) MB, 3.6 / 0.0 ms (average mu = 0.273, current mu = 0.298) task
                        2022-10-30 10:32:23.261 - error: host.ioBroker-slave0 Caught by controller[0]: [173788:0x31445880] 294612 ms: Scavenge 452.2 (463.3) -> 450.6 (463.3) MB, 3.6 / 0.0 ms (average mu = 0.273, current mu = 0.298) task
                        2022-10-30 10:32:23.261 - error: host.ioBroker-slave0 Caught by controller[0]: [173788:0x31445880] 294675 ms: Scavenge 452.2 (463.3) -> 450.8 (463.3) MB, 3.6 / 0.0 ms (average mu = 0.273, current mu = 0.298) task
                        2022-10-30 10:32:23.262 - error: host.ioBroker-slave0 Caught by controller[0]: <--- JS stacktrace --->
                        2022-10-30 10:32:23.262 - error: host.ioBroker-slave0 Caught by controller[0]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
                        2022-10-30 10:32:23.263 - error: host.ioBroker-slave0 Caught by controller[1]: 1: 0xafdf9c node::Abort() [io.enocean.0]
                        2022-10-30 10:32:23.263 - error: host.ioBroker-slave0 Caught by controller[2]: 2: 0xa21604 void node::FPrintF<>(_IO_FILE*, char const*) [io.enocean.0]
                        2022-10-30 10:32:23.264 - error: host.ioBroker-slave0 Caught by controller[3]: 3: 0xcd0368 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [io.enocean.0]
                        2022-10-30 10:32:23.264 - error: host.ioBroker-slave0 Caught by controller[4]: 4: 0xcd0538 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [io.enocean.0]
                        2022-10-30 10:32:23.266 - error: host.ioBroker-slave0 Caught by controller[4]: 5: 0xe8c23c [io.enocean.0]
                        2022-10-30 10:32:23.267 - error: host.ioBroker-slave0 Caught by controller[4]: 6: 0xe8ccc4 [io.enocean.0]
                        2022-10-30 10:32:23.267 - error: host.ioBroker-slave0 Caught by controller[5]: 7: 0xe9b10c [io.enocean.0]
                        2022-10-30 10:32:23.268 - error: host.ioBroker-slave0 Caught by controller[5]: 8: 0xe9b92c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [io.enocean.0]
                        2022-10-30 10:32:23.268 - error: host.ioBroker-slave0 Caught by controller[6]: 9: 0xe9c978 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [io.enocean.0]
                        2022-10-30 10:32:23.269 - error: host.ioBroker-slave0 Caught by controller[7]: 10: 0xea005c v8::internal::IncrementalMarkingJob::Task::RunInternal() [io.enocean.0]
                        2022-10-30 10:32:23.269 - error: host.ioBroker-slave0 Caught by controller[8]: 11: 0xd9a550 non-virtual thunk to v8::internal::CancelableTask::Run() [io.enocean.0]
                        2022-10-30 10:32:23.270 - error: host.ioBroker-slave0 Caught by controller[9]: 12: 0xb62eac [io.enocean.0]
                        2022-10-30 10:32:23.270 - error: host.ioBroker-slave0 Caught by controller[10]: 13: 0xb66450 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [io.enocean.0]
                        2022-10-30 10:32:23.270 - error: host.ioBroker-slave0 Caught by controller[11]: 14: 0x14f92d4 [io.enocean.0]
                        2022-10-30 10:32:23.271 - error: host.ioBroker-slave0 Caught by controller[12]: 15: 0x150b338 [io.enocean.0]
                        2022-10-30 10:32:23.271 - error: host.ioBroker-slave0 Caught by controller[12]: 16: 0x14f9d10 uv_run [io.enocean.0]
                        2022-10-30 10:32:23.272 - error: host.ioBroker-slave0 Caught by controller[13]: 17: 0xa4a0ac node::SpinEventLoop(node::Environment*) [io.enocean.0]
                        2022-10-30 10:32:23.272 - error: host.ioBroker-slave0 Caught by controller[14]: 18: 0xb3ab58 node::NodeMainInstance::Run() [io.enocean.0]
                        2022-10-30 10:32:23.273 - error: host.ioBroker-slave0 Caught by controller[15]: 19: 0xac83d0 node::Start(int, char**) [io.enocean.0]
                        2022-10-30 10:32:23.273 - error: host.ioBroker-slave0 Caught by controller[15]: 20: 0x7f90197e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
                        2022-10-30 10:32:23.274 - error: host.ioBroker-slave0 Caught by controller[16]: 21: 0xa48724 [io.enocean.0]
                        2022-10-30 10:32:23.274 - warn: host.ioBroker-slave0 instance system.adapter.enocean.0 terminated due to SIGABRT
                        2022-10-30 10:32:23.275 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 terminated with code NaN ()
                        2022-10-30 10:32:23.276 - info: host.ioBroker-slave0 Restart adapter system.adapter.enocean.0 because enabled
                        2022-10-30 10:32:53.469 - info: host.ioBroker-slave0 instance system.adapter.enocean.0 started with pid 173961
                        2022-10-30 10:32:56.126 - debug: enocean.0 (173961) Redis Objects: Use Redis connection: 192.168.115.6:9001
                        2022-10-30 10:32:56.201 - debug: enocean.0 (173961) Objects client ready ... initialize now
                        2022-10-30 10:32:56.210 - debug: enocean.0 (173961) Objects create System PubSub Client
                        2022-10-30 10:32:56.213 - debug: enocean.0 (173961) Objects create User PubSub Client
                        2022-10-30 10:32:56.270 - debug: enocean.0 (173961) Objects client initialize lua scripts
                        2022-10-30 10:32:56.309 - debug: enocean.0 (173961) Objects connected to redis: 192.168.115.6:9001
                        2022-10-30 10:32:56.363 - debug: enocean.0 (173961) Redis States: Use Redis connection: 192.168.115.6:9000
                        2022-10-30 10:32:56.442 - debug: enocean.0 (173961) States create System PubSub Client
                        2022-10-30 10:32:56.446 - debug: enocean.0 (173961) States create User PubSub Client
                        2022-10-30 10:32:56.531 - debug: enocean.0 (173961) States connected to redis: 192.168.115.6:9000
                        2022-10-30 10:32:57.364 - info: enocean.0 (173961) starting. Version 0.8.3 in /opt/iobroker/node_modules/iobroker.enocean, node: v16.18.0, js-controller: 4.0.23
                        2022-10-30 10:32:59.388 - error: enocean.0 (173961) Timeout for response: Get version information
                        2022-10-30 10:33:00.891 - error: enocean.0 (173961) Timeout for response: Get repeater mode and level
                        2022-10-30 10:33:02.394 - error: enocean.0 (173961) Timeout for response: Get frequency
                        2022-10-30 10:33:03.897 - error: enocean.0 (173961) Timeout for response: Get base ID
                        2022-10-30 10:33:05.399 - error: enocean.0 (173961) Timeout for response: Read learnd devices
                        2022-10-30 10:33:05.401 - info: enocean.0 (173961) {"AppVersion":"undefined.undefined.undefined.undefined","ApiVersion":"undefined.undefined.undefined.undefined"}
                        
                        Jey Cee 1 Reply Last reply Reply Quote 0
                        • Jey Cee
                          Jey Cee Developer @JuFu last edited by

                          @jufu jetzt zeugt das log exakt was ich erwartet hab. Der Stick wird erkannt.
                          Wie ich schon ziemlich am Anfang gesgat hab Scroll mal in der Auswahl nach unten.

                          J 1 Reply Last reply Reply Quote 0
                          • J
                            JuFu @Jey Cee last edited by

                            @jey-cee Meinst Du die Zeile 21 wo er "/dev/ttyAMA0","/dev/ttyUSB0","/dev/serial/by-id/usb-EnOcean_GmbH_EnOcean_USB_300_DD_FT6XA94C-if00-port0" mitlogged?!
                            Aber danach kommen nur Fehlermeldungen und der Adapter verbindet nicht mit dem Stick, oder interpretiere ich das falsch?

                            Was sollte ich als nächstes probieren um den Adapter mit dem USB-Stick zum laufen zu bringen?

                            Jey Cee 1 Reply Last reply Reply Quote 0
                            • Jey Cee
                              Jey Cee Developer @JuFu last edited by

                              @jufu Der Stick ist in der Auswahl, du siehst ihn nur nicht. Deshalb musst du runter Scrolöen in der Auswahl.

                              J 1 Reply Last reply Reply Quote 0
                              • J
                                JuFu @Jey Cee last edited by

                                @jey-cee Alles grün jetzt!
                                Morgen geht's weiter!
                                Vielen, vielen Dank!

                                W 1 Reply Last reply Reply Quote 0
                                • W
                                  Wahl-HHer @JuFu last edited by

                                  Hallo zusammen,

                                  ich habe auch ein Problem Enocean an meinem PI zum Laufen zu bringen.
                                  Mein aktueller Stand ist Folgender:

                                  Bluetooth und Wifi sind mittels der Einträge

                                  dtoverlay=disable-bt
                                  dtoverlay=disable-wifi
                                  in der config-Datei deaktiviert

                                  Außerdem habe ich den Dienst hciuart deaktiviert.

                                  sudo systemctl disable hciuart

                                  Dann den PI neu gebootet.

                                  Trotzdem läuft die Instanz noch nicht und im Log sind folgende Warnungen enthalten.

                                  bef2adf9-f4a6-45f0-ba55-95599e120e37-grafik.png

                                  Die Einstellungen der Instanz sehen so aus.
                                  e0bafd2a-6567-4322-8eb5-240e590870bb-grafik.png

                                  Die Schnittstelle scheint auch die richtige zu sein.

                                  a79ccc4d-e2c1-42ee-a556-95d32b15df58-grafik.png

                                  Hat jemand Tipps?

                                  J 1 Reply Last reply Reply Quote 0
                                  • J
                                    JuFu @Wahl-HHer last edited by

                                    @wahl-hher ich hatte das Problem das ich in 'Serielle Schnittstelle' nicht nach unten scrollen konnte und somit den Adapter nicht auswählen konnte.
                                    Könnte am Firefox gelegen haben ...

                                    W 1 Reply Last reply Reply Quote 0
                                    • W
                                      Wahl-HHer @JuFu last edited by

                                      Ich konnte scrollen.
                                      Bei mir läufts jetzt auch, aber keine Ahnung was ich jetzt anders gemacht habe. 😄

                                      1 Reply Last reply Reply Quote 0
                                      • B
                                        BausSH @Jey Cee last edited by

                                        @jey-cee Nachdem ich mich einige Zeit mit FHEM für Enocean über Wasser gehalten habe, habe ich es jetzt gewagt und deinen Adapter installiert. Was soll ich sagen? Alle Geräte laufen fehlerfrei. Vielen Dank für die tolle Arbeit.

                                        Eine Kleinigkeit ist mir nur aufgefallen: Ich habe Nodon-Bewegungsmelder. Die Meldung ist verdreht: Bewegung ist false, keine Bewegung ist true. Wie gesagt: nur eine Kleinigkeit. Nichts, was nicht steuerbar wäre.

                                        Und eine Frage habe ich noch: Manchmal bleiben die Nodon-Bewegungsmelder auf Dauerbewegung stehen. Könnte das am Adapter liegen oder ist das ein Fehler der Geräte?

                                        Jey Cee 1 Reply Last reply Reply Quote 0
                                        • Jey Cee
                                          Jey Cee Developer @BausSH last edited by

                                          @baussh danke für die Rückmeldung zum nodon Bewegungsmelder. Das werde ich ändern.

                                          Was deine Frage angeht, wäre meine erste Vermutung das es am Empfang liegt. Wenn der rssi Wert >-80 ist, könnte es sein.
                                          Da ich bisher keine vergleichbaren Meldungen (um welches Gerät es sich handelt ist hier ziemlich egal) bekommen habe, die sich nicht mit Empfangsproblemen erklären liesen, würde ich sagen es ist unwahrscheinlich das es am Adapter liegt.

                                          B 1 Reply Last reply Reply Quote 0
                                          • B
                                            BausSH @Jey Cee last edited by

                                            @jey-cee RSSI-Werte von mehr als 80, oder darunter? Die beiden Bewegungsmelder, die etwas unzuverlässig melden, haben nämlich Werte von 73 und 75. Ich werde trotzdem mal meinen Repeater umstellen. Vielleicht arbeiten die dann besser. Danke auf jeden Fall für die schnelle Antwort.

                                            Jey Cee 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

                                            enocean
                                            25
                                            243
                                            26541
                                            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