VIS - No Connection
-
Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)heißt auch das der Adapter nicht gestartet ist.
systemctl start iobrokerUnd danach mal in das Log schauen:
tail -n 100 /opt/iobroker/log/iobroker.current.loguns schauen was da steht wenn er es nicht schaffen sollte zu starten (und hier posten)
@bananajoe sagte in VIS - No Connection:
Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)heißt auch das der Adapter nicht gestartet ist.
systemctl start iobrokerUnd danach mal in das Log schauen:
tail -n 100 /opt/iobroker/log/iobroker.current.loguns schauen was da steht wenn er es nicht schaffen sollte zu starten (und hier posten)
anbei die Eingabe und die Ausgabe....
pi@raspberrypi:~ $ systemctl start iobroker ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to start 'iobroker.service'. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === pi@raspberrypi:~ $ tail -n 100 /opt/iobroker/log/iobroker.current.log 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=false) 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=false) 2022-02-01 18:39:47.690 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.2 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.ical.0 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.ical.1 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.shelly.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.synology.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.tr-064.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.weatherunderground.0 (force=false, process=false) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.binance.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.daswetter.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.dwd.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.eufy-security.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fb-checkpresence.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fritzbox.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.gartenbewaesserung.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.info.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.logparser.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.mercedesme.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.mihome-lamp.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.snmp.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sourceanalytix.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sprinklecontrol.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.tankerkoenig.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.upnp.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-inventwo.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-plumb.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-rgraph.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=true) 2022-02-01 18:39:47.728 - info: backitup.0 (1499) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.733 - info: web.0 (1639) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.736 - info: backitup.0 (1499) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.737 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal 2022-02-01 18:39:47.727 - info: alexa2.0 (1588) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.739 - info: web.0 (1639) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.740 - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal 2022-02-01 18:39:47.741 - info: host.raspberrypi stopInstance system.adapter.web.0 send kill signal 2022-02-01 18:39:47.742 - info: alexa2.0 (1588) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:48.739 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 killing pid 1588 2022-02-01 18:39:48.742 - info: host.raspberrypi stopInstance system.adapter.backitup.0 killing pid 1499 2022-02-01 18:39:48.743 - info: host.raspberrypi stopInstance system.adapter.web.0 killing pid 1639 2022-02-01 18:39:55.804 - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.805 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.865 - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.866 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.924 - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.925 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:56.503 - info: host.raspberrypi terminated 2022-02-01 21:08:11.162 - info: host.raspberrypi iobroker.js-controller version 3.3.22 js-controller starting 2022-02-01 21:08:11.169 - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2022-02-01 21:08:11.170 - info: host.raspberrypi hostname: raspberrypi, node: v14.19.0 2022-02-01 21:08:11.170 - info: host.raspberrypi ip addresses: 192.168.178.36 fe80::32fa:9c31:3feb:e244 2022-02-01 21:10:27.194 - info: host.raspberrypi connected to Objects and States 2022-02-01 21:10:27.443 - info: host.raspberrypi added notifications configuration of host 2022-02-01 21:10:28.420 - info: host.raspberrypi 51 instances found 2022-02-01 21:10:28.511 - info: host.raspberrypi starting 4 instances 2022-02-01 21:10:28.538 - warn: host.raspberrypi startInstance cannot find adapter "eufy-security@0.7.4". Try to install it... 1 attempt 2022-02-01 21:10:28.539 - info: host.raspberrypi iobroker install eufy-security@0.7.4 using installedFrom 2022-02-01 21:10:28.843 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 1454 2022-02-01 21:10:30.810 - info: alexa2.0 (1454) starting. Version 3.12.0 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:34.536 - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 1469 2022-02-01 21:10:34.786 - error: host.raspberrypi iobroker npm-install: host.raspberrypi Unknown packetName eufy-security 2022-02-01 21:10:34.803 - info: host.raspberrypi iobroker npm-install: host.raspberrypi download eufy-securityFile not found: eufy-security 2022-02-01 21:10:34.837 - info: host.raspberrypi iobroker npm-install: exit 1 2022-02-01 21:10:36.513 - info: alexa2.0 (1454) Alexa-Push-Connection (macDms = true) established. Disable Polling 2022-02-01 21:10:36.561 - info: backitup.0 (1469) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:36.728 - info: backitup.0 (1469) [iobroker] backup was activated at 11:20 every 1 day(s) 2022-02-01 21:10:36.871 - info: alexa2.0 (1454) Unknown Device, but enabling commands, Try it and report back if commands work. 2022-02-01 21:10:36.872 - info: alexa2.0 (1454) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2022-02-01 21:10:36.873 - info: alexa2.0 (1454) Device-type:A2N49KXGVA18AR (REMINDERS,VOLUME_SETTING,ASX_TIME_ZONE,ADAPTIVE_LISTENING,SUPPORTS_SOFTWARE_VERSION,MICROPHONE,TIMERS_AND_ALARMS,NO_TIME_ZONE_SETTING,PERSISTENT_CONNECTION) 2022-02-01 21:10:36.976 - info: backitup.0 (1469) [ccu] backup was activated at 01:30 every 3 day(s) 2022-02-01 21:10:38.534 - info: vis.0 (1484) starting. Version 1.4.6 in /opt/iobroker/node_modules/iobroker.vis, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:38.797 - info: vis.0 (1484) vis license is OK. 2022-02-01 21:10:40.528 - info: vis.0 (1484) Changes in index.html detected => update cache.manifest 2022-02-01 21:10:40.581 - info: vis.0 (1484) Upload vis anew, while changes detected... 2022-02-01 21:10:40.734 - info: host.raspberrypi instance system.adapter.web.0 started with pid 1534 2022-02-01 21:10:43.444 - info: web.0 (1534) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:43.735 - info: host.raspberrypi "system.adapter.vis.0" disabled 2022-02-01 21:10:43.737 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.758 - info: host.raspberrypi "system.adapter.vis.0" enabled 2022-02-01 21:10:43.759 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.980 - info: web.0 (1534) socket.io server listening on port 8082 2022-02-01 21:10:43.986 - info: web.0 (1534) http server listening on port 8082 2022-02-01 21:10:53.614 - info: alexa2.0 (1454) Subscribing to states... 2022-02-01 21:10:53.615 - info: alexa2.0 (1454) Deleting the following states: ["Echo-Devices.G070VM14937317FB.Info.multiroomParents"] 2022-02-01 21:11:33.380 - info: vis.0 (1484) Uploaded. 0 2022-02-01 21:11:33.894 - info: vis.0 (1484) Terminated (NO_ERROR): Without reason 2022-02-01 21:11:34.603 - info: host.raspberrypi instance system.adapter.vis.0 terminated while should be started once pi@raspberrypi:~ $ -
@bananajoe sagte in VIS - No Connection:
Loaded: loaded (/lib/systemd/system/iobroker.service; enabled; vendor preset: enabled)heißt auch das der Adapter nicht gestartet ist.
systemctl start iobrokerUnd danach mal in das Log schauen:
tail -n 100 /opt/iobroker/log/iobroker.current.loguns schauen was da steht wenn er es nicht schaffen sollte zu starten (und hier posten)
anbei die Eingabe und die Ausgabe....
pi@raspberrypi:~ $ systemctl start iobroker ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units === Authentication is required to start 'iobroker.service'. Authenticating as: ,,, (pi) Password: ==== AUTHENTICATION COMPLETE === pi@raspberrypi:~ $ tail -n 100 /opt/iobroker/log/iobroker.current.log 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=false) 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=false) 2022-02-01 18:39:47.690 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.2 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.ical.0 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.ical.1 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.shelly.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.synology.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.tr-064.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.weatherunderground.0 (force=false, process=false) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.binance.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.daswetter.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.dwd.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.eufy-security.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fb-checkpresence.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fritzbox.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.gartenbewaesserung.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.info.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.logparser.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.mercedesme.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.mihome-lamp.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.snmp.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sourceanalytix.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sprinklecontrol.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.tankerkoenig.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.upnp.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-inventwo.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-plumb.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-rgraph.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=true) 2022-02-01 18:39:47.728 - info: backitup.0 (1499) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.733 - info: web.0 (1639) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.736 - info: backitup.0 (1499) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.737 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal 2022-02-01 18:39:47.727 - info: alexa2.0 (1588) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.739 - info: web.0 (1639) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.740 - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal 2022-02-01 18:39:47.741 - info: host.raspberrypi stopInstance system.adapter.web.0 send kill signal 2022-02-01 18:39:47.742 - info: alexa2.0 (1588) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:48.739 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 killing pid 1588 2022-02-01 18:39:48.742 - info: host.raspberrypi stopInstance system.adapter.backitup.0 killing pid 1499 2022-02-01 18:39:48.743 - info: host.raspberrypi stopInstance system.adapter.web.0 killing pid 1639 2022-02-01 18:39:55.804 - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.805 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.865 - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.866 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.924 - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.925 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:56.503 - info: host.raspberrypi terminated 2022-02-01 21:08:11.162 - info: host.raspberrypi iobroker.js-controller version 3.3.22 js-controller starting 2022-02-01 21:08:11.169 - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2022-02-01 21:08:11.170 - info: host.raspberrypi hostname: raspberrypi, node: v14.19.0 2022-02-01 21:08:11.170 - info: host.raspberrypi ip addresses: 192.168.178.36 fe80::32fa:9c31:3feb:e244 2022-02-01 21:10:27.194 - info: host.raspberrypi connected to Objects and States 2022-02-01 21:10:27.443 - info: host.raspberrypi added notifications configuration of host 2022-02-01 21:10:28.420 - info: host.raspberrypi 51 instances found 2022-02-01 21:10:28.511 - info: host.raspberrypi starting 4 instances 2022-02-01 21:10:28.538 - warn: host.raspberrypi startInstance cannot find adapter "eufy-security@0.7.4". Try to install it... 1 attempt 2022-02-01 21:10:28.539 - info: host.raspberrypi iobroker install eufy-security@0.7.4 using installedFrom 2022-02-01 21:10:28.843 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 1454 2022-02-01 21:10:30.810 - info: alexa2.0 (1454) starting. Version 3.12.0 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:34.536 - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 1469 2022-02-01 21:10:34.786 - error: host.raspberrypi iobroker npm-install: host.raspberrypi Unknown packetName eufy-security 2022-02-01 21:10:34.803 - info: host.raspberrypi iobroker npm-install: host.raspberrypi download eufy-securityFile not found: eufy-security 2022-02-01 21:10:34.837 - info: host.raspberrypi iobroker npm-install: exit 1 2022-02-01 21:10:36.513 - info: alexa2.0 (1454) Alexa-Push-Connection (macDms = true) established. Disable Polling 2022-02-01 21:10:36.561 - info: backitup.0 (1469) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:36.728 - info: backitup.0 (1469) [iobroker] backup was activated at 11:20 every 1 day(s) 2022-02-01 21:10:36.871 - info: alexa2.0 (1454) Unknown Device, but enabling commands, Try it and report back if commands work. 2022-02-01 21:10:36.872 - info: alexa2.0 (1454) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2022-02-01 21:10:36.873 - info: alexa2.0 (1454) Device-type:A2N49KXGVA18AR (REMINDERS,VOLUME_SETTING,ASX_TIME_ZONE,ADAPTIVE_LISTENING,SUPPORTS_SOFTWARE_VERSION,MICROPHONE,TIMERS_AND_ALARMS,NO_TIME_ZONE_SETTING,PERSISTENT_CONNECTION) 2022-02-01 21:10:36.976 - info: backitup.0 (1469) [ccu] backup was activated at 01:30 every 3 day(s) 2022-02-01 21:10:38.534 - info: vis.0 (1484) starting. Version 1.4.6 in /opt/iobroker/node_modules/iobroker.vis, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:38.797 - info: vis.0 (1484) vis license is OK. 2022-02-01 21:10:40.528 - info: vis.0 (1484) Changes in index.html detected => update cache.manifest 2022-02-01 21:10:40.581 - info: vis.0 (1484) Upload vis anew, while changes detected... 2022-02-01 21:10:40.734 - info: host.raspberrypi instance system.adapter.web.0 started with pid 1534 2022-02-01 21:10:43.444 - info: web.0 (1534) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:43.735 - info: host.raspberrypi "system.adapter.vis.0" disabled 2022-02-01 21:10:43.737 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.758 - info: host.raspberrypi "system.adapter.vis.0" enabled 2022-02-01 21:10:43.759 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.980 - info: web.0 (1534) socket.io server listening on port 8082 2022-02-01 21:10:43.986 - info: web.0 (1534) http server listening on port 8082 2022-02-01 21:10:53.614 - info: alexa2.0 (1454) Subscribing to states... 2022-02-01 21:10:53.615 - info: alexa2.0 (1454) Deleting the following states: ["Echo-Devices.G070VM14937317FB.Info.multiroomParents"] 2022-02-01 21:11:33.380 - info: vis.0 (1484) Uploaded. 0 2022-02-01 21:11:33.894 - info: vis.0 (1484) Terminated (NO_ERROR): Without reason 2022-02-01 21:11:34.603 - info: host.raspberrypi instance system.adapter.vis.0 terminated while should be started once pi@raspberrypi:~ $@pahan sagte in VIS - No Connection:
eufy-security
als du den Befehl ausgeführt hast (tail) war er noch am starten
läuft er denn jetzt? Wenn nicht den tail wiederholen und was noch zum obigen fehlt posten.
Dereufy-securityspackt rum, ansonsten sieht es gar nicht so schlecht aus -
@pahan sagte in VIS - No Connection:
eufy-security
als du den Befehl ausgeführt hast (tail) war er noch am starten
läuft er denn jetzt? Wenn nicht den tail wiederholen und was noch zum obigen fehlt posten.
Dereufy-securityspackt rum, ansonsten sieht es gar nicht so schlecht aus@bananajoe sagte in VIS - No Connection:
@pahan sagte in VIS - No Connection:
eufy-security
als du den Befehl ausgeführt hast (tail) war er noch am starten
läuft er denn jetzt? Wenn nicht den tail wiederholen und was noch zum obigen fehlt posten.
Dereufy-securityspackt rum, ansonsten sieht es gar nicht so schlecht ausja, mit dem eufy adapter scheint es in letzter Zeit Schwierigkeiten zu geben, aber ich befürchte in meinem Fall deutlich größere Probleme bekommen zu haben...zumindest startet der iobroker auch nach einer längerer Wartezeit leider nicht. Anbei die aktuelle Ausgabe des tails..:
pi@raspberrypi:~ $ tail -n 100 /opt/iobroker/log/iobroker.current.log 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=false) 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=false) 2022-02-01 18:39:47.690 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.2 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.ical.0 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.ical.1 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.shelly.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.synology.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.tr-064.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.weatherunderground.0 (force=false, process=false) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.binance.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.daswetter.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.dwd.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.eufy-security.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fb-checkpresence.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fritzbox.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.gartenbewaesserung.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.info.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.logparser.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.mercedesme.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.mihome-lamp.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.snmp.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sourceanalytix.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sprinklecontrol.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.tankerkoenig.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.upnp.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-inventwo.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-plumb.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-rgraph.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=true) 2022-02-01 18:39:47.728 - info: backitup.0 (1499) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.733 - info: web.0 (1639) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.736 - info: backitup.0 (1499) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.737 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal 2022-02-01 18:39:47.727 - info: alexa2.0 (1588) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.739 - info: web.0 (1639) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.740 - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal 2022-02-01 18:39:47.741 - info: host.raspberrypi stopInstance system.adapter.web.0 send kill signal 2022-02-01 18:39:47.742 - info: alexa2.0 (1588) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:48.739 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 killing pid 1588 2022-02-01 18:39:48.742 - info: host.raspberrypi stopInstance system.adapter.backitup.0 killing pid 1499 2022-02-01 18:39:48.743 - info: host.raspberrypi stopInstance system.adapter.web.0 killing pid 1639 2022-02-01 18:39:55.804 - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.805 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.865 - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.866 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.924 - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.925 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:56.503 - info: host.raspberrypi terminated 2022-02-01 21:08:11.162 - info: host.raspberrypi iobroker.js-controller version 3.3.22 js-controller starting 2022-02-01 21:08:11.169 - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2022-02-01 21:08:11.170 - info: host.raspberrypi hostname: raspberrypi, node: v14.19.0 2022-02-01 21:08:11.170 - info: host.raspberrypi ip addresses: 192.168.178.36 fe80::32fa:9c31:3feb:e244 2022-02-01 21:10:27.194 - info: host.raspberrypi connected to Objects and States 2022-02-01 21:10:27.443 - info: host.raspberrypi added notifications configuration of host 2022-02-01 21:10:28.420 - info: host.raspberrypi 51 instances found 2022-02-01 21:10:28.511 - info: host.raspberrypi starting 4 instances 2022-02-01 21:10:28.538 - warn: host.raspberrypi startInstance cannot find adapter "eufy-security@0.7.4". Try to install it... 1 attempt 2022-02-01 21:10:28.539 - info: host.raspberrypi iobroker install eufy-security@0.7.4 using installedFrom 2022-02-01 21:10:28.843 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 1454 2022-02-01 21:10:30.810 - info: alexa2.0 (1454) starting. Version 3.12.0 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:34.536 - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 1469 2022-02-01 21:10:34.786 - error: host.raspberrypi iobroker npm-install: host.raspberrypi Unknown packetName eufy-security 2022-02-01 21:10:34.803 - info: host.raspberrypi iobroker npm-install: host.raspberrypi download eufy-securityFile not found: eufy-security 2022-02-01 21:10:34.837 - info: host.raspberrypi iobroker npm-install: exit 1 2022-02-01 21:10:36.513 - info: alexa2.0 (1454) Alexa-Push-Connection (macDms = true) established. Disable Polling 2022-02-01 21:10:36.561 - info: backitup.0 (1469) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:36.728 - info: backitup.0 (1469) [iobroker] backup was activated at 11:20 every 1 day(s) 2022-02-01 21:10:36.871 - info: alexa2.0 (1454) Unknown Device, but enabling commands, Try it and report back if commands work. 2022-02-01 21:10:36.872 - info: alexa2.0 (1454) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2022-02-01 21:10:36.873 - info: alexa2.0 (1454) Device-type:A2N49KXGVA18AR (REMINDERS,VOLUME_SETTING,ASX_TIME_ZONE,ADAPTIVE_LISTENING,SUPPORTS_SOFTWARE_VERSION,MICROPHONE,TIMERS_AND_ALARMS,NO_TIME_ZONE_SETTING,PERSISTENT_CONNECTION) 2022-02-01 21:10:36.976 - info: backitup.0 (1469) [ccu] backup was activated at 01:30 every 3 day(s) 2022-02-01 21:10:38.534 - info: vis.0 (1484) starting. Version 1.4.6 in /opt/iobroker/node_modules/iobroker.vis, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:38.797 - info: vis.0 (1484) vis license is OK. 2022-02-01 21:10:40.528 - info: vis.0 (1484) Changes in index.html detected => update cache.manifest 2022-02-01 21:10:40.581 - info: vis.0 (1484) Upload vis anew, while changes detected... 2022-02-01 21:10:40.734 - info: host.raspberrypi instance system.adapter.web.0 started with pid 1534 2022-02-01 21:10:43.444 - info: web.0 (1534) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:43.735 - info: host.raspberrypi "system.adapter.vis.0" disabled 2022-02-01 21:10:43.737 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.758 - info: host.raspberrypi "system.adapter.vis.0" enabled 2022-02-01 21:10:43.759 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.980 - info: web.0 (1534) socket.io server listening on port 8082 2022-02-01 21:10:43.986 - info: web.0 (1534) http server listening on port 8082 2022-02-01 21:10:53.614 - info: alexa2.0 (1454) Subscribing to states... 2022-02-01 21:10:53.615 - info: alexa2.0 (1454) Deleting the following states: ["Echo-Devices.G070VM14937317FB.Info.multiroomParents"] 2022-02-01 21:11:33.380 - info: vis.0 (1484) Uploaded. 0 2022-02-01 21:11:33.894 - info: vis.0 (1484) Terminated (NO_ERROR): Without reason 2022-02-01 21:11:34.603 - info: host.raspberrypi instance system.adapter.vis.0 terminated while should be started once pi@raspberrypi:~ $ -
@bananajoe sagte in VIS - No Connection:
@pahan sagte in VIS - No Connection:
eufy-security
als du den Befehl ausgeführt hast (tail) war er noch am starten
läuft er denn jetzt? Wenn nicht den tail wiederholen und was noch zum obigen fehlt posten.
Dereufy-securityspackt rum, ansonsten sieht es gar nicht so schlecht ausja, mit dem eufy adapter scheint es in letzter Zeit Schwierigkeiten zu geben, aber ich befürchte in meinem Fall deutlich größere Probleme bekommen zu haben...zumindest startet der iobroker auch nach einer längerer Wartezeit leider nicht. Anbei die aktuelle Ausgabe des tails..:
pi@raspberrypi:~ $ tail -n 100 /opt/iobroker/log/iobroker.current.log 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=false) 2022-02-01 18:39:47.689 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=false) 2022-02-01 18:39:47.690 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.2 (force=false, process=false) 2022-02-01 18:39:47.691 - info: host.raspberrypi stopInstance system.adapter.ical.0 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.ical.1 (force=false, process=false) 2022-02-01 18:39:47.692 - info: host.raspberrypi stopInstance system.adapter.mihome-vacuum.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.shelly.0 (force=false, process=false) 2022-02-01 18:39:47.693 - info: host.raspberrypi stopInstance system.adapter.synology.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.tr-064.0 (force=false, process=false) 2022-02-01 18:39:47.694 - info: host.raspberrypi stopInstance system.adapter.weatherunderground.0 (force=false, process=false) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.backitup.0 (force=false, process=true) 2022-02-01 18:39:47.695 - info: host.raspberrypi stopInstance system.adapter.binance.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.daswetter.0 (force=false, process=false) 2022-02-01 18:39:47.696 - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.dwd.0 (force=false, process=false) 2022-02-01 18:39:47.697 - info: host.raspberrypi stopInstance system.adapter.eufy-security.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fb-checkpresence.0 (force=false, process=false) 2022-02-01 18:39:47.698 - info: host.raspberrypi stopInstance system.adapter.fritzbox.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.gartenbewaesserung.0 (force=false, process=false) 2022-02-01 18:39:47.699 - info: host.raspberrypi stopInstance system.adapter.info.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.logparser.0 (force=false, process=false) 2022-02-01 18:39:47.700 - info: host.raspberrypi stopInstance system.adapter.mercedesme.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.mihome-lamp.0 (force=false, process=false) 2022-02-01 18:39:47.701 - info: host.raspberrypi stopInstance system.adapter.snmp.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sourceanalytix.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.sprinklecontrol.0 (force=false, process=false) 2022-02-01 18:39:47.702 - info: host.raspberrypi stopInstance system.adapter.tankerkoenig.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.trashschedule.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.upnp.0 (force=false, process=false) 2022-02-01 18:39:47.703 - info: host.raspberrypi stopInstance system.adapter.vis-canvas-gauges.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-hqwidgets.0 (force=false, process=false) 2022-02-01 18:39:47.704 - info: host.raspberrypi stopInstance system.adapter.vis-inventwo.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false) 2022-02-01 18:39:47.705 - info: host.raspberrypi stopInstance system.adapter.vis-plumb.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-rgraph.0 (force=false, process=false) 2022-02-01 18:39:47.706 - info: host.raspberrypi stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=false) 2022-02-01 18:39:47.707 - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=true) 2022-02-01 18:39:47.728 - info: backitup.0 (1499) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.733 - info: web.0 (1639) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.736 - info: backitup.0 (1499) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.737 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 send kill signal 2022-02-01 18:39:47.727 - info: alexa2.0 (1588) Got terminate signal TERMINATE_YOURSELF 2022-02-01 18:39:47.739 - info: web.0 (1639) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:47.740 - info: host.raspberrypi stopInstance system.adapter.backitup.0 send kill signal 2022-02-01 18:39:47.741 - info: host.raspberrypi stopInstance system.adapter.web.0 send kill signal 2022-02-01 18:39:47.742 - info: alexa2.0 (1588) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2022-02-01 18:39:48.739 - info: host.raspberrypi stopInstance system.adapter.alexa2.0 killing pid 1588 2022-02-01 18:39:48.742 - info: host.raspberrypi stopInstance system.adapter.backitup.0 killing pid 1499 2022-02-01 18:39:48.743 - info: host.raspberrypi stopInstance system.adapter.web.0 killing pid 1639 2022-02-01 18:39:55.804 - info: host.raspberrypi instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.805 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.865 - info: host.raspberrypi instance system.adapter.alexa2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.866 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:55.924 - info: host.raspberrypi instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2022-02-01 18:39:55.925 - info: host.raspberrypi All instances are stopped. 2022-02-01 18:39:56.503 - info: host.raspberrypi terminated 2022-02-01 21:08:11.162 - info: host.raspberrypi iobroker.js-controller version 3.3.22 js-controller starting 2022-02-01 21:08:11.169 - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2022-02-01 21:08:11.170 - info: host.raspberrypi hostname: raspberrypi, node: v14.19.0 2022-02-01 21:08:11.170 - info: host.raspberrypi ip addresses: 192.168.178.36 fe80::32fa:9c31:3feb:e244 2022-02-01 21:10:27.194 - info: host.raspberrypi connected to Objects and States 2022-02-01 21:10:27.443 - info: host.raspberrypi added notifications configuration of host 2022-02-01 21:10:28.420 - info: host.raspberrypi 51 instances found 2022-02-01 21:10:28.511 - info: host.raspberrypi starting 4 instances 2022-02-01 21:10:28.538 - warn: host.raspberrypi startInstance cannot find adapter "eufy-security@0.7.4". Try to install it... 1 attempt 2022-02-01 21:10:28.539 - info: host.raspberrypi iobroker install eufy-security@0.7.4 using installedFrom 2022-02-01 21:10:28.843 - info: host.raspberrypi instance system.adapter.alexa2.0 started with pid 1454 2022-02-01 21:10:30.810 - info: alexa2.0 (1454) starting. Version 3.12.0 in /opt/iobroker/node_modules/iobroker.alexa2, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:34.536 - info: host.raspberrypi instance system.adapter.backitup.0 started with pid 1469 2022-02-01 21:10:34.786 - error: host.raspberrypi iobroker npm-install: host.raspberrypi Unknown packetName eufy-security 2022-02-01 21:10:34.803 - info: host.raspberrypi iobroker npm-install: host.raspberrypi download eufy-securityFile not found: eufy-security 2022-02-01 21:10:34.837 - info: host.raspberrypi iobroker npm-install: exit 1 2022-02-01 21:10:36.513 - info: alexa2.0 (1454) Alexa-Push-Connection (macDms = true) established. Disable Polling 2022-02-01 21:10:36.561 - info: backitup.0 (1469) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:36.728 - info: backitup.0 (1469) [iobroker] backup was activated at 11:20 every 1 day(s) 2022-02-01 21:10:36.871 - info: alexa2.0 (1454) Unknown Device, but enabling commands, Try it and report back if commands work. 2022-02-01 21:10:36.872 - info: alexa2.0 (1454) Report to developer as GitHub issue with details for device. Please grab full next line pot. from logfile on disk if cutted 2022-02-01 21:10:36.873 - info: alexa2.0 (1454) Device-type:A2N49KXGVA18AR (REMINDERS,VOLUME_SETTING,ASX_TIME_ZONE,ADAPTIVE_LISTENING,SUPPORTS_SOFTWARE_VERSION,MICROPHONE,TIMERS_AND_ALARMS,NO_TIME_ZONE_SETTING,PERSISTENT_CONNECTION) 2022-02-01 21:10:36.976 - info: backitup.0 (1469) [ccu] backup was activated at 01:30 every 3 day(s) 2022-02-01 21:10:38.534 - info: vis.0 (1484) starting. Version 1.4.6 in /opt/iobroker/node_modules/iobroker.vis, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:38.797 - info: vis.0 (1484) vis license is OK. 2022-02-01 21:10:40.528 - info: vis.0 (1484) Changes in index.html detected => update cache.manifest 2022-02-01 21:10:40.581 - info: vis.0 (1484) Upload vis anew, while changes detected... 2022-02-01 21:10:40.734 - info: host.raspberrypi instance system.adapter.web.0 started with pid 1534 2022-02-01 21:10:43.444 - info: web.0 (1534) starting. Version 3.4.16 in /opt/iobroker/node_modules/iobroker.web, node: v14.19.0, js-controller: 3.3.22 2022-02-01 21:10:43.735 - info: host.raspberrypi "system.adapter.vis.0" disabled 2022-02-01 21:10:43.737 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.758 - info: host.raspberrypi "system.adapter.vis.0" enabled 2022-02-01 21:10:43.759 - info: host.raspberrypi stopInstance system.adapter.vis.0 (force=false, process=true) 2022-02-01 21:10:43.980 - info: web.0 (1534) socket.io server listening on port 8082 2022-02-01 21:10:43.986 - info: web.0 (1534) http server listening on port 8082 2022-02-01 21:10:53.614 - info: alexa2.0 (1454) Subscribing to states... 2022-02-01 21:10:53.615 - info: alexa2.0 (1454) Deleting the following states: ["Echo-Devices.G070VM14937317FB.Info.multiroomParents"] 2022-02-01 21:11:33.380 - info: vis.0 (1484) Uploaded. 0 2022-02-01 21:11:33.894 - info: vis.0 (1484) Terminated (NO_ERROR): Without reason 2022-02-01 21:11:34.603 - info: host.raspberrypi instance system.adapter.vis.0 terminated while should be started once pi@raspberrypi:~ $ich sehe keine Admin-Instanz in deinen Logs. ist auf Port 8082 was erreichbar?
-
@bananajoe sagte in VIS - No Connection:
ich sehe keine Admin-Instanz in deinen Logs. ist auf Port 8082 was erreichbar?
in der Tat, auf port 8082 ist die alte VIS erreichbar,
auf port 8081 nach wie vor nichts -
@bananajoe sagte in VIS - No Connection:
ich sehe keine Admin-Instanz in deinen Logs. ist auf Port 8082 was erreichbar?
in der Tat, auf port 8082 ist die alte VIS erreichbar,
auf port 8081 nach wie vor nichts@pahan sagte in VIS - No Connection:
@bananajoe sagte in VIS - No Connection:
ich sehe keine Admin-Instanz in deinen Logs. ist auf Port 8082 was erreichbar?
in der Tat, auf port 8082 ist die alte VIS erreichbar,
auf port 8081 nach wie vor nichtsich habe auch schon eine admin-instanz hinzugefügt, nun habe zwei davon, aber keine davon funktioniert.
-
@bananajoe sagte in VIS - No Connection:
ich sehe keine Admin-Instanz in deinen Logs. ist auf Port 8082 was erreichbar?
in der Tat, auf port 8082 ist die alte VIS erreichbar,
auf port 8081 nach wie vor nichts@pahan sagte in VIS - No Connection:
auf port 8081 nach wie vor nichts
dann fangen wir mal wieder von vorne an! Bitte aktuelle Ausgabe von:
iobroker list instances -
@homoran sagte in VIS - No Connection:
iobroker list instancesgibt aus:
pi@raspberrypi:~ $ iobroker list instances system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.admin.1 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.binance.0 : binance : raspberrypi - disabled system.adapter.daswetter.0 : daswetter : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.dwd.0 : dwd : raspberrypi - disabled system.adapter.email.0 : email : raspberrypi - disabled system.adapter.eufy-security.0 : eufy-security : raspberrypi - disabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.fritzbox.0 : fritzbox : raspberrypi - disabled system.adapter.gartenbewaesserung.0 : gartenbewaesserung : raspberrypi - disabled system.adapter.history.0 : history : raspberrypi - disabled system.adapter.hm-rega.0 : hm-rega : raspberrypi - disabled system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - disabled, port: 18701 system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - disabled, port: 12001 system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - disabled, port: 12010 system.adapter.ical.0 : ical : raspberrypi - disabled system.adapter.ical.1 : ical : raspberrypi - disabled system.adapter.icons-fatcow-hosting.0 : icons-fatcow-hosting : raspberrypi - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled system.adapter.influxdb.0 : influxdb : raspberrypi - disabled, port: 8086 system.adapter.info.0 : info : raspberrypi - disabled system.adapter.iot.0 : iot : raspberrypi - disabled system.adapter.javascript.0 : javascript : raspberrypi - disabled system.adapter.logparser.0 : logparser : raspberrypi - disabled system.adapter.mercedesme.0 : mercedesme : raspberrypi - disabled system.adapter.mihome-lamp.0 : mihome-lamp : raspberrypi - disabled, port: 54321 system.adapter.mihome-vacuum.0 : mihome-vacuum : raspberrypi - disabled, port: 54321 system.adapter.shelly.0 : shelly : raspberrypi - disabled, port: 1882, bind: 0.0.0.0 system.adapter.snmp.0 : snmp : raspberrypi - disabled system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - disabled system.adapter.sprinklecontrol.0 : sprinklecontrol : raspberrypi - disabled system.adapter.synology.0 : synology : raspberrypi - disabled, port: 5000 system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - disabled system.adapter.tr-064.0 : tr-064 : raspberrypi - disabled system.adapter.trashschedule.0 : trashschedule : raspberrypi - disabled system.adapter.upnp.0 : upnp : raspberrypi - disabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : raspberrypi - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - disabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberrypi - disabled system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : raspberrypi - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - disabled system.adapter.vis-plumb.0 : vis-plumb : raspberrypi - disabled system.adapter.vis-rgraph.0 : vis-rgraph : raspberrypi - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - disabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive pi@raspberrypi:~ $ -
@homoran sagte in VIS - No Connection:
iobroker list instancesgibt aus:
pi@raspberrypi:~ $ iobroker list instances system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.admin.1 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.binance.0 : binance : raspberrypi - disabled system.adapter.daswetter.0 : daswetter : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.dwd.0 : dwd : raspberrypi - disabled system.adapter.email.0 : email : raspberrypi - disabled system.adapter.eufy-security.0 : eufy-security : raspberrypi - disabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.fritzbox.0 : fritzbox : raspberrypi - disabled system.adapter.gartenbewaesserung.0 : gartenbewaesserung : raspberrypi - disabled system.adapter.history.0 : history : raspberrypi - disabled system.adapter.hm-rega.0 : hm-rega : raspberrypi - disabled system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - disabled, port: 18701 system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - disabled, port: 12001 system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - disabled, port: 12010 system.adapter.ical.0 : ical : raspberrypi - disabled system.adapter.ical.1 : ical : raspberrypi - disabled system.adapter.icons-fatcow-hosting.0 : icons-fatcow-hosting : raspberrypi - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled system.adapter.influxdb.0 : influxdb : raspberrypi - disabled, port: 8086 system.adapter.info.0 : info : raspberrypi - disabled system.adapter.iot.0 : iot : raspberrypi - disabled system.adapter.javascript.0 : javascript : raspberrypi - disabled system.adapter.logparser.0 : logparser : raspberrypi - disabled system.adapter.mercedesme.0 : mercedesme : raspberrypi - disabled system.adapter.mihome-lamp.0 : mihome-lamp : raspberrypi - disabled, port: 54321 system.adapter.mihome-vacuum.0 : mihome-vacuum : raspberrypi - disabled, port: 54321 system.adapter.shelly.0 : shelly : raspberrypi - disabled, port: 1882, bind: 0.0.0.0 system.adapter.snmp.0 : snmp : raspberrypi - disabled system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - disabled system.adapter.sprinklecontrol.0 : sprinklecontrol : raspberrypi - disabled system.adapter.synology.0 : synology : raspberrypi - disabled, port: 5000 system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - disabled system.adapter.tr-064.0 : tr-064 : raspberrypi - disabled system.adapter.trashschedule.0 : trashschedule : raspberrypi - disabled system.adapter.upnp.0 : upnp : raspberrypi - disabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : raspberrypi - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - disabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberrypi - disabled system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : raspberrypi - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - disabled system.adapter.vis-plumb.0 : vis-plumb : raspberrypi - disabled system.adapter.vis-rgraph.0 : vis-rgraph : raspberrypi - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - disabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive pi@raspberrypi:~ $@pahan sagte in VIS - No Connection:
admin.1
iobroker del iobroker.admin.1 iobroker start iobroker.admin.0 -
@homoran sagte in VIS - No Connection:
iobroker list instancesgibt aus:
pi@raspberrypi:~ $ iobroker list instances system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.admin.1 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : raspberrypi - enabled + system.adapter.backitup.0 : backitup : raspberrypi - enabled system.adapter.binance.0 : binance : raspberrypi - disabled system.adapter.daswetter.0 : daswetter : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.dwd.0 : dwd : raspberrypi - disabled system.adapter.email.0 : email : raspberrypi - disabled system.adapter.eufy-security.0 : eufy-security : raspberrypi - disabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.fritzbox.0 : fritzbox : raspberrypi - disabled system.adapter.gartenbewaesserung.0 : gartenbewaesserung : raspberrypi - disabled system.adapter.history.0 : history : raspberrypi - disabled system.adapter.hm-rega.0 : hm-rega : raspberrypi - disabled system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - disabled, port: 18701 system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - disabled, port: 12001 system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - disabled, port: 12010 system.adapter.ical.0 : ical : raspberrypi - disabled system.adapter.ical.1 : ical : raspberrypi - disabled system.adapter.icons-fatcow-hosting.0 : icons-fatcow-hosting : raspberrypi - disabled system.adapter.icons-mfd-png.0 : icons-mfd-png : raspberrypi - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled system.adapter.influxdb.0 : influxdb : raspberrypi - disabled, port: 8086 system.adapter.info.0 : info : raspberrypi - disabled system.adapter.iot.0 : iot : raspberrypi - disabled system.adapter.javascript.0 : javascript : raspberrypi - disabled system.adapter.logparser.0 : logparser : raspberrypi - disabled system.adapter.mercedesme.0 : mercedesme : raspberrypi - disabled system.adapter.mihome-lamp.0 : mihome-lamp : raspberrypi - disabled, port: 54321 system.adapter.mihome-vacuum.0 : mihome-vacuum : raspberrypi - disabled, port: 54321 system.adapter.shelly.0 : shelly : raspberrypi - disabled, port: 1882, bind: 0.0.0.0 system.adapter.snmp.0 : snmp : raspberrypi - disabled system.adapter.sourceanalytix.0 : sourceanalytix : raspberrypi - disabled system.adapter.sprinklecontrol.0 : sprinklecontrol : raspberrypi - disabled system.adapter.synology.0 : synology : raspberrypi - disabled, port: 5000 system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - disabled system.adapter.tr-064.0 : tr-064 : raspberrypi - disabled system.adapter.trashschedule.0 : trashschedule : raspberrypi - disabled system.adapter.upnp.0 : upnp : raspberrypi - disabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : raspberrypi - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - disabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberrypi - disabled system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : raspberrypi - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : raspberrypi - disabled system.adapter.vis-plumb.0 : vis-plumb : raspberrypi - disabled system.adapter.vis-rgraph.0 : vis-rgraph : raspberrypi - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - disabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - disabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive pi@raspberrypi:~ $@pahan sagte in VIS - No Connection:
system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.admin.1 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: adminbeide auf Port 8081 geht ja auch nicht.
deswegen laufen wahrscheinlich beide nicht mehriobroker start admin.0 -
@pahan sagte in VIS - No Connection:
system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.admin.1 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0, run as: adminbeide auf Port 8081 geht ja auch nicht.
deswegen laufen wahrscheinlich beide nicht mehriobroker start admin.0 -
@homoran sagte in VIS - No Connection:
iobroker start admin.0er ist angesprungen, vielen vielen Dank für Eure Unterstützung !!!
-
aber jetzt mal eine generelle Frage zum Abschluss:
ich werde es in Zukunft sein lassen, auf Beta zu laufen, diese habe ich in den Einstellungen auch schon gelöscht.
Was empfiehlt sich nun, alle Adapter auf die stable Version downzugraden oder das doch so laufen zu lassen? -
aber jetzt mal eine generelle Frage zum Abschluss:
ich werde es in Zukunft sein lassen, auf Beta zu laufen, diese habe ich in den Einstellungen auch schon gelöscht.
Was empfiehlt sich nun, alle Adapter auf die stable Version downzugraden oder das doch so laufen zu lassen?@pahan sagte in VIS - No Connection:
Was empfiehlt sich nun, alle Adapter auf die stable Version downzugraden oder das doch so laufen zu lassen?
wenn jetzt (wirklich) keine Probleme mehr sind lässt du das Repo auf stable.
Irgendwann sind die jetzigen Verionen dann auch da drin. Danach kommen auch dort weitere Upgrades -
aber jetzt mal eine generelle Frage zum Abschluss:
ich werde es in Zukunft sein lassen, auf Beta zu laufen, diese habe ich in den Einstellungen auch schon gelöscht.
Was empfiehlt sich nun, alle Adapter auf die stable Version downzugraden oder das doch so laufen zu lassen?@pahan sagte in VIS - No Connection:
aber jetzt mal eine generelle Frage zum Abschluss:
ich werde es in Zukunft sein lassen, auf Beta zu laufen, diese habe ich in den Einstellungen auch schon gelöscht.
Was empfiehlt sich nun, alle Adapter auf die stable Version downzugraden oder das doch so laufen zu lassen?Öhm, du kannst auch alles auf Beta laufen lassen (mache ich zum Beispiel). Dann solltest du aber halt eine gute Backup-Strategie haben für den Fall es es mal Mist ist (hatte ich aber erst einmal).
Mein ioBroker läuft in einer VM (virtuelle Maschine), da hab ich eine Kopie des kompletten Systems. Und/oder ich kann Snapshots machen (Zustand einfrieren um später dahin zurück springen zu können.)Im Prinzip könnet die Komplettsicherung des Ordners
/opt/iobrokerreichen wenn ich mich nicht irre. Der müsste im Fehlerfall gelöscht und wieder zurückkopiert werden (unter Beibehaltung aller Besitzer und Berechtigungen).Wenn man das eher scheut dann halt auf Stable bleiben (aber selbst da hätte ich gerne ein simples Backup. Ich liebe VMs einfach)
-
@pahan sagte in VIS - No Connection:
aber jetzt mal eine generelle Frage zum Abschluss:
ich werde es in Zukunft sein lassen, auf Beta zu laufen, diese habe ich in den Einstellungen auch schon gelöscht.
Was empfiehlt sich nun, alle Adapter auf die stable Version downzugraden oder das doch so laufen zu lassen?Öhm, du kannst auch alles auf Beta laufen lassen (mache ich zum Beispiel). Dann solltest du aber halt eine gute Backup-Strategie haben für den Fall es es mal Mist ist (hatte ich aber erst einmal).
Mein ioBroker läuft in einer VM (virtuelle Maschine), da hab ich eine Kopie des kompletten Systems. Und/oder ich kann Snapshots machen (Zustand einfrieren um später dahin zurück springen zu können.)Im Prinzip könnet die Komplettsicherung des Ordners
/opt/iobrokerreichen wenn ich mich nicht irre. Der müsste im Fehlerfall gelöscht und wieder zurückkopiert werden (unter Beibehaltung aller Besitzer und Berechtigungen).Wenn man das eher scheut dann halt auf Stable bleiben (aber selbst da hätte ich gerne ein simples Backup. Ich liebe VMs einfach)
Hallo liebe Community,
ihr habt mir kürzlich sehr geholfen und ich hatte meinen iobroker zum Laufen gebracht, leider hielt das nicht lange....
Aktuell läuft wieder nichts, weder VIS noch die Admin Instanz ist erreichbar. Wenn ich per Shell "iobroker stop" ausführe, um diesen danach zu "fixen", dann springt der Kursor sofort nach der Eingabe in die nächste Zeile, so als ob er nichts ausgeführt hat. Nach dem Befehl "iobroker fix" passiert genau das gleiche.
Könnten wir uns bitte zusammen auf Fehlersuche begeben?
Der Befehl:
which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejsliefert folgendes:
pi@raspberrypi:/opt/iobroker $ which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.0 v14.19.0 6.14.16 pi /opt/iobroker Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Hit:3 https://packages.grafana.com/oss/deb stable InRelease Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease Hit:5 https://repos.influxdata.com/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 226 packages can be upgraded. Run 'apt list --upgradable' to see them. nodejs: Installed: 14.19.0-deb-1nodesource1 Candidate: 14.20.0-deb-1nodesource1 Version table: 14.20.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages *** 14.19.0-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf PackagesDas blöde ist, dass ich seit dem letzten Fix rein gar nix gemacht hatte. Ich vermute, das Problem kommt daher, weil der Speicher voll gelaufen ist und dadurch nichts mehr ging. Eine 17GB log-Datei habe ich bereits gelöscht
-
Hallo liebe Community,
ihr habt mir kürzlich sehr geholfen und ich hatte meinen iobroker zum Laufen gebracht, leider hielt das nicht lange....
Aktuell läuft wieder nichts, weder VIS noch die Admin Instanz ist erreichbar. Wenn ich per Shell "iobroker stop" ausführe, um diesen danach zu "fixen", dann springt der Kursor sofort nach der Eingabe in die nächste Zeile, so als ob er nichts ausgeführt hat. Nach dem Befehl "iobroker fix" passiert genau das gleiche.
Könnten wir uns bitte zusammen auf Fehlersuche begeben?
Der Befehl:
which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejsliefert folgendes:
pi@raspberrypi:/opt/iobroker $ which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.0 v14.19.0 6.14.16 pi /opt/iobroker Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Hit:3 https://packages.grafana.com/oss/deb stable InRelease Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease Hit:5 https://repos.influxdata.com/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 226 packages can be upgraded. Run 'apt list --upgradable' to see them. nodejs: Installed: 14.19.0-deb-1nodesource1 Candidate: 14.20.0-deb-1nodesource1 Version table: 14.20.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages *** 14.19.0-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf PackagesDas blöde ist, dass ich seit dem letzten Fix rein gar nix gemacht hatte. Ich vermute, das Problem kommt daher, weil der Speicher voll gelaufen ist und dadurch nichts mehr ging. Eine 17GB log-Datei habe ich bereits gelöscht
@pahan sagte in VIS - No Connection:
dann springt der Kursor sofort nach der Eingabe in die nächste Zeile, so als ob er nichts ausgeführt hat.
Das ist 'linuxisch' für 'alles okay, Befehl ausgeführt'. Fehler werden zurückgemeldet.
-
Hallo liebe Community,
ihr habt mir kürzlich sehr geholfen und ich hatte meinen iobroker zum Laufen gebracht, leider hielt das nicht lange....
Aktuell läuft wieder nichts, weder VIS noch die Admin Instanz ist erreichbar. Wenn ich per Shell "iobroker stop" ausführe, um diesen danach zu "fixen", dann springt der Kursor sofort nach der Eingabe in die nächste Zeile, so als ob er nichts ausgeführt hat. Nach dem Befehl "iobroker fix" passiert genau das gleiche.
Könnten wir uns bitte zusammen auf Fehlersuche begeben?
Der Befehl:
which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejsliefert folgendes:
pi@raspberrypi:/opt/iobroker $ which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v14.19.0 v14.19.0 6.14.16 pi /opt/iobroker Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease Hit:3 https://packages.grafana.com/oss/deb stable InRelease Hit:4 https://deb.nodesource.com/node_14.x bullseye InRelease Hit:5 https://repos.influxdata.com/debian bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 226 packages can be upgraded. Run 'apt list --upgradable' to see them. nodejs: Installed: 14.19.0-deb-1nodesource1 Candidate: 14.20.0-deb-1nodesource1 Version table: 14.20.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.x bullseye/main armhf Packages *** 14.19.0-deb-1nodesource1 100 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf PackagesDas blöde ist, dass ich seit dem letzten Fix rein gar nix gemacht hatte. Ich vermute, das Problem kommt daher, weil der Speicher voll gelaufen ist und dadurch nichts mehr ging. Eine 17GB log-Datei habe ich bereits gelöscht
@pahan sagte in VIS - No Connection:
226 packages can be upgraded. Run 'apt list --upgradable' to see them.
Das sind schon mal 226 Fehler, die per Update zu bereinigen sind:
iob stop sudo apt update sudo apt full-upgrade sudo reboot -
@pahan sagte in VIS - No Connection:
dann springt der Kursor sofort nach der Eingabe in die nächste Zeile, so als ob er nichts ausgeführt hat.
Das ist 'linuxisch' für 'alles okay, Befehl ausgeführt'. Fehler werden zurückgemeldet.
@thomas-braun sagte in VIS - No Connection:
Das ist 'linuxisch' für 'alles okay, Befehl ausgeführt'. Fehler werden zurückgemeldet.
Das ist schon klar, aber es passiert sofort, früher hatte er zumindest mal eine halbe Sekunde gedauert.
Nach dem "iobroker fix" passiert exakt das Gleiche, nämlich nichts -
@thomas-braun sagte in VIS - No Connection:
Das ist 'linuxisch' für 'alles okay, Befehl ausgeführt'. Fehler werden zurückgemeldet.
Das ist schon klar, aber es passiert sofort, früher hatte er zumindest mal eine halbe Sekunde gedauert.
Nach dem "iobroker fix" passiert exakt das Gleiche, nämlich nichtsErst die anderen Hausaufgaben...
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
437
Online32.7k
Benutzer82.6k
Themen1.3m
Beiträge