Skip to content

Please consider fixing issues detected by repository checker #497

Description

@ioBroker-Bot

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 energiefluss-erweitert 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.energiefluss-erweitert

Downloads Number of Installations (latest) Number of Installations (stable) - Test and Release

ERRORS:

  • ❗ [E0036] @alcalzone/release-script 5.2.0 specified. 5.2.1 is required as minimum, 5.2.1 (or newer) is current. Please update devDependencies at package.json
  • ❗ [E3022] "test-and-release.yml": job "deploy" uses node.js 22 which is below the minimum required version 24. Please update to node.js 24.
  • ❗ [E3022] Workflow "test-and-release.yml": job "deploy" uses node.js 22 which is below the minimum required version 24. Please update to node.js 24.

WARNINGS:

  • 👀 [W0028] Minimum node.js version 22 recommended. Please adapt "{'engines' : { 'node' >= '20' } }" to "{'engines' : { 'node' >= '22' } }" at package.json.
  • 👀 [W0028] Minimum node.js version 22 recommended. The current engines.node clause ">= 20" allows Node.js 20.0.0 as minimum. Please update it to require at least ">=22" at package.json.
  • 👀 [W0034] @iobroker/adapter-core 3.3.2 specified. 3.4.1 (or newer) is current. Please update dependencies at package.json
  • 👀 [W0066] "@types/node":"^25.7.0" at package.json allows major version greater than 20. Downgrade to node.js 20.x.x to avoid wrong typing is recommended.
  • 👀 [W0066] "@types/node":"^25.9.0" at package.json allows major version greater than 20. Downgrade to node.js 20.x.x to avoid wrong typing is recommended.
  • 👀 [W0066] "@types/node":"^25.9.1" at package.json allows major version greater than 20. Downgrade to node.js 20.x.x to avoid wrong typing is recommended.
  • 👀 [W0066] "@types/node":"^25.9.2" at package.json allows major version greater than 20. Downgrade to node.js 20.x.x to avoid wrong typing is recommended.
  • 👀 [W0066] "@types/node":"^25.9.3" at package.json allows major version greater than 20. Downgrade to node.js 20.x.x to avoid wrong typing is recommended.
  • 👀 [W0086] "@tsconfig/node14" should match the major node.js version from package.json engines.node (>=20). Please update to @tsconfig/node20 at package.json.
  • 👀 [W0090] "/tsconfig.json" should be adjusted to match "@tsconfig/node20" (for example: "extends": "@tsconfig/node20/tsconfig.json").
  • 👀 [W1133] io-package.json: instanceObject "calculation.battery.remaining_target_DT" role "value" expects common.type to be one of [number], but found "string"
  • 👀 [W3032] Just for Info: No workflow run for "test-and-release.yml" triggered by tag "v0.8.2" was found for current release 0.8.2. Workflow logs might be deleted already.
  • 👀 [W3048] "test-and-release.yml": job "check-and-lint" step using "ioBroker/testing-action-check" specifies "lint-command". This command should not be changed; the default value should be used.
  • 👀 [W3050] "test-and-release.yml": could not retrieve log for "check-and-lint" job in run #1357.
  • 👀 [W3050] "test-and-release.yml": could not retrieve log for "check-and-lint" job in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (20.x, macos-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (20.x, macos-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (20.x, ubuntu-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (20.x, ubuntu-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (20.x, windows-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (20.x, windows-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (22.x, macos-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (22.x, macos-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (22.x, ubuntu-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (22.x, ubuntu-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (22.x, windows-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (22.x, windows-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (24.x, macos-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (24.x, macos-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (24.x, ubuntu-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (24.x, ubuntu-latest)" in run #1386.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (24.x, windows-latest)" in run #1357.
  • 👀 [W3052] "test-and-release.yml": could not retrieve log for job "adapter-tests (24.x, windows-latest)" in run #1386.
  • 👀 [W5060] Package "url" is listed in dependencies of package.json but not imported or required by any scanned source file. Dependency might be unused.
  • 👀 [W6019] README.md contains 61 changelog entries. Consider adding CHANGELOG_OLD.md file supported by @alcalzone/releasescript.
  • 👀 [W6028] Changelog entry header(s) do not match required version format "x.y.z": 0.5.1-alpha.11 (2024-11-12), 0.5.1-alpha.10 (2024-10-24), 0.5.1-alpha.9 (2024-09-23), 0.5.1-alpha.8 (2024-09-18), 0.5.1-alpha.7 (2024-09-16), 0.5.1-alpha.6 (2024-08-29), 0.5.1-alpha.5 (2024-08-27), 0.5.1-alpha.4 (2024-08-07), 0.5.1-alpha.3 (2024-07-18), 0.5.1-alpha.2 (2024-07-09), 0.5.1-alpha.1 (2024-07-04), 0.5.1-alpha.0 (2024-06-28), 0.5.0-alpha.0 (2024-06-24), 0.0.2-alpha.24 (2023-11-14), 0.0.2-alpha.23 (2023-10-25), 0.0.2-alpha.22 (2023-10-20), 0.0.2-alpha.21 (2023-10-17), 0.0.2-alpha.20 (2023-09-22), 0.0.2-alpha.19 (2023-09-14), 0.0.2-alpha.18 (2023-09-11), 0.0.2-alpha.17 (2023-09-07), 0.0.2-alpha.16 (2023-08-31), 0.0.2-alpha.15 (2023-08-10), 0.0.2-alpha.14 (2023-08-04), 0.0.2-alpha.13 (2023-07-26), 0.0.2-alpha.12 (2023-07-18), 0.0.2-alpha.11 (2023-07-17), 0.0.2-alpha.10 (2023-07-10), 0.0.2-alpha.9 (2023-07-04), 0.0.2-alpha.8 (2023-06-26), 0.0.2-alpha.7 (2023-05-25), 0.0.2-alpha.6 (2023-05-24), 0.0.2-alpha.5 (2023-05-24), 0.0.2-alpha.4 (2023-05-17), 0.0.2-alpha.3 (2023-05-17), 0.0.2-alpha.2 (2023-05-15), 0.0.2-alpha.1 (2023-04-28), 0.0.2-alpha.0 (2023-04-28)
  • 👀 [W8004] Please process PR [#478] "[iobroker-bot] Update Node.js versions in test-and-release workflow"
  • 👀 [W8004] Please process PR [#487] "[iobroker-bot] Add Dependabot Ignore Rule for @types/node Major Version Updates"
  • 👀 [W8004] Please process PR [#488] "[iobroker-bot] Drop Node.js 20 support (End of Life)"
  • 👀 [W8004] Please process PR [#489] "[iobroker-bot] Add CHANGELOG_OLD.md to store older changelog entries"
  • 👀 [W8004] Please process PR [[[iobroker-bot] Align @tsconfig/nodeXX with engines.node in package.json #499] "[iobroker-bot] Align @tsconfig/nodeXX with engines.node in package.json"]([iobroker-bot] Align @tsconfig/nodeXX with engines.node in package.json #499)
  • 👀 [W8004] Please process PR [#500] "[iobroker-bot] Add Dependabot Ignore Rule for @types/node Major Version Updates"
  • 👀 [W8917] At least major versions of @types/node should not be updated by dependabot. Please add ignore block at dependabot.yml.

SUGGESTIONS:

  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 206 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 207 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 208 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 209 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 210 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 211 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 212 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 213 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists for 214 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] A newer version (0.34.5) for package "sharp" (dependencies) exists. The newer version has been published for more than 200 days. Please evaluate if upgrading from 0.32.6 to 0.34.5 is possible.
  • 📌 [S0082] Package "sharp" (dependencies) can be updated from 0.32.6 to 0.34.5. The newer version has been published for 201 days. Please evaluate updating package.json.
  • 📌 [S0082] Package "sharp" (dependencies) can be updated from 0.32.6 to 0.34.5. The newer version has been published for 202 days. Please evaluate updating package.json.
  • 📌 [S0082] Package "sharp" (dependencies) can be updated from 0.32.6 to 0.34.5. The newer version has been published for 203 days. Please evaluate updating package.json.
  • 📌 [S0082] Package "sharp" (dependencies) can be updated from 0.32.6 to 0.34.5. The newer version has been published for 204 days. Please evaluate updating package.json.
  • 📌 [S0082] Package "sharp" (dependencies) can be updated from 0.32.6 to 0.34.5. The newer version has been published for 205 days. Please evaluate updating package.json.
  • 📌 [S2008] Version 0.8.2 tagged as "latest" at npm is not signed with provenance. Trusted publishing is recommended.
  • 📌 [S3021] "test-and-release.yml": job "check-and-lint" uses node.js 22. Consider updating to the recommended version 24.
  • 📌 [S3021] Workflow "test-and-release.yml": job "check-and-lint" uses node.js 22. Consider updating to the recommended version 24.
  • 📌 [S3032] Just for Info: No workflow run for "test-and-release.yml" triggered by tag "v0.8.2" was found for current release 0.8.2. Workflow logs might be deleted already.
  • 📌 [S3032] No workflow run for "test-and-release.yml" triggered by tag "v0.8.2" was found for current release 0.8.2. Workflow logs might be deleted already.
  • 📌 [S5022] Please consider migrating to admin 5 UI (jsonConfig) or react based UI.
  • 📌 [S5601] i18n directory "admin/i18n" uses long format ({lang}/translations.json). Consider migrating to short format ({lang}.json) using "npm run translate convert".
  • 📌 [S5601] i18n directory "www/js/i18n" uses long format ({lang}/translations.json). Consider migrating to short format ({lang}.json) using "npm run translate convert".

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.

your
ioBroker Check and Service Bot

@mcm1957 for evidence

Last update at Wed, 01 Jul 2026 10:07:16 GMT based on commit d5bf2d3
ioBroker.repochecker 5.19.6

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions