Adapter startet nicht mehr about iobroker.yahka

[peer69]

Gibts dazu eine Lösung? Den gleichen Fehler habe ich auch.

[GermanBluefox]

Habt ihr letzte Zeit node.js upgedated?

[peer69]

Ja. Allerdings kann ich da keinen unmittelbaren Zusammenhang herstellen. Ich habe testweise ein Full-Backup aus Januar mit entsprechenden Versionsständen wiederhergestellt und dort gab es plötzlich den gleichen Fehler. Auch ein Installieren alter Versionen des Adapters hat daran nichts geändert. Der Adapter kommt bei mir jetzt wieder hoch, den Fehler sehe ich aber im Log. Entsteht offenbar beim Stoppen des Adapters. Ist nicht ganz deckungsgleich zum Log von Basti8787 aber ähnlich:

https://pastebin.com/aV8f1K2F

[TA2k]

Das selbe hier
Node v8.11.3
Npm 6.1.0
yahka 0.8.0

error | by controller[35]: 2018-07-11T22:43:12.092Z engine.io-client:socket flushing 1 packets in socket
-- | --
Caught | 2018-07-12 00:43:12.146 | error | by controller[35]: 2018-07-11T22:43:12.091Z socket.io-parser encoded {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"options":{"
Caught | 2018-07-12 00:43:12.145 | error | by controller[34]: 2018-07-11T22:43:12.091Z socket.io-parser encoding packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"}],"opt
Caught | 2018-07-12 00:43:12.145 | error | by controller[34]: 2018-07-11T22:43:12.090Z socket.io-client:manager writing packet {"type":2,"data":["setState","system.adapter.yahka.0.alive",{"val":false,"ack":true,"from":"system.adapter.yahka.0"

[TA2k]

Socket.ios:
npm list socket.io
[email protected] /opt/iobroker
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ └─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ └── [email protected]
├─┬ [email protected]
│ └─┬ [email protected]
│ └── [email protected]
└── [email protected] extraneous

[TA2k]

Pause Yahka Adapter.
Restart iobroker machine
Rename the name of the bridge :yahka.0 to a simple name
Start Yahka Adapter

Simple name fix the detecting
Start as last instance fix the error.

[Basti8787]

What do you mean when saying "Rename ... to a simple name"? Do I have to actually rename the Adapter to "Yahka" for example?
Do I have to keep the different name?
Does this really fix the error or is it a work around wich will last as long as I keep the name other than the original?

[TA2k]

not the adapter name the name of the bridge device

simple means without special characters like dots

[Basti8787]

Okay, thanks. I'll try that out in about 8 hours or so.

[peer69]

Doesn't work for me. Still getting the errors from socket.io

[TA2k]

Did you pause the instance and restart the iobroker linux machine and start the instance as last ?

[peer69]

Yep. Thats what I did. Looks like a parsing error to me so yahka probably isn't the main cause of this error but I didn't see anything like this with any other adapter.

[TA2k]

I installed the 0.8.0
npm install https://github.com/jensweigele/ioBroker.yahka.git#develop --production --save --prefix "/opt/iobroker"
but there was only minor improvements

[Basti8787]

I already had chosen a different name.. do you really mean the name of the bridge or the serial?

[TA2k]

only name and it helps to count up username/mac

[Basti8787]

Unfortunately it also does not work for me, too

[Mr-REM-Esq]

I had chosen a different name too. Didn't restart the iobroker linux machine, only pause Yahka Adapter.
Now I see the bridge in my iPhone.