js-controller 2.0 ab sofort im Latest Repo

Meister Mopper

@apollon77
Alles klar.
Schönen Dank!

Diginix

@apollon77
Fertig konfiguriertes Objekt mit aktiver history und materialui Einstellungen:

{
  "from": "system.host.BT3-PRO.cli",
  "ts": 1573827041571,
  "user": "system.user.admin",
  "common": {
    "name": "Example state",
    "role": "switch",
    "type": "boolean",
    "read": true,
    "write": true,
    "def": false,
    "custom": {
      "history.0": {
        "enabled": true,
        "changesOnly": true,
        "debounce": 0,
        "maxLength": "100",
        "retention": "86400",
        "changesRelogInterval": 0,
        "changesMinDelta": 0,
        "aliasId": ""
      },
      "material": {
        "admin": {
          "name": "Example state",
          "colorOn": "rgba(255,155,0,1)",
          "doubleSize": "",
          "colorOff": "rgba(230,230,230,0.7)",
          "icon": "data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iaXNvLTg4NTktMSI/Pgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkNhcGFfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiCgkgdmlld0JveD0iMCAwIDUxMiA1MTIiIHN0eWxlPSJlbmFibGUtYmFja2dyb3VuZDpuZXcgMCAwIDUxMiA1MTI7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4KPGc+Cgk8cGF0aCBkPSJNMjk4LjY2NywyOTguNjY3YzE3LjY0MywwLDMyLTE0LjM1NywzMi0zMmMwLTE3LjY0My0xNC4zNTctMzItMzItMzJjLTE3LjY0MywwLTMyLDE0LjM1Ny0zMiwzMgoJCUMyNjYuNjY3LDI4NC4zMDksMjgxLjAyNCwyOTguNjY3LDI5OC42NjcsMjk4LjY2N3ogTTI5OC42NjcsMjU2YzUuODY3LDAsMTAuNjY3LDQuNzc5LDEwLjY2NywxMC42NjdzLTQuOCwxMC42NjctMTAuNjY3LDEwLjY2NwoJCWMtNS44NjcsMC0xMC42NjctNC43NzktMTAuNjY3LTEwLjY2N1MyOTIuOCwyNTYsMjk4LjY2NywyNTZ6Ii8+Cgk8cGF0aCBkPSJNNDQ4LDQ5MC42NjdoLTMydi00ODBDNDE2LDQuNzc5LDQxMS4yMjEsMCw0MDUuMzMzLDBIMTA2LjY2N2MtMC41OTcsMC0xLjEzMSwwLjI1Ni0xLjcwNywwLjM0MQoJCWMtMC41NTUsMC4wODUtMS4wODgsMC4xNDktMS42MjEsMC4zMmMtMC45MzksMC4zMi0xLjc0OSwwLjc4OS0yLjU2LDEuMzQ0Yy0wLjMyLDAuMjEzLTAuNzA0LDAuMjc3LTEuMDAzLDAuNTMzCgkJYy0wLjEwNywwLjA4NS0wLjE0OSwwLjIxMy0wLjI1NiwwLjMyYy0wLjc2OCwwLjcwNC0xLjM2NSwxLjU3OS0xLjg5OSwyLjQ5NmMtMC4yMTMsMC4zNDEtMC41MTIsMC42MTktMC42NjEsMC45ODEKCQlDOTYuMzYzLDcuNjgsOTYsOS4xMDksOTYsMTAuNjY3djQ4MEg2NGMtNS44ODgsMC0xMC42NjcsNC43NzktMTAuNjY3LDEwLjY2N0M1My4zMzMsNTA3LjIyMSw1OC4xMTIsNTEyLDY0LDUxMmg0Mi42NjcKCQljMC41NzYsMCwxLjE3My0wLjA0MywxLjc0OS0wLjE0OWwyNTYtNDIuNjY3YzUuMTQxLTAuODUzLDguOTE3LTUuMzEyLDguOTE3LTEwLjUxN1Y1My4zMzNjMC01LjIyNy0zLjc3Ni05LjY2NC04LjkxNy0xMC41MTcKCQlMMjM1LjU0MSwyMS4zMzNoMTU5LjEyNXY0ODBjMCw1Ljg4OCw0Ljc3OSwxMC42NjcsMTAuNjY3LDEwLjY2N0g0NDhjNS44ODgsMCwxMC42NjctNC43NzksMTAuNjY3LTEwLjY2NwoJCUM0NTguNjY3LDQ5NS40NDUsNDUzLjg4OCw0OTAuNjY3LDQ0OCw0OTAuNjY3eiBNMzUyLDYyLjM1N3YzODcuMjY0bC0yMzQuNjY3LDM5LjEyNVYyMy4yNTNMMzUyLDYyLjM1N3oiLz4KPC9nPgo8L3N2Zz4K",
          "iconOff": "data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iaXNvLTg4NTktMSI/Pgo8c3ZnIHZlcnNpb249IjEuMSIgaWQ9IkNhcGFfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeD0iMHB4IiB5PSIwcHgiCgkgdmlld0JveD0iMCAwIDUxMiA1MTIiIHN0eWxlPSJlbmFibGUtYmFja2dyb3VuZDpuZXcgMCAwIDUxMiA1MTI7IiB4bWw6c3BhY2U9InByZXNlcnZlIj4KPGc+Cgk8cGF0aCBkPSJNNDQ4LDQ5MC42NjdoLTMydi00ODBDNDE2LDQuNzc5LDQxMS4yMjEsMCw0MDUuMzMzLDBIMTA2LjY2N0MxMDAuNzc5LDAsOTYsNC43NzksOTYsMTAuNjY3djQ4MEg2NAoJCWMtNS44ODgsMC0xMC42NjcsNC43NzktMTAuNjY3LDEwLjY2N0M1My4zMzMsNTA3LjIyMSw1OC4xMTIsNTEyLDY0LDUxMmgzODRjNS44ODgsMCwxMC42NjctNC43NzksMTAuNjY3LTEwLjY2NwoJCUM0NTguNjY3LDQ5NS40NDUsNDUzLjg4OCw0OTAuNjY3LDQ0OCw0OTAuNjY3eiBNMzk0LjY2Nyw0OTAuNjY3SDExNy4zMzNWMjEuMzMzaDI3Ny4zMzNWNDkwLjY2N3oiLz4KCTxwYXRoIGQ9Ik0zNDEuMzMzLDI3Ny4zMzNjMTcuNjQzLDAsMzItMTQuMzU3LDMyLTMyYzAtMTcuNjQzLTE0LjM1Ny0zMi0zMi0zMmMtMTcuNjQzLDAtMzIsMTQuMzU3LTMyLDMyCgkJQzMwOS4zMzMsMjYyLjk3NiwzMjMuNjkxLDI3Ny4zMzMsMzQxLjMzMywyNzcuMzMzeiBNMzQxLjMzMywyMzQuNjY3YzUuODg4LDAsMTAuNjY3LDQuNzc5LDEwLjY2NywxMC42NjcKCQlTMzQ3LjIyMSwyNTYsMzQxLjMzMywyNTZzLTEwLjY2Ny00Ljc3OS0xMC42NjctMTAuNjY3UzMzNS40NDUsMjM0LjY2NywzNDEuMzMzLDIzNC42Njd6Ii8+CjwvZz4KPC9zdmc+Cg==",
          "background": "",
          "enabled": true
        }
      }
    }
  },
  "native": {},
  "acl": {
    "object": 1604,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator",
    "state": 1638
  },
  "_id": "0_userdata.0.example_state",
  "type": "state"
}

Danach klicke ich auf den Schraubenschlüssel ganz am Ende des Objektes im Adminadapter und ändere z.B. bei history die Vorhaltezeit von 1 Tag auf 3 Tage und speichere. In dem Moment wird der komplette material Block eliminiert.
Passiert natürlich auch bei Anpassungen andere Einstellungen des Objektes.

Das Objekt sieht dann so aus:

{
 "from": "system.host.BT3-PRO.cli",
 "ts": 1573827041571,
 "user": "system.user.admin",
 "common": {
   "name": "Example state",
   "role": "switch",
   "type": "boolean",
   "read": true,
   "write": true,
   "def": false,
   "custom": {
     "history.0": {
       "enabled": true,
       "changesOnly": true,
       "debounce": 0,
       "maxLength": "100",
       "retention": "259200",
       "changesRelogInterval": 0,
       "changesMinDelta": 0,
       "aliasId": ""
     }
   }
 },
 "native": {},
 "acl": {
   "object": 1604,
   "owner": "system.user.admin",
   "ownerGroup": "system.group.administrator",
   "state": 1638
 },
 "_id": "0_userdata.0.example_state",
 "type": "state"
}

apollon77

@Diginix Ok, ich kann es nachvollziehen und kläre gerade was

Diginix

@apollon77
Bin ja immer beruhigt wenn es sich bei anderen auch so verhält und reproduzierbar ist.
Warum muss ich eigentlich immer die Fehler finden.

apollon77

@Diginix
Generell war aber erst dein letzter Post hier der der es mich befähigt hat es nachzustellen. Ich persönlich bin der Meinung das der Bug in Material liegt und der es an einer falschen Stelle speichert ... schauen wir mal

Magst Du beim Tester-Team mit machen? @arteck sucht leute die erst erste Dinge testen wollen

Diginix

@apollon77
Wenn es Dinge sind die man einfach wieder zurückrollen kann, wie Adapter Versionen oder Einstellungen, die nichts an der Objektstruktur und Werten "versauen", kann ich gern testen. Ich sehe mein System aber als produktiv. Das JS-Controller Update habe ich also recht lange rausgezögert weil der Einfluss aufs System schon mächtiger ist, als ein einzelner Adapter.
Aber prinzipiell unterstütze ich gern wo ich kann, also darf mir @arteck gern mal Infos zukommen lassen wie das abläuft.

apollon77

@Diginix Solche tests über die wir da reden machen nur auf einem zweiten Testsystem Sinn.

Diginix

@apollon77
Ich habe noch einen PI3 der früher für den ioBroker geknechtet wurde.
Also auch machbar. Der muss ja sicher nur für den Zeitraum der Tests laufen.

apollon77

@Diginix Zum Beispiel :-))

ChrisXY

jemand erfahrungen mit dem firetv adapter ? Der scheint noch nicht zu laufen?

host.iobroker	2019-12-14 20:50:49.958	error	instance system.adapter.firetv.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at startup (internal/bootstrap/node.js:283:19)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:653:32)
host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:778:30)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.firetv/firetv.js:6:14)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:25:18)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:692:17)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:562:25)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: Error: Cannot find module './node_modules/adbkit/lib/adb/client'
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: ^
host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: throw err;
host.iobroker	2019-12-14 20:50:49.956	error	Caught by controller[0]: internal/modules/cjs/loader.js:638

apollon77

@ChrisXY das scheint weniger mit Controller 2 zu tun zu haben. Installiert den Adapter mal neu. Bzw GitHub issue öffnen.

frankyboy73

Hi, bei mir klappt es leider nicht mit dem Update. Nach dem Update Versuch geht leider gar nichts mehr und ich muss neu aufsetzten.
Ich habe nen Raspberry pi 4 und Raspian Buster drauf, neuste Version.
Folgendes habe ich als Ausgabe.

Update js-controller from @1.2.3 to @2.1.1
npm install iobroker.js-controller@2.1.1 --unsafe-perm  --production --prefix "/opt/iobroker" (System call)
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
In file included from ../src/unix_dgram.cc:5:
../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                              ^
In file included from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
../src/unix_dgram.cc: At global scope:
/home/iobroker/.cache/node-gyp/10.18.0/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
       (node::addon_register_func) (regfunc),                          \
                                           ^
/home/iobroker/.cache/node-gyp/10.18.0/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
   ^~~~~~~~~~~~~
../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
 NODE_MODULE(unix_dgram, Initialize)
 ^~~~~~~~~~~
In file included from /home/iobroker/.cache/node-gyp/10.18.0/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
/home/iobroker/.cache/node-gyp/10.18.0/include/node/node_object_wrap.h:84:78:   required from here
/home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                reinterpret_cast<Callback>(callback), type);
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
../../nan/nan_object_wrap.h:65:61:   required from here
/home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
(node:916) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
    at handleError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:190:15)
    at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:304:14)
(node:916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:916) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:916) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
    at handleError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:190:15)
    at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:304:14)
(node:916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)


╭─────────────────────────────────────────────────────────╮
│                                                         │
│ Manual installation of ioBroker is no longer supported  │
│ on Linux, OSX and FreeBSD!                              │
│ Please refer to the documentation on how to install it! │
│ https://github.com/ioBroker/ioBroker/wiki/Installation  │
│                                                         │
╰─────────────────────────────────────────────────────────╯


npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 100
npm ERR! iobroker@2.0.3 postinstall: `node lib/install.js`
npm ERR! Exit status 100
npm ERR!
npm ERR! Failed at the iobroker@2.0.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2020-01-14T16_45_21_540Z-debug.log
host.raspberrypi Cannot install iobroker.js-controller@2.1.1: 100

Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
Hier gehts zur Hilfe.

frankyboy73

Hi, ich habe das Problem gefunden. Ich hatte für meinen neuen PI 4 ein Backup vom Pi 3 genommen. Bei meiner Backup Variante speicher ich den Iobroker Data und den Node Modules Ordner und kopiere die für das Wiederherstellen wieder in den Iobroker Ordner. Damit habe ich dann wohl auf dem neuen System ein bisschen was vermurkst. Ich habe jetzt über mein System noch mal die Iobroker Installation drübergebügelt und es läuft alles inklusive js-controller Version 2.1.1

apollon77

@frankyboy73 node_modules zu kopieren ist eine extrem "blöde Idee" weil hier viel mit symbolischen Links und solchen Dingen gearbeitet wird die durch ein "Normales" copy kaputt gehen ... Aber super das Du es gelöst hast.

PS: WOW einen js.controller 1.2.3 hat ich schon ewig nimmer gesehn

frankyboy73

OK, da werde ich in Zukunft wohl doch nur noch die normale Backup Methode nutzen. Der Vorteil war, das man ruck zuck alles wieder am laufen hatte.

Lief bis jetzt alles super mit dem js-controller 1.2.3. Ich wollte nur auf größer 2 weil sonst der ALexa2 Adapter in der neuen Version nicht mehr geht.

Danke für deine Antwort/Info

gentlel

Kann hier jemand helfen? Hier funktioniert nichts mehr

iobroker:/opt/iobroker$ sudo npm install iobroker.js-controller@2.0.25

> iobroker.js-controller@2.0.25 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.13.0

> iobroker.js-controller@2.0.25 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iob.bat'
fs.js:114
    throw err;
    ^

Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../tmp'
    at Object.mkdirSync (fs.js:752:3)
    at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:586:58)
    at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:233:23)
    at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2312:5)
    at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:86)
    at Module._compile (internal/modules/cjs/loader.js:701:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
    at Module.load (internal/modules/cjs/loader.js:600:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
    at Function.Module._load (internal/modules/cjs/loader.js:531:3)
npm WARN ELOOP: too many symbolic links encountered, stat '/opt/iobroker/node_modules/noble'
npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.js-controller@2.0.25 install: `node iobroker.js setup first`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the iobroker.js-controller@2.0.25 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-01-17T20_16_38_051Z-debug.log

sigi234

@gentlel

Fixer mal laufen lassen?

gentlel

@sigi234 Ja aber der zeigt das hier an obwohl iobroker in /opt/iobroker ist

iobroker:~$ curl -sL https://iobroker.net/fix.sh | bash -

library: loaded
Library version=2020-01-13
ioBroker is not installed in /opt/iobroker! Cannot fix anything...

Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
Hier gehts zur Hilfe.

sigi234

@gentlel sagte in js-controller 2.0 ab sofort im Latest Repo:

@sigi234 Ja aber der zeigt das hier an obwohl iobroker in /opt/iobroker ist

iobroker:~$ curl -sL https://iobroker.net/fix.sh | bash -

library: loaded
Library version=2020-01-13
ioBroker is not installed in /opt/iobroker! Cannot fix anything...

Was kommt bei:

cd /opt/iobroker
iobroker list instances
node -v
nodejs -v
npm -v

gentlel

@sigi234 said in js-controller 2.0 ab sofort im Latest Repo:

iobroker list instances

elmar@iobroker:/opt/iobroker$ iobroker list instances
internal/modules/cjs/loader.js:584
    throw err;
    ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

node -v
v10.15.3
nodejs -v
npm -v
6.13.0

Bis gerade eben lief iobroker ganz normal. Dann habe ich die homematic adapter upgedatet und die wollten js controller 2.0 haben seit dem geht nichts mehr

Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
Hier gehts zur Hilfe.

NEWS