Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Adapter Hyundai (Bluelink) oder KIA (UVO)

    NEWS

    • [erledigt] 15. 05. Wartungsarbeiten am ioBroker Forum

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Adapter Hyundai (Bluelink) oder KIA (UVO)

    This topic has been deleted. Only users with topic management privileges can see it.
    • MaBu59
      MaBu59 @arteck last edited by

      @arteck
      Ich glaube, ich habe dir zu viele Zeilen gesendet. War mein erster Versuch. Sorry!!

      arteck 1 Reply Last reply Reply Quote 0
      • arteck
        arteck Developer Most Active @MaBu59 last edited by

        @mabu59 der knallt bei

        reserveChargeInfo2

        was immer da auch drin steht .. ich brauch die Login Daten..sonst wird das nix

        M 1 Reply Last reply Reply Quote 0
        • M
          marchusar @arteck last edited by marchusar

          @arteck
          Sorry, war nicht am PC - hier jetzt die Log:

          2025-05-04 15:53:55.158 - info: host.raspberrypi4 instance system.adapter.bluelink.0 in version "3.1.2" (non-npm: Newan/ioBroker.bluelink#parsecheck) started with pid 23102
          2025-05-04 15:53:59.236 - info: bluelink.0 (23102) starting. Version 3.1.2 (non-npm: Newan/ioBroker.bluelink#parsecheck) in /opt/iobroker/node_modules/iobroker.bluelink, node: v20.19.1, js-controller: 7.0.6
          2025-05-04 15:53:59.266 - info: bluelink.0 (23102) Login to api
          2025-05-04 15:54:01.542 - info: bluelink.0 (23102) 1 Vehicles found
          2025-05-04 15:54:01.674 - info: bluelink.0 (23102) Read new update for KNAC381xxx from the server
          2025-05-04 15:54:01.984 - error: bluelink.0 (23102) PARSECHECK [object Object] coord [object Object]
          2025-05-04 15:54:02.008 - error: bluelink.0 (23102) PARSECHECK [object Object] speed [object Object]
          2025-05-04 15:54:02.021 - error: bluelink.0 (23102) PARSECHECK [object Object] accuracy [object Object]
          2025-05-04 15:54:02.027 - error: bluelink.0 (23102) PARSECHECK [object Object] vehicleLocation [object Object]
          2025-05-04 15:54:02.111 - error: bluelink.0 (23102) PARSECHECK [object Object] doorOpen [object Object]
          2025-05-04 15:54:02.134 - error: bluelink.0 (23102) PARSECHECK [object Object] airTemp [object Object]
          2025-05-04 15:54:02.220 - error: bluelink.0 (23102) PARSECHECK [object Object] etc1 [object Object]
          2025-05-04 15:54:02.232 - error: bluelink.0 (23102) PARSECHECK [object Object] etc2 [object Object]
          2025-05-04 15:54:02.285 - error: bluelink.0 (23102) PARSECHECK [object Object] etc3 [object Object]
          2025-05-04 15:54:02.298 - error: bluelink.0 (23102) PARSECHECK [object Object] atc [object Object]
          2025-05-04 15:54:02.299 - error: bluelink.0 (23102) PARSECHECK [object Object] remainTime2 [object Object]
          2025-05-04 15:54:02.318 - error: bluelink.0 (23102) PARSECHECK [object Object] evModeRange [object Object]
          2025-05-04 15:54:02.375 - error: bluelink.0 (23102) PARSECHECK [object Object] totalAvailableRange [object Object]
          2025-05-04 15:54:02.376 - error: bluelink.0 (23102) PARSECHECK [object Object] rangeByFuel [object Object]
          2025-05-04 15:54:02.407 - error: bluelink.0 (23102) PARSECHECK [object Object] time [object Object]
          2025-05-04 15:54:02.408 - error: bluelink.0 (23102) PARSECHECK [object Object] reservInfo [object Object]
          2025-05-04 15:54:02.478 - error: bluelink.0 (23102) PARSECHECK [object Object] airTemp [object Object]
          2025-05-04 15:54:02.490 - error: bluelink.0 (23102) PARSECHECK [object Object] reservFatcSet [object Object]
          2025-05-04 15:54:02.491 - error: bluelink.0 (23102) PARSECHECK [object Object] reservChargeInfoDetail [object Object]
          2025-05-04 15:54:02.492 - error: bluelink.0 (23102) PARSECHECK [object Object] reservChargeInfo [object Object]
          2025-05-04 15:54:02.517 - error: bluelink.0 (23102) PARSECHECK [object Object] starttime [object Object]
          2025-05-04 15:54:02.575 - error: bluelink.0 (23102) PARSECHECK [object Object] endtime [object Object]
          2025-05-04 15:54:02.576 - error: bluelink.0 (23102) PARSECHECK [object Object] offPeakPowerTime1 [object Object]
          2025-05-04 15:54:02.585 - error: bluelink.0 (23102) PARSECHECK [object Object] offpeakPowerInfo [object Object]
          2025-05-04 15:54:02.655 - error: bluelink.0 (23102) PARSECHECK [object Object] time [object Object]
          2025-05-04 15:54:02.656 - error: bluelink.0 (23102) PARSECHECK [object Object] reservInfo [object Object]
          2025-05-04 15:54:02.727 - error: bluelink.0 (23102) PARSECHECK [object Object] airTemp [object Object]
          2025-05-04 15:54:02.737 - error: bluelink.0 (23102) PARSECHECK [object Object] reservFatcSet [object Object]
          2025-05-04 15:54:02.738 - error: bluelink.0 (23102) PARSECHECK [object Object] reservChargeInfoDetail [object Object]
          2025-05-04 15:54:02.739 - error: bluelink.0 (23102) PARSECHECK [object Object] reserveChargeInfo2 [object Object]
          2025-05-04 15:54:02.806 - error: bluelink.0 (23102) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-04 15:54:02.807 - error: bluelink.0 (23102) unhandled promise rejection: The state contains the forbidden properties day, time!
          2025-05-04 15:54:02.810 - error: bluelink.0 (23102) Error: The state contains the forbidden properties day, time!
          at Validator.validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:299:13)
          at Bluelink._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4984:21)
          at Bluelink.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4962:17)
          at Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:140:34)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Bluelink.readStatusVin (/opt/iobroker/node_modules/iobroker.bluelink/main.js:391:17)
          at async Bluelink.readStatus (/opt/iobroker/node_modules/iobroker.bluelink/main.js:355:13)
          2025-05-04 15:54:02.810 - error: bluelink.0 (23102) The state contains the forbidden properties day, time!
          2025-05-04 15:54:02.821 - info: bluelink.0 (23102) Adapter bluelink cleaned up everything...
          2025-05-04 15:54:02.824 - info: bluelink.0 (23102) terminating
          2025-05-04 15:54:02.825 - warn: bluelink.0 (23102) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-05-04 15:54:02.830 - error: bluelink.0 (23102) PARSECHECK [object Object] ect [object Object]
          2025-05-04 15:54:02.831 - error: bluelink.0 (23102) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-04 15:54:02.832 - error: bluelink.0 (23102) unhandled promise rejection: The state contains the forbidden properties day, time!
          2025-05-04 15:54:02.833 - error: bluelink.0 (23102) Error: The state contains the forbidden properties day, time!
          at Validator.validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:299:13)
          at Bluelink._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4984:21)
          at Bluelink.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4962:17)
          at Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:140:34)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Bluelink.readStatusVin (/opt/iobroker/node_modules/iobroker.bluelink/main.js:391:17)
          at async Bluelink.readStatus (/opt/iobroker/node_modules/iobroker.bluelink/main.js:355:13)
          2025-05-04 15:54:02.834 - error: bluelink.0 (23102) The state contains the forbidden properties day, time!
          2025-05-04 15:54:02.927 - error: bluelink.0 (23102) PARSECHECK [object Object] evModeRange [object Object]
          2025-05-04 15:54:02.939 - error: bluelink.0 (23102) PARSECHECK [object Object] totalAvailableRange [object Object]
          2025-05-04 15:54:02.940 - error: bluelink.0 (23102) PARSECHECK [object Object] rangeByFuel [object Object]
          2025-05-04 15:54:02.947 - error: bluelink.0 (23102) PARSECHECK [object Object] dte [object Object]
          2025-05-04 15:54:02.976 - error: bluelink.0 (23102) PARSECHECK [object Object] evModeRange [object Object]
          2025-05-04 15:54:02.991 - error: bluelink.0 (23102) PARSECHECK [object Object] totalAvailableRange [object Object]
          2025-05-04 15:54:02.992 - error: bluelink.0 (23102) PARSECHECK [object Object] rangeByFuel [object Object]
          2025-05-04 15:54:02.998 - error: bluelink.0 (23102) PARSECHECK [object Object] dte [object Object]
          2025-05-04 15:54:03.004 - error: bluelink.0 (23102) PARSECHECK [object Object] reservChargeInfos [object Object]
          2025-05-04 15:54:03.035 - error: bluelink.0 (23102) PARSECHECK [object Object] batteryPower [object Object]
          2025-05-04 15:54:03.036 - error: bluelink.0 (23102) PARSECHECK [object Object] evStatus [object Object]
          2025-05-04 15:54:03.173 - error: bluelink.0 (23102) PARSECHECK [object Object] tirePressureLamp [object Object]
          2025-05-04 15:54:03.194 - error: bluelink.0 (23102) PARSECHECK [object Object] batSignalReferenceValue [object Object]
          2025-05-04 15:54:03.201 - error: bluelink.0 (23102) PARSECHECK [object Object] battery [object Object]
          2025-05-04 15:54:03.217 - error: bluelink.0 (23102) PARSECHECK [object Object] stopLamp [object Object]
          2025-05-04 15:54:03.247 - error: bluelink.0 (23102) PARSECHECK [object Object] headLamp [object Object]
          2025-05-04 15:54:03.328 - info: bluelink.0 (23102) terminating
          2025-05-04 15:54:03.396 - warn: bluelink.0 (23102) get state error: Connection is closed.
          2025-05-04 15:54:03.425 - error: bluelink.0 (23102) Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightRearLamp": DB closed
          2025-05-04 15:54:03.427 - warn: bluelink.0 (23102) Could not perform strict object check of state bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightFrontLamp: DB closed
          2025-05-04 15:54:03.428 - warn: bluelink.0 (23102) get state error: Connection is closed.
          2025-05-04 15:54:03.429 - error: bluelink.0 (23102) Error extract objectKeys: KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.[object Object]
          2025-05-04 15:54:03.430 - error: bluelink.0 (23102) Error: Could not check object existence of bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightRearLamp: Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightRearLamp": DB closed
          2025-05-04 15:54:03.430 - error: bluelink.0 (23102) PARSECHECK [object Object] turnSignalLamp [object Object]
          2025-05-04 15:54:03.431 - error: bluelink.0 (23102) PARSECHECK [object Object] lampWireStatus [object Object]
          2025-05-04 15:54:03.435 - error: bluelink.0 (23102) Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.windowOpen": Connection is closed.
          2025-05-04 15:54:03.684 - error: host.raspberrypi4 instance system.adapter.bluelink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-05-04 15:54:03.685 - info: host.raspberrypi4 Restart adapter system.adapter.bluelink.0 because enabled
          2025-05-04 15:54:34.900 - info: host.raspberrypi4 instance system.adapter.bluelink.0 in version "3.1.2" (non-npm: Newan/ioBroker.bluelink#parsecheck) started with pid 23155
          2025-05-04 15:54:38.281 - info: bluelink.0 (23155) starting. Version 3.1.2 (non-npm: Newan/ioBroker.bluelink#parsecheck) in /opt/iobroker/node_modules/iobroker.bluelink, node: v20.19.1, js-controller: 7.0.6
          2025-05-04 15:54:38.315 - info: bluelink.0 (23155) Login to api
          2025-05-04 15:54:41.016 - info: bluelink.0 (23155) 1 Vehicles found
          2025-05-04 15:54:41.199 - info: bluelink.0 (23155) Read new update for KNAC381xxx from the server
          2025-05-04 15:54:41.518 - error: bluelink.0 (23155) PARSECHECK [object Object] coord [object Object]
          2025-05-04 15:54:41.538 - error: bluelink.0 (23155) PARSECHECK [object Object] speed [object Object]
          2025-05-04 15:54:41.595 - error: bluelink.0 (23155) PARSECHECK [object Object] accuracy [object Object]
          2025-05-04 15:54:41.602 - error: bluelink.0 (23155) PARSECHECK [object Object] vehicleLocation [object Object]
          2025-05-04 15:54:41.639 - error: bluelink.0 (23155) PARSECHECK [object Object] doorOpen [object Object]
          2025-05-04 15:54:41.665 - error: bluelink.0 (23155) PARSECHECK [object Object] airTemp [object Object]
          2025-05-04 15:54:41.747 - error: bluelink.0 (23155) PARSECHECK [object Object] etc1 [object Object]
          2025-05-04 15:54:41.805 - error: bluelink.0 (23155) PARSECHECK [object Object] etc2 [object Object]
          2025-05-04 15:54:41.818 - error: bluelink.0 (23155) PARSECHECK [object Object] etc3 [object Object]
          2025-05-04 15:54:41.833 - error: bluelink.0 (23155) PARSECHECK [object Object] atc [object Object]
          2025-05-04 15:54:41.834 - error: bluelink.0 (23155) PARSECHECK [object Object] remainTime2 [object Object]
          2025-05-04 15:54:41.885 - error: bluelink.0 (23155) PARSECHECK [object Object] evModeRange [object Object]
          2025-05-04 15:54:41.935 - error: bluelink.0 (23155) PARSECHECK [object Object] totalAvailableRange [object Object]
          2025-05-04 15:54:41.936 - error: bluelink.0 (23155) PARSECHECK [object Object] rangeByFuel [object Object]
          2025-05-04 15:54:41.965 - error: bluelink.0 (23155) PARSECHECK [object Object] time [object Object]
          2025-05-04 15:54:41.965 - error: bluelink.0 (23155) PARSECHECK [object Object] reservInfo [object Object]
          2025-05-04 15:54:42.035 - error: bluelink.0 (23155) PARSECHECK [object Object] airTemp [object Object]
          2025-05-04 15:54:42.046 - error: bluelink.0 (23155) PARSECHECK [object Object] reservFatcSet [object Object]
          2025-05-04 15:54:42.047 - error: bluelink.0 (23155) PARSECHECK [object Object] reservChargeInfoDetail [object Object]
          2025-05-04 15:54:42.048 - error: bluelink.0 (23155) PARSECHECK [object Object] reservChargeInfo [object Object]
          2025-05-04 15:54:42.069 - error: bluelink.0 (23155) PARSECHECK [object Object] starttime [object Object]
          2025-05-04 15:54:42.082 - error: bluelink.0 (23155) PARSECHECK [object Object] endtime [object Object]
          2025-05-04 15:54:42.083 - error: bluelink.0 (23155) PARSECHECK [object Object] offPeakPowerTime1 [object Object]
          2025-05-04 15:54:42.091 - error: bluelink.0 (23155) PARSECHECK [object Object] offpeakPowerInfo [object Object]
          2025-05-04 15:54:42.115 - error: bluelink.0 (23155) PARSECHECK [object Object] time [object Object]
          2025-05-04 15:54:42.116 - error: bluelink.0 (23155) PARSECHECK [object Object] reservInfo [object Object]
          2025-05-04 15:54:42.186 - error: bluelink.0 (23155) PARSECHECK [object Object] airTemp [object Object]
          2025-05-04 15:54:42.200 - error: bluelink.0 (23155) PARSECHECK [object Object] reservFatcSet [object Object]
          2025-05-04 15:54:42.203 - error: bluelink.0 (23155) PARSECHECK [object Object] reservChargeInfoDetail [object Object]
          2025-05-04 15:54:42.203 - error: bluelink.0 (23155) PARSECHECK [object Object] reserveChargeInfo2 [object Object]
          2025-05-04 15:54:42.266 - error: bluelink.0 (23155) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-04 15:54:42.267 - error: bluelink.0 (23155) unhandled promise rejection: The state contains the forbidden properties day, time!
          2025-05-04 15:54:42.269 - error: bluelink.0 (23155) Error: The state contains the forbidden properties day, time!
          at Validator.validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:299:13)
          at Bluelink._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4984:21)
          at Bluelink.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4962:17)
          at Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:140:34)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Bluelink.readStatusVin (/opt/iobroker/node_modules/iobroker.bluelink/main.js:391:17)
          at async Bluelink.readStatus (/opt/iobroker/node_modules/iobroker.bluelink/main.js:355:13)
          2025-05-04 15:54:42.270 - error: bluelink.0 (23155) The state contains the forbidden properties day, time!
          2025-05-04 15:54:42.275 - info: bluelink.0 (23155) Adapter bluelink cleaned up everything...
          2025-05-04 15:54:42.276 - info: bluelink.0 (23155) terminating
          2025-05-04 15:54:42.278 - warn: bluelink.0 (23155) Terminated (UNCAUGHT_EXCEPTION): Without reason
          2025-05-04 15:54:42.282 - error: bluelink.0 (23155) PARSECHECK [object Object] ect [object Object]
          2025-05-04 15:54:42.284 - error: bluelink.0 (23155) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
          2025-05-04 15:54:42.285 - error: bluelink.0 (23155) unhandled promise rejection: The state contains the forbidden properties day, time!
          2025-05-04 15:54:42.286 - error: bluelink.0 (23155) Error: The state contains the forbidden properties day, time!
          at Validator.validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/validator.js:299:13)
          at Bluelink._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4984:21)
          at Bluelink.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/cjs/lib/adapter/adapter.js:4962:17)
          at Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:140:34)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Json2iob.parse (/opt/iobroker/node_modules/iobroker.bluelink/lib/json2iob.js:97:25)
          at async Bluelink.readStatusVin (/opt/iobroker/node_modules/iobroker.bluelink/main.js:391:17)
          at async Bluelink.readStatus (/opt/iobroker/node_modules/iobroker.bluelink/main.js:355:13)
          2025-05-04 15:54:42.287 - error: bluelink.0 (23155) The state contains the forbidden properties day, time!
          2025-05-04 15:54:42.357 - error: bluelink.0 (23155) PARSECHECK [object Object] evModeRange [object Object]
          2025-05-04 15:54:42.373 - error: bluelink.0 (23155) PARSECHECK [object Object] totalAvailableRange [object Object]
          2025-05-04 15:54:42.373 - error: bluelink.0 (23155) PARSECHECK [object Object] rangeByFuel [object Object]
          2025-05-04 15:54:42.380 - error: bluelink.0 (23155) PARSECHECK [object Object] dte [object Object]
          2025-05-04 15:54:42.447 - error: bluelink.0 (23155) PARSECHECK [object Object] evModeRange [object Object]
          2025-05-04 15:54:42.460 - error: bluelink.0 (23155) PARSECHECK [object Object] totalAvailableRange [object Object]
          2025-05-04 15:54:42.461 - error: bluelink.0 (23155) PARSECHECK [object Object] rangeByFuel [object Object]
          2025-05-04 15:54:42.469 - error: bluelink.0 (23155) PARSECHECK [object Object] dte [object Object]
          2025-05-04 15:54:42.475 - error: bluelink.0 (23155) PARSECHECK [object Object] reservChargeInfos [object Object]
          2025-05-04 15:54:42.553 - error: bluelink.0 (23155) PARSECHECK [object Object] batteryPower [object Object]
          2025-05-04 15:54:42.554 - error: bluelink.0 (23155) PARSECHECK [object Object] evStatus [object Object]
          2025-05-04 15:54:42.656 - error: bluelink.0 (23155) PARSECHECK [object Object] tirePressureLamp [object Object]
          2025-05-04 15:54:42.679 - error: bluelink.0 (23155) PARSECHECK [object Object] batSignalReferenceValue [object Object]
          2025-05-04 15:54:42.686 - error: bluelink.0 (23155) PARSECHECK [object Object] battery [object Object]
          2025-05-04 15:54:42.699 - error: bluelink.0 (23155) PARSECHECK [object Object] stopLamp [object Object]
          2025-05-04 15:54:42.774 - error: bluelink.0 (23155) PARSECHECK [object Object] headLamp [object Object]
          2025-05-04 15:54:42.780 - info: bluelink.0 (23155) terminating
          2025-05-04 15:54:42.791 - warn: bluelink.0 (23155) get state error: Connection is closed.
          2025-05-04 15:54:42.800 - error: bluelink.0 (23155) Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.leftRearLamp": DB closed
          2025-05-04 15:54:42.803 - warn: bluelink.0 (23155) Could not perform strict object check of state bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.leftFrontLamp: DB closed
          2025-05-04 15:54:42.805 - warn: bluelink.0 (23155) get state error: Connection is closed.
          2025-05-04 15:54:42.807 - error: bluelink.0 (23155) Error extract objectKeys: KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.[object Object]
          2025-05-04 15:54:42.807 - error: bluelink.0 (23155) Error: Could not check object existence of bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.leftRearLamp: Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.leftRearLamp": DB closed
          2025-05-04 15:54:42.814 - error: bluelink.0 (23155) Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightRearLamp": Connection is closed.
          2025-05-04 15:54:42.818 - error: bluelink.0 (23155) Error extract objectKeys: KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.[object Object]
          2025-05-04 15:54:42.818 - error: bluelink.0 (23155) Error: Could not check object existence of bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightRearLamp: Cannot check object existence of "bluelink.0.KNAC381xxx.vehicleStatusRaw.vehicleStatus.lampWireStatus.turnSignalLamp.rightRearLamp": Connection is closed.
          2025-05-04 15:54:42.819 - error: bluelink.0 (23155) PARSECHECK [object Object] turnSignalLamp [object Object]
          2025-05-04 15:54:42.819 - error: bluelink.0 (23155) PARSECHECK [object Object] lampWireStatus [object Object]
          2025-05-04 15:54:43.003 - error: host.raspberrypi4 instance system.adapter.bluelink.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
          2025-05-04 15:54:43.003 - info: host.raspberrypi4 Restart adapter system.adapter.bluelink.0 because 
          
          1 Reply Last reply Reply Quote 0
          • M
            marchusar @Meister Mopper last edited by marchusar

            @meister-mopper
            Bei mir läuft u.a. die Homematic nicht, wenn ich auf 64bit umstelle. Gerade nochmal versucht...

            Mein Zigbee läuft und bietet den Direktlink in der Config selbst so an. Auch hier hatte ich mit dem by-id Link schon mal Schwierigkeiten und seitdem ich es so nutze läuft es stabil.

            Die je 2 Instanzen sind für lokalen Zugriff ohne Passwort und externen Zugriff mit SSL und Passwort. Das funktioniert auch einwandfrei.

            1 Reply Last reply Reply Quote 0
            • M
              marchusar @arteck last edited by

              @arteck
              meine reserveChargeInfo2 aus der 3.1.0 :
              bb099754-34df-44cf-872c-a72802c7738b-image.png

              1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active last edited by arteck

                neue Version 3.1.3 ist unterwegs.. habe paar Fehler behoben..

                und ich hätte mal hier

                https://github.com/Newan/ioBroker.bluelink/tarball/bluelinky9
                

                eine Version zum Testen ür alle die das neue System im Auto haben .. wo der ccs2Status Knoten weg fallen würde und die Infos ganz normal zur Verfügung stehen würden wie früher.. unter vehicleStatus ..

                e6c1bc0e-baa7-4584-8460-c5f7a3717f46-grafik.png

                der ccs2Status Knoten würde dann nicht mehr aktualisiert..und könnte manuell gelöscht werden...

                Peter V. MaBu59 Neuschwansteini 3 Replies Last reply Reply Quote 0
                • Peter V.
                  Peter V. @arteck last edited by

                  @arteck said in Adapter Hyundai (Bluelink) oder KIA (UVO):

                  https://github.com/Newan/ioBroker.bluelink/tarball/bluelinky9

                  Mit dieser Version sind bei mir die (seltenen) Fehlermeldungen wieder weg und Maps läuft auch wieder.
                  Kia Ceed BJ 2024
                  Top, danke

                  1 Reply Last reply Reply Quote 0
                  • MaBu59
                    MaBu59 @arteck last edited by

                    @arteck
                    Diese Version erzeugt bei mir auch keine Fehlermeldungen mehr und läuft!!
                    Siehst Du eine Chance, den "ccs2Status" ans Laufen zu bringen oder ist der Aufwand zu hoch?
                    Danke für Deinen Einsatz!!

                    arteck 1 Reply Last reply Reply Quote 0
                    • arteck
                      arteck Developer Most Active @MaBu59 last edited by

                      @mabu59 sagte in Adapter Hyundai (Bluelink) oder KIA (UVO):

                      Siehst Du eine Chance, den "ccs2Status" ans Laufen zu bringen oder ist der Aufwand zu hoch?

                      was meinst du ???

                      MaBu59 1 Reply Last reply Reply Quote 0
                      • Neuschwansteini
                        Neuschwansteini @arteck last edited by

                        @arteck sagte in Adapter Hyundai (Bluelink) oder KIA (UVO):

                        neue Version 3.1.3 ist unterwegs.. habe paar Fehler behoben..

                        und ich hätte mal hier

                        https://github.com/Newan/ioBroker.bluelink/tarball/bluelinky9
                        

                        eine Version zum Testen ür alle die das neue System im Auto haben .. wo der ccs2Status Knoten weg fallen würde und die Infos ganz normal zur Verfügung stehen würden wie früher.. unter vehicleStatus ..

                        gerade mal getestet, sieht genauso aus wie die normale 3.1.3 .. nur mit einem Fehler beim Starten:

                        bluelink.0
                        2025-05-06 08:35:42.388	error	TypeError: Cannot read properties of undefined (reading 'airCtrlOn') at Bluelink.setNewFullStatus (/opt/iobroker/node_modules/iobroker.bluelink/main.js:620:46) at Bluelink.readStatusVin (/opt/iobroker/node_modules/iobroker.bluelink/main.js:392:28) at async Bluelink.readStatus (/opt/iobroker/node_modules/iobroker.bluelink/main.js:355:13) at async Pe.<anonymous> (/opt/iobroker/node_modules/iobroker.bluelink/main.js:298:21)
                        

                        e6c1bc0e-baa7-4584-8460-c5f7a3717f46-grafik.png

                        der ccs2Status Knoten würde dann nicht mehr aktualisiert..und könnte manuell gelöscht werden...

                        hatte ich vorher gemacht, ist jetzt wieder da.. ?
                        Ist die Version auch eine 3.1.3 ?

                        arteck 1 Reply Last reply Reply Quote 0
                        • MaBu59
                          MaBu59 @arteck last edited by

                          @arteck
                          Du hast geschrieben "wo der ccs2Status Knoten weg fallen würde".
                          Ich verstehe das so, ohne den Knoten funktioniert der Adapter, mit dem Knoten nicht.
                          Der Knoten müßte angepasst werden, damit der Adapter funktioniert.
                          Ich habe vermutet, dass der Aufwand dafür sehr hoch ist.

                          Neuschwansteini 1 Reply Last reply Reply Quote 0
                          • Neuschwansteini
                            Neuschwansteini @MaBu59 last edited by

                            @mabu59

                            nee, frueher gabs den Ordner mit ccs2Status nicht, das sind 394 Objects weniger.. 🙂
                            Funktioniert bei meinem leider nicht, oder ich was falsch gemacht.. ?

                            1 Reply Last reply Reply Quote 0
                            • arteck
                              arteck Developer Most Active @Neuschwansteini last edited by

                              @neuschwansteini dann brauch ich mehr kontext...

                              auch ein KIA ?? welches Baujahr ??

                              gibts den DP "vehicleStatus.airCtrlOn"

                              Neuschwansteini 1 Reply Last reply Reply Quote 0
                              • Neuschwansteini
                                Neuschwansteini @arteck last edited by

                                @arteck sagte in Adapter Hyundai (Bluelink) oder KIA (UVO):

                                @neuschwansteini dann brauch ich mehr kontext...

                                auch ein KIA ?? welches Baujahr ??

                                Ioniq 5N - 2024. ccNC - Zugangsdaten hast du (ilovegym)

                                gibts den DP "vehicleStatus.airCtrlOn"

                                ja, der wurde erstellt

                                1 Reply Last reply Reply Quote 0
                                • arteck
                                  arteck Developer Most Active last edited by

                                  sache geklärt... die 3.1.3 ist freigegeben..

                                  M gbackus 2 Replies Last reply Reply Quote 3
                                  • M
                                    marchusar @arteck last edited by

                                    @arteck Danke. 3.1.3 funktioniert nun bei mir einwandfrei und die DriveHistory kommt auch wieder. 👍 Vielen Dank.

                                    Ich weiß nicht, ob es hier schon angekommen ist und wie das bei Hyundai aussieht. Es gibt eine neue "Kia" App (vorher "Kia Connect") mit der man für die alten Systeme (ab Modelljahr 23 oder 24) nun auch die Fenster öffnen und schließen kann und scheinbar bei allen die Blinker und Horn ansteuern kann. Außerdem wird nach Akzeptieren der Bedingungen in der App nun eine Fahrbewertung erstellt.

                                    Meinst du, dass du das auch eingebaut bekommst?

                                    arteck 1 Reply Last reply Reply Quote 0
                                    • arteck
                                      arteck Developer Most Active @marchusar last edited by

                                      @marchusar ja app gesehen..
                                      ich sehe zur Zeit kein Mehrwert zu der connect

                                      P 1 Reply Last reply Reply Quote 0
                                      • P
                                        Peguschwein @arteck last edited by

                                        Danke für das update
                                        KIA Niro (der Neue)
                                        und KIA EV3 2025 kommen nun auch einige Daten SOC / km Stand und Reichweite reichen mir schon vollkommen

                                        1 Reply Last reply Reply Quote 0
                                        • gbackus
                                          gbackus @arteck last edited by

                                          @arteck
                                          Hallo arteck. Ich habe den Adapter jetzt auch installiert und kann für mich wichtige Informationen meines Hyundais IONIQ 6 daraus beziehen. Vielen Dank dafür.

                                          Allerdings finde ich im ioBroker-Protokoll folgende info-Meldung:
                                          info State value to set for "bluelink.0.KMHM541C7PAXXXXXX.vehicleStatus.steerWheelHeat" has to be type "number" but received type "boolean"

                                          Nicht das die Temperatur des Lenkrades für mich wichtig wäre aber dur kannst ja mal schauen, ob da ein type-error vorliegt.
                                          Beste Grüße

                                          Neuschwansteini arteck 2 Replies Last reply Reply Quote 0
                                          • Neuschwansteini
                                            Neuschwansteini @gbackus last edited by

                                            @gbackus

                                            Das muesste Lenkradheizung an/aus sein, also ein boolean in iobroker, in der bluelinky-Adaption kommt es als 0-aus / 1-an rueber, ist dann wohl nicht im Adapter uebersetzt..

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            767
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            126
                                            1950
                                            563249
                                            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