[gelöst] Keine Instanz nach Adapterinstallation
-
Habe meinen Adapter apsystems-ecu (Eigenentwicklung) modifiziert.
Testinstallation auf meinem Testsystem x86/W10 waren erfolgreich.Bei der Testinstallation auf meinem Produktivsystem wird keine Instanz angelegt. Auch fehlt der Konfigurationsdialog.
Testablauf/Umgebung Produktivsystem:
- Mein Produktivsystem
cat /etc/os-release NAME="Linux Mint" VERSION="19.3 (Tricia)" ID=linuxmint ID_LIKE=ubuntu PRETTY_NAME="Linux Mint 19.3" VERSION_ID="19.3" HOME_URL="https://www.linuxmint.com/" SUPPORT_URL="https://forums.linuxmint.com/" BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/" PRIVACY_POLICY_URL="https://www.linuxmint.com/" VERSION_CODENAME=tricia UBUNTU_CODENAME=bionic ... Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz 8GB RAM- iobroker version
$ iobroker version 3.3.22- Updates wurden durchgeführt
$ iobroker update -i Used repository: stable hash unchanged, use cached sources update done Adapter "admin" : 5.2.3 , installed 5.2.3 Adapter "alexa2" : 3.11.2 , installed 3.11.2 Adapter "backitup" : 2.2.3 , installed 2.2.3 Adapter "daswetter" : 3.0.9 , installed 3.0.9 Adapter "devices" : 1.0.9 , installed 1.0.9 Adapter "discovery" : 2.7.3 , installed 2.7.3 Adapter "echarts" : 1.0.3 , installed 1.0.3 Adapter "frontier_silicon": 0.0.10 , installed 0.0.10 Adapter "history" : 1.9.14 , installed 1.9.14 Adapter "homekit-controller": 0.3.3 , installed 0.3.3 Adapter "hue" : 3.5.31 , installed 3.5.31 Adapter "ical" : 1.11.4 , installed 1.11.4 Adapter "icons-addictive-flavour-png": 0.1.0 , installed 0.1.0 Adapter "icons-fatcow-hosting": 0.1.0 , installed 0.1.0 Adapter "icons-icons8" : 0.0.1 , installed 0.0.1 Adapter "icons-material-png": 0.1.0 , installed 0.1.0 Adapter "icons-material-svg": 0.1.0 , installed 0.1.0 Adapter "icons-mfd-png" : 1.0.2 , installed 1.0.2 Adapter "icons-mfd-svg" : 1.0.2 , installed 1.0.2 Adapter "icons-open-icon-library-png": 0.1.2 , installed 0.1.3 Adapter "icons-ultimate-png": 1.0.1 , installed 1.0.1 Adapter "influxdb" : 1.9.5 , installed 1.9.5 Adapter "info" : 1.9.8 , installed 1.9.8 Adapter "javascript" : 5.2.13 , installed 5.2.13 Controller "js-controller" : 3.3.22 , installed 3.3.22 Adapter "lovelace" : 2.0.6 , installed 2.1.4 Adapter "maxcube" : 1.0.4 , installed 1.0.4 Adapter "mqtt" : 2.4.0 , installed 2.4.0 Adapter "nina" : 0.0.25 , installed 0.0.25 Adapter "node-red" : 2.4.1 , installed 2.4.1 Adapter "octoprint" : 2.1.0 , installed 2.1.0 Adapter "ping" : 1.5.0 , installed 1.5.0 Adapter "simple-api" : 2.6.1 , installed 2.6.1 Adapter "socketio" : 3.1.5 , installed 3.1.5 Adapter "sonoff" : 2.4.5 , installed 2.4.5 Adapter "systeminfo" : 0.3.1 , installed 0.3.1 Adapter "tankerkoenig" : 2.1.1 , installed 2.1.1 Adapter "telegram" : 1.10.0 , installed 1.10.0 Adapter "tr-064" : 4.2.14 , installed 4.2.14 Adapter "trashschedule" : 1.4.1 , installed 1.4.1 Adapter "vis" : 1.4.5 , installed 1.4.5 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 0.1.5 , installed 0.1.5 Adapter "vis-colorpicker": 1.2.0 , installed 1.2.0 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets" : 1.1.7 , installed 1.1.7 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-justgage" : 1.0.2 , installed 1.0.2 Adapter "vis-keyboard" : 0.0.2 , installed 0.0.2 Adapter "vis-lcars" : 1.0.4 , installed 1.0.4 Adapter "vis-metro" : 1.1.2 , installed 1.1.2 Adapter "vis-plumb" : 1.0.2 , installed 1.0.2 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "vis-weather" : 2.5.5 , installed 2.5.5 Adapter "web" : 3.4.16 , installed 3.4.16 Adapter "windows-control": 0.1.5 , installed 0.1.5 Adapter "zigbee" : 1.6.6 , installed 1.6.6- Deinstallation der aktuellen Instanz unauffällig
- Neuinstallation des Adapters über iobroker/Adapter ist scheinbar OK
$ iobroker url https://github.com/npeter/ioBroker.apsystems-ecu --host BIGPETSH --debug install npeter/ioBroker.apsystems-ecu#b6a124f42df262ca04ef11130ec32e47e057cadf NPM version: 6.14.16 npm install npeter/ioBroker.apsystems-ecu#b6a124f42df262ca04ef11130ec32e47e057cadf --prefix "/opt/iobroker" (System call) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.7 (node_modules/iobroker.info/node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/chalk/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/virtual-device-sdk/package.json' + iobroker.apsystems-ecu@0.2.1added 6 packages from 26 contributors in 14.829s 88 packages are looking for funding run `npm fund` for details upload [4] apsystems-ecu.admin /opt/iobroker/node_modules/iobroker.apsystems-ecu/admin/words.js words.js application/javascript upload [3] apsystems-ecu.admin /opt/iobroker/node_modules/iobroker.apsystems-ecu/admin/style.css style.css text/css upload [2] apsystems-ecu.admin /opt/iobroker/node_modules/iobroker.apsystems-ecu/admin/index_m.html index_m.html text/html upload [1] apsystems-ecu.admin /opt/iobroker/node_modules/iobroker.apsystems-ecu/admin/apsystems-ecu.png apsystems-ecu.png image/png upload [0] apsystems-ecu.admin /opt/iobroker/node_modules/iobroker.apsystems-ecu/admin/admin.d.ts admin.d.ts video/mp2t Process exited with code 0- iobroker list adapters ist scheinbar OK
$ iobroker list adapters system.adapter.admin : admin - v5.2.3 system.adapter.alexa2 : alexa2 - v3.11.2 system.adapter.apsystems-ecu : apsystems-ecu - v0.2.1 ...- Instanz fehlt scheinbar
(base) bigpet@BIGPETSH:/opt/iobroker$ iobroker list instances + system.adapter.admin.0 : admin : BIGPETSH - enabled, port: 8181, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : BIGPETSH - enabled + system.adapter.backitup.0 : backitup : BIGPETSH - enabled- Die Instanz fehlt scheinbar:- Es wurde der Adaper-Creator verwendet
/* * Created with @iobroker/create-adapter v1.26.3 */ // The adapter-core module gives you access to the core ioBroker functions // you need to create an adapter const utils = require('@iobroker/adapter-core'); const myEcu = require('./lib/ecu'); // Load your modules here, e.g.: // const fs = require("fs"); class ApsystemsEcu extends utils.Adapter { /** * @param {Partial<utils.AdapterOptions>} [options={}] */ constructor(options) { super({ ...options, name: 'apsystems-ecu', }); this.ecu = new myEcu.Ecu(this); this.on('ready', this.onReady.bind(this)); this.on('stateChange', this.onStateChange.bind(this)); // this.on('objectChange', this.onObjectChange.bind(this)); // this.on('message', this.onMessage.bind(this)); this.on('unload', this.onUnload.bind(this)); } /** * Is called when databases are connected and adapter received configuration. */ async onReady() { // Reset the connection indicator during startup this.setState('info.connection', false, true); this.ecu.init(); } /** * Is called when adapter shuts down - callback has to be called under any circumstances! * @param {() => void} callback */ onUnload(callback) { try { this.ecu.unload(); callback(); } catch (e) { callback(); } } // If you need to react to object changes, uncomment the following block and the corresponding line in the constructor. // You also need to subscribe to the objects with `this.subscribeObjects`, similar to `this.subscribeStates`. // /** // * Is called if a subscribed object changes // * @param {string} id // * @param {ioBroker.Object | null | undefined} obj // */ // onObjectChange(id, obj) { // if (obj) { // // The object was changed // this.log.info(`object ${id} changed: ${JSON.stringify(obj)}`); // } else { // // The object was deleted // this.log.info(`object ${id} deleted`); // } // } /** * Is called if a subscribed state changes * @param {string} id * @param {ioBroker.State | null | undefined} state */ onStateChange(id, state) { if (state) { // The state was changed this.ecu.onStateChange(id, state); this.log.info(`state ${id} changed: ${state.val} (ack = ${state.ack})`); } else { // The state was deleted this.log.info(`state ${id} deleted`); } } // If you need to accept messages in your adapter, uncomment the following block and the corresponding line in the constructor. // /** // * Some message was sent to this instance over message box. Used by email, pushover, text2speech, ... // * Using this method requires "common.message" property to be set to true in io-package.json // * @param {ioBroker.Message} obj // */ // onMessage(obj) { // if (typeof obj === 'object' && obj.message) { // if (obj.command === 'send') { // // e.g. send email or pushover or whatever // this.log.info('send command'); // // Send response in callback if required // if (obj.callback) this.sendTo(obj.from, obj.command, 'Message received', obj.callback); // } // } // } } // @ts-ignore parent is a valid property on module if (module.parent) { // Export the constructor in compact mode /** * @param {Partial<utils.AdapterOptions>} [options={}] */ module.exports = (options) => new ApsystemsEcu(options); } else { // otherwise start the instance directly new ApsystemsEcu(); }Wäre schön, wenn jemand einen Tip für mich hätte! Fehlen noch Informationen?
Danke und Grüße -
@peter_n
Manuelle Installation außerhalb der Repositories bedarf einer manuellen Instanz. -
@peter_n sagte in [Frage] Keine Instanz nach Adapterinstallation:
Bei der Testinstallation auf meinem Produktivsystem wird keine Instanz angelegt. Auch fehlt der Konfigurationsdialog.
letzteres kommt erst mit der Instanz. Diese erst nach manueller Instanzierung
-
@homoran said in [Frage] Keine Instanz nach Adapterinstallation:
letzteres kommt erst mit der Instanz. Diese erst nach manueller Instanzierung
Viele Danke für die Hilfe.
Hat mit dem manuellen Anlegen der Instanz funktioniert!Eine Detailfrage:
Warum ging das im NOV 2021 scheinbar noch? Auch hat scheinbar ein Testbenutzer die Installation Erstversion ohne manuelle Instantierung erfolgreich geschafft! -
@peter_n sagte in [Frage] Keine Instanz nach Adapterinstallation:
Warum ging das im NOV 2021 scheinbar noch?
Das ging noch nie.
-
OK Danke!
-
@peter_n said in [gelöst] Keine Instanz nach Adapterinstallation:
OK Danke!
