Skip to content

Error/Bug

6.6k Topics 74.8k Posts

Hier könnt ihr Fehler von ioBroker melden

NEWS

  • Nach Update auf Zigbee 3.5.5 läuft die Jalousie falsch herum

    Unsolved
    33
    0 Votes
    33 Posts
    415 Views
    poppeleP
    Jetzt nochmals 2 Zyklen ich hoffe dies ist jetzt komplett Messages from 08:34:41 for device 0xa4c13818f1b0022a O01: User state change of state zigbee.0.a4c13818f1b0022a.position with value 56 (ack: false) from system.adapter.web.0 O02: Change state 'position' at device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' type 'SC500ZB-v4' O03: Publishing to 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' of model SC500ZB-v4 with position Os4.0: Setting' converter to converter with key(s)'["position","tilt"]} O04: convert position with value 56 and options {} for device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' without Endpoint O05: Attempt 1 at converting data for position with preparedValue 56, meta.state {}, meta.message {"position":56} SUCCESS: convert result {"state":{"position":56}} for device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' Messages from 08:34:41 for device 0xa4c13818f1b0022a I01: Zigbee Event of Type attributeReport from device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":56,"tuyaMovingState":0},"linkquality":91,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,33,10,8,0,32,56,0,240,48,0]},"zclTransactionSequenceNumber":33,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1} I03: message received '{"available":true}' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' type 'SC500ZB-v4' I04: value generated 'true' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Available' I04-1: value generated '91' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Link quality' I02: 3 converters available for 'SC500ZB-v4' 'SC500ZB-v4-Büro (a4c13818f1b0022a)' with cluster 'closuresWindowCovering' and type 'attributeReport' I02.1a: converter 1 : Cluster closuresWindowCovering I02.0b: data: {"currentPositionLiftPercentage":56,"tuyaMovingState":0} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"position":44,"state":"OPEN"} I02.2a: converter 2 : Cluster closuresWindowCovering I02.1b: data: {"currentPositionLiftPercentage":56,"tuyaMovingState":0} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"moving":"UP"} I02.3a: converter 3 : Cluster closuresWindowCovering I02.2b: data: {"currentPositionLiftPercentage":56,"tuyaMovingState":0} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:undefined I02.3d: candidates: [{"position":44,"state":"OPEN"},{"moving":"UP"},{}] => payload {"position":44,"state":"OPEN","moving":"UP"} => processed payload : {"position":44,"state":"OPEN","moving":"UP"} I03-1: message received '{"position":44,"state":"OPEN","moving":"UP"}' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' type 'SC500ZB-v4' I04-2: value generated 'OPEN' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'state' I04-3: value generated '44' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Position of this cover' I04-4: value generated 'UP' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'moving' Messages from 08:34:47 for device 0xa4c13818f1b0022a I01: Zigbee Event of Type attributeReport from device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":56,"tuyaMovingState":1},"linkquality":94,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,34,10,8,0,32,56,0,240,48,1]},"zclTransactionSequenceNumber":34,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1} I04: value generated '94' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Link quality' I02: 3 converters available for 'SC500ZB-v4' 'SC500ZB-v4-Büro (a4c13818f1b0022a)' with cluster 'closuresWindowCovering' and type 'attributeReport' I02.1a: converter 1 : Cluster closuresWindowCovering I02.0b: data: {"currentPositionLiftPercentage":56,"tuyaMovingState":1} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"position":44,"state":"OPEN"} I02.2a: converter 2 : Cluster closuresWindowCovering I02.1b: data: {"currentPositionLiftPercentage":56,"tuyaMovingState":1} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"moving":"STOP"} I02.3a: converter 3 : Cluster closuresWindowCovering I02.2b: data: {"currentPositionLiftPercentage":56,"tuyaMovingState":1} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:undefined I02.3d: candidates: [{"position":44,"state":"OPEN"},{"moving":"STOP"},{}] => payload {"position":44,"state":"OPEN","moving":"STOP"} => processed payload : {"position":44,"state":"OPEN","moving":"STOP"} I03: message received '{"position":44,"state":"OPEN","moving":"STOP"}' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' type 'SC500ZB-v4' I04-1: value generated 'OPEN' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'state' I04-2: value generated '44' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Position of this cover' I04-3: value generated 'STOP' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'moving' Messages from 08:37:22 for device 0xa4c13818f1b0022a O01: User state change of state zigbee.0.a4c13818f1b0022a.position with value 46 (ack: false) from system.adapter.web.0 O02: Change state 'position' at device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' type 'SC500ZB-v4' O03: Publishing to 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' of model SC500ZB-v4 with position Os4.0: Setting' converter to converter with key(s)'["position","tilt"]} O04: convert position with value 46 and options {} for device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' without Endpoint O05: Attempt 1 at converting data for position with preparedValue 46, meta.state {}, meta.message {"position":46} SUCCESS: convert result {"state":{"position":46}} for device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)' Messages from 08:37:23 for device 0xa4c13818f1b0022a I01: Zigbee Event of Type attributeReport from device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":46,"tuyaMovingState":2},"linkquality":98,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,35,10,8,0,32,46,0,240,48,2]},"zclTransactionSequenceNumber":35,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1} I03: message received '{"available":true}' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' type 'SC500ZB-v4' I04: value generated 'true' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Available' I04-1: value generated '98' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Link quality' I02: 3 converters available for 'SC500ZB-v4' 'SC500ZB-v4-Büro (a4c13818f1b0022a)' with cluster 'closuresWindowCovering' and type 'attributeReport' I02.1a: converter 1 : Cluster closuresWindowCovering I02.0b: data: {"currentPositionLiftPercentage":46,"tuyaMovingState":2} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"position":54,"state":"OPEN"} I02.2a: converter 2 : Cluster closuresWindowCovering I02.1b: data: {"currentPositionLiftPercentage":46,"tuyaMovingState":2} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"moving":"DOWN"} I02.3a: converter 3 : Cluster closuresWindowCovering I02.2b: data: {"currentPositionLiftPercentage":46,"tuyaMovingState":2} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:undefined I02.3d: candidates: [{"position":54,"state":"OPEN"},{"moving":"DOWN"},{}] => payload {"position":54,"state":"OPEN","moving":"DOWN"} => processed payload : {"position":54,"state":"OPEN","moving":"DOWN"} I03-1: message received '{"position":54,"state":"OPEN","moving":"DOWN"}' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' type 'SC500ZB-v4' I04-2: value generated 'OPEN' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'state' I04-3: value generated '54' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Position of this cover' I04-4: value generated 'DOWN' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'moving' Messages from 08:37:25 for device 0xa4c13818f1b0022a I01: Zigbee Event of Type attributeReport from device 'SC500ZB-v4-Büro (0xa4c13818f1b0022a)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":46,"tuyaMovingState":1},"linkquality":91,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,36,10,8,0,32,46,0,240,48,1]},"zclTransactionSequenceNumber":36,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1} I04: value generated '91' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Link quality' I02: 3 converters available for 'SC500ZB-v4' 'SC500ZB-v4-Büro (a4c13818f1b0022a)' with cluster 'closuresWindowCovering' and type 'attributeReport' I02.1a: converter 1 : Cluster closuresWindowCovering I02.0b: data: {"currentPositionLiftPercentage":46,"tuyaMovingState":1} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"position":54,"state":"OPEN"} I02.2a: converter 2 : Cluster closuresWindowCovering I02.1b: data: {"currentPositionLiftPercentage":46,"tuyaMovingState":1} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:{"moving":"STOP"} I02.3a: converter 3 : Cluster closuresWindowCovering I02.2b: data: {"currentPositionLiftPercentage":46,"tuyaMovingState":1} options: {"invert_cover":"true","cover_position_tilt_disable_report":"false","resend_states":""} meta:{"deviceIEEE":"0xa4c13818f1b0022a","logger":"StatesController","state":{"state":""}} result:undefined I02.3d: candidates: [{"position":54,"state":"OPEN"},{"moving":"STOP"},{}] => payload {"position":54,"state":"OPEN","moving":"STOP"} => processed payload : {"position":54,"state":"OPEN","moving":"STOP"} I03: message received '{"position":54,"state":"OPEN","moving":"STOP"}' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' type 'SC500ZB-v4' I04-1: value generated 'OPEN' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'state' I04-2: value generated '54' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'Position of this cover' I04-3: value generated 'STOP' from device 'SC500ZB-v4-Büro (a4c13818f1b0022a)' for 'moving'
  • [gelöst] Error 25 bei Node-Red 7.0.2 Update

    Unsolved gelöst
    3
    0 Votes
    3 Posts
    47 Views
    NegaleinN
    jetzt hat es geklappt. Dürfte einen Schluckauf gehabt haben. ;)
  • [Gelöst] IOB Restart alle 60 Min.

    Solved
    26
    0 Votes
    26 Posts
    445 Views
    ESP8266E
    Man muss mich nicht nach Tagen dran erinnern. Schau dir doch selber die Überschrift an.
  • [Maxcul Adapter] Einfach mal Danke sagen !

    Unsolved
    1
    0 Votes
    1 Posts
    70 Views
    No one has replied
  • ioBroker ohne Zugriff auf Weboberflächen Admin & Visu

    Unsolved
    64
    0 Votes
    64 Posts
    8k Views
    D
    Hallo Zusammen, Hier noch einmal ein riesen Dank bei allen Helfern!!! Mein System läuft bis jetzt soweit immer noch Stabil durch. Ich muss jetzt nur mal nachschauen was den Speicher angeblich volllaufen lassen hat. ich habe für Diagramme E-Charts angelegt welche über History Datnbankeinträge macht für die Langzeitaufzeichnung. Jetzt speichert der aber nur 1 Woche und es ist auch nicht viel was aufgezeichnet wird. Ca . 15 Datenpunkte. Hat da evtl wer eine Vermutung?
  • iobroker kann Datenbank nicht erreichen nach Komplettabsturz

    Unsolved
    26
    0 Votes
    26 Posts
    419 Views
    Thomas BraunT
    @Schasa Bitte vollständig. Ohne Änderungen von dir.
  • Update Script auf 10.0.0

    Unsolved
    3
    0 Votes
    3 Posts
    141 Views
    V
    Danke. Funktioniert doch. Ich habe Script Adapter neu installiert. Debug ausgeschaltet.
  • Geräte-Tab lädt nicht

    Unsolved
    12
    1
    0 Votes
    12 Posts
    203 Views
    E
    @Thomas-Braun sagte: @e:)azor86 devices latest: 3.0.2 for 31 days stable: 1.2.14 for 5 months sorry bin jetzt erst dazu gekommen und hab die Beta installiert, der Rest ist noch auf älterem Stand und es hat funktioniert . dann werde ich mich jetzt mal um die nächsten Themen kümmern :) danke :)
  • Adapter: contact -> Fehler im log

    Unsolved contact google
    8
    0 Votes
    8 Posts
    2k Views
    bahnuhrB
    @alle habs hinbekommen mit dem oauth mit hilfe von chatgpt. Danke für die Infos hier.
  • Modbus Adapter Client in error state

    Unsolved
    2
    6
    0 Votes
    2 Posts
    97 Views
    ubeckerU
    diesen Fehler habe ich schon seit langem. Ist auch schon oft so beschrieben worden. Wenn der Fehler auf meinen Systemen (3 Systeme mit Modbus) auftritt Starte ich den Modbusadapter per script neu. Dann sind ca. 14 Tage Ruhe. Wenn ich den Adapter nicht neu starte kommt der Fehler immer häufiger bis täglich. Ich hoffe mit jeder neuen Version das der Fehler beseitigt ist.
  • ESP Home Fehlermeldung

    Solved
    86
    1
    0 Votes
    86 Posts
    4k Views
    A
    @simonf04 Ja, es funktioniert einwandfrei und ich habe gerade einen zusätzlichen ESP32-Cam-S direkt mit eine separatem USBtoRS232 geflasht und das läuft einwanfrei. Nochmals ganz herzlichen Dank für die Arbeit und den Support. Gruss Andi
  • web Adapter: warn im log

    Unsolved error log
    3
    0 Votes
    3 Posts
    1k Views
    bahnuhrB
    Hallo, hat jemand mal ne Info für mich. Bekomme weiterhin (heute vermehrt) o.g. Meldungen als warn im log.
  • Alarm Adapter Fehler Reiter Anwesenheit

    Unsolved
    3
    1
    0 Votes
    3 Posts
    844 Views
    F
    habe ich schon gemacht, war nur neugierig ob das nur bei mir so ist :)
  • Zigbee Adapter mit LAN Dongle kein automatisches verbinden

    Unsolved
    27
    0 Votes
    27 Posts
    9k Views
    B
    Kurze Info: Verbindung läuft nun seit 9 Tagen absolut fehlerfrei :) habe zusätzlich auf die neueste ZigBee Firmware von meinem SLZB-06 upgedatet. Entwickler-Firmware Revision: 20260311 Release notes Zigbee Coordinator Firmware - CC26xx Series - Build 20260311 (same as 20260310 with 115200 baudrate) (Beta) Build Date: 11 Mar 2026 SDK: 8.32.00.07 (released 22 Dec 2025) Adapter Type: zstack Baudrate: 115200 [image: 1783696693220-screenshot-2026-07-10-171344-resized.png]
  • TADO Adapter Axios Error getState

    Unsolved
    1
    0 Votes
    1 Posts
    373 Views
    No one has replied
  • [gelöst] Schwierigkeiten mit alexa-Adapter

    Unsolved
    212
    1 Votes
    212 Posts
    32k Views
    da_WoodyD
    hi! gerate war testtime. updates für proxmox eingetrudelt. nach dem roboot des servers war der alexa adapter blitzschnell wieder grün! thnx für den fix!
  • gesperrter Datenpunkt bei adapter daikin-cloud

    Unsolved
    12
    0 Votes
    12 Posts
    4k Views
    maximal1981M
    es war sogar daikin-cloud.0.useSlowPolling dauerhaft aktiv entspricht 48 Abfragen/Tag und darüber werden nur 2 Räume von 5 gesteuert. und die blauen Balken zeigen die true Werte für die 2 Anlagen. [image: 1783367874226-screenshot-2026-07-06-215019.png] [image: 1783367879517-screenshot-2026-07-06-215517.png] Der 2.te Raum sieht gleich aus: [image: 1783368347600-screenshot-2026-07-06-220243.png] [image: 1783368358906-screenshot-2026-07-06-220322.png] [image: 1783368364390-screenshot-2026-07-06-220413.png] [image: 1783368369444-screenshot-2026-07-06-220434.png] EDIT: das mit dem pooling interval wurde erst jetzt eingebaut LOL: Guestezimmer - denglisch EDIT2: F.ck, schickt der A.... (nicht böse gemeint - der Adapter ist trotzdem toll/top) die Ist-Temp vermutlich auch immer raus?
  • BackitUp killt system (im Docker)

    Unsolved
    1
    0 Votes
    1 Posts
    607 Views
    No one has replied
  • [gelöst]Sprinklecontrol Feuchtigkeit aktualisiert nicht

    Unsolved
    2
    0 Votes
    2 Posts
    1k Views
    F
    Hat sich erledigt war ein Bug und wurde behoben
  • JS Adapter leer nach aktiveren der Spieglung

    Unsolved
    4
    2
    0 Votes
    4 Posts
    2k Views
    BananaJoeB
    Ok, das Issue hast du aufgemacht weil er nicht warnt wenn man den falschen Pfad nimmt (weil man die Anleitung ignoriert). Das heißt, das Problem besteht nicht wenn du dich an die Anleitung hältst? Ok, hab das ganze Issue gelesen

396

Online

33.0k

Users

83.6k

Topics

1.3m

Posts