As you support vis-2 now, a restart vis-2 seems to be appropiate. Maybe the restart vis should be kept to ensure that vis(1) is restarted after upgradung this adapter to 2.x.x and hence to remove vis(1) widgets form vis(1).

    "restartAdapters": [
      "vis"0
    ],

In addition the visWidget section should be checked. According to README only vis-2 is supported, but the section tells that major version 2 is not supported (while this indiocates that version 1 is supported)

    "visWidgets": {
      "ignoreInVersions": [
        2
      ]
    },

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

Please see the result of the check below.

ioBroker.radar-trap

-

ERRORS:

• ❗ [E204] Versions "2.1.1, 2.1.0" listed at common.news at io-package.json do not exist at NPM. Please remove from news section.

WARNINGS:

• 👀 [E851] .npmignore found but "files" is used at package.json. Please remove .npmignore.
• 👀 [W040] "keywords" within package.json should contain "ioBroker"
• 👀 [W162] js-controller 5.0.17 listed as dependency but 5.0.19 is recommended. Please consider updating dependency at io-package.json.

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

Think about adding version 1.0.4 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=1.0.4 (41 days old)
Installs: stable=0 (0%), latest=3 (12.5%), total=24
Click to edit

Think about adding version 1.0.4 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=1.0.4 (39 days old)
Installs: stable=0 (0%), latest=3 (12.5%), total=24
Click to edit

Think about adding version 2.0.0 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=2.0.0 (30 days old)
Installs: stable=0 (0%), latest=23 (34.33%), total=67

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 2.0.0 at this time.

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

Describe the bug
If I enter my token from Mapbox, it loads the world. If I then click on the tab routs, it is infinitely loading.
Without any result, even changing to debug mode, the adapter not outputs any information.
Tested in a docker environment, once inside a Debian distro, and once inside an LXC.

To Reproduce
Steps to reproduce the behavior:

1. Install Adapter
2. Add default API Mapbox token
3. Click on routs "Routen"
4. See error

Expected behavior
Not sure how it should look, never used it before

Screenshots & Logfiles
No logging as said but I later append a screenshot

Versions:

• Adapter version: v2.2.0
• JS-Controller version: 5.0.19
• Node version: v18.20.3
• Operating system: docker (official image - v9.1.2)

Additional context
There had been no objects created at all in the object structure seems to me ought.

Think about adding version 1.0.7 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=1.0.7 (30 days old)
Installs: stable=0 (0%), latest=13 (34.21%), total=38

Click to use developer portal
Click to edit

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

Why do I need vis to install this adapter? i dont have vis, but i want to use the features of your adapter. ;-)

Current io-package.json is no valid json file. Please fix ASAP as the broke file blocks checks for central repositories and might cause the repobuild job to fail.

Besides your last commit reverted several changes to io-packeg.json (license, installedFrom rreappered) etc. Please fix / revert.

Please note that I might need to remove the adpter from repositories if io-package.json is not fixed as soon as possible.

Thanks

From which source are the radars?

I couldn't find it in the code

Thank you!

Im Log kommt folgender Eintrag:
radar-trap.0 | 2024-07-27 08:00:20.491 | info | Method "createState" is deprecated and will be removed in js-controller 7, use "extendObject/setObjectNotExists" instead

Adapter Version 2.2.1
js-controller 6.0.9
node-js 20.15.1

Bitte mal prüfen :)

Think about adding version 1.3.1 to stable repository.

Version: stable=0.0.0 (0 days old) => latest=1.3.1 (30 days old)
Installs: stable=0 (0%), latest=26 (38.81%), total=67

Click to use developer portal
Click to edit

Note: This is an automatically generated message and not personally authored by bluefox!
Do not close this issue manually as a new issue will be created if condition for update still exists
@mcm1957 for evidence