Alte Objekte von alten AGS werden nicht vollständig gelöscht

Ich habe heute mit ein paar Städten gespielt (verschiedene AGS) und wie es aussieht werden die letzten Objekte nicht komplett von den AGS gelöscht, wenn die Werte nicht mehr in der Instanz eingetragen sind.

Nina Version: 0.0.23

Update stable version in repo from 0.0.15 to 0.0.22

Think about update stable version to 0.0.22

Version: stable=0.0.15 (85 days old) => latest=0.0.22 (15 days old)
Installs: stable=975 (55.46%), latest=382 (21.73%), total=1758
Click to edit

Wunschdatenpunkt Sender/Melder

Hallo und guten Morgen,

erst einmal ein großes Kompliment an den/die entwikler dieses Adapters, wirklich großartige Arbeit und sher einfach zu verarbeiten (sinnvolle Objekte).

Ich würde gerne einen Wunsch zu einem Datenpunkt äußern:
Bisher gibt es den Datenpunkt "sender" bzw. "senderName", welcher an sich schon sehr gut ist. Leider wird hier zum Teil eine Zusammenstellung von Abkürzungen eingetragen (z.B. DE-NW-D-SE020). Ich verstehe was dieser ausdrückt, eine verarbeitung in einer Sprachangabe ist allerdings nicht möglich. In der gleichen Warnung steht unter "parameter03" der ausgeschriebene Name des Senders (Lagezentrum der Landesregierung NRW), was sich super in eine Ansage einbinden lässt.

Leider ist hier das Problem, dass bei anderen Sendern/Warnungen unter "parameter03" ganz andere Sachen drinstehen könnten (z.B. Windrichtung). Somit kann dieser auch nicht in die Ansage einfließen.

Konkret möchte ich in einer Sprachansage durch Alexa bei Warungen in 4 unterschiedlichen Städten (Wir, Eltern, usw.) auch eine Information einbinden, wo weitere Informationen zu finden sind (da ich sonst nur die Headline ansagen lasse).

Könnte hier jemand der Ahnung von dem Ganzen hat evtl. einen neuen Datenpunkt einrichten bzw. den/die Vorhandenen anpassen?

Gruß
Jan

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.nina

[E154] common.dependencies must contain {"js-controller": ">=2.0.0"} or {"js-controller": ">=3.0.0"}
[E605] No actual year found in copyright. Please add "Copyright (c) 2019-2022 tomboxi [email protected]" at the end of README.md
[E701] No actual year found in LICENSE. Please add "Copyright (c) 2019-2022 tomboxi [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

State activeWarn enthält Warnungen vom DWD obwohl deaktiviert

Describe the bug
In den Einstellungen ist Ignoriere Deutscher Wetterdienst/Unwetter Meldungen aktiviert, sodass keine Meldungen vom DWD angezeigt werden. Der State nina.0.XXXXX.activeWarn zählt DWD-Warnungen dennoch mit.
Just in diesem Moment besteht eine Unwetter-Warnung, sonst keine. Die Warnung selbst wird nicht angezeigt, activeWarn steht jedoch auf 1.

Expected behavior
Meiner Ansicht nach dürften DWD-Warnungen nicht mitgezählt werden, wenn diese Art der Meldung deaktiviert ist.

Additional context
Eventuell könnte das auch auf Hochwassermeldungen zutreffen, das habe ich jedoch nicht geprüft.

Zu viele Warnungen - Nur 5 Zeichen AGS ausgewertet

Ich nutze Version 0.0.25 und habe AGS 07338018 über den Link gesucht, gefunden und in der Instanz eingetragen.

Bei den Objekten gibt es aber nicht nina.0.07338018 sondern nina.0.07338 und auch im Log steht Found AGS for: Rhein-Pfalz-Kreis was der 07338 entspricht.

Für 07338018 gibt es keine Warnungen, ich sehe aber Warnungen für 07338015.
Das scheint mir nicht richtig zu sein, kann man das irgendwie unterbinden?

Please check ioBroker.nina with js-controller 2.0

Hi,

the new js-controller 2.0 will come into latest repository in the next days and we want to make sure that all adapters are working well. We already did a 2 weeks Beta test and so some adapter were aleady checked and some needed slight adjustments.

You can find more information in ioBroker/ioBroker.js-controller#482 and in the ioBroker Forum. If you have more technical questions please write in the referenced issue or in the Developer thread please. General questions are best in the genral thread.

Please update your systems to js-controller 2.0 and check your adapter.

Please close this issue once you have checked your adapter or received successfull reports from users.

Thank you very much for your support. Please contact us in the other Threads or Forum on any question.

Logo aktualisieren (hat weißen Hintergrund)

Sollte ein transparentes PNG sein

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.nina

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

I have also found warnings that may be fixed if possible.

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

Fehlermeldung

Ich bekomme leider egal in welcher Version diese Fehlermeldung

nina.0	2019-07-27 15:56:04.963	error	{}
nina.0	2019-07-27 15:56:04.961	error	{"errno":"EPROTO","code":"EPROTO","syscall":"write"}

Fehler im Log

Moin, ich habe in letzter Zeit in dem Log vom dem ioBroker immer mehrere Fehlermeldungen von dem Nina-Adapter. Jedoch werden die Warnungen noch korrekt angezeigt. Liegt der Fehler bei mir oder ist das ein allgemeiner Fehler vom Adapter?

nina.0 | 2022-09-18 11:40:19.626 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:40:19.582 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:38:19.642 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:36:19.635 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:34:20.724 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:34:19.627 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:30:19.600 | error | Request error{"errno":-104,"code":"ECONNRESET","syscall":"read"} nina.0 | 2022-09-18 11:28:20.731 | error | Request error{"code":"ECONNRESET"}

Danke schon mal im Voraus😊

Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token in JSON at position 0

Seit ein paar Tagen, tritt bei jedem (nicht nur vereinzelt) Aufruf diese Warnmeldung auf.


nina.0 | 2019-10-02 10:32:24.871 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:32:24.871 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:32:24.870 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:32:24.869 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:27:24.850 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:27:24.850 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:27:24.848 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:27:24.846 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:22:24.841 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:22:24.840 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:22:24.839 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:22:24.838 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:12:24.819 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:07:24.813 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:02:24.777 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:02:24.775 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 10:02:24.774 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:57:24.853 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:57:24.853 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:57:24.852 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:57:24.851 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:52:24.756 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:52:24.754 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:47:24.777 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:47:24.776 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:47:24.775 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:47:24.774 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:42:24.736 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:42:24.735 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:42:24.734 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:42:24.733 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:37:24.726 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:37:24.725 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:37:24.724 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:37:24.722 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:32:24.762 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:32:24.761 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:32:24.761 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:32:24.760 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:27:24.706 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:27:24.705 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:27:24.704 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:27:24.702 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:22:24.728 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:17:24.732 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:17:24.732 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:17:24.730 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:17:24.729 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:12:24.707 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:12:24.704 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:12:24.703 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:12:24.702 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:07:24.663 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:07:24.663 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:07:24.662 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:07:24.660 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:02:24.728 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:02:24.727 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 09:02:24.679 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 08:57:24.645 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}
nina.0 | 2019-10-02 08:57:24.644 | warn | Website sends unparsable data, you can ignore if it happens only once: SyntaxError: Unexpected token � in JSON at position 0 {}

Startet nicht auf dem Raspi 4 / Debian Buster

In Kombination mit einem Raspi 4 und Buster scheint es ein Problem zu geben.

Der Log gibt folgendes aus:
nina.0 error SyntaxError: Unexpected token u in JSON at position 0 {}
nina.0 error Request error{"errno":"EPROTO","code":"EPROTO","syscall":"write"}

edit: Found this discussion so i'll close this
https://forum.iobroker.net/topic/23866/aufruf-nina-gefahrenmeldung-adapter/61?lang=en-GB&page=4

Objekt-Browser klappt bei Update auf

Hallo!
Immer wenn sich der Nina-Adapter aktualisiert wird der komplette "Ast" der Instanz (inkl. aller "Zweige") im Objekt-Browser aufgeklappt und ioBroker verschiebt auch den Fokus.
Ist etwas ärgerlich wenn man gerade an einem anderen Objekt arbeitet.

Könnte es ein Bug des Adapters sein oder ist der Fehler evtl. bei ioBroker zu suchen?

Nina-Adapter: v0.0.23
Node.js version 12.18.4
NPM version 6.14.6

Absturz bei Verbindungsfehler

Bei fehlender Verbindung stürzt der Adapeter ab.

nina.0	2020-03-07 08:58:12.947	info	(3565) Terminated (NO_ERROR): Without reason
nina.0	2020-03-07 08:58:12.946	info	(3565) terminating
nina.0	2020-03-07 08:58:12.939	error	at process._tickCallback (internal/process/next_tick.js:63:19)
nina.0	2020-03-07 08:58:12.939	error	at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
nina.0	2020-03-07 08:58:12.939	error	at emitErrorNT (internal/streams/destroy.js:91:8)
nina.0	2020-03-07 08:58:12.939	error	at TLSSocket.emit (events.js:198:13)
nina.0	2020-03-07 08:58:12.939	error	at TLSSocket.socketErrorListener (_http_client.js:401:9)
nina.0	2020-03-07 08:58:12.939	error	at ClientRequest.emit (events.js:198:13)
nina.0	2020-03-07 08:58:12.939	error	at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:881:8)
nina.0	2020-03-07 08:58:12.939	error	at Request.emit (events.js:198:13)
nina.0	2020-03-07 08:58:12.939	error	at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
nina.0	2020-03-07 08:58:12.939	error	at Request.request.get [as _callback] (/opt/iobroker/node_modules/iobroker.nina/main.js:181:38)
nina.0	2020-03-07 08:58:12.939	error	(3565) TypeError: Cannot read property 'indexOf' of undefined
nina.0	2020-03-07 08:58:12.938	error	(3565) uncaught exception: Cannot read property 'indexOf' of undefined
nina.0	2020-03-07 08:58:12.937	error	(3565) Request error{"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"94.125.29.174","port":443}
nina.0	2020-03-07 08:58:12.934	error	at process._tickCallback (internal/process/next_tick.js:63:19)
nina.0	2020-03-07 08:58:12.934	error	at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
nina.0	2020-03-07 08:58:12.934	error	at emitErrorNT (internal/streams/destroy.js:91:8)
nina.0	2020-03-07 08:58:12.934	error	at TLSSocket.emit (events.js:198:13)
nina.0	2020-03-07 08:58:12.934	error	at TLSSocket.socketErrorListener (_http_client.js:401:9)
nina.0	2020-03-07 08:58:12.934	error	at ClientRequest.emit (events.js:198:13)
nina.0	2020-03-07 08:58:12.934	error	at Request.onRequestError (/opt/iobroker/node_modules/request/request.js:881:8)
nina.0	2020-03-07 08:58:12.934	error	at Request.emit (events.js:198:13)
nina.0	2020-03-07 08:58:12.934	error	at self.callback (/opt/iobroker/node_modules/request/request.js:185:22)
nina.0	2020-03-07 08:58:12.934	error	at Request.request.get [as _callback] (/opt/iobroker/node_modules/iobroker.nina/main.js:181:38)
nina.0	2020-03-07 08:58:12.934	error	(3565) TypeError: Cannot read property 'indexOf' of undefined
nina.0	2020-03-07 08:58:12.933	error	(3565) uncaught exception: Cannot read property 'indexOf' of undefined
nina.0	2020-03-07 08:58:12.925	error	(3565) Request error{"errno":"ETIMEDOUT","code":"ETIMEDOUT","syscall":"connect","address":"94.125.29.174","port":443}

Update stable version in repo from 0.0.25 to 0.0.26

Think about update stable version to 0.0.26

Version: stable=0.0.25 (906 days old) => latest=0.0.26 (15 days old)
Installs: stable=2969 (84.71%), latest=290 (8.27%), total=3505

Click to use developer portal
Click to edit

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

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.nina

[E815] file tsconfig.json found in repository, but not found in .npmignore

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

Verify Compact mode for your adapter

We have detected that your adapter supports the compact mode. Please use the latest js-controller 2.0 and verify that everything works.

Some more information what is important to check can be found at ioBroker/ioBroker.js-controller#512

On questions please answer to the linked issue. Please close this issue after your test and add the version number that you have tested please as a comment.

Thank you for your support.

Please add your adapter to ioBroker.discovery

I am an automatic service from ioBroker that searches adapters and makes suggestions.

I noticed that your adapter is not integrated in the ioBroker.discovery. Using the Discovery adapter, ioBroker can automatically find devices or suggest services to the user for installation. If possible I would live to see your adapter added there.

Some adapters have already been added and you can use them as blueprints. See: https://github.com/ioBroker/ioBroker.discovery You need to fork this project and then create a PR for your adapter to be added.

Basically the plugins can do HTTP calls, UDP discovery, MDNS, UPNP and will iterate over all devices found by IP scan and check local serial ports. If you want you can also add new discovery methods but please try to do that with at least dependencies as possible.

Then create one file under lib/adapters for your adapter to implement the detection and proposal of an instance to the user.

On questions, the other developers will support in the forum or via GitHub issues too.

If no detection is possible, simply close this issue and I won't bother you again. ;-)

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

Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,

Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.

Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16

Please add both versions to the adapter testing which is executed on commits.

If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!

On questions please talk to us at ioBroker/ioBroker.js-controller#1138

Please close the issue after you checked it.

Thank you very much for your support!

link to AGS + AGS input

I just installed the NiNA-adaptor to my IObroker.

issue:
the link to the website providing the AGS handle is very hidden in the text. (in former times links were underlined or have an icon...)
issue
first I wanted to add two cities by their AGS code, but I decided to delete the second code but I didn't delete the comma after the first code. So I got plenty of entries in the error log like these:
nina.0 2022-05-01 10:06:51.609 error Error: DB closed
till IOB said "too many errors" and stopped the adaptor followed by this error log
host.raspberrypi 2022-05-01 10:06:51.657 error instance system.adapter.nina.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

after deleting the comma everything went wonderful.

(4465) Cannot reach https://warnung.bund.de/bbk.status/status_

nina.0	2021-01-03 02:31:00.668	warn	(4465) Cannot reach https://warnung.bund.de/bbk.status/status_033510180000.json Server. Statuscode: 404

Die AGS habe ich mir hier her geholt: hoffe das ist richtig, weil es über den Link nicht ging.
https://www.riserid.eu/glossarbegriffe/source/default/term/amtlicher-gemeindeschluessel-ags/

State value has wrong type (js-controller 3.3.x)

js-controller: 3.3.4
Admin 5.0.11
Nina Adapter:

Using new js-controller 3.3.4 will throw the following warnings:


nina.0 | 2021-05-01 12:21:29.450 | warn | (2310) State value to set for "nina.0.03252.identifierList" has wrong type "object" but has to be "string"
nina.0 | 2021-05-01 12:21:29.449 | warn | (2310) State value to set for "nina.0.03241.identifierList" has wrong type "object" but has to be "string"

Just for tracking see ioBroker/ioBroker.js-controller#1299

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.nina

[E201] Bluefox was not found in the collaborators on NPM!. Please execute in adapter directory: "npm owner add bluefox iobroker.nina"

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

Link zu AGS-Suche tauschen / erweitern

Mit dem aktuellen JSON kann bestimmt kaum jemand etwas anfangen. Daher entweder eine Suche implementieren oder hierher verlinken: https://www.statistikportal.de/de/gemeindeverzeichnis

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!

Review comments ...

Please remove .vscode from GitHub
using getStates (which gets state values) might not return all objects ... so maybe better use getObjects? https://github.com/TA2k/ioBroker.nina/blob/master/main.js#L40
will https://github.com/TA2k/ioBroker.nina/blob/master/main.js#L42 do something at all? you use the states-object keys and iterate and delObject if the key is not in object states ?! Or do I miss something here?
you might want to add error handling here for statuscode 200 and such :-) https://github.com/TA2k/ioBroker.nina/blob/master/main.js#L67
setInterval ... personally don't like :-)) But you know why ... https://github.com/TA2k/ioBroker.nina/blob/master/main.js#L114
please do not implement state7object change if not used

Thank you!

no existing object

under js-controller 3.2.12

Cannot parse JSON: undefined

Ich bekomme mehrmals am Tag folgenden Fehler im Log:

(2109) Cannot parse JSON: undefined

Habe den rawJSON State aktiviert.
Der Fehler wird immer so 10-30 Mal nacheinander in den Log geschrieben innerhalb 1-2 Sekunden. Mehrfach am Tag.

Es läuft soweit aber alles ohne Probleme. (Es wäre nur cool wenn sich die Objekte nicht immer aufklappen würden wenn der Adapter für neue Warnungen checkt, aber daran gewöhnt man sich:D)

Adapter: 0.0.23
Node.js: v12.14.1
js-controller: 3.0.20

Problem mit RegEx bei AGS Nummern

Wenn eine AGS Nummer auf 0 endet wird diese durch die RegEx Prüfung mit entfernt und Einträge aus den JSON Daten daher nichtmehr erkannt. Eine schnelle Lösung ist die AGS Nummer ohne die 0 am Ende im Adapter zu nutzen, es sollte allerdings vom Script auch erkannt werden z.B. durch eine Prüfung der Länge der AGS. Ein Beispiel wäre die 05570 in den angehängten JSON Daten.

gefahrendurchsagen.zip

fullText ohne instruction => NaNundefined

nina.0.03460.warnung01.info01.fullText (Voller Text headline + description + instruction) enthält folgenden Text:
"Rauch- und Geruchsbelästigung im Bereich Goldenstedt NaNundefined"

Vermutlich kommt das daher, dass diese Meldung ohne Handlungsempfehlung ausgegeben wurde.
https://warnung.bund.de/meldung/biw.BIWAPP-72820/Rauch-_und_Geruchsbelästigung_im_Bereich_Goldenstedt

Please add link to main page of NINA service in README

Erros in Log & Verbunden mit nina = falsch

After installation and configuration of the adapter, there are erros in the log file and the status of "Verbunden mit nina" is wrong.

2019-10-13 12:58:50.808 - error: nina.0 (9843) Request
error{"errno":"EPROTO","code":"EPROTO","syscall":"write"}
2019-10-13 12:58:50.810 - error: nina.0 (9843) SyntaxError: Unexpected
token u in JSON at position 0 {}
2019-10-13 12:58:50.814 - error: nina.0 (9843) Request
error{"errno":"EPROTO","code":"EPROTO","syscall":"write"}
2019-10-13 12:58:50.815 - error: nina.0 (9843) SyntaxError: Unexpected
token u in JSON at position 0 {}
2019-10-13 12:58:50.817 - error: nina.0 (9843) Request
error{"errno":"EPROTO","code":"EPROTO","syscall":"write"}
2019-10-13 12:58:50.818 - error: nina.0 (9843) SyntaxError: Unexpected
token u in JSON at position 0 {}
2019-10-13 12:58:50.831 - error: nina.0 (9843) Request
error{"errno":"EPROTO","code":"EPROTO","syscall":"write"}
2019-10-13 12:58:50.832 - error: nina.0 (9843) SyntaxError: Unexpected
token u in JSON at position 0 {}
2019-10-13 12:58:50.833 - error: nina.0 (9843) Request
error{"errno":"EPROTO","code":"EPROTO","syscall":"write"}
2019-10-13 12:58:50.834 - error: nina.0 (9843) SyntaxError: Unexpected
token u in JSON at position 0 {}

Compatibility check to js-controller 3.3 and Admin5 React UI

Dear Adapter developer,

with js-controller 3.2 and js-controller 3.3 some additional checks were added to make sure that created objects match to the specifications and also written state values match to the object definition.

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

Please take the 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 log there from these checks please adjust the adapter and fix the relevant cases.

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

Additionally we are preparing Admin 5 which will have a completely rewritten UI. Please install Admin 5, activate that new UI and verify that the configuration of you adapter works as expected also there.

More informations on Admin 5 can be found in Forum https://forum.iobroker.net/topic/44282/test-adapter-admin-5-0-x-alpha-der-neuen-ui

Please close the issue after you checked it.

Thank you very much for your support!

ta2k / iobroker.nina Goto Github PK

iobroker.nina's Issues

Think about update stable version to 0.0.22

Think about update stable version to 0.0.26

Recommend Projects

Recommend Topics

Recommend Org

Jobs