Hi,

ist bei mir leider auch so. (zumindest habe ich fast minuetliche disconnects)

Ich hatte schon die 0.7 und bin dann wieder zurück auf die 0.6.2. Kein Unterschied.

Der Hub ist aber mit dem WLAN verbunden und stets ansprechbar. An der Verbindung kann es nicht liegen.

Das WLAN-Signal ist super stark. Bis gestern ist mir auch nichts aufgefallen. Es fing erst heute Nacht an.

Systemaenderungen habe ich nicht vorgenommen. Nur normales Scripten. Heute habe ich den WEB Adapter upgegraded aber laut log

fingen die Probleme schon vorher an.

Aus dem log mit debug kann ich auch nicht viel entnehmen

! harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.outputCount {"val":18,"ack":true,"ts":1493201321708,"q":0,"from":"system.adapter.harmony.0","lc":1493201321708} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.inputCount {"val":10,"ack":true,"ts":1493201321708,"q":0,"from":"system.adapter.harmony.0","lc":1493201321708} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.uptime {"val":121,"ack":true,"ts":1493201321707,"q":0,"from":"system.adapter.harmony.0","lc":1493201321707} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.memHeapUsed {"val":16.26,"ack":true,"ts":1493201321707,"q":0,"from":"system.adapter.harmony.0","lc":1493201321707} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.memHeapTotal {"val":18.22,"ack":true,"ts":1493201321707,"q":0,"from":"system.adapter.harmony.0","lc":1493201321707} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.memRss {"val":34,"ack":true,"ts":1493201321707,"q":0,"from":"system.adapter.harmony.0","lc":1493201321707} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.connected {"val":true,"ack":true,"ts":1493201321706,"q":0,"from":"system.adapter.harmony.0","lc":1493201201699} harmony.0 2017-04-26 12:08:41.710 debug redis publish io.system.adapter.harmony.0.alive {"val":true,"ack":true,"ts":1493201321706,"q":0,"from":"system.adapter.harmony.0","lc":1493201201698} harmony.0 2017-04-26 12:08:32.235 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.activities.LG_TV {"val":0,"ack":true,"ts":1493201312231,"q":0,"from":"system.adapter.harmony.0","lc":1492809570691} harmony.0 2017-04-26 12:08:32.235 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.activities.TV {"val":0,"ack":true,"ts":1493201312230,"q":0,"from":"system.adapter.harmony.0","lc":1493201291542} harmony.0 2017-04-26 12:08:32.234 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.activities.currentStatus {"val":0,"ack":true,"ts":1493201312230,"q":0,"from":"system.adapter.harmony.0","lc":1493201291542} harmony.0 2017-04-26 12:08:32.234 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.activities.currentActivity {"val":"PowerOff","ack":true,"ts":1493201312229,"q":0,"from":"system.adapter.harmony.0","lc":1493201291541} harmony.0 2017-04-26 12:08:32.234 debug redis publish io.harmony.0.Harmony_Hub.activities.LG_TV {"val":0,"ack":true,"ts":1493201312231,"q":0,"from":"system.adapter.harmony.0","lc":1492809570691} harmony.0 2017-04-26 12:08:32.234 debug redis publish io.harmony.0.Harmony_Hub.activities.TV {"val":0,"ack":true,"ts":1493201312230,"q":0,"from":"system.adapter.harmony.0","lc":1493201291542} harmony.0 2017-04-26 12:08:32.234 debug redis publish io.harmony.0.Harmony_Hub.activities.currentStatus {"val":0,"ack":true,"ts":1493201312230,"q":0,"from":"system.adapter.harmony.0","lc":1493201291542} harmony.0 2017-04-26 12:08:32.234 debug redis publish io.harmony.0.Harmony_Hub.activities.currentActivity {"val":"PowerOff","ack":true,"ts":1493201312229,"q":0,"from":"system.adapter.harmony.0","lc":1493201291541} harmony.0 2017-04-26 12:08:32.229 debug current activity: PowerOff harmony.0 2017-04-26 12:08:32.204 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.hubConnected {"val":true,"ack":true,"ts":1493201312202,"q":0,"from":"system.adapter.harmony.0","lc":1493201311422} harmony.0 2017-04-26 12:08:32.204 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.hubBlocked {"val":false,"ack":true,"ts":1493201312202,"q":0,"from":"system.adapter.harmony.0","lc":1493201312202} harmony.0 2017-04-26 12:08:32.204 debug redis publish io.harmony.0.Harmony_Hub.hubConnected {"val":true,"ack":true,"ts":1493201312202,"q":0,"from":"system.adapter.harmony.0","lc":1493201311422} harmony.0 2017-04-26 12:08:32.204 debug redis publish io.harmony.0.Harmony_Hub.hubBlocked {"val":false,"ack":true,"ts":1493201312202,"q":0,"from":"system.adapter.harmony.0","lc":1493201312202} harmony.0 2017-04-26 12:08:31.424 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.hubConnected {"val":true,"ack":true,"ts":1493201311422,"q":0,"from":"system.adapter.harmony.0","lc":1493201311422} harmony.0 2017-04-26 12:08:31.424 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.hubBlocked {"val":true,"ack":true,"ts":1493201311422,"q":0,"from":"system.adapter.harmony.0","lc":1493201311422} harmony.0 2017-04-26 12:08:31.424 debug redis publish io.harmony.0.Harmony_Hub.hubConnected {"val":true,"ack":true,"ts":1493201311422,"q":0,"from":"system.adapter.harmony.0","lc":1493201311422} harmony.0 2017-04-26 12:08:31.424 debug redis publish io.harmony.0.Harmony_Hub.hubBlocked {"val":true,"ack":true,"ts":1493201311422,"q":0,"from":"system.adapter.harmony.0","lc":1493201311422} harmony.0 2017-04-26 12:08:31.424 info connected to Harmony Hub harmony.0 2017-04-26 12:08:30.090 info connecting to Harmony Hub harmony.0 2017-04-26 12:08:30.089 info discovered Harmony Hub harmony.0 2017-04-26 12:08:26.792 debug xmpp offline harmony.0 2017-04-26 12:08:26.789 debug xmpp offline harmony.0 2017-04-26 12:08:26.771 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.hubBlocked {"val":false,"ack":true,"ts":1493201306770,"q":0,"from":"system.adapter.harmony.0","lc":1493201280245} harmony.0 2017-04-26 12:08:26.771 debug redis pmessage io.harmony.0.* io.harmony.0.Harmony_Hub.hubConnected {"val":false,"ack":true,"ts":1493201306769,"q":0,"from":"system.adapter.harmony.0","lc":1493201306769} harmony.0 2017-04-26 12:08:26.771 debug redis publish io.harmony.0.Harmony_Hub.hubBlocked {"val":false,"ack":true,"ts":1493201306770,"q":0,"from":"system.adapter.harmony.0","lc":1493201280245} harmony.0 2017-04-26 12:08:26.771 debug redis publish io.harmony.0.Harmony_Hub.hubConnected {"val":false,"ack":true,"ts":1493201306769,"q":0,"from":"system.adapter.harmony.0","lc":1493201306769} harmony.0 2017-04-26 12:08:26.771 warn client ended harmony.0 2017-04-26 12:08:26.771 debug xmpp offline harmony.0 2017-04-26 12:08:26.770 warn lost Harmony Hub harmony.0 2017-04-26 12:08:26.707 debug redis publish io.system.adapter.harmony.0.outputCount {"val":8,"ack":true,"ts":1493201306706,"q":0,"from":"system.adapter.harmony.0","lc":1493201306706} harmony.0 2017-04-26 12:08:26.707 debug redis publish io.system.adapter.harmony.0.inputCount {"val":0,"ack":true,"ts":1493201306706,"q":0,"from":"system.adapter.harmony.0","lc":1493201306706} harmony.0 2017-04-26 12:08:26.706 debug redis publish io.system.adapter.harmony.0.uptime {"val":106,"ack":true,"ts":1493201306706,"q":0,"from":"system.adapter.harmony.0","lc":1493201306706} harmony.0 2017-04-26 12:08:26.706 debug redis publish io.system.adapter.harmony.0.memHeapUsed {"val":21.67,"ack":true,"ts":1493201306705,"q":0,"from":"system.adapter.harmony.0","lc":1493201306705} harmony.0 2017-04-26 12:08:26.706 debug redis publish io.system.adapter.harmony.0.memHeapTotal {"val":30.78,"ack":true,"ts":1493201306705,"q":0,"from":"system.adapter.harmony.0","lc":1493201216696} harmony.0 2017-04-26 12:08:26.706 debug redis publish io.system.adapter.harmony.0.memRss {"val":42.67,"ack":true,"ts":1493201306704,"q":0,"from":"system.adapter.harmony.0","lc":1493201306704} harmony.0 2017-04-26 12:08:26.706 debug redis publish io.system.adapter.harmony.0.connected {"val":true,"ack":true,"ts":1493201306704,"q":0,"from":"system.adapter.harmony.0","lc":1493201201699} harmony.0 2017-04-26 12:08:26.706 debug redis publish io.system.adapter.harmony.0.alive {"val":true,"ack":true,"ts":1493201306704,"q":0,"from":"system.adapter.harmony.0","lc":1493201201698} !

Ich habe das gleiche Problem wie thronis.

Der Adapter startet immer dann neu, wenn ich eine Aktion ausführen möchte.

Die Fehler im LOG sind identisch wie im Screenshot von thronis gezeigt.

Was könnte dafür die Ursache sein?

LG,

Thorsten
2057_harmony_fehler.png

Da kann ich mich mit einreihen in das selbe Problem. Mein Log zeigt die gleiche Fehlermeldung an mit der 0.70 wie bei Thorsten.

In der 0.62 werden zwar keine Fehlermeldungen ausgegeben, jedoch Infos dass der Adapter neu gestartet wird.

Das passiert bei mir sobald ich eine activity auslöse, egal ob der Adapter die Harmony mal wieder verloren hat (ist offenbar ein Problem auf Logitech-Seite) oder nicht. Wäre super wenn es einen fix für die 0.70 bald gäbe.

Besten Dank im voraus!

Weitere Angaben wären schön, da ich es bei mir nicht reproduzieren kann. Also: Betriebssystem, Node Version, genaues Vorgehen wie es zu dem Fehler kommt.

Auch bitte mal das hier im Verzeichnis des Harmony Adapter ausführen und Ergebnis hier posten:

npm ls

Hallo Pman,

leider kann ich momentan nicht an meinen Rasberry dran.

Aber hier vorab paar Infos:

• Raspberry Pi 3 mit Raspbian Jessie (alles aktuell)

• node v6.10.2

• npm 3.10.10

Der Fehler taucht auf, sobald eine Aktion bzw. Activity ausgeführt werden soll, z.B "Alexa, Fernseher einschalten."

Diese Activity schaltet meinen TV, den Vodafone Receiver und den Verstärker ein.

Das Ergebnis aus "npm ls" liefere ich dir heute Abend noch nach.

Vielen Dank und Grüße

Fozi

Hallo alle zusammen,

Ich habe genau das gleich Problem wie ihr auch.

Leider bin ich noch neu und kenne mich kaum aus, sodass ich euch mit dem npm ls Befehl nicht weiter helfen kann :cry:

Das hier spuckt der Log aus.

host.raspberrypi   2017-05-03 02:41:06.981   info   Restart adapter system.adapter.harmony.0 because enabled
host.raspberrypi   2017-05-03 02:41:06.981   error   instance system.adapter.harmony.0 terminated with code 0 (OK)
harmony.0   2017-05-03 02:41:06.960   info   terminating
harmony.0   2017-05-03 02:41:06.937   warn   change activities, not currentActivity
harmony.0   2017-05-03 02:41:06.923   info   terminating
harmony.0   2017-05-03 02:41:06.920   error   at null._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3030:38)
harmony.0   2017-05-03 02:41:06.920   error   at Adapter.emit (events.js:172:7)
harmony.0   2017-05-03 02:41:06.920   error   at emitTwo (events.js:87:13)
harmony.0   2017-05-03 02:41:06.920   error   at Adapter. (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:34:15)
harmony.0   2017-05-03 02:41:06.920   error   at Object.semaphore.take (/opt/iobroker/node_modules/iobroker.harmony/node_modules/semaphore/lib/semaphore.js:45:9)
harmony.0   2017-05-03 02:41:06.920   error   at Object.item.task (/opt/iobroker/node_modules/iobroker.harmony/node_modules/semaphore/lib/semaphore.js:34:29)
harmony.0   2017-05-03 02:41:06.920   error   at /opt/iobroker/node_modules/iobroker.harmony/harmony.js:36:9
harmony.0   2017-05-03 02:41:06.920   error   at processStateChange (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:67:21)
harmony.0   2017-05-03 02:41:06.920   error   at switchActivity (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:137:92)
harmony.0   2017-05-03 02:41:06.920   error   at Promise.fin.Promise.finally (/opt/iobroker/node_modules/iobroker.harmony/node_modules/harmonyhubjs-client/node_modules/q/q.js:1775:15)
harmony.0   2017-05-03 02:41:06.920   error   Error: Q can't apply finally callback
harmony.0   2017-05-03 02:41:06.907   error   uncaught exception: Q can't apply finally callback
harmony.0   2017-05-03 02:40:39.602   warn   change activities, not currentActivity
harmony.0   2017-05-03 02:40:39.032   info   hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.activities.currentActivity=PowerOff
harmony.0   2017-05-03 02:40:25.498   info   synced hub config
harmony.0   2017-05-03 02:40:24.418   info   connected to Karim's Harmony Hub
harmony.0   2017-05-03 02:40:22.035   info   connecting to Karim's Harmony Hub
harmony.0   2017-05-03 02:40:21.919   info   discovered Karim's Harmony Hub
harmony.0   2017-05-03 02:40:20.660   info   searching for Harmony Hubs...
harmony.0   2017-05-03 02:40:20.615   info   starting. Version 0.7.0 in /opt/iobroker/node_modules/iobroker.harmony, node: v4.8.2
host.raspberrypi   2017-05-03 02:40:18.153   info   instance system.adapter.harmony.0 started with pid 10372
host.raspberrypi   2017-05-03 02:39:48.132   info   Restart adapter system.adapter.harmony.0 because enabled
host.raspberrypi   2017-05-03 02:39:48.131   error   instance system.adapter.harmony.0 terminated with code 0 (OK)
harmony.0   2017-05-03 02:39:48.106   info   terminating
harmony.0   2017-05-03 02:39:48.078   warn   change activities, not currentActivity
harmony.0   2017-05-03 02:39:48.055   info   terminating
harmony.0   2017-05-03 02:39:48.052   error   at null._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3030:38)
harmony.0   2017-05-03 02:39:48.052   error   at Adapter.emit (events.js:172:7)
harmony.0   2017-05-03 02:39:48.052   error   at emitTwo (events.js:87:13)
harmony.0   2017-05-03 02:39:48.052   error   at Adapter. (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:34:15)
harmony.0   2017-05-03 02:39:48.052   error   at Object.semaphore.take (/opt/iobroker/node_modules/iobroker.harmony/node_modules/semaphore/lib/semaphore.js:45:9)
harmony.0   2017-05-03 02:39:48.052   error   at Object.item.task (/opt/iobroker/node_modules/iobroker.harmony/node_modules/semaphore/lib/semaphore.js:34:29)
harmony.0   2017-05-03 02:39:48.052   error   at /opt/iobroker/node_modules/iobroker.harmony/harmony.js:36:9
harmony.0   2017-05-03 02:39:48.052   error   at processStateChange (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:67:21)
harmony.0   2017-05-03 02:39:48.052   error   at switchActivity (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:137:92)
harmony.0   2017-05-03 02:39:48.052   error   at Promise.fin.Promise.finally (/opt/iobroker/node_modules/iobroker.harmony/node_modules/harmonyhubjs-client/node_modules/q/q.js:1775:15)
harmony.0   2017-05-03 02:39:48.052   error   Error: Q can't apply finally callback
harmony.0   2017-05-03 02:39:48.040   error   uncaught exception: Q can't apply finally callback
harmony.0   2017-05-03 02:39:26.314   warn   change activities, not currentActivity
harmony.0   2017-05-03 02:39:25.585   info   hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.activities.currentActivity=PowerOff

Lieben Gruß, Karim.

@Pman:

Weitere Angaben wären schön, da ich es bei mir nicht reproduzieren kann. Also: Betriebssystem, Node Version, genaues Vorgehen wie es zu dem Fehler kommt.

Auch bitte mal das hier im Verzeichnis des Harmony Adapter ausführen und Ergebnis hier posten:

npm ls
```` `  

Betriebssystem:

ARMBIAN 5.25 stable Debian GNU/Linux 8 (jessie) 3.4.113-sun8i

Node:

7.9.0

npm:

4.2.0

Wie es zu dem Fehler kommt:

Ich starte Aktion indem ich Objekt harmony.0.HubWohn.activities.Fernsehen auf "2" setze. (entweder per Scene, als auch per Script, als auch per Alexa/Cloud Adapter)

(beim ausschalten, indem ich Objekt harmony.0.HubWohn.activities.Fernsehen auf "0" setze, passiert das nicht, da funktioniert es)

Log:

! 2017-05-02 20:57:41.192 - [31merror[39m: harmony.0 uncaught exception: Q can't apply finally callback
! 2017-05-02 20:57:41.219 - [31merror[39m: harmony.0 Error: Q can't apply finally callback
! at Promise.fin.Promise.finally (/opt/iobroker/node_modules/q/q.js:1775:15)
! at switchActivity (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:137:92)
! at processStateChange (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:67:21)
! at /opt/iobroker/node_modules/iobroker.harmony/harmony.js:36:9
! at Object.item.task (/opt/iobroker/node_modules/semaphore/lib/semaphore.js:34:29)
! at Object.take (/opt/iobroker/node_modules/semaphore/lib/semaphore.js:45:9)
! at Adapter. <anonymous>(/opt/iobroker/node_modules/iobroker.harmony/harmony.js:34:15)
! at emitTwo (events.js:106:13)
! at Adapter.emit (events.js:194:7)
! at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3030:38)
! 2017-05-02 20:57:41.226 - [32minfo[39m: harmony.0 terminating
! 2017-05-02 20:57:41.329 - [32minfo[39m: harmony.0 terminating
! 2017-05-02 20:57:41.490 - [31merror[39m: host.orangepiplus2e instance system.adapter.harmony.0 terminated with code 0 (OK)
! 2017-05-02 20:57:41.504 - [32minfo[39m: host.orangepiplus2e Restart adapter system.adapter.harmony.0 because enabled[/spoiler]</anonymous>
Ergebnis npm ls:
! root@orangepiplus2e:/opt/iobroker/node_modules/iobroker.harmony# npm ls
! iobroker.harmony@0.7.0 /opt/iobroker/node_modules/iobroker.harmony
! ├── UNMET DEPENDENCY harmonyhubjs-client@^1.1.10
! ├── UNMET DEPENDENCY harmonyhubjs-discover@^1.0.2
! └── UNMET DEPENDENCY semaphore@~1.0.3
! npm ERR! missing: harmonyhubjs-client@^1.1.10, required by iobroker.harmony@0.7.0
! npm ERR! missing: harmonyhubjs-discover@^1.0.2, required by iobroker.harmony@0.7.0
! npm ERR! missing: semaphore@~1.0.3, required by iobroker.harmony@0.7.0

Diese Logs helfen jetzt nicht, bei "npm ls" sollten eigentlich alle genutzten Module mit Version erscheinen.

Ich habe aber auch so einen Fehler gefunden, vielleicht hilft es schon, bitte von GIT testen.

https://github.com/Pmant/ioBroker.harmony

Ja aber du wolltest doch das npm ls ausdrücklich im Harmony Verzeichnis!?

Ich werde testen….

Hallo Pman, hier wie versprochen die Infos zu meinem Setting:

• Raspberry Pi 3 mit Raspbian Jessie (alles aktuell)

• node v6.10.3 (heute Abend kam das upgrade von 6.10.2 auf 6.10.3, aber mit 6.10.2 kommt das selbe Crashverhalten))

• npm 3.10.10

Die Ergebnisse aus "npm ls":

! ````
pi@raspberrypi:/opt/iobroker/node_modules $ npm ls
iobroker@1.0.0 /opt/iobroker
??? binrpc@1.0.0 extraneous
??? harmonyhubjs-client@1.1.10 extraneous
??? harmonyhubjs-discover@1.0.2 extraneous
??? homematic-xmlrpc@1.0.2 extraneous
??? iobroker@0.9.0 extraneous
??? iobroker.cloud@0.8.2 extraneous
??? iobroker.discovery@0.2.3 extraneous
??? iobroker.harmony@0.7.0 extraneous
??? iobroker.hm-rega@1.4.4 extraneous
??? iobroker.hm-rpc@1.4.6 extraneous
??? iobroker.hue@0.6.8 extraneous
??? iobroker.javascript@3.3.4 extraneous
??? iobroker.js-controller@1.0.0 extraneous
??? iobroker.scenes@0.2.6 extraneous
??? iobroker.simple-api@1.5.1 extraneous
??? iobroker.socketio@1.7.4 extraneous
??? iobroker.sonos@1.5.0 extraneous
??? iobroker.tr-064@0.3.15 extraneous
??? iobroker.vis@0.14.2 extraneous
??? iobroker.web@2.0.4 extraneous
??? jsonwebtoken@7.4.0 extraneous
??? mdns-discovery@0.1.12 extraneous
??? netmask@1.0.6 extraneous
??? node-hue-api@2.4.2 extraneous
??? node-ssdp@3.2.1 extraneous
??? semaphore@1.0.5 extraneous
??? soef@0.2.1 extraneous
??? tr-O64@0.2.4 extraneous
! npm ERR! extraneous: binrpc@1.0.0 /opt/iobroker/node_modules/binrpc
npm ERR! extraneous: harmonyhubjs-client@1.1.10 /opt/iobroker/node_modules/harmonyhubjs-client
npm ERR! extraneous: harmonyhubjs-discover@1.0.2 /opt/iobroker/node_modules/harmonyhubjs-discover
npm ERR! extraneous: homematic-xmlrpc@1.0.2 /opt/iobroker/node_modules/homematic-xmlrpc
npm ERR! extraneous: iobroker@0.9.0 /opt/iobroker/node_modules/iobroker
npm ERR! extraneous: iobroker.cloud@0.8.2 /opt/iobroker/node_modules/iobroker.cloud
npm ERR! extraneous: iobroker.discovery@0.2.3 /opt/iobroker/node_modules/iobroker.discovery
npm ERR! extraneous: iobroker.harmony@0.7.0 /opt/iobroker/node_modules/iobroker.harmony
npm ERR! extraneous: iobroker.hm-rega@1.4.4 /opt/iobroker/node_modules/iobroker.hm-rega
npm ERR! extraneous: iobroker.hm-rpc@1.4.6 /opt/iobroker/node_modules/iobroker.hm-rpc
npm ERR! extraneous: iobroker.hue@0.6.8 /opt/iobroker/node_modules/iobroker.hue
npm ERR! extraneous: iobroker.javascript@3.3.4 /opt/iobroker/node_modules/iobroker.javascript
npm ERR! extraneous: iobroker.js-controller@1.0.0 /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! extraneous: iobroker.scenes@0.2.6 /opt/iobroker/node_modules/iobroker.scenes
npm ERR! extraneous: iobroker.simple-api@1.5.1 /opt/iobroker/node_modules/iobroker.simple-api
npm ERR! extraneous: iobroker.socketio@1.7.4 /opt/iobroker/node_modules/iobroker.socketio
npm ERR! extraneous: iobroker.sonos@1.5.0 /opt/iobroker/node_modules/iobroker.sonos
npm ERR! extraneous: iobroker.tr-064@0.3.15 /opt/iobroker/node_modules/iobroker.tr-064
npm ERR! extraneous: iobroker.vis@0.14.2 /opt/iobroker/node_modules/iobroker.vis
npm ERR! extraneous: iobroker.web@2.0.4 /opt/iobroker/node_modules/iobroker.web
npm ERR! extraneous: jsonwebtoken@7.4.0 /opt/iobroker/node_modules/jsonwebtoken
npm ERR! extraneous: mdns-discovery@0.1.12 /opt/iobroker/node_modules/mdns-discovery
npm ERR! extraneous: netmask@1.0.6 /opt/iobroker/node_modules/netmask
npm ERR! extraneous: node-hue-api@2.4.2 /opt/iobroker/node_modules/node-hue-api
npm ERR! extraneous: node-ssdp@3.2.1 /opt/iobroker/node_modules/node-ssdp
npm ERR! extraneous: semaphore@1.0.5 /opt/iobroker/node_modules/semaphore
npm ERR! extraneous: soef@0.2.1 /opt/iobroker/node_modules/soef
npm ERR! extraneous: tr-O64@0.2.4 /opt/iobroker/node_modules/tr-O64

Hier die Fehler aus dem Log, wenn ich über "Alexa, Fernseher einschalten." die Activity "Fernsehen" aufrufe.

Der Adapter crashed und startet sich wieder.

Interessanterweise crashed er aber nicht, wenn ich die Activity mit "Alexa, schalte Fernseher aus." wieder beende.

>! ````
harmony.0	2017-05-03 20:19:16.002	info	synced hub config
harmony.0	2017-05-03 20:19:15.032	info	connected to Hub-Studio
harmony.0	2017-05-03 20:19:12.608	info	connecting to Hub-Studio
harmony.0	2017-05-03 20:19:12.464	info	discovered Hub-Studio
harmony.0	2017-05-03 20:19:11.109	info	searching for Harmony Hubs...
harmony.0	2017-05-03 20:19:11.060	info	starting. Version 0.7.0 in /opt/iobroker/node_modules/iobroker.harmony, node: v6.10.3
host.raspberrypi	2017-05-03 20:19:08.706	info	instance system.adapter.harmony.0 started with pid 1619
host.raspberrypi	2017-05-03 20:18:38.684	info	Restart adapter system.adapter.harmony.0 because enabled
host.raspberrypi	2017-05-03 20:18:38.683	error	instance system.adapter.harmony.0 terminated with code 0 (OK)
harmony.0	2017-05-03 20:18:38.656	info	terminating
harmony.0	2017-05-03 20:18:38.626	info	terminating
harmony.0	2017-05-03 20:18:38.622	error	at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:3030:38)
harmony.0	2017-05-03 20:18:38.622	error	at Adapter.emit (events.js:191:7)
harmony.0	2017-05-03 20:18:38.622	error	at emitTwo (events.js:106:13)
harmony.0	2017-05-03 20:18:38.622	error	at Adapter. (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:34:15)
harmony.0	2017-05-03 20:18:38.622	error	at Object.take (/opt/iobroker/node_modules/iobroker.harmony/node_modules/semaphore/lib/semaphore.js:45:9)
harmony.0	2017-05-03 20:18:38.622	error	at Object.item.task (/opt/iobroker/node_modules/iobroker.harmony/node_modules/semaphore/lib/semaphore.js:34:29)
harmony.0	2017-05-03 20:18:38.622	error	at /opt/iobroker/node_modules/iobroker.harmony/harmony.js:36:9
harmony.0	2017-05-03 20:18:38.622	error	at processStateChange (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:67:21)
harmony.0	2017-05-03 20:18:38.622	error	at switchActivity (/opt/iobroker/node_modules/iobroker.harmony/harmony.js:137:92)
harmony.0	2017-05-03 20:18:38.622	error	at Promise.fin.Promise.finally (/opt/iobroker/node_modules/iobroker.harmony/node_modules/q/q.js:1775:15)
harmony.0	2017-05-03 20:18:38.622	error	Error: Q can't apply finally callback
harmony.0	2017-05-03 20:18:38.620	error	uncaught exception: Q can't apply finally callback

Ich hoffe das hilft dir weiter!

Ich werde auch mal die neue Version aus Git testen und Rückmeldung geben.

Ich habe die 0.7.1 aus dem Git-Repo aufgespielt und der Adapter scheint nicht mehr abzustürtzen, es tauchen auch keine Fehler mehr auf im Log beim Start oder Beenden einer Activity.

Herzlichen Dank, Pman für die rasche Hilfe!

Sollte doch noch was auftauschen melde ich mich wieder.

Schönen Abend noch!

@andyb:

Ja aber du wolltest doch das npm ls ausdrücklich im Harmony Verzeichnis!?

Ich werde testen…. `
Stimmt, ab npm 3 sind die Module ja nicht mehr unbedingt im Unterverzeichnis, bei mir ist das noch so.

@Fozi:

Ich habe die 0.7.1 aus dem Git-Repo aufgespielt und der Adapter scheint nicht mehr abzustürtzen, es tauchen auch keine Fehler mehr auf im Log beim Start oder Beenden einer Activity.

Herzlichen Dank, Pman für die rasche Hilfe!

Sollte doch noch was auftauschen melde ich mich wieder.

Schönen Abend noch! `
Habe mal auf npm geladen, bin aber weiter für Feedback dankbar.

Mit diesem Button installieren.

@thronis:

Wer suchet der findet^^ `
Wer liest, auch :D

Schau mal in die Hilfe zu den Adaptern - da findest zu (fast) alles zu den Konfig-Möglichkeiten. ==> http://www.iobroker.net/?page_id=2236&lang=de

Gruß,

Eric

Von unterwegs getippert

Also es ist zwar besser geworden, aber es gibt immer noch Fehler.

Ich bin aber auch noch blutiger Anfänger, sodass ich keine Ahnung habe, was da schief läuft.

harmony.0	2017-05-04 22:17:57.313	info	synced hub config
harmony.0	2017-05-04 22:17:56.201	info	connected to Karim's Harmony Hub
harmony.0	2017-05-04 22:17:53.914	info	connecting to Karim's Harmony Hub
harmony.0	2017-05-04 22:17:53.804	info	discovered Karim's Harmony Hub
harmony.0	2017-05-04 22:17:50.826	warn	could not connect to Karim's Harmony Hub: Error: Timed out after 5000 ms
harmony.0	2017-05-04 22:17:40.800	info	keep alive failed: Error: Timed out after 5000 ms
harmony.0	2017-05-04 22:17:38.950	info	client ended: Karim's_Harmony_Hub
harmony.0	2017-05-04 22:17:38.943	warn	lost Karim's Harmony Hub
cloud.0	2017-05-04 22:09:22.453	info	Connection changed: CONNECTED1
cloud.0	2017-05-04 22:09:22.149	info	2017-05-04T20:09:22.149Z Connected system.user.admin
cloud.0	2017-05-04 22:09:12.005	info	Connection changed: DISCONNECTED1
cloud.0	2017-05-04 22:09:12.002	info	Connection changed: DISCONNECTED3
cloud.0	2017-05-04 22:09:11.995	error	Ping timeout
harmony.0	2017-05-04 22:05:13.450	warn	error sending command, client offline
harmony.0	2017-05-04 22:05:09.557	warn	error sending command, client offline
harmony.0	2017-05-04 22:05:09.540	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=0
harmony.0	2017-05-04 22:05:09.539	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=0
harmony.0	2017-05-04 22:04:45.548	warn	error sending command, client offline
harmony.0	2017-05-04 22:04:45.517	warn	error sending command, client offline
harmony.0	2017-05-04 22:04:45.475	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=1
harmony.0	2017-05-04 22:04:45.470	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Amazon_Fire_TV.Home=0
harmony.0	2017-05-04 22:04:45.470	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=1
harmony.0	2017-05-04 22:04:45.465	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Amazon_Fire_TV.Home=0
harmony.0	2017-05-04 20:57:16.266	warn	error sending command, client offline
harmony.0	2017-05-04 20:57:16.246	warn	error sending command, client offline
harmony.0	2017-05-04 20:57:16.239	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Philips-Fernseher.InputHdmi1=1
harmony.0	2017-05-04 20:57:16.235	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Philips-Fernseher.InputHdmi1=1
harmony.0	2017-05-04 20:57:12.454	warn	error sending command, client offline
harmony.0	2017-05-04 20:57:12.425	warn	error sending command, client offline
harmony.0	2017-05-04 20:57:12.395	warn	error sending command, client offline
harmony.0	2017-05-04 20:57:12.368	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=0
harmony.0	2017-05-04 20:57:12.367	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Amazon_Fire_TV.Home=1
harmony.0	2017-05-04 20:57:12.363	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=0
harmony.0	2017-05-04 20:57:12.356	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Amazon_Fire_TV.Home=1
harmony.0	2017-05-04 20:57:12.352	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Philips-Fernseher.PowerToggle=1
harmony.0	2017-05-04 20:57:12.343	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.Philips-Fernseher.PowerToggle=1
harmony.0	2017-05-04 20:44:46.107	warn	error sending command, client offline
hue.0	2017-05-04 20:44:42.433	info	final lightState for Philips_hue.Treppe:{"bri":254,"on":true,"level":100}
hue.0	2017-05-04 20:44:42.426	info	final lightState for Philips_hue.Sideboard:{"bri":254,"on":true,"level":100}
hue.0	2017-05-04 20:44:42.386	info	final lightState for Philips_hue.Pflanzen:{"bri":254,"on":true,"level":100}
hue.0	2017-05-04 20:44:42.375	info	final lightState for Philips_hue.Esszimmer:{"bri":254,"on":true,"level":100}
hue.0	2017-05-04 20:44:42.353	info	final lightState for Philips_hue.Couch:{"bri":254,"on":true,"level":100}
harmony.0	2017-05-04 20:44:42.263	warn	error sending command, client offline
harmony.0	2017-05-04 20:44:42.224	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=0
harmony.0	2017-05-04 20:44:42.223	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.AV-Receiver.PowerOff=0
harmony.0	2017-05-04 20:44:36.369	warn	change activities, not currentActivity
harmony.0	2017-05-04 20:44:36.031	warn	change activities, not currentActivity
harmony.0	2017-05-04 20:44:36.029	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.activities.currentActivity=Musik
harmony.0	2017-05-04 20:44:35.997	warn	error changing activity, client offline
harmony.0	2017-05-04 20:44:28.714	warn	change activities, not currentActivity
harmony.0	2017-05-04 20:44:28.478	info	hub busy, stateChange delayed: harmony.0.Karim's_Harmony_Hub.activities.currentActivity=Musik
harmony.0	2017-05-04 20:44:28.468	warn	change activities, not currentActivity
harmony.0	2017-05-04 20:44:28.461	warn	error changing activity, client offline
harmony.0	2017-05-04 20:43:09.516	warn	error sending command, client offline

Lieben Gruß, Karim.

@Karim:

Also es ist zwar besser geworden, aber es gibt immer noch Fehler.

Ich bin aber auch noch blutiger Anfänger, sodass ich keine Ahnung habe, was da schief läuft.

Lieben Gruß, Karim. `
In diesem Fall würde ich auf WLAN Probleme Tippen, einmal wird auch Cloud neu verbunden. Der Harmony Hub ist einfach extrem empfindlich, was das angeht. Ich habe den Hub jetzt 24 Stunden an einer weiter vom Router entfernten Stelle angeschlossen. Mein Log ist komplett voll mit Disconnects und oft auf darauf folgenden Abstürzen des Adapters, da sich der Hub beim Wiederverbinden teilweise schon wieder ausklinkt. Das positive ist, dass er schlussendlich immer wieder automatisch verbunden hat.

Als nächstes werde ich es nochmal direkt beim Router testen.