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/t4qjXH8N/ioBroker.wiffi-wz

• [E145] No news found for actual version 2.2.1
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [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) 2014-2022 Christian Vorholt [email protected]" at the end of README.md

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

wind data has wrong unit. Should be km/h but is m/s...

When trying the latest master tarball with the Weatherman, the adapter crashes:

2018-07-29 18:28:11.995  - debug: wiffi-wz.0 objectDB connected
2018-07-29 18:28:12.097  - debug: wiffi-wz.0 statesDB connected
2018-07-29 18:28:12.116  - info: wiffi-wz.0 States connected to redis: 127.0.0.1:6379
2018-07-29 18:28:12.321  - info: wiffi-wz.0 starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.wiffi-wz, node: v6.14.3
2018-07-29 18:28:12.377  - info: wiffi-wz.0 Opening socket ...
2018-07-29 18:28:12.380  - info: wiffi-wz.0 Opening local server on 0.0.0.0:8181
2018-07-29 18:28:12.407  - info: wiffi-wz.0 Server listening on 0.0.0.0:8181
2018-07-29 18:28:12.425  - info: mqtt.0 send2Server wiffi-wz.0.info.connection[undefined]
2018-07-29 18:28:12.435  - warn: mqtt.0 Cannot resolve topic name for ID: wiffi-wz.0.info.connection (object not found)
2018-07-29 18:28:12.445  - debug: wiffi-wz.0 got ip 192.168.178.82
2018-07-29 18:28:12.494  - error: wiffi-wz.0 uncaught exception: Cannot read property 'length' of undefined
2018-07-29 18:28:12.496  - error: wiffi-wz.0 TypeError: Cannot read property 'length' of undefined
at /opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:307:28
at getid (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:270:3)
at createStates (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:276:3)
at Socket. (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:331:7)
at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:316:9)
at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:241:12)
at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:345:8)
at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2018-07-29 18:28:12.500  - info: wiffi-wz.0 cleaned everything up...
2018-07-29 18:28:12.516  - info: wiffi-wz.0 terminating
2018-07-29 18:28:12.519  - info: mqtt.0 send2Server wiffi-wz.0.info.connection[undefined]
2018-07-29 18:28:12.544  - warn: mqtt.0 Cannot resolve topic name for ID: wiffi-wz.0.info.connection (object not found)
2018-07-29 18:28:12.567  - error: Caught by controller[0]: TypeError: Cannot read property 'length' of undefined
2018-07-29 18:28:12.567  - error: Caught by controller[0]:     at /opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:307:28
2018-07-29 18:28:12.568  - error: Caught by controller[0]:     at getid (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:270:3)
2018-07-29 18:28:12.568  - error: Caught by controller[0]:     at createStates (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:276:3)
2018-07-29 18:28:12.569  - error: Caught by controller[0]:     at Socket. (/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:331:7)
2018-07-29 18:28:12.569  - error:  Caught by controller[0]:     at Socket.onack  (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:316:9)
2018-07-29 18:28:12.569  - error:  Caught by controller[0]:     at Socket.onpacket  (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:241:12)
2018-07-29 18:28:12.570  - error: Caught by controller[0]:     at Manager. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2018-07-29 18:28:12.571  - error:  Caught by controller[0]:     at Manager.Emitter.emit  (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:133:20)
2018-07-29 18:28:12.572  - error:  Caught by controller[0]:     at Manager.ondecoded  (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:345:8)
2018-07-29 18:28:12.572  - error: Caught by controller[0]:     at Decoder. (/opt/iobroker/node_modules/component-bind/index.js:21:15)
2018-07-29 18:28:12.573  - error: host.piheizung instance system.adapter.wiffi-wz.0 terminated with code 0 (OK)
2018-07-29 18:28:12.573  - info: host.piheizung Restart adapter system.adapter.wiffi-wz.0 because enabled

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.

As soon as I start wiffi-wz the incoming events of admin adapter increase by 150. This will cause the admin web interface to not update the states anymore:

Admin.0 Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)

I'm using two devices (Weatherman and Rainyman) which have less than 80 states. I've other adapters with way more states causing less stress for the admin interface so I really wonder what causes this stress?
You can directly feel the difference on the web interface performance with wiffi-wz instance turned on or off...

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

Please see the result of the check below.

ioBroker.wiffi-wz

-

ERRORS:

• ❗ [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '12.0.0' } }" at package.json.
• ❗ [E033] @iobroker/adapter-core 2.5.0 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
• ❗ [E036] @iobroker/testing 2.4.4 specified. 4.1.3 is required as minimum, 4.1.3 is recommended. Please update devDependencies at package.json
• ❗ [E145] No "common.news" found for actual version 2.2.1 in io-package.json
• ❗ [E150] No "common.connectionType" found in io-package.json
• ❗ [E152] No "common.dataSource" found in io-package.json
• ❗ [E204] Version "2.1.0" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.
• ❗ [E605] No actual year found in copyright. Please add "Copyright (c) 2024 Christian Vorholt [email protected]" at the end of README.md

WARNINGS:

• 👀 [W105] Missing suggested translation into uk,zh-cn of "common.titleLang" in io-package.json.
• 👀 [W109] Missing suggested translation into uk,zh-cn of "common.desc" in io-package.json.
• 👀 [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
• 👀 [W145] Missing suggested translation into uk,zh-cn of some "common.news" in io-package.json.
• 👀 [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
• 👀 [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
• 👀 [W513] "gulpfile.js" found in repo! Think about migrating to @iobroker/adapter-dev package
• 👀 [W522] Please consider migrating to admin 5 UI (jsonConfig).
• 👀 [W853] .npmignore found - consider using package.json object "files" instead.

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

Wenn ich die Datenpunkte der Wetterstation im Blockly weiterverarbeitete und das Script starte, sich ein paar Werte ändern, zerschiesst sich das Blockly soweit, dass ich den IoBroker aus einem Backup zurückspielen muss.
Ein Debuglog habe ich nicht, da es sich zwar reproduzieren lassen kann, aber dort nichts drin steht. Das Script bricht ab und der Blocklycode ist nicht mehr da!
es geht mir vor allem um die Werte "Regensensor-Wert" (18) und "Windspitze"(5).
Habe zwar schon versucht, die Werte in Zahlen zu konvertieren um damit arbeiten zu können, leider ohne Erfolg

folgende Meldung erscheint seit dem Upgrade des Js-Controllers
Verwende einen Pulscounter stall.biz
31972) State "wiffi-wz.0.info.connection" has no existing object, this might lead to an error in future versions

Hi,
after updating to js controller 3.3.x i got:

I use wiffi-wz Adapter 2.2.1

erstmal danke für den Adapter 🙂

Soweit funktioniert auch alles, also ich bekomme die Werte im ioBroker übertragen.

Ich will, wenn der Regenmelder (wahr) ist, eine Aktion ausführen lassen.

Der Status wird auch soweit immer aktualisiert, aber selbst wenn der Status wahr ist (Regen), wird die Aktion nicht gestartet. ioBroker ignoriert jegliche Änderungen die vom Weatherman kommen und führt bei einer Änderung nichts aus, wie wenn er es gar nicht mitbekommt.

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

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/t4qjXH8N/ioBroker.wiffi-wz

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

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

May be such an icon is better?

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!

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!

in weatherman sind daten vorhanden,

aber leider kommen keine Daten in iobroker an.

ich denke ich habe den controller richtig konfiguriert:

aktuelle Version 1.2.4 hab ich

im adapter die iobroker adresse als lokale server-ip ausgewählt
hab den adapter auch schon im debug-modus laufen, es kamen aber bisher keine relevanten Daten
2018-08-31 07:33:00.588 - debug: wiffi-wz.0 redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1535693580586,"q":0,"from":"system.adapter.admin.0","lc":1535693580586} 2018-08-31 07:33:00.590 - debug: wiffi-wz.0 system.adapter.admin.0: logging false 2018-08-31 07:46:16.845 - debug: wiffi-wz.0 redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1535694376844,"q":0,"from":"system.adapter.admin.0","lc":1535694376844} 2018-08-31 07:46:16.846 - debug: wiffi-wz.0 system.adapter.admin.0: logging true

json liefert:
{"modultyp":"weatherman","vars":[{"name":"0","homematic_name":"w_ip","desc":"weatherman_ip","type":"string","unit":"","value":"192.168.xxx.yy"},{"name":"1","homematic_name":"w_temperature","desc":"aussentemperatur","type":"number","unit":"gradC","value":16.9},{"name":"21","homematic_name":"w_windchill","desc":"gefuehlte_temperatur","type":"number","unit":"gradC","value":16.9},{"name":"9","homematic_name":"w_taupunkt","desc":"taupunkt_temperatur","type":"number","unit":"gradC","value":9.1},{"name":"29","homematic_name":"w_temp_gestern","desc":"temp_m_gestern","type":"number","unit":"gradC","value":0.0},{"name":"14","homematic_name":"w_sky_temp","desc":"himmel_temperatur","type":"number","unit":"gradC","value":0.0},{"name":"2","homematic_name":"w_humidity","desc":"rel_feuchte","type":"number","unit":"%","value":60.0},{"name":"17","homematic_name":"w_hum_abs","desc":"abs_feuchte","type":"number","unit":"g/m3","value":8.6},{"name":"18","homematic_name":"w_rain_activity","desc":"regenmelderwert","type":"number","unit":"","value":6},{"name":"7","homematic_name":"w_rain_status","desc":"regenstatus","type":"boolean","unit":"","value":false},{"name":"8","homematic_name":"w_rain_intensity","desc":"regenstaerke","type":"number","unit":"mm/h","value":0.0},{"name":"19","homematic_name":"w_rain_volume_1","desc":"regen_pro_h","type":"number","unit":"mm","value":0.0},{"name":"20","homematic_name":"w_rain_volume_24","desc":"regen_pro_24h","type":"number","unit":"mm","value":0.0},{"name":"27","homematic_name":"w_rain_yesterday","desc":"regen_gestern","type":"number","unit":"mm","value":0.0},{"name":"3","homematic_name":"w_barometer","desc":"nn_luftdruck","type":"number","unit":"mb","value":1300.00},{"name":"11","homematic_name":"w_barotrend","desc":"luftdrucktrend","type":"string","unit":"","value":"not_valid"},{"name":"4","homematic_name":"w_wind_avg","desc":"avg_windgeschwindigkeit","type":"number","unit":"m/s","value":0.0},{"name":"5","homematic_name":"w_wind_peak","desc":"peak_windgeschwindigkeit","type":"number","unit":"m/s","value":0.0},{"name":"24","homematic_name":"w_windstaerke","desc":"bft_windgeschwindigkeit","type":"number","unit":"bft","value":0},{"name":"23","homematic_name":"w_wind_direction","desc":"windrichtung","type":"string","unit":"","value":"N"},{"name":"6","homematic_name":"w_wind_dir","desc":"windwinkel","type":"number","unit":"grad","value":0},{"name":"10","homematic_name":"w_lux","desc":"helligkeit","type":"number","unit":"lux","value":0.0},{"name":"15","homematic_name":"w_sun_temp","desc":"sonnentemperatur","type":"number","unit":"gradC","value":18.0},{"name":"22","homematic_name":"w_diff_temp","desc":"sonnen_difftemperatur","type":"number","unit":"gradC","value":1.1},{"name":"16","homematic_name":"w_sonne_scheint","desc":"sonne_scheint","type":"boolean","unit":"","value":false},{"name":"26","homematic_name":"w_sonne_heute","desc":"sonne_heute","type":"number","unit":"h","value":0.0},{"name":"28","homematic_name":"w_sonne_gestern","desc":"sonne_gestern","type":"number","unit":"h","value":0.0},{"name":"12","homematic_name":"w_elevation","desc":"sonne_elevation","type":"number","unit":"grad","value":-2.7},{"name":"13","homematic_name":"w_azimut","desc":"sonne_azimut","type":"number","unit":"grad","value":81.5}],"Systeminfo":{"MAC-Adresse":"9:ee:17:22:66:44","Homematic_CCU_ip":"192.168.yyy.xxx","WLAN_ssid":"meine-ssid","WLAN_Signal_dBm":-50,"sec_seit_reset":1960,"zeitpunkt":"2018-08-31 07:42:19","firmware":"weatherman_66"}}

As soon as I start wiffi-wz the incoming events of admin adapter increase by 150. This will cause the admin web interface to not update the states anymore:

Admin.0 Unsubscribe from all states, except system's, because over 3 seconds the number of events is over 200 (in last second 0)

I'm using two devices (Weatherman and Rainyman) which have less than 80 states. I've other adapters with way more states causing less stress for the admin interface so I really wonder what causes this stress?
You can directly feel the difference on the web interface performance with wiffi-wz instance turned on or off...

Nach dem Update auf den aktuellen js-controller folgender log-Eintrag:
2021-05-01 00:00:32.055 - �[33mwarn�[39m: wiffi-wz.0 (25505) State value to set for "wiffi-wz.0.root.192_168_1_142.w_elevation" has value "-21.6" less than min "360"

es werden überhaupt keine Datenpunkte erstellt
keine Daten vom wiffi, log meldet:
Datagram error, could not find an ip!

Adapter: 2.0.0
Adapter neu installiert um alle Änderungen aktuell zu haben
Wiffi meldet: connected with CCU
wiffi-Firmware: rainyman_91 (Problem besteht mind. seit Version _87)

Blockly weigert sich den folgenden Datenpunkt weiter zu verarbeiten:
{ "type": "state", "common": { "name": 1, "desc": "aussentemperatur", "unit": "°C", "role": "value", "id": "w_temperatur", "type": "number", "read": true, "write": false, "custom": { "influxdb.0": { "enabled": true, "changesOnly": true, "debounce": "", "retention": "31536000", "changesRelogInterval": "1800", "changesMinDelta": 0, "storageType": "Number", "aliasId": "Aussentemperatur" } } }, "native": {}, "from": "system.adapter.wiffi-wz.0", "user": "system.user.admin", "ts": 1566662224431, "_id": "wiffi-wz.0.root.192_168_1_142.w_temperatur", "acl": { "object": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator", "state": 1636 } }

Bei diesem Wert geht es:
{ "type": "state", "common": { "read": true, "write": false, "desc": "regen_mm_gestern", "unit": "mm", "role": "value", "id": "w_regen_mm_gestern", "name": "27", "type": "number" }, "native": {}, "from": "system.adapter.wiffi-wz.0", "user": "system.user.admin", "ts": 1566662224436, "_id": "wiffi-wz.0.root.192_168_1_142.w_regen_mm_gestern", "acl": { "object": 1636, "state": 1636, "owner": "system.user.admin", "ownerGroup": "system.group.administrator" } }

Warum ist das so?
Wenn ich den ersten Wert per js-in einen eigenen DP "umsetze", kann ich ihn verarbeiten!

Hi,

nice adapter works flawlessly. The only thing I was wondering about is the purpose of the root device, defined in

IMHO, the devices which are currently created as channels, should be of type device and the root device seems to be redundant. Maybe consider changing this, when you have other breaking changes to implement. ;-)

hi, seit dem Update bekomme ich keine Statusänderung der beiden Bewegungsmelder und des Noise sensor des WiffiWZ an den Iobroker übertragen . Besteht das Problem noch bei wem anders oder muss hier bei mir weiter suchen...Auf der Gui des WiffiWZ wird die Bewegung und noise erkannt...
Werte werden aktualisiert aber stehen immer nur auf false... Um das zu verifizieren wollte ich auf die vorherige Version zurück, aber das funktioniert nicht...Wie kann ich downgraden...Einebestimmte Version über den Admin hat nicht funktioniert

Think about update stable version to 2.2.0

Version: stable=2.1.4 (185 days old) => latest=2.2.0 (25 days old)
Installs: stable=109 (57.98%), latest=67 (35.64%), total=188
Click to edit

Hi,

i have a lot of history settings activated. However some of them get turned off every few days.
Do you by any chance manage these settings in your adapter?
Create the states anew and reset these settings?

All my other history settings in the other adapters i use never showed this behaviour.

Any chance that the "create states for wiffi" might affect the history settings?

THX for your help and greetings,
Markus

Hallo,

Bei mir ist seit gestern der Pulsecounter aktiv, soweit läuft es auch, allerdings bekomme im Log vom Iobroker folgende Meldungen:
https://forum.iobroker.net/assets/uploads/files/1565811138503-80c35f51-f0d2-460c-a452-f73ff2a30d56-grafik.png
Hier ein Bild der Objekte, die der Adapter vom wiffi_counter_29 bekommt:
https://forum.iobroker.net/assets/uploads/files/1565811705311-99ea2d89-c315-485b-a897-5f07c6dfb74b-grafik.png

Ich gehe davon aus, dass Eugen was umgestellt hat in dem Modul.
Die Werte auf meienr Web-Seite sehen normal aus:
https://forum.iobroker.net/assets/uploads/files/1565811307312-e696669b-74b9-448b-8cc4-e8b2a455d769-grafik.png

Grüße
Ralf

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.

Could you please release a new version containing the latest commits, js-controller 3.3 will be stable in a few weeks and w/o the changes the adapter will log several warnings frequently

Think about update stable version to 2.2.0

Version: stable=2.1.4 (187 days old) => latest=2.2.0 (27 days old)
Installs: stable=107 (57.84%), latest=66 (35.68%), total=185
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/t4qjXH8N/ioBroker.wiffi-wz

• [E130] Too many news found in io-package.json. Mast be less than 21. Please remove old news.

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

Setup

3. Tell wiffi-wz that it has to send data in JSON format without HTML header (Note that the weatherman may use a different parameter number)

http://[wiffi ip]/?param:27:1

But I see parameter http://[wiffi ip]/?param:12:8181 in Wethermen2 parameter description for that.

Gruß Philipp

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/t4qjXH8N/ioBroker.wiffi-wz

• [E104] No common.title found in io-package.json
• [E150] No common.connectionType found in io-package.json
• [E152] No common.dataSource found in io-package.json
• [E605] No actual year found in copyright. Please add "Copyright (c) 2014-2021 Christian Vorholt [email protected]" at the end of README.md
• [E701] No actual year found in LICENSE. Please add "Copyright (c) 2014-2021 Christian Vorholt [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

Sorry but no one role is valid.
Please take roles from here:
https://github.com/ioBroker/ioBroker/blob/master/doc/STATE_ROLES.md

After first start and init of the objects in iobroker, the Log shows many like the following messages, As recommended, I report this here.

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!

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