You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter vw-connect for common errors and appropiate suggestions to keep this adapter up to date.
This check is based on the current head revisions (master / main branch) of the adapter repository
❗ [E6007] Future year (2030) found in copyright at README.md. Please use "Copyright (c) 2019-2026 ta2k tombox2020@gmail.com" at start of LICENSE section.
❗ [E6015] README.md must use English language only but appears to contain German text (detected: "unzuverlässig: das Auto"). Please remove or translate.
❗ [E7005] Future year (2030) found in LICENSE. Please use "Copyright (c) 2019-2026 ta2k tombox2020@gmail.com" at the start of LICENSE
WARNINGS:
👀 [W0028] Minimum node.js version 22 recommended. The current engines.node clause ">=20.19.0" allows Node.js 20.19.0 as minimum. Please update it to require at least ">=22" at package.json.
👀 [W0040] "keywords" within package.json should contain "ioBroker"
👀 [W0050] 'request' package is deprecated and no longer maintained. Consider migrating to native 'node:fetch' or 'axios' if more complex functionality is needed.
👀 [W1027] Missing suggested translation into uk of "common.titleLang" in io-package.json.
👀 [W1032] Many "common.news" found in io-package.json. Repository builder will truncate at 7 news. Please remove old news.
👀 [W1034] Missing suggested translation into uk of "common.desc" in io-package.json.
👀 [W1073] Potential sensitive data "password,atoken,rtoken,vwatoken,vwrtoken,wc_access_token,wc_refresh_token,pin,tibberClientSecret" not listed at "protectedNative" in io-package.json
👀 [W1074] Potential sensitive data "password, atoken, rtoken, vwatoken, vwrtoken, wc_access_token, wc_refresh_token, pin, tibberClientSecret" not listed at "encryptedNative" in io-package.json
👀 [W1078] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "common.adminUI.config".
👀 [W1081] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
👀 [W1084] "common.main" is deprecated and ignored. Please remove from io-package.json. Executable is defined by entry "main" at package.json.
👀 [W1084] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
👀 [W2002] Version of package.json (0.9.8) doesn't match latest version on NPM (0.9.7)
👀 [W3019] "test-and-release.yml": job "deploy" step using "ioBroker/testing-action-deploy@v1" has "npm-token" parameter specified. Trusted publishing will not work while "npm-token" is set.
👀 [W3024] "test-and-release.yml": job "adapter-tests" matrix uses node.js 25 which is not in the list of recommended testing versions (20, 22, 24, 26, 27).
👀 [W3032] "test-and-release.yml" run triggered by tag "v0.9.6" for current release 0.9.6 failed run #760.
👀 [W3032] "test-and-release.yml" run triggered by tag "v0.9.8" for current release 0.9.8 failed run #775.
👀 [W3035] "test-and-release.yml" run triggered by tag "v0.9.7" for npm latest release 0.9.7 failed run #770.
👀 [W3051] "test-and-release.yml": "testing-action-check" in run #761 on branch "master"does not log the expected defaults for "npm run test:package". Please check the log,
👀 [W3051] "test-and-release.yml": "testing-action-check" in run #765 on branch "master"does not log the expected defaults for "npm run test:package". Please check the log,
👀 [W3051] "test-and-release.yml": "testing-action-check" in run #766 on branch "master"does not log the expected defaults for "npm run test:package". Please check the log,
👀 [W3051] "test-and-release.yml": "testing-action-check" in run #774 on branch "master"does not log the expected defaults for "npm run test:package". Please check the log,
👀 [W5060] Package "json-bigint" is listed in dependencies of package.json but not imported or required by any scanned source file. Dependency might be unused.
👀 [W6023] Sentry plugin is configured in io-package.json but the required Sentry information was not found in README.md. Please add the standard Sentry notice near the top of README.md.
👀 [W9501] .npmignore found but "files" is used at package.json. Please remove .npmignore.
SUGGESTIONS:
📌 [S0062] Consider adding and using package "@iobroker/adapter-dev".
📌 [S0062] Consider adding and using package "@iobroker/eslint-config".
📌 [S0071] No devDependency for "@iobroker/eslint-config" found. Consider migrating to the shared ESLint config.
📌 [S0073] "eslint":"^10.4.1" is >= 9.0.0 but "@iobroker/eslint-config" is not used. Consider migrating to "@iobroker/eslint-config".
📌 [S0085] No devDependency "@tsconfig/nodeXX" found. Consider adding one for proper type checking (see ioBroker.examples for examples).
📌 [S2008] Version 0.9.6 tagged as "latest" at npm is not signed with provenance. Trusted publishing is recommended.
📌 [S2008] Version 0.9.7 tagged as "latest" at npm is not signed with provenance. Trusted publishing is recommended.
📌 [S3014] "test-and-release.yml": job "adapter-tests" should declare "needs: check-and-lint" to run after linting.
📌 [S3018] "test-and-release.yml": job "deploy" is missing required permissions "contents: write" and "id-token: write" at job level. Trusted publishing will not work without them.
📌 [S4047] Adapter "vw-connect" is not yet available in the stable repository. Please consider adding it.
📌 [S5004] Plain setInterval() found in source files (main.js). Please use this.setInterval() or adapter.setInterval() instead.
📌 [S5005] Plain setTimeout() found in source files (main.js). Please use this.setTimeout() or adapter.setTimeout() instead.
📌 [S5022] Please consider migrating to admin 5 UI (jsonConfig) or react based UI.
📌 [S5032] "lib/tools.js" found in repo but not used anywhere. Consider removing file.
📌 [S5043] Package "crypto" is a built-in Node.js module. Please use "node:crypto" instead.
📌 [S5043] Package "fs" is a built-in Node.js module. Please use "node:fs" instead.
📌 [S5043] Package "https" is a built-in Node.js module. Please use "node:https" instead.
📌 [S5043] Package "path" is a built-in Node.js module. Please use "node:path" instead.
📌 [S5043] Package "url" is a built-in Node.js module. Please use "node:url" instead.
📌 [S5043] Package "zlib" is a built-in Node.js module. Please use "node:zlib" instead.
📌 [S5065] ".travis.yml" was found. This file is most likely obsolete and can be removed after verifying that travis is no longer used.
📌 [S8005] No GitHub release found. Please use GitHub releases for easier identification of the current release and consider using "@iobroker/action-deploy".
📌 [S8901] Dependabot configuration file ".github/dependabot.yml" not found. Consider adding dependabot to keep dependencies up to date.
📌 [S9006] .commitinfo file should be excluded by .gitignore, please add a line with text ".commitinfo" to .gitignore
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible - at least with next minor release. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository. Priority bugfixes will not be blocked by existing errors as long as tests pass.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or @iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users. Let's work together for the best user experience.
Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter vw-connect for common errors and appropiate suggestions to keep this adapter up to date.
This check is based on the current head revisions (master / main branch) of the adapter repository
Please see the result of the check below.
ioBroker.vw-connect
ERRORS:
WARNINGS:
SUGGESTIONS:
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible - at least with next minor release. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository. Priority bugfixes will not be blocked by existing errors as long as tests pass.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheckor
@iobroker-bot recreatePlease note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@ioBroker-Bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 14 Aug 2026 02:10:28 GMT based on commit a73d78c
ioBroker.repochecker 5.20.9