Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

seit Version 1.0.0 startet der Adapter nicht mehr #9

Closed
Shepherd7 opened this issue Dec 14, 2020 · 13 comments
Closed

seit Version 1.0.0 startet der Adapter nicht mehr #9

Shepherd7 opened this issue Dec 14, 2020 · 13 comments

Comments

@Shepherd7
Copy link

Shepherd7 commented Dec 14, 2020

bekomme ihn nicht gestartet.
erste Version 0.1.0 hat funktioniert.
Hoffe man kann damit was anfangen.
wenn ich Adapter starte unter debug bringt er das gleiche, also keine mehr infos.

System ist: Unraid 6.9RC1 mit docker Image von buanet.

Plattform: linux
Betriebssystem: linux
Die Architektur: x64
CPUs: 8
Geschwindigkeit: 3653 MHz
Modell: Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz
RAM: 7.6 GB
System-Betriebszeit: 2 T. 20:11:02
Node.js: v12.20.0
NPM: 6.14.8
Datenträgergröße: 20.0 GiB
Datenträger verfügbar: 11.9 GiB
Adapter-Anzahl: 382
Betriebszeit: 00:22:41
Aktive Instanzen: 11
js-controller 3.16

und

Home Assistent im docker unter Unraid

Version 2020.12.0
Installation Type Home Assistant Container
Development false
Supervisor false
Docker true
Virtual Environment false
Python Version 3.8.6
Operating System Family Linux
Operating System Version 5.9.13-Unraid
CPU Architecture x86_64
Timezone Europe/Berlin
host.8abf9d670426 2020-12-14 16:43:08.848 error instance system.adapter.hass.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.8abf9d670426 2020-12-14 16:43:08.848 error Caught by controller[0]: at internal/main/run_main_module.js:17:47
host.8abf9d670426 2020-12-14 16:43:08.848 error Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:708:14)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:863:32)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:999:30)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at Object. (/opt/iobroker/node_modules/iobroker.hass/main.js:399:5)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.hass/main.js:18:56)
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: ReferenceError: stop is not defined
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: ^
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: Object.assign(options, {name: adapterName, unload: stop});
host.8abf9d670426 2020-12-14 16:43:08.847 error Caught by controller[0]: /opt/iobroker/node_modules/iobroker.hass/main.js:18
host.8abf9d670426 2020-12-14 16:43:08.628 info instance system.adapter.hass.0 started with pid 491
@greatluis
Copy link

Leider bei mir dasselbe !
Wollte den Adater nutzen, jedoch erhalte ich die gleichen Fehlermeldungen

@EdgarM73
Copy link

dito, selber Fehler

@sudo0815
Copy link

Leider auch bei mir!?

@edicine
Copy link

edicine commented Dec 22, 2020

fuck hier geht auch nix mehr....und auf die alte 0.1.0 komme ich auch nicht mehr

@Shepherd7
Copy link
Author

Shepherd7 commented Dec 22, 2020

Habe einen fork gefunden der noch 0.1.0 ist.
Über katze in iobroker installieren und installiert 0.1.0 und verbindung geht.

https://github.com/alexalex89/ioBroker.hass.git

Hoffe aber da dieses Issues bearbeietet wird.

Liebe Grüße shepherd

@root01
Copy link

root01 commented Jan 20, 2021

Please fix v1.0.0 start issue.
Thanks

@techloverde
Copy link

Same problem here

@andreas-w2
Copy link

Same problem...
Previous version worked fine. Upgraded it and it stopped working. Appears to be a problem with the token?
Any forecast if and when there will be fix? If it helps... i can act as a tester if needed :-)

Anyone found a solution for the meantime?

@andreas-w2
Copy link

@GermanBluefox
Hi - sorry for bothering. Would be a nice present for easter 2021 to see a fix ;-)
thx

@sanstarr
Copy link

is this adapter dead?
thx for an answer

@andreas-w2
Copy link

Hi
@GermanBluefox We would love to hear from you...

@sanstarr Unfortunatly, nothing heard. I had opened a fork to see, if i could fix... .but found out: i am not a coder :-D

bye

@Apollon77
Copy link
Collaborator

Please try GitHub version and tell me if that works

@andreas-w2
Copy link

andreas-w2 commented Aug 23, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants