Hi,

I don't know if it's a bug or if the service just don't provide wrong weather data: Rain is always 0 mm. I live near Hamburg, Germany. Maybe you could have a look at it? Very much appreciated. Thank you.

M.

Hi, it looks like you are using @alcalzone/release-script to manage your releases.
When updating to the latest version, you need to remove the following line from your .github/workflows/test-and-release.yml if you want the releases to keep working:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/master' &&
      startsWith(github.ref, 'refs/tags/v')

It may also look like this one:

  deploy:
    # Trigger this step only when a commit on master is tagged with a version number
    if: |
      contains(github.event.head_commit.message, '[skip ci]') == false &&
      github.event_name == 'push' &&
-     github.event.base_ref == 'refs/heads/main' &&
      startsWith(github.ref, 'refs/tags/v')

yr.0.forecast.day0.humidity bleibt leer (und Fehler SQL: Object?).

yr.0.forecast.day0.precipitation_chance hat als Wer null.

Hallo Meldung:

host.Medion | 2018-08-10 12:10:07.017 | info | instance system.adapter.yr.0 terminated with code 0 (OK)
yr.0 | 2018-08-10 12:10:01.987 | warn | Translate: "East-southeast": {"en": "East-southeast", "de": "East-southeast", "ru": "East-southeast"}, please send to developer

Sigi

Der Adapter spuckt regelmässig Fehlermeldungen raus:

Nur als Info:
In Norwegen sind Anfang des Jahres viele Kommunen geändert/zusammengeschlossen worden.
Ich denke, yr.no ist deshalb in einer größeren Anpassungphase. Auch die Android-App ist davon betroffen. Einen Hinweis findet man auch innerhalb der App.

Ich wohne in Norwegen und habe dies deshalb mitbekommen.
Dieser Eintrag ist für andere Anwender gedacht, die auch Probleme mit dem Adapter haben.

Describe the bug
IoBroker exceeds api.met.no traffic limits as stated in Terms of Service

Additional context
I am the sysadmin of the MET Norway Weather API. Our Terms of Service states that traffic to api.met.no must not exceed 20 requests per second. At times, ioBroker generates over 1000, generating huge spikes in our traffic:

    2 Mar  1 01:05:55
    2 Mar  1 01:05:57
    2 Mar  1 01:05:59
  177 Mar  1 01:06:00
  523 Mar  1 01:06:01
 1045 Mar  1 01:06:02
  698 Mar  1 01:06:03
  262 Mar  1 01:06:04
  112 Mar  1 01:06:05
  141 Mar  1 01:06:06
   74 Mar  1 01:06:07
   45 Mar  1 01:06:08
   22 Mar  1 01:06:09
   21 Mar  1 01:06:10
   20 Mar  1 01:06:11
   16 Mar  1 01:06:12
   14 Mar  1 01:06:13
    9 Mar  1 01:06:14
    5 Mar  1 01:06:15
    4 Mar  1 01:06:16
    2 Mar  1 01:06:17
    4 Mar  1 01:06:18
    1 Mar  1 01:06:19
    3 Mar  1 01:06:21
    1 Mar  1 01:06:22
    3 Mar  1 01:06:23
    2 Mar  1 01:06:24

As is clearly evident from the statisticks, there appears to be some periodic jobs starting at 6 min over every hour generating massive burst of traffic:

1049 Mar  1 02:06:02
1045 Mar  1 01:06:02
 999 Mar  1 03:06:02
 979 Mar  1 04:06:02
 963 Mar  1 05:06:02
 958 Mar  1 00:06:02
 914 Mar  1 07:06:02
 906 Mar  1 08:06:02
 881 Mar  1 06:06:02
 870 Mar  1 11:06:03
 841 Mar  1 11:06:02
 838 Mar  1 10:06:02
 831 Mar  1 10:06:03
 795 Mar  1 08:06:03
 766 Mar  1 03:06:03
 754 Mar  1 07:06:03
 748 Mar  1 00:06:03
 742 Mar  1 05:06:03
 735 Mar  1 06:06:03
 720 Mar  1 09:06:02
 712 Mar  1 04:06:03
 698 Mar  1 01:06:03
 679 Mar  1 02:06:03
 662 Mar  1 09:06:03
 554 Mar  1 09:06:04
 528 Mar  1 05:06:01
 523 Mar  1 01:06:01
 520 Mar  1 08:06:01
 519 Mar  1 02:06:01
 515 Mar  1 04:06:01
 510 Mar  1 07:06:01
 508 Mar  1 00:06:01
 497 Mar  1 06:06:01
 487 Mar  1 03:06:01
 451 Mar  1 10:06:01
 436 Mar  1 06:06:04
 429 Mar  1 11:06:04
 425 Mar  1 09:06:01
 406 Mar  1 11:06:01
 377 Mar  1 10:06:04
 355 Mar  1 07:06:04
 347 Mar  1 04:06:04
 325 Mar  1 05:06:04
 322 Mar  1 03:06:04
 308 Mar  1 02:06:04
 308 Mar  1 00:06:04
 296 Mar  1 08:06:04
 283 Mar  1 09:06:05
 262 Mar  1 01:06:04
 199 Mar  1 11:06:05

In total, your traffic averages around 7500 requests per hour, which is fine. The problem is that a lot of it appears simultaneously, potentially affecting other users. As is stated in the TOS:

Don't schedule many requests at the same time, e.g. every hour on the dot or when the forecast model runs are finished. Add a random number of minutes to the time of the requests as our data are continously updated. Spread your traffic evenly out over time so it makes a flat curve, not a sawtooth.

Furthermore, half of the traffic is going to the /weatherapi/weathericon/2.0/legends endpoint, which is totally unnecessary. This is a static file that will never be changed unless the icons change. You should download this and bundle it with your application. We will soon remove this endpoint and pack the file inside the icons archive instead.

Finally, note that the TOS explicitly prohibits the use of the Yr trademark and logo in third party applications:

You are not allowed to make services/sites that appear to be made by Yr, NRK or The Norwegian Meteorological Institute. In other words, you may not use the word "Yr" as a part of your service name, or attach the Yr logo to your service.

To continue using the service, we require you to implement the following measures:

1. Distribute your traffic evenly over time, instead of periodic spikes
2. Instead of contacting api.met.no, we will generate a custom subdomain which you must use for all traffic
3. Remove the requests to /weatherapi/weathericon/2.0/legends
4. Stop using the Yr logo and trademark in the application. ioBroker/metno would be fine

Hello,

I can't set up YYYY/MM/DD in iobroker main setup so it shows invalid date for the days.

Hallo,

ich kann leider das datum so nicht in ioBroker einstellen. Daher kann er das datum nicht richtig ziehen bzw darstellen.

gibt es dafür eine Lösung!

[{"date":"11/04/2021","icon":"/adapter/yr/icons/03n.svg","state":"Teils wolkig","temperatureMin":3,"temperatureMax":3,"precipitation":0,"windDirection":"NW","windSpeed":10.4,"pressure":1020,"temperatureActual":3},{"date":"12/04/2021","icon":"/adapter/yr/icons/02d.svg","state":"Schönwetter","temperatureMin":-1,"temperatureMax":6,"precipitation":1,"windDirection":"WSW","windSpeed":11.2,"pressure":1025},{"date":"13/04/2021","icon":"/adapter/yr/icons/01n.svg","state":"Klarer Himmel","temperatureMin":-2,"temperatureMax":8,"precipitation":0,"windDirection":"WNW","windSpeed":8.3,"pressure":1032}]

Sentry Issue: IOBROKER-YR-K

Error: DB closed
  ?, in runMicrotasks
...
(1 additional frame(s) were not displayed)

Edit: Habe den Adapter und Instanz komplett gelöscht, und bekomme ihn jetzt gar nicht mehr zum laufen (weder in alter noch in neuer Version)

Seit dem letzten Update (latest) bekomme ich beim Start hunderte Zeilen, wo das Objekt nicht korrekt gepflegt ist.

Ich weiß, dass ich es ausblenden kann - aber sollten diese Fehler noch da sein, oder liegt es an meinem System?

Der Adapter wird dann auch gestoppt, oder der JS Controller, ich weiß nicht wie ich die Meldung interpretieren soll:

`

Hallo kann es sein das die Icon für die Wetterdarstellung nicht richtig abgedated werden?
Wenn ich auf yr.no schaue sind da andere angegeben. Irgendwie stimmt die Uhrzeitauswertung wohl nicht.

Zur Zeit sollte eigentlich von 12-18 Uhr gelten, Sonnenschein mit Wolken.
angezeigt oder im Icon Object angegeben wird 18-24 Uhr, bewölkt und nacht.

Ich denke da ist etwas verrutscht.

Dear Adapter develop,

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!

Hey,
ich habe hier seid gestern "instance system.adapter.yr.0 terminated with code 1 (JS_CONTROLLER_STOPPED)" und ich bekomme es einfach nicht gelöst.
IoB läuft auf einer Proxmox CT alle Adapter sind auf dem neuesten Stand.

iobroker debug yr
Debugger listening on ws://127.0.0.1:9229/39d84cde-292e-42b6-9700-c33a0851613f
For help, see: https://nodejs.org/en/docs/inspector
internal/modules/cjs/loader.js:1102
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^

Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /opt/iobroker/node_modules/got/dist/source/index.js
require() of ES modules is not supported.
require() of /opt/iobroker/node_modules/got/dist/source/index.js from /opt/iobroker/node_modules/iobroker.yr/main.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /opt/iobroker/node_modules/got/package.json.

at new NodeError (internal/errors.js:322:7)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1102:13)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:93:18)
at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.yr/main.js:4:13)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32) {

code: 'ERR_REQUIRE_ESM'

• Adapter version: 5.0.0
• Node version: 14.18.3

Think about update stable version to 5.0.0

Version: stable=3.0.5 (120 days old) => latest=5.0.0 (15 days old)
Installs: stable=1702 (58.19%), latest=351 (12%), total=2925
Click to edit

Seit Version 2.01 werden bei mir die beiden Fehler

temperature_max und temperature_min unter day2 in den Objekten nicht mehr aktualisiert.

For Admin3 some changes are needed: see http://forum.iobroker.net/viewtopic.php?f=24&t=10268

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!

Wie im Issue bereits angesprochen,

hat der Adapter in früheren Versionen unter dem Objektordner Forecast Tageszusammenfassungen angegeben (Day0, Day1, Day2...) Jetzt gibt er den Forecast in Stunden ab Stunde 0h (jetzt) an.

Das ist zwar auch schön, aber so eine Tageszusammenfassung in Form eines "Day" Objektes, ist für die generelle Übersicht auch sinnvoll. Kann man die alte Funktion mit dem Tagesforcast zu dem Stundenforecast hinzufügen?

Abgesehen davon: Vorher gab es ein Objekt, welches den Link zum aktuellen Meteogram für den Ort wiedergegeben hat, dieses Objekt fehlt nun ebenfalls. Ich habe den Link für mich gespeichert und da er auf die yr.no Homepage verweist ist es kein Problem, aber für neue User fehlt diese Info / Möglichkeit.

Info:

Please reinstall the adapter!
Error while loading Legend data: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.yr/legend.json'

Any workaround?

Getting the following error:

2020-07-03 10:30:07.378 - warn: yr.0 (18607) Translate: "NB! Read the comments in the apiChanges section in the XML": {"en": "NB! Read the comments in the apiChanges section in the XML", "de": "NB! Read the comments in the apiChanges section in the XML", "ru": "NB! Read the comments in the apiChanges section in the XML"}, please send to developer

System data:

Platform: linux
Distribution: Ubuntu
Architecture: x64
Model: Common KVM processor
RAM: 3.85 GB
Node.js: v10.21.0
NPM: 6.14.4
JS-Controller (1): 3.1.6
Admin: 4.1.1
Model: ARMv7 Processor rev 4 (v7l)
RAM: 926.05 MB
Node.js: v10.21.0
NPM: 6.14.4
yr.no: 2.0.3

created by ioBroker.info

My fault - I will create a pull request ASAP.

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.

schalte ich die Compact Sicht ein in Einstellungen bekomme ich trotzdem alle Daten also auch die 24h

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.

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/ioBroker/ioBroker.yr

• [E802] No topics found in the repository. Please go to "https://github.com/ioBroker/ioBroker.yr", press the settings button beside the about title and add some topics.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2022 hobbyquaker [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2014-2022 hobbyquaker [email protected]" at the start of LICENSE

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected
• [W801] .npmignore not found

Thanks,
your automatic 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/ioBroker/ioBroker.yr

• [E802] No topics found in the repository. Please go to "https://github.com/ioBroker/ioBroker.yr", press the settings button beside the about title and add some topics.
• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2022 hobbyquaker [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2014-2022 hobbyquaker [email protected]" at the start of LICENSE

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

• [W505] setTimeout found in "main.js", but no clearTimeout detected
• [W801] .npmignore not found

Thanks,
your automatic adapter checker.

Seit Version 2.01 bekomme ich im Log täglich folgenden Fehler als "Info" eingestellt.

Der State yr.0.forecastHourly.*.time wird als Type "string" angelegt, enthält aber einen Unix-Timestamp in Millisekunden.
Durch den Typ "string" kann die Zeit in VIS mit dem Widget TimeStampValue nicht angezeigt werden.
Daher als Statetyp bitte in "value" umsetzen

Versions:

• Adapter version: 3.0.5

Danke, Ralf

The date fild from all 3 days is empty. error invalid date

Siehe Screenshot

in diesem Beispiel sind es diese:
http://symbol.yr.no/grafikk/sym/b38/40n.png
http://symbol.yr.no/grafikk/sym/b38/02n.png

Ich denke es liegt an der Webseite. Derzeit werden auf der Webseite andere Symbole angezeigt mit dieser URL:
http://symbol.yr.no/grafikk/sym/v2016/png/38/ 40n.png

Vielleicht genügt es die Base URL in der yr.js anzupassen.

in the german translation of "Partly cloudy" is a english "cloudy" left...

The following message I get after the Update.
Do I have to do anything about the new JSON-API to make it work?

`

yr.0.forecast.day0.text:

Teils Wolkig cloudy -> ohne "cloudy"

The upcoming version 2.0.0 of js-controller will support a new mode for low memory devices. For this, a few minor adjustments to the adapter must be made. Please follow these instructions: https://forum.iobroker.net/viewtopic.php?f=24&t=20387#p213466

The Readme is not correct if checking via iobroker:

At NPM and GIT it is updated but not at Admin.

ist im allen Tagen so

Think about update stable version to 5.3.0

Version: stable=5.1.2 (59 days old) => latest=5.3.0 (15 days old)
Installs: stable=1626 (50.14%), latest=316 (9.74%), total=3243
Click to edit