GELÖST: Materialdesign Widgets mit großen Problemen

ExMatador

Ich setze für meine Visualisierung VIS ein (nicht VIS2). Läuft seit Jahren stabil.
Seit ein paar Tagen fallen die Materialdesign Widgets mit dem Fehler "Datenpunkt xy existiert nicht" auf, der MD Switch reagiert gar nicht mehr.
Aktualisiere ich mittels F5 den View, wird der DP gefunden. Passiert mit dem MD Widget "Bar Chart", dem MD Widget "Switch" (läuft auch nach F5 nicht) und vermutlich noch weiteren.
Bin mit allen Adaptern, nodeJS, etc. aktuell, habe vor allem keine neueren Updates durchgeführt.

Was kann das sein? Jemand eine Idee?

Danke
ExMatador

Ro75

@exmatador sagte in Materialdesign Widgets mit großen Problemen:

Materialdesign Widgets mit dem Fehler "Datenpunkt xy existiert nicht"

bitte mal zeigen. Und dann ggfs. mal die Langfassung von

iob diag

hier hinterher. Bei mir laufen auch die Widgets vom Material Design. Und solche Meldungen hatte ich noch nie. Also bitte mal zeigen.

Ro75.

ExMatador

@ro75
iob diag ist bei mir nicht verfügbar
iob status all liefert

iobroker is running on this host.


Instance "admin.1" is running
Instance "alexa2.0" is running
Instance "lupusec.0" is running
Instance "discovery.0" is running
Instance "net-tools.0" is running
Instance "chromecast.0" is running
Instance "cloud.0" is not running
Instance "backitup.0" is running
Instance "web.0" is running
Instance "vis.0" is not running
Instance "vis-fancyswitch.0" is not running
Instance "minuvis.0" is not running
Instance "icons-mfd-png.0" is not running
Instance "deconz.0" is not running
Instance "javascript.0" is running
Instance "email.0" is running
Instance "tr-064.0" is running
Instance "pushover.0" is running
Instance "icons-mfd-svg.0" is not running
Instance "vis-jqui-mfd.0" is not running
Instance "iot.0" is running
Instance "text2command.0" is running
Instance "vis-inventwo.0" is running
Instance "lgtv.0" is running
Instance "smartgarden.0" is running
Instance "daswetter.0" is not running
Instance "pollenflug.0" is running
Instance "flot.0" is not running
Instance "history.0" is running
Instance "icons-material-svg.0" is not running
Instance "material.0" is not running
Instance "dwd.0" is not running
Instance "icons-icons8.0" is not running
Instance "sainlogic.0" is running
Instance "denon.0" is running
Instance "mercedesme.0" is running
Instance "shelly.0" is not running
Instance "alias-manager.0" is not running
Instance "geofency.0" is running
Instance "ical.0" is not running
Instance "trashschedule.0" is running
Instance "zigbee.0" is not running
Instance "echarts.0" is running
Instance "influxdb.0" is running
Instance "vis-timeandweather.0" is not running
Instance "heos.0" is running
Instance "scenes.0" is running
Instance "vis-hqwidgets.0" is not running
Instance "vis-map.0" is not running
Instance "vis-material-advanced.0" is not running
Instance "vis-materialdesign.0" is running
Instance "socketio.0" is running
Instance "simple-api.0" is running
Instance "whatsapp-cmb.0" is running
Instance "ping.0" is running
Instance "ws.0" is running
Instance "zigbee.1" is running
Instance "tvspielfilm.0" is not running
Instance "ical.1" is not running
Instance "octoprint.0" is running
Instance "tuya.0" is running
Instance "govee-app.0" is running
Instance "countdown.0" is running
Instance "homepilot20.0" is running
Instance "mqtt-client.0" is running
Instance "vis-canvas-gauges.0" is not running
Instance "vis-metro.0" is not running
Instance "homeconnect.0" is running
Instance "frigate.0" is not running
Instance "hoover.0" is running

SYSTEM/memoryLimitMB: 0
SYSTEM/hostname: MichaelGK
SYSTEM/statisticsInterval: 15000
SYSTEM/checkDiskInterval: 300000
SYSTEM/instanceStartInterval: 2000
SYSTEM/compact: false
SYSTEM/allowShellCommands: true
SYSTEM/memLimitWarn: 100
SYSTEM/memLimitError: 50
MULTIHOSTSERVICE/enabled: false
MULTIHOSTSERVICE/secure: true
NETWORK/IPv4: true
NETWORK/IPv6: true
OBJECTS/type: jsonl
OBJECTS/host: 127.0.0.1
OBJECTS/port: 9001
OBJECTS/user:
OBJECTS/pass:
OBJECTS/noFileCache: false
OBJECTS/connectTimeout: 5000
OBJECTS/OPTIONS/retryStrategy: (reconnectCount) => {
            if (!ready && initError) {
                return new Error('No more tries');
            }
            if (this.stop) {
                return new Error('Client has stopped ... no retries anymore');
            }
            if (ready && reconnectCount >= retry_max_count) {
                return new Error('Stop trying to reconnect');
            }
            // A function that receives an options object as parameter including the retry attempt,
            // the total_retry_time indicating how much time passed since the last time connected,
            // the error why the connection was lost and the number of times_connected in total.
            // If you return a number from this function, the retry will happen exactly after that
            // time in milliseconds. If you return a non-number, no further retry will happen and
            // all offline commands are flushed with errors. Return an error to return that
            // specific error to all offline commands.
            if (!ready) {
                return 300;
            }
            else {
                return retry_max_delay;
            }
        }
OBJECTS/OPTIONS/enableReadyCheck: true
OBJECTS/OPTIONS/host: 127.0.0.1
OBJECTS/OPTIONS/port: 9001
OBJECTS/OPTIONS/db: 0
OBJECTS/OPTIONS/family: 0
OBJECTS/OPTIONS/autoResubscribe: false
OBJECTS/OPTIONS/connectionName:
OBJECTS/BACKUP/disabled: false
OBJECTS/BACKUP/files: 24
OBJECTS/BACKUP/hours: 48
OBJECTS/BACKUP/period: 120
OBJECTS/BACKUP/path:
OBJECTS/JSONLOPTIONS/AUTOCOMPRESS/sizeFactor: 2
OBJECTS/JSONLOPTIONS/AUTOCOMPRESS/sizeFactorMinimumSize: 25000
OBJECTS/JSONLOPTIONS/THROTTLEFS/intervalMs: 60000
OBJECTS/JSONLOPTIONS/THROTTLEFS/maxBufferedCommands: 1000
OBJECTS/maxQueue: 1000
STATES/type: jsonl
STATES/host: 127.0.0.1
STATES/port: 9000
STATES/maxQueue: 1000
STATES/user:
STATES/pass:
STATES/connectTimeout: 5000
STATES/OPTIONS/retryStrategy: (reconnectCount) => {
            if (!ready && initError) {
                return new Error('No more tries');
            }
            if (this.stop) {
                return new Error('Client has stopped ... no retries anymore');
            }
            if (ready && reconnectCount >= retry_max_count) {
                return new Error('Stop trying to reconnect');
            }
            // A function that receives an options object as parameter including the retry attempt,
            // the total_retry_time indicating how much time passed since the last time connected,
            // the error why the connection was lost and the number of times_connected in total.
            // If you return a number from this function, the retry will happen exactly after that
            // time in milliseconds. If you return a non-number, no further retry will happen and
            // all offline commands are flushed with errors. Return an error to return that
            // specific error to all offline commands.
            if (!ready) {
                return 300;
            }
            return retry_max_delay;
            /*if (options.error.code === 'ECONNREFUSED') {
                // End reconnecting on a specific error and flush all commands with a individual error
                return new Error('The server refused the connection');
            }
            if (options.total_retry_time > 1000 * 60 * 60) {
                // End reconnecting after a specific timeout and flush all commands with a individual error
                return new Error('Retry time exhausted');
            }
            if (options.times_connected > 10) {
                // End reconnecting with built in error
                return undefined;
            }
            // reconnect after
            return Math.max(options.attempt * 100, 3000);*/
        }
STATES/OPTIONS/enableReadyCheck: true
STATES/OPTIONS/host: 127.0.0.1
STATES/OPTIONS/port: 9000
STATES/OPTIONS/db: 0
STATES/OPTIONS/family: 0
STATES/OPTIONS/autoResubscribe: false
STATES/OPTIONS/connectionName:
STATES/BACKUP/disabled: false
STATES/BACKUP/files: 24
STATES/BACKUP/hours: 48
STATES/BACKUP/period: 120
STATES/BACKUP/path:
STATES/JSONLOPTIONS/AUTOCOMPRESS/sizeFactor: 2
STATES/JSONLOPTIONS/AUTOCOMPRESS/sizeFactorMinimumSize: 25000
STATES/JSONLOPTIONS/THROTTLEFS/intervalMs: 60000
STATES/JSONLOPTIONS/THROTTLEFS/maxBufferedCommands: 1000
LOG/level: info
LOG/maxDays: 7
LOG/noStdout: true
LOG/TRANSPORT/FILE1/type: file
LOG/TRANSPORT/FILE1/enabled: true
LOG/TRANSPORT/FILE1/filename: log/iobroker
LOG/TRANSPORT/FILE1/fileext: .log
LOG/TRANSPORT/FILE1/maxSize: 0
LOG/TRANSPORT/FILE1/maxFiles: 0
LOG/TRANSPORT/FILE1/level:
LOG/TRANSPORT/SYSLOG1/type: syslog
LOG/TRANSPORT/SYSLOG1/enabled: false
LOG/TRANSPORT/SYSLOG1/host: localhost
LOG/TRANSPORT/SYSLOG1/protocol: udp4
LOG/TRANSPORT/SYSLOG1/localhost: iobroker
LOG/TRANSPORT/SYSLOG1/level:
LOG/TRANSPORT/SYSLOG1/port: 0
LOG/TRANSPORT/SYSLOG1/path:
LOG/TRANSPORT/SYSLOG1/facility:
LOG/TRANSPORT/SYSLOG1/sysLogType:
LOG/TRANSPORT/SYSLOG1/app_name:
LOG/TRANSPORT/SYSLOG1/eol:
dataDir: ../../iobroker-data/

DP existiert nicht.jpg

ExMatador

Ro75

@exmatador ich kann gar nix erkennen und iob diag muss gehen. Mit was historisierst du?

Ro75

ExMatador

@ro75
Mit influx 2

Thomas Braun

@exmatador sagte in Materialdesign Widgets mit großen Problemen:

iob diag ist bei mir nicht verfügbar

iob stop
iob fix
iob start

Dann

iob diag

Samson71

Ist iob diag auch unter Windows verfügbar? Wenn nein, dann erklärt sich die Nichtverfügbarkeit.

ExMatador

@samson71
Ja bin unter Windows unterwegs
iob fix - wenn es denn funktioniert - hat am Verhalten nichts geändert

ExMatador

@exmatador
Ich bekomme permanent einen Disconnect vom admin-Adapter.
Ist vermutlich nicht ok.

admin.1
2024-10-05 23:14:49.944 info <== Disconnect system.user.admin from ::ffff:192.168.178.43 admin

Auch der web-Adapter hat permanent einen Disconnect und Connect

web.0
2024-10-05 23:28:16.032	info	==> Connected system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:28:13.406	info	<== Disconnect system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:28:13.405	info	<== Disconnect system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:28:12.225	info	==> Connected system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:28:10.941	info	<== Disconnect system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:28:00.566	info	==> Connected system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:27:50.849	info	==> Connected system.user.admin from ::ffff:192.168.178.43
web.0
2024-10-05 23:27:24.929	info	<== Disconnect system.user.admin from ::ffff:192.168.178.43 vis.0
web.0
2024-10-05 23:26:24.726	info	==> Connected system.user.admin from ::ffff:192.168.178.43

ExMatador

@exmatador
Problem gelöst: ein "View in Widget 8" war 2x vorhanden und beide lagen pixelgenau übereinander. Daher gab es View-Probleme en masse.
ExMatador

NEWS

GELÖST: Materialdesign Widgets mit großen Problemen

Support us

1.5k
Online

30.9k
Users

77.6k
Topics

1.2m
Posts

NEWS

GELÖST: Materialdesign Widgets mit großen Problemen

Support us

1.5kOnline

30.9kUsers

77.6kTopics

1.2mPosts

1.5k
Online

30.9k
Users

77.6k
Topics

1.2m
Posts