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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    Test Adapter EnOcean v0.8.x

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

      @jey-cee sagte in Test Adapter EnOcean v0.8.x:

      @gmon sagte in Test Adapter EnOcean v0.8.x:

      hab ich da irgendwas falsch konfiguriert? Die 04 gibt es gar nicht als Aktor.

      Es scheint so als hat der Aktor die ID 04, sonst würde keine Rückmeldung von dieser ID kommen. Die Lösung ist ganz einfach diese ID zu verwenden.

      Wo ändere ich die dann? Ich muss wohl aus der 03 eine 04 machen, oder?

      5052b007-75bd-4386-aff1-24782ce1b6e5-grafik.png

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

        @gmon du musst das Gerät neu anlegen.

        G 2 Replies Last reply Reply Quote 0
        • G
          Gmon @Jey Cee last edited by

          @jey-cee sagte in Test Adapter EnOcean v0.8.x:

          @gmon du musst das Gerät neu anlegen.

          Ok, danke. Das gilt dann vermutlich fuer die anderen auch.
          Was ist da wann schiefgelaufen?

          Hab da auch noch eine neue Fehlermeldung im Log, aktueller Adapter 0.8.3, kann aber schon frueher drin gewesen sein:
          2022-10-03 08:21:20.480 warn The data length for a 4BS telegram is incorrect. The length is 7

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

            @gmon sagte in Test Adapter EnOcean v0.8.x:

            Was ist da wann schiefgelaufen?

            Das kann ich dir nicht sagen.

            @gmon sagte in Test Adapter EnOcean v0.8.x:

            Hab da auch noch eine neue Fehlermeldung im Log,

            Die Meldung kommt wenn benötigte Datenpunkte nicht gesetzt, also null sind oder falsche Werte beinhalten.

            1 Reply Last reply Reply Quote 0
            • G
              Gmon @Jey Cee last edited by

              @jey-cee sagte in Test Adapter EnOcean v0.8.x:

              @gmon du musst das Gerät neu anlegen.

              Die anderen sind auch alle um eins verschoben. Kann man das nicht irgendwo in den Konfigurationsdateien fixen? Neu anlegen gibt viel Arbeit.

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

                @gmon sagte in Test Adapter EnOcean v0.8.x:

                @jey-cee sagte in Test Adapter EnOcean v0.8.x:

                @gmon du musst das Gerät neu anlegen.

                Die anderen sind auch alle um eins verschoben. Kann man das nicht irgendwo in den Konfigurationsdateien fixen? Neu anlegen gibt viel Arbeit.

                Die Konfiguration ist nicht das Problem, aber du kannst die IDs der Objekte nicht ändern.

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

                  Ich hänge mich auch nochmal ran.
                  War vor kurzem schon mal hier wegen Einbindung von Eltako FSSA-230.

                  Das hat soweit dann geklappt.

                  Leider ist das Anzeige-/Schaltverhalten noch inkonsistent.

                  Kurzer Screencast zeigt das Problem.

                  Dabei habe ich Folgendes gemacht:

                  1. Zuerst mit der Maus manuell den Wert vom State geändert. -> Relais schaltet nicht
                  2. Dann mit dem besagten Zigbee Taster über das Blockly Skript. Wert wird gesetzt, Relais schaltet aber auch nicht.
                  3. Zuletzt am Aktor selbst, mit dort eingebautem Push-Button. Relais schaltet Hörbar, Status wird aber nicht, bzw. unregelmäßig aktualisiert (Datenpunkt "RO")

                  Wenn das Relais zum Beispiel an ist, und ich setzte den State auf OFF/0, dann schaltete es trotzdem nicht aus.

                  Ich versuche es jetzt mal noch näher am EnOcean Stick...

                  https://www.icloud.com/iclouddrive/0eb08pe0oLRoFEjAsHTv0cIPg#Bildschirmaufnahme_2022-10-09_um_09.41

                  P.S.: Log zeigt (zumindest für mich) nichts Auffälliges

                  2022-10-09 08:16:18.485 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC', payload '{\\\"action\\\":\\\"on\\\",\\\"battery\\\":87,\\\"linkquality\\\":40,\\\"update\\\":{\\\"state\\\":\\\"idle\\\"}}'\"}","ack":true,"ts":1665303378480,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303378480}
2022-10-09 08:16:18.486 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC', payload '{\"action\":\"on\",\"battery\":87,\"linkquality\":40,\"update\":{\"state\":\"idle\"}}'"}
2022-10-09 08:16:18.493 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/battery', payload '87'\"}","ack":true,"ts":1665303378487,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303378487}
2022-10-09 08:16:18.493 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/battery', payload '87'"}
2022-10-09 08:16:18.502 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/linkquality', payload '40'\"}","ack":true,"ts":1665303378498,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303378498}
2022-10-09 08:16:18.502 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/linkquality', payload '40'"}
2022-10-09 08:16:18.507 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/update-state', payload 'idle'\"}","ack":true,"ts":1665303378498,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303378498}
2022-10-09 08:16:18.507 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/update-state', payload 'idle'"}
2022-10-09 08:16:18.512 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/action', payload 'on'\"}","ack":true,"ts":1665303378498,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303378498}
2022-10-09 08:16:18.512 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/action', payload 'on'"}
2022-10-09 08:16:22.553 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC', payload '{\\\"action\\\":\\\"off\\\",\\\"battery\\\":87,\\\"linkquality\\\":21,\\\"update\\\":{\\\"state\\\":\\\"idle\\\"}}'\"}","ack":true,"ts":1665303382542,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303382542}
2022-10-09 08:16:22.553 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC', payload '{\"action\":\"off\",\"battery\":87,\"linkquality\":21,\"update\":{\"state\":\"idle\"}}'"}
2022-10-09 08:16:22.571 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/battery', payload '87'\"}","ack":true,"ts":1665303382564,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303382564}
2022-10-09 08:16:22.571 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/battery', payload '87'"}
2022-10-09 08:16:22.580 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/linkquality', payload '21'\"}","ack":true,"ts":1665303382572,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303382572}
2022-10-09 08:16:22.581 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/linkquality', payload '21'"}
2022-10-09 08:16:22.597 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/update-state', payload 'idle'\"}","ack":true,"ts":1665303382572,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303382572}
2022-10-09 08:16:22.597 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/update-state', payload 'idle'"}
2022-10-09 08:16:22.622 - silly: enocean.0 (117731) States system redis pmessage *.logging/mqtt.0.zigbee2mqtt.bridge.logging:{"val":"{\"level\":\"info\",\"message\":\"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/action', payload 'off'\"}","ack":true,"ts":1665303382615,"q":0,"from":"system.adapter.mqtt.0","user":"system.user.admin","lc":1665303382615}
2022-10-09 08:16:22.622 - silly: enocean.0 (117731) mqtt.0.zigbee2mqtt.bridge: logging {"level":"info","message":"MQTT publish: topic 'zigbee2mqtt/Button Nisi PC/action', payload 'off'"}
2022-10-09 08:16:22.632 - silly: enocean.0 (117731) States user redis pmessage enocean.0.*.CMD/enocean.0.ff8b2b80.CMD:{"val":0,"ack":false,"ts":1665303382623,"q":0,"c":"script.js.Denise_PC","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1665303382623}
2022-10-09 08:16:22.632 - debug: enocean.0 (117731) state ff8b2b80.CMD changed: 0 (ack = false) state: {"val":0,"ack":false,"ts":1665303382623,"q":0,"c":"script.js.Denise_PC","from":"system.adapter.javascript.0","user":"system.user.admin","lc":1665303382623}
2022-10-09 08:16:22.640 - debug: enocean.0 (117731) Sent data: 55000707017af650ff992c923000ff8b2b80ff005e
2022-10-09 08:16:22.644 - silly: enocean.0 (117731) States user redis pmessage enocean.0.*.CMD/enocean.0.ff8b2b80.CMD:{"val":0,"ack":true,"ts":1665303382642,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303382623}
2022-10-09 08:16:22.665 - info: enocean.0 (117731) 55000100026500
2022-10-09 08:16:22.665 - debug: enocean.0 (117731) 55000100026500
2022-10-09 08:16:22.665 - debug: enocean.0 (117731) Packet type 2 received: {"code":"OK"}
2022-10-09 08:16:26.040 - info: enocean.0 (117731) 55000a0701eba5141b0f28058697b00001ffffffff4f00
2022-10-09 08:16:26.041 - debug: enocean.0 (117731) 55000a0701eba5141b0f28058697b00001ffffffff4f00
2022-10-09 08:16:26.043 - debug: enocean.0 (117731) Message for ID 058697b0 has been received. It was repeated 0 times.
2022-10-09 08:16:26.050 - silly: enocean.0 (117731) States user redis pmessage enocean.0.gateway.*/enocean.0.gateway.lastID:{"val":"058697b0","ack":true,"ts":1665303386046,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303255482}
2022-10-09 08:16:26.248 - info: enocean.0 (117731) 55000a0701eba58777870f040198a73001ffffffff5c00
2022-10-09 08:16:26.248 - debug: enocean.0 (117731) 55000a0701eba58777870f040198a73001ffffffff5c00
2022-10-09 08:16:26.251 - debug: enocean.0 (117731) Message for ID 040198a7 has been received. It was repeated 0 times.
2022-10-09 08:16:26.254 - silly: enocean.0 (117731) States user redis pmessage enocean.0.gateway.*/enocean.0.gateway.lastID:{"val":"040198a7","ack":true,"ts":1665303386253,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303386253}
2022-10-09 08:16:28.279 - info: enocean.0 (117731) 55000707017af670ff8b2b803001ffffffff5c00
2022-10-09 08:16:28.279 - debug: enocean.0 (117731) 55000707017af670ff8b2b803001ffffffff5c00
2022-10-09 08:16:28.281 - debug: enocean.0 (117731) Message for ID ff8b2b80 has been received. It was repeated 0 times.
2022-10-09 08:16:28.285 - silly: enocean.0 (117731) States user redis pmessage enocean.0.gateway.*/enocean.0.gateway.lastID:{"val":"ff8b2b80","ack":true,"ts":1665303388284,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303388284}
2022-10-09 08:16:41.860 - info: enocean.0 (117731) 55000707017af650ff8b2b803001ffffffff5b00
2022-10-09 08:16:41.860 - debug: enocean.0 (117731) 55000707017af650ff8b2b803001ffffffff5b00
2022-10-09 08:16:41.862 - debug: enocean.0 (117731) Message for ID ff8b2b80 has been received. It was repeated 0 times.
2022-10-09 08:16:41.866 - silly: enocean.0 (117731) States user redis pmessage enocean.0.gateway.*/enocean.0.gateway.lastID:{"val":"ff8b2b80","ack":true,"ts":1665303401865,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303388284}
2022-10-09 08:16:54.480 - silly: enocean.0 (117731) States user redis pmessage enocean.0.*.CMD/enocean.0.ff8b2b80.CMD:{"val":1,"ack":false,"ts":1665303414479,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1665303414479}
2022-10-09 08:16:54.481 - debug: enocean.0 (117731) state ff8b2b80.CMD changed: 1 (ack = false) state: {"val":1,"ack":false,"ts":1665303414479,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1665303414479}
2022-10-09 08:16:54.485 - silly: enocean.0 (117731) States user redis pmessage enocean.0.*.CMD/enocean.0.ff8b2b80.CMD:{"val":1,"ack":true,"ts":1665303414484,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303414479}
2022-10-09 08:16:54.504 - debug: enocean.0 (117731) Sent data: 55000707017af670ff992c923000ff8b2b80ff00a0
2022-10-09 08:16:54.513 - info: enocean.0 (117731) 55000100026500
2022-10-09 08:16:54.513 - debug: enocean.0 (117731) 55000100026500
2022-10-09 08:16:54.514 - debug: enocean.0 (117731) Packet type 2 received: {"code":"OK"}
2022-10-09 08:16:54.753 - info: enocean.0 (117731) 55000707017af670ff8b2b803001ffffffff5f00
2022-10-09 08:16:54.753 - debug: enocean.0 (117731) 55000707017af670ff8b2b803001ffffffff5f00
2022-10-09 08:16:54.755 - debug: enocean.0 (117731) Message for ID ff8b2b80 has been received. It was repeated 0 times.
2022-10-09 08:16:54.759 - silly: enocean.0 (117731) States user redis pmessage enocean.0.gateway.*/enocean.0.gateway.lastID:{"val":"ff8b2b80","ack":true,"ts":1665303414757,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303388284}
2022-10-09 08:16:59.774 - silly: enocean.0 (117731) States user redis pmessage enocean.0.*.CMD/enocean.0.ff8b2b80.CMD:{"val":0,"ack":false,"ts":1665303419773,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1665303419773}
2022-10-09 08:16:59.775 - debug: enocean.0 (117731) state ff8b2b80.CMD changed: 0 (ack = false) state: {"val":0,"ack":false,"ts":1665303419773,"q":0,"from":"system.adapter.admin.0","user":"system.user.admin","lc":1665303419773}
2022-10-09 08:16:59.779 - silly: enocean.0 (117731) States user redis pmessage enocean.0.*.CMD/enocean.0.ff8b2b80.CMD:{"val":0,"ack":true,"ts":1665303419778,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303419773}
2022-10-09 08:16:59.825 - debug: enocean.0 (117731) Sent data: 55000707017af650ff992c923000ff8b2b80ff005e
2022-10-09 08:16:59.840 - info: enocean.0 (117731) 55000100026500
2022-10-09 08:16:59.841 - debug: enocean.0 (117731) 55000100026500
2022-10-09 08:16:59.841 - debug: enocean.0 (117731) Packet type 2 received: {"code":"OK"}
2022-10-09 08:17:21.804 - info: enocean.0 (117731) 55000a0701eba5141e1128058697b00001ffffffff4f00
2022-10-09 08:17:21.804 - debug: enocean.0 (117731) 55000a0701eba5141e1128058697b00001ffffffff4f00
2022-10-09 08:17:21.806 - debug: enocean.0 (117731) Message for ID 058697b0 has been received. It was repeated 0 times.
2022-10-09 08:17:21.809 - silly: enocean.0 (117731) States user redis pmessage enocean.0.gateway.*/enocean.0.gateway.lastID:{"val":"058697b0","ack":true,"ts":1665303441808,"q":0,"from":"system.adapter.enocean.0","user":"system.user.admin","lc":1665303441808}
                  1 Reply Last reply Reply Quote 0
                  • michif100
                    michif100 last edited by

                    OK, Kommando zurück, ich lösche das hier nicht, vielleicht nützt es mal noch jemandem, aber es muss wohl die Empfangsstärke gewesen sein!

                    Bei -92 dB war es sehr unzuverlässig, jetzt näher an der Zentrale mit -75 dB geht es zuverlässig!

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

                      @michif100 im idealfall liegt der rssi Wert immer unter -70dB. Darüber kann es je nach Gerät schon nicht mehr Funktionieren mit dem Steuern.

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

                        @jey-cee Hallo, ich wollte ebenfalls versuchen meine EnOcean Geräte über einen USB300 und dem EnOcean Adapter v0.8.3 in den ioButler einzubinden.
                        setting.JPG
                        Bekomme aber als port nur /dev/ttyAMA0 angeboten.
                        Der USB300 steckt in einem Raspi der als Slave im ioBroker-Netz hängt.

                        Was mach ich falsch?
                        Juergen

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

                          @jufu

                          Gemeinhin nimmt man den Link aus

                          ls -lA /dev/serial/by-id

                          und trägt den da ein.

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

                            @jufu hast du den Adapter auch sicher auf dem Slave installiert?
                            Wird der Stick überhaupt am Raspi erkannt?
                            Wenn Ja, mach das Auswahlfeld auf und scroll mal.

                            @thomas-braun sagte in Test Adapter EnOcean v0.8.x:

                            @jufu

                            Gemeinhin nimmt man den Link aus

                            ls -lA /dev/serial/by-id

                            und trägt den da ein.

                            Erkennt der Adapter selbstständig und das ist ein reines Auswahfeld.

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

                              @jey-cee ja, Adapter ist auf dem Slave installiert und den USB300 finde ich auch per ls -lA … auf dem Raspberry.
                              Im Auswahlfeld wird mir aber nur /dev/ttyAMA0 angeboten.
                              Auf dem Raspberry läuft nur zusätzlich der Rasp-Adapter für Zugriff auf die GPIO und das funktioniert auch.

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

                                @jufu dann stell bitte mal das Loglevel für die Instanz auf debug und poste das Log.

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

                                  @jey-cee hier das log auf dem ioBroker
                                  debug.JPG

                                  und hier auf dem Raspberry:pi.JPG
                                  (Bin noch zu sehr Anfänger um das zu interpretieren).
                                  Aber schon mal herzlichen Dank für die Unterstützung.

                                  J Thomas Braun 2 Replies Last reply Reply Quote 0
                                  • J
                                    JuFu @JuFu last edited by

                                    @jufu jetzt kam noch mehr ...debug1.JPG

                                    Jey Cee 1 Reply Last reply Reply Quote 0
                                    • Thomas Braun
                                      Thomas Braun Most Active @JuFu last edited by Thomas Braun

                                      @jufu

                                      Der Stick lebt aber nicht unter /dev/ttyAMA0 sondern unter /dev/ttyUSB0
                                      Da stimmt dann offenbar die Erkennung nicht, wenn man das nicht manuell überschreiben kann.

                                      Und bitte keine Screenshots von Text. Kann man nicht kopieren und die Suchfunktion findet das auch nicht wieder.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            754
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

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