Neuinstallation des Adapters hat nichts bewirkt.
Bekomme den Fehler seit ca 2 Tagen. Hatte ein Node Update von 12 auf 14 durchgeführt.
Alle anderen Adapter haben das aber problemlos verkraftet. Ob der Fehler tatsächlich daher kommt mag ich nicht zu beurteilen

Installierte Version: 2.1.1

pio4gb Plattform linux Betriebssystem linux Architektur arm CPUs 4 Geschwindigkeit 1500 MHz Modell ARMv7 Processor rev 3 (v7l) RAM 3.75 GB System-Betriebszeit 3 T. 00:36:35 Node.js v14.19.2 time 1652608634970 timeOffset -120 Anzahl der Adapter 490 NPM 6.14.17 Datenträgergröße 58.29 GB freier Festplattenspeicher 51.26 GB Betriebszeit 3 T. 00:36:28 Aktive Instanzen 19 Weg /opt/iobroker/ Hostname pio4gb

`

Think about update stable version to 1.2.1

Version: stable=1.2.0 (15 days old) => latest=1.2.1 (665 days old)
Installs: stable=162 (43.78%), latest=20 (5.41%), total=370
Click to edit

Think about update stable version to 2.1.1

Version: stable=2.0.10 (60 days old) => latest=2.1.1 (911 days old)
Installs: stable=301 (54.83%), latest=4 (0.73%), total=549
Click to edit

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.

Hi, my last entry from the adapter was on 21.2.2021, this was the last update from the meteosat-page, what the adapter get.
In the debug mode, the adapter show absolut no error messages, the page is reachable and in the log it looks like fine.
The config show ( and in the logfile ) that the rss is used, but with this there are in the last days warnings ( storm, etc.)

Can you check the requests, please?
What I have changed was only Node 14.16.0 and js-controller up to 3.2.16

Think about update stable version to 2.1.0

Version: stable=2.0.10 (56 days old) => latest=2.1.0 (907 days old)
Installs: stable=368 (66.79%), latest=4 (0.73%), total=551
Click to edit

https://github.com/jack-blackson/ioBroker.meteoalarm/blob/master/main.js#L701

This produced 91k messages on 77 users in the last 90 days ... Please do something with it or remove it from Sentry reporting :-)

Seit einem der letzten Updates vom Admin kommt diese Warnung regelmässig alle 10 Minuten im Cron Takt.
Ich habe direkt Netzwerk Verbindung mit Kabel, also kein WLAN.

With Admin 3.6.5, js-controller 1.5.14, and Meteoalarm 1.05 ( and older versions, too) the adapter stop itself:
`

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.

Hey there, it would be nice to have Switzerland added to the list of available countries...
Thanks!

Think about update stable version to 2.0.6

Version: stable=2.0.5 (46 days old) => latest=2.0.6 (780 days old)
Installs: stable=303 (66.89%), latest=6 (1.32%), total=453
Click to edit

Hello,
It looks like the Geocode-File for Switzerland has been updated and it's working again.
If so, could you add Switzerland again?
Thanks a lot for checking.

Cheers

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency mocha was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi
First of all, thanks for your effort on ioBroker.meteoalarm.
Can you add Switzerland (CH) do the supportet countrys?

best regards
Urs

Hallo, erst mal Dank für Deinen Adapter!

wie stelle ich es an das diese Warnungen mit sayit und sonos ausgegeben werden?

Lieben Dank für Deine Hilfe!

meteoalarm 2.0.10
In meinem Logfile finde ich nach jedem Aufruf des Adapters die Meldung "Fehler: Error: Unexpected close tagLine: 0Column: 595Char: >".
Liegt das daran, dass für meine Region gerade 'keine aktuelle Wetterwarnung' vorliegt oder ein genereller Fehler (Änderung bei meteoalarm.org)?

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!

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency @iobroker/testing was updated from 2.1.0 to 2.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@iobroker/testing is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Think about update stable version to 2.0.3

Version: stable=2.0.2 (25 days old) => latest=2.0.3 (728 days old)
Installs: stable=239 (58.44%), latest=16 (3.91%), total=409
Click to edit

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/jack-blackson/ioBroker.meteoalarm

• [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 jack_blackson [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019-2022 jack_blackson [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

The devDependency mocha was updated from 6.2.1 to 6.2.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

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

Hallo,

nach einen Update des js-controllers auf V 3.3.1 kommen folgende Warnmeldungen:

`

`

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')

Hi
Getting following error on meteoalarm adapter (2.1.1) when there is an alert.

Think about update stable version to 1.2.0

Version: stable=1.1.3 (64 days old) => latest=1.2.0 (659 days old)
Installs: stable=167 (45.75%), latest=83 (22.74%), total=365
Click to edit

Think about update stable version to 1.1.0

Version: stable=1.0.9 (54 days old) => latest=1.1.0 (232 days old)
Installs: stable=169 (83.66%), latest=2 (0.99%), total=202
Click to edit

PLATTFORM: LINUX RAM: 3.7 GB NODE.JS: V14.19.3 NPM: 6.14.17

`host.pio4gb-Server
2022-06-04 06:30:07.264 warn Objects 127.0.0.1:36492 Error from InMemDB: Error: Not exists

meteoalarm.2
2022-06-04 06:30:07.143 info starting. Version 2.1.4 (non-npm: jack-blackson/ioBroker.meteoalarm) in /opt/iobroker/node_modules/iobroker.meteoalarm, node: v14.19.3, js-controller: 4.0.23
host.pio4gb
2022-06-04 06:30:06.690 info iobroker exit 0

meteoalarm.2
2022-06-04 19:30:08.267 error Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.typeText": Connection is closed.

meteoalarm.2
2022-06-04 19:30:08.265 error [localCreateState] error: Could not check object existence of meteoalarm.2.alarms.Alarm_2.type: Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.type": Connection is closed., stack: Error: Could not check object existence of meteoalarm.2.alarms.Alarm_2.type: Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.type": Connection is closed. at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2973:17) at Adapter.setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:3518:30)

meteoalarm.2
2022-06-04 19:30:08.263 error Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.type": Connection is closed.

meteoalarm.2
2022-06-04 19:30:08.260 error [localCreateState] error: Could not check object existence of meteoalarm.2.alarms.Alarm_2.levelText: Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.levelText": Connection is closed., stack: Error: Could not check object existence of meteoalarm.2.alarms.Alarm_2.levelText: Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.levelText": Connection is closed. at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2973:17) at Adapter.setObjectNotExists (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:3518:30)

meteoalarm.2
2022-06-04 19:30:07.939 error Cannot check object existence of "meteoalarm.2.alarms.Alarm_2.levelText": Connection is closed.

meteoalarm.2
2022-06-04 19:30:07.938 error [localCreateState] error: DB closed, stack: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at Socket.emit (domain.js:475:12) at TCP. (net.js:686:12)`

`

Hi, since some days meteoalarm results are in german and! in english! Its not possible to disable the english text at the webpage.

We need a split text object for german and english in the Adapter, because with Alexa it's really crazy the english text to hear.. :-)

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!

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The dependency @iobroker/adapter-core was updated from 2.2.1 to 2.3.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@iobroker/adapter-core is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Think about update stable version to 1.1.4

Version: stable=1.1.3 (12 days old) => latest=1.1.4 (607 days old)
Installs: stable=174 (50.43%), latest=17 (4.93%), total=345
Click to edit

Think about update stable version to 2.1.3

Version: stable=2.1.2 (7 days old) => latest=2.1.3 (1015 days old)
Installs: stable=218 (35.91%), latest=1 (0.16%), total=607
Click to edit

Hallo, es kommt immer dieser Fehler:
`

`

Hi,

I always used the following alarm object IDs to show i.e. just the headline of an alarm in my VIS dashboard:
meteoalarm.0.alarms.Alarm_1.headline
meteoalarm.0.alarms.Alarm_2.headline

Something has changed now, so that the alarms have individual IDs like this:
meteoalarm.0.alarms.249002760DWDPVW1668956100000d9643b09-4cc4-4bbf-90ef-83ea00be2b20MUL.headline

As every new alarm get a new ID, I´m no longer able to just display the first 3 alarms, for example.
I´m currently running version 2.3.1, but honestly I´m not sure, when this behavior changed...
Is there a trick, which I did not see, how to resolve this?

Thanks and regards

Hallo, habe den neuen Js Controller Version 4.0.0 Alpha installiert, seit dem kommt das:

`

Plattform: Windows
RAM: 16 GB
NODE.JS: V14.18.3
NPM: 6.14.15
JS Controller: 4.0.0
Admin: 5.2.3
Web: 4.1.1
Socket.io: 4.1.0

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!

Sentry Issue: IOBROKER-METEOALARM-1W

TypeError: result.feed.entry.forEach is not a function
  File "/opt/iobroker/node_modules/iobroker.meteoalarm/main.js", line 179, in null.<anonymous>
    result.feed.entry.forEach(function (element){
  File "/opt/iobroker/node_modules/xml2js/lib/parser.js", line 304, in Parser.<anonymous>
    return cb(null, result);
  File "events.js", line 314, in Parser.emit
  File "domain.js", line 483, in Parser.EventEmitter.emit
  File "/opt/iobroker/node_modules/xml2js/lib/parser.js", line 262, in SAXParser.onclosetag
    return _this.emit("end", _this.resultObject);
...
(5 additional frame(s) were not displayed)

there are some wrong types, maybe this is interessting for changes

`

`

Hello, can you please add Luxembourg to the supported countries ?
Thanks
MBL

Should be

"connectionType": "cloud",
"dataSource": "poll",

instead of

Documentation: https://github.com/ioBroker/ioBroker.repositories/blob/master/README.md#connection-types

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/jack-blackson/ioBroker.meteoalarm

• [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 jack_blackson [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2019-2022 jack_blackson [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

Hi
Thanks for your effort on ioBroker.meteoalarm.
May i ask to add Ireland (IE) to list of supported countries ... I know its small but green ;)
example: "https://www.meteoalarm.eu/en_UK/0/0/IE007.html"
Thanks a lot.

"instance system.adapter.meteoalarm.0 already running with pid xxxxxxx"

Das passiert, wenn die Internetverbindung nicht vorhanden ist und dann wieder kommt. Mobiler Hotspot ;)

Hi, first of all, thank you very much for this nice adapter.

Can you please add Switzerland to meteoalarm?

thank you and best regards:
ColossusCH

Hallo,
habe seit dem Upgrade von der Version 0.5 auf auf die Version 1.0.4 immer diese Fehlermeldung im Log.
2019-09-16 09:50:01.762 - info: host.ioBroker object change system.adapter.meteoalarm.0 2019-09-16 09:50:01.763 - info: host.ioBroker "system.adapter.meteoalarm.0" enabled 2019-09-16 09:50:01.797 - info: host.ioBroker instance system.adapter.meteoalarm.0 started with pid 28552 2019-09-16 09:50:13.117 - error: host.ioBroker instance system.adapter.meteoalarm.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2019-09-16 09:50:13.118 - info: host.ioBroker Do not restart adapter system.adapter.meteoalarm.0 because desired by instance

Es werden zwar die Objekte erzeugt aber der Adapter bleibt deaktiviert.

Think about update stable version to 2.1.2

Version: stable=2.1.1 (97 days old) => latest=2.1.2 (2 days old)
Installs: stable=436 (73.4%), latest=6 (1.01%), total=594
Click to edit

Think about update stable version to 2.0.2

Version: stable=1.2.1 (38 days old) => latest=2.0.2 (703 days old)
Installs: stable=163 (42.12%), latest=14 (3.62%), total=387
Click to edit

Halo,

I hop you can add my country to dies adapter.

thank You