Please consider fixing issues detected by repository checker

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 fiat for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.fiat

-

ERRORS:

❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
❗ [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
❗ [E145] Missing mandatory translation into de of some "common.news" in io-package.json.

WARNINGS:

SUGGESTIONS:

📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. 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.

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
@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, 11 Sep 2024 05:16:33 GMT

Please consider fixing issues detected by repository checker

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 fiat for common errors and appropiate suggestions to keep this adapter up to date.

Please see the result of the check below.

ioBroker.fiat

-

ERRORS:

❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommened
❗ [E162] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.

WARNINGS:

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. 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.

Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.

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

sessioninfo missing

Hallo

Bekomme diese Fehlermeldung bei meiner anmeldung.
App funktioniert aber adapter nicht.

Ist dies schon bekannt?

MFG
Patrick

Please consider fixing issues detected by repository checker

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 fiat for common errors and appropiate suggestions to keep this adapter up to date.

This check is based the current head revisions (master / main branch) of the adapter repository

Please see the result of the check below.

ioBroker.fiat

-

ERRORS:

❗ [E026] "{'engines': {'node'>='16'}}" is required at package.json, "{'engines':{'node'>='18'}}" is recommended
❗ [E145] Missing mandatory translation into de of some "common.news" in io-package.json.
❗ [E157] js-controller 3.0.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.

WARNINGS:

SUGGESTIONS:

📌 [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. 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.

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
@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 Sun, 22 Sep 2024 05:15:40 GMT based on commit 13faa91
ioBroker.repochecker 3.0.7

wrong value type

Hallo, ich erhalte die folgenden Protokolleinträge .
Kannst du dir das mal anschauen und den typ ändern ?

Vielen Dank

fiat.0	2022-11-14 22:53:42.499	info	State value to set for "fiat.0.ZAREAFDNxxxxx.status.vehicleInfo.tyrePressure04.pressure.value" has to be type "number" but received type "string"
fiat.0	2022-11-14 22:53:42.499	info	State value to set for "fiat.0.ZAREAFDNxxxxx.status.vehicleInfo.tyrePressure03.pressure.value" has to be type "number" but received type "string"
fiat.0	2022-11-14 22:53:42.499	info	State value to set for "fiat.0.ZAREAFDNxxxxx.status.vehicleInfo.tyrePressure02.pressure.value" has to be type "number" but received type "string"
fiat.0	2022-11-14 22:53:42.498	info	State value to set for "fiat.0.ZAREAFDNxxxxx.status.vehicleInfo.tyrePressure01.pressure.value" has to be type "number" but received type "string"
fiat.0	2022-11-14 22:53:42.448	info	State value to set for "fiat.0.ZAREAFDNxxxxx.location.latitude" has to be type "number" but received type "string"

Think about to fix the issues found by adapter checker

I am an automatic service that looks for possible errors in ioBroker and creates an issue for it. The link below leads directly to the test:

https://adapter-check.iobroker.in/?q=https://raw.githubusercontent.com/TA2k/ioBroker.fiat

[E605] No actual year found in copyright. Please add "Copyright (c) 2022 TA2k [email protected]" at the end of README.md
[E701] No actual year found in LICENSE. Please add "Copyright (c) 2022 TA2k [email protected]" at the start of LICENSE

Thanks,
your automatic adapter checker.

P.S.: There is a community in Github, which supports the maintenance and further development of adapters. There you will find many experienced developers who are always ready to assist anyone. New developers are always welcome there. For more informations visit: https://github.com/iobroker-community-adapters/info

Update stable version in repo from 0.0.6 to 0.0.7

Think about update stable version to 0.0.7

Version: stable=0.0.6 (139 days old) => latest=0.0.7 (15 days old)
Installs: stable=82 (82.83%), latest=8 (8.08%), total=99
Click to edit

Support refreshing status?

I've noticed the code contains a commented out DEEPREFRESH command. Is it possible to request a status refresh from the vehicle, i.e. update the vehicle's soc value?

Update stable version in repo from 0.0.8 to 0.0.9

Think about update stable version to 0.0.9

Version: stable=0.0.8 (269 days old) => latest=0.0.9 (15 days old)
Installs: stable=225 (76.79%), latest=38 (12.97%), total=293

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!

Update stable version in repo from 0.0.8 to 0.0.10

Think about update stable version to 0.0.10

Version: stable=0.0.8 (509 days old) => latest=0.0.10 (15 days old)
Installs: stable=234 (67.83%), latest=31 (8.99%), total=345

Click to use developer portal
Click to edit

Do not close this issue manually as a new issue will be created if condition for update still exists.

Please drop a comment if any reason exists which blocks updating to version 0.0.10 at this time.

Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

Compatibility check and testing for node.js 22

Notification from ioBroker Check and Service Bot

Dear Adapter developer,

Node.js 22 will become the official node.js LTS release October 2024 - see node-releases

So please check your adapter with Node.js 22.

Please add node.js 22 to the adapter testing matrix which is executed on commits. This check is normally controlled by workflow located at .github/workflows/test-and-release.yml. The recommended testmatrix is [18.x, 20.x, 22.x] now. It's ok to test node.js 20.x and 22.x only if there are any technical reasons (i.e. requirements caused by dependencies) to do so.

In any case please set the 'engines' clause in package.json according to the minimum node version used at testing. Please also do this if the adapter is not able to work with certain Node.js versions, so that ioBroker can prevent users from installing the adapter if not compatible. If you detect any incompatibility with node.js 22 please try to fix it and / or let us know if the problem seems to be located at core components.

Please close the issue after you checked it.

Feel free to contact me (@ioBroker-Bot) if you have any questions.

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

Note: If you added node 22 tests already, simply close this issue.

Compatibility check to js-controller 4.0

Dear Adapter developer,

with js-controller 4.0 object definitions are now also checked that min/max in only provided for number/mixed objects and that the type of the default value matches to the object type.

If something is not correct this is logged as 'warning' or 'info' log.

Please also make sure to update to the lastest @iobroker/testing dependency 2.5.4 or to accept the PR from Apollon77 for legacy testing!

Please spent some time to verify your adapter by ideally starting with a fresh instance and do some actions and verify the log. If you see a warn or info log there from these checks please adjust the adapter and fix the relevant cases.

For questions please refer to ioBroker/ioBroker.js-controller#1749

Please close the issue after you checked it.

Thank you very much for your support to get the best experience for the growing numbers of ioBroker users!

Jeep Uconnect Portal

Hello, would it be possible to add a Jeep version? It uses same Uconnect stuff just via the uconnect Jeep portal.

Would be great if i can modify the code to login to the jeep portal :-)

With kind Regads
Michael

Error Messages on every fetch in Log when Location Tracking disabled in Car

Describe the bug
In my Car (Fiat 500e) i disabled the location tracking. On every fetch i have some error messages in the ioBroker log.

Expected behavior
Do not fill the location objects and no error messages in the log

Screenshots & Logfiles

It´s on every fetch this same set of error messages

Versions:

Adapter version: 0.0.8
JS-Controller version: 4.0.24
Node version: 18.15.0
Operating system: Docker / Linux

ta2k / iobroker.fiat Goto Github PK

iobroker.fiat's Issues

Notification from ioBroker Check and Service Bot

This check is based the current head revisions (master / main branch) of the adapter repository

Notification from ioBroker Check and Service Bot

Notification from ioBroker Check and Service Bot

This check is based the current head revisions (master / main branch) of the adapter repository

Think about update stable version to 0.0.7

Think about update stable version to 0.0.9

Think about update stable version to 0.0.10

Notification from ioBroker Check and Service Bot

Recommend Projects

Recommend Topics

Recommend Org