[Aufruf] Neuer Adapter für den Wiffi-wz, den Weatherman und den Rainyman von Stall.biz bereit zum testen

[x4tlaoguo]

Hey,

erstmal vielen Dank fürs Testen!

Sorry für den Fehler beim einlesen der Wiffi-Daten, (fast) alles getestet und dann rutscht mir das durch.

@Smartboart ich habe dir eine Testversion per PN geschickt.

[coyote]

Hi,

würdest du den wiffi-pump noch mit in deinen Adapter einbauen.

Gruß

[x4tlaoguo]

Liebe Tester,

vielen Dank für euren Einsatz. Ich werde als erstes die aktuelle Version 1.2.4 als Release taggen und die Verschiebung in den stable-Branch von Io-Broker anstoßen.

@coyote: Bitte stelle deinen Adapter auf "debug" und schicke mir das Datagram per PN. Dann können wir gemeinsam versuchen den Wiffi-pump zu unterstützen.

[willi5]

Hi

möchte mich anschließen.

Installation mit folgender debug-Ausgabe:

Fertig mit Fehler: host.EG Cannot install https://github.com/t4qjXH8N/ioBroker.wi … all/master: 4294963214

$ ./iobroker url "https://github.com/t4qjXH8N/ioBroker.wi ... all/master" wiffi-wz --debug

install https://github.com/t4qjXH8N/ioBroker.wi ... all/master

npm install https://github.com/t4qjXH8N/ioBroker.wi ... all/master --production --save --prefix "C:/ioBroker" (System call)

npm

WARN rollback Rolling back iobroker.wiffi-wz@1.2.4 failed (this is probably harmless): EBUSY: resource busy or locked, rmdir 'C:\ioBroker\node_modules\iobroker.wiffi-wz'

npm

ERR! path C:\ioBroker\node_modules\iobroker.wiffi-wznpm ERR! code EBUSY

npm

ERR! errno -4082npm

ERR!

syscall

rename

npm

ERR! EBUSY: resource busy or locked, rename 'C:\ioBroker\node_modules\iobroker.wiffi-wz' -> 'C:\ioBroker\node_modules.iobroker.wiffi-wz.DELETE'

npm ERR! A complete log of this run can be found in:npm ERR! C:\WINDOWS\system32\config\systemprofile\AppData\Roaming\npm-cache_logs\2018-08-29T12_49_35_996Z-debug.log

ERROR: host.EG Cannot install https://github.com/t4qjXH8N/ioBroker.wi ... all/master: 4294963214

ERROR: process exited with code 25

Adapter wird erfolgreich gelöscht. Erscheint aber weiterhin bei den Adaptern. Bei nochmaligem Löschen, gleicher Vorgang.

Bei der Instanzen-Installation geht das Installationsfenster auf und bleibt bis zum manuellen Abbruch des Prozesses.

Vielen Dank für Deine Mühe.

willi5

Ich vergaß.

Node: 10

npm: 6.2

Wiffi-wz: Version 1.2.4

[x4tlaoguo]

Hm,

ich bin mir nicht sicher ob das ein Problem des Adapters ist. Hast du das Probiert, was npm dir sagt?

ERR! EBUSY: resource busy or locked, rename 'C:\ioBroker\node_modules\iobroker.wiffi-wz' -> 'C:\ioBroker\node_modules.iobroker.wiffi-wz.DELETE' ?

Was passiert, wenn Du den Iobroker stopst mit "iobroker stop" und dann den Adapter löschst? Also den Ordner "node_modules/iobroker.wiffi-wz" löschst?

Mir fällt auf, dass diese Probleme bisher nur unter Windows auftreten….

[x4tlaoguo]

Achso,

noch etwas, mir ist aufgefallen, dass dieser Fehler auftritt wenn meine eine Kommandozeile geöffnet hat und in dem entsprechenden Ordner ist. Ebenso kann der Fehler auftreten wenn der Explorer den Ordner geöffnet hat.

[willi5]

HI,

ich habe den Ordner Ordner "node_modules/iobroker.wiffi-wz" gelöscht. Der wiffi-wz ist weiterhin vorhanden, es fehlt nur das Löschsymbol.

Auf der SSD und in der Registry ist wiffi-wz nicht vorhanden.

[x4tlaoguo]

Hey, wo genau ist der vorhanden? Ist der unter Adapter oder Instanzen vorhanden?

[Farmer-cb]

Hallo

hab mir die Station auch besorgt

leider kommen bei mir im adapter wiffi-wz keine Daten an

daten sind im weatherman

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.xxx.yyy","WLAN_ssid":"meine_ssid","WLAN_Signal_dBm":-50,"sec_seit_reset":1960,"zeitpunkt":"2018-08-31 07:42:19","firmware":"weatherman_66"}} !
denke ich habe den weatherman richtig konfiguriert:

hab den adapter bereits auf debug, leider kommen aktuell keine aussagekräftige daten an:

! 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 !

ach ja adapter-version 1.2.4

mir ist gerade noch aufgefallen, das, jedesmal wenn ich den adapter neustarte error-meldung im log auftauchen:

! ````
wiffi-wz.0 2018-08-31 07:56:44.121 info Server listening on 0.0.0.0:8181
wiffi-wz.0 2018-08-31 07:56:44.121 info Opening local server on 0.0.0.0:8181
wiffi-wz.0 2018-08-31 07:56:44.120 info Opening socket ...
wiffi-wz.0 2018-08-31 07:56:44.055 info starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.wiffi-wz, node: v6.14.3
host.iobroker 2018-08-31 07:56:42.255 info instance system.adapter.wiffi-wz.0 started with pid 820
host.iobroker 2018-08-31 07:56:39.855 info instance system.adapter.wiffi-wz.0 terminated with code 0 (OK)
Caught 2018-08-31 07:56:39.854 error by controller[4]: at processImmediate [as _immediateCallback] (timers.js:617:5)
Caught 2018-08-31 07:56:39.854 error by controller[4]: at tryOnImmediate (timers.js:645:5)
Caught 2018-08-31 07:56:39.854 error by controller[4]: at runCallback (timers.js:672:20)
Caught 2018-08-31 07:56:39.853 error by controller[4]: at Immediate._tickCallback (internal/process/next_tick.js:104:9)
Caught 2018-08-31 07:56:39.853 error by controller[4]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
Caught 2018-08-31 07:56:39.853 error by controller[4]: at emitCloseNT (net.js:1568:8)
Caught 2018-08-31 07:56:39.853 error by controller[4]: at Server.emit (events.js:185:7)
Caught 2018-08-31 07:56:39.852 error by controller[4]: at emitNone (events.js:86:13)
Caught 2018-08-31 07:56:39.852 error by controller[4]: at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
Caught 2018-08-31 07:56:39.851 error by controller[4]: ReferenceError: sock is not defined
Caught 2018-08-31 07:56:39.851 error by controller[3]: at process._tickCallback (internal/process/next_tick.js:104:9)
Caught 2018-08-31 07:56:39.850 error by controller[3]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
Caught 2018-08-31 07:56:39.849 error by controller[3]: at emitCloseNT (net.js:1568:8)
Caught 2018-08-31 07:56:39.849 error by controller[3]: at Server.emit (events.js:185:7)
Caught 2018-08-31 07:56:39.848 error by controller[3]: at emitNone (events.js:86:13)
Caught 2018-08-31 07:56:39.848 error by controller[3]: at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
Caught 2018-08-31 07:56:39.848 error by controller[3]: ReferenceError: sock is not defined
Caught 2018-08-31 07:56:39.847 error by controller[2]: at process._tickCallback (internal/process/next_tick.js:104:9)
Caught 2018-08-31 07:56:39.847 error by controller[2]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
Caught 2018-08-31 07:56:39.846 error by controller[2]: at emitCloseNT (net.js:1568:8)
Caught 2018-08-31 07:56:39.846 error by controller[2]: at Server.emit (events.js:185:7)
Caught 2018-08-31 07:56:39.846 error by controller[2]: at emitNone (events.js:86:13)
Caught 2018-08-31 07:56:39.845 error by controller[2]: at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
Caught 2018-08-31 07:56:39.845 error by controller[2]: ReferenceError: sock is not defined
Caught 2018-08-31 07:56:39.845 error by controller[1]: at processImmediate [as _immediateCallback] (timers.js:617:5)
Caught 2018-08-31 07:56:39.844 error by controller[1]: at tryOnImmediate (timers.js:645:5)
Caught 2018-08-31 07:56:39.844 error by controller[1]: at runCallback (timers.js:672:20)
Caught 2018-08-31 07:56:39.844 error by controller[1]: at Immediate._tickCallback (internal/process/next_tick.js:104:9)
Caught 2018-08-31 07:56:39.843 error by controller[1]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
Caught 2018-08-31 07:56:39.843 error by controller[1]: at emitCloseNT (net.js:1568:8)
Caught 2018-08-31 07:56:39.843 error by controller[1]: at Server.emit (events.js:185:7)
Caught 2018-08-31 07:56:39.842 error by controller[1]: at emitNone (events.js:86:13)
Caught 2018-08-31 07:56:39.842 error by controller[1]: at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
Caught 2018-08-31 07:56:39.842 error by controller[1]: ReferenceError: sock is not defined
Caught 2018-08-31 07:56:39.841 error by controller[0]: at process._tickCallback (internal/process/next_tick.js:104:9)
Caught 2018-08-31 07:56:39.841 error by controller[0]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
Caught 2018-08-31 07:56:39.841 error by controller[0]: at emitCloseNT (net.js:1568:8)
Caught 2018-08-31 07:56:39.840 error by controller[0]: at Server.emit (events.js:185:7)
Caught 2018-08-31 07:56:39.840 error by controller[0]: at emitNone (events.js:86:13)
Caught 2018-08-31 07:56:39.840 error by controller[0]: at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
Caught 2018-08-31 07:56:39.839 error by controller[0]: ReferenceError: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.811 info Stopping adapter ...
wiffi-wz.0 2018-08-31 07:56:39.810 error at process._tickCallback (internal/process/next_tick.js:104:9)
wiffi-wz.0 2018-08-31 07:56:39.810 error at _combinedTickCallback (internal/process/next_tick.js:77:11)
wiffi-wz.0 2018-08-31 07:56:39.810 error at emitCloseNT (net.js:1568:8)
wiffi-wz.0 2018-08-31 07:56:39.810 error at Server.emit (events.js:185:7)
wiffi-wz.0 2018-08-31 07:56:39.810 error at emitNone (events.js:86:13)
wiffi-wz.0 2018-08-31 07:56:39.810 error at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
wiffi-wz.0 2018-08-31 07:56:39.810 error ReferenceError: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.809 error uncaught exception: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.800 info Stopping adapter ...
wiffi-wz.0 2018-08-31 07:56:39.799 error at processImmediate [as _immediateCallback] (timers.js:617:5)
wiffi-wz.0 2018-08-31 07:56:39.799 error at tryOnImmediate (timers.js:645:5)
wiffi-wz.0 2018-08-31 07:56:39.799 error at runCallback (timers.js:672:20)
wiffi-wz.0 2018-08-31 07:56:39.799 error at Immediate._tickCallback (internal/process/next_tick.js:104:9)
wiffi-wz.0 2018-08-31 07:56:39.799 error at _combinedTickCallback (internal/process/next_tick.js:77:11)
wiffi-wz.0 2018-08-31 07:56:39.799 error at emitCloseNT (net.js:1568:8)
wiffi-wz.0 2018-08-31 07:56:39.799 error at Server.emit (events.js:185:7)
wiffi-wz.0 2018-08-31 07:56:39.799 error at emitNone (events.js:86:13)
wiffi-wz.0 2018-08-31 07:56:39.799 error at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
wiffi-wz.0 2018-08-31 07:56:39.799 error ReferenceError: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.799 error uncaught exception: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.793 info Stopping adapter ...
wiffi-wz.0 2018-08-31 07:56:39.792 error at process._tickCallback (internal/process/next_tick.js:104:9)
wiffi-wz.0 2018-08-31 07:56:39.792 error at _combinedTickCallback (internal/process/next_tick.js:77:11)
wiffi-wz.0 2018-08-31 07:56:39.792 error at emitCloseNT (net.js:1568:8)
wiffi-wz.0 2018-08-31 07:56:39.792 error at Server.emit (events.js:185:7)
wiffi-wz.0 2018-08-31 07:56:39.792 error at emitNone (events.js:86:13)
wiffi-wz.0 2018-08-31 07:56:39.792 error at Server. <anonymous>(/opt/iobroker/node_modules/iobroker.wiffi-wz/main.js:221:36)
wiffi-wz.0 2018-08-31 07:56:39.792 error ReferenceError: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.782 error uncaught exception: sock is not defined
wiffi-wz.0 2018-08-31 07:56:39.744 info Stopping adapter ...</anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous></anonymous>

und dann bleibt der adapter gelb

[coyote]

Gerät im Adapter eingetragen? Port ist auf 8181

Dann musst du auch im Weatherman den Port eintragen und die IP von iobroker.

Also den ccu Parameter auf IP von iobroker und param12 auf 8181

[x4tlaoguo]

Hey farmer,

dies ist tatsächlich ein blöder Fehler. Ich konnte den Fehler reproduzieren und habe eine hoffentlich gefixte Version auf Github hinterlegt.

Vielen Dank fürs Testen!

[Farmer-cb]

leider hab ich ein neues Problem,

ich depp :oops: , wollte jetzt den adapter löschen und neu installieren, geht leider nicht .

wenn ich den adapter lösche, läuft es zwar durch, aber der adapter bleibt sichtbar, nur das löschsymbol verschwindet.

neu installieren lässt er sich auch nicht, da bleibt er hängen:

$ ./iobroker url "https://github.com/t4qjXH8N/ioBroker.wiffi-wz/tarball/master" wiffi-wz
install https://github.com/t4qjXH8N/ioBroker.wiffi-wz/tarball/master
npm install https://github.com/t4qjXH8N/ioBroker.wiffi-wz/tarball/master --production --save --prefix "/opt/iobroker" (System call)

beim löschen sagt er:

$ ./iobroker del wiffi-wz
Delete adapter "wiffi-wz"
host.iobroker no instances of adapter wiffi-wz found
host.iobroker Counted 1 devices of wiffi-wz
host.iobroker Counted 1 states of wiffi-wz
host.iobroker Counted 1 states (wiffi-wz.*) from states
host.iobroker Counted 7 states (system.adapter.wiffi-wz.*) from states
host.iobroker Deleting 2 object(s).
host.iobroker Deleting 8 state(s).
npm uninstall iobroker.wiffi-wz --silent --save --prefix "/opt/iobroker" (System call)

anschliessend steht er in tab-adapters so (ohne das löschsymbol:

was kann ich sonst machen um den adapter wieder zu installieren???? :?: :?: :?:

[Stabilostick]

Ich sag doch, dass da ein Problem mit dem Setup ist. [emoji56]

[Farmer-cb]

@Stabilostick:

Ich sag doch, dass da ein Problem mit dem Setup ist. [emoji56] `

hattest/hast du das selbe problem :?:

[x4tlaoguo]

Ok, ich konnte das Problem teilweise nachvollziehen.

Der BUSY-Fehler tritt auf, wenn man im Admin-Interface den Adapter von Github installieren/aktualisieren will, und die Wiffi-Instanz noch läuft.

Lösung: iobroker admin stop, iobroker admin start, Wiffi-Instanz stoppen und dann aktualisieren

[Farmer-cb]

ich hab keine Instance von wiffi-wz laufen

root@iobroker:~# ps -ef | grep io.*.0
root         9     2  0 10:18 ?        00:00:00 [migration/0]
root       459   395  1 10:18 ?        00:00:25 io.admin.0
root       467   395  0 10:18 ?        00:00:19 io.web.0
root       501   395  6 10:18 ?        00:02:26 io.javascript.0
root       507   395  0 10:18 ?        00:00:05 io.socketio.0
root       523   395  0 10:18 ?        00:00:08 io.cloud.0
root       529   395  1 10:18 ?        00:00:31 io.tr-064.0
root       551   395  0 10:18 ?        00:00:19 io.sql.0
root       587   395  1 10:19 ?        00:00:31 io.s7.0
root       609   395  0 10:19 ?        00:00:05 io.simple-api.0
root       623   395  0 10:19 ?        00:00:18 io.parser.0
root       663   395  0 10:19 ?        00:00:08 io.telegram.0
root       669   395  0 10:19 ?        00:00:07 io.sonos.0
root       679   395  0 10:19 ?        00:00:04 io.sayit.0
root       693   395  0 10:19 ?        00:00:19 io.sonoff.0
root       703   395  0 10:19 ?        00:00:13 io.mihome-vacuum.0
root       730   395  0 10:19 ?        00:00:04 io.backitup.0
root       751   395  0 10:19 ?        00:00:06 io.broadlink2.0
root       772   395  0 10:20 ?        00:00:11 io.alexa2.0
root       792   395  1 10:20 ?        00:00:37 io.sonnen.0
root       859   517  0 10:54 pts/0    00:00:00 grep io.*.0

[x4tlaoguo]

stimmt, jetzt nicht mehr

[Farmer-cb]

beim aktualisieren bleibt er immernoch hängen

[Stabilostick]

War viewtopic.php?t=16504#p173494

[coyote]

Hey x4tlaoguo,

konntest du schon mal nach dem Wiffi-Pump schauen um den einzufügen?

Gruß