Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. English
  3. Visualization
  4. Not able to start VIS after recent power loss. SOLVED

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.7k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.2k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    3.1k

Not able to start VIS after recent power loss. SOLVED

Geplant Angeheftet Gesperrt Verschoben Visualization
vis
5 Beiträge 2 Kommentatoren 660 Aufrufe 1 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • A Offline
    A Offline
    ap2017
    schrieb am zuletzt editiert von ap2017
    #1

    Not able to start VIS after recent power loss, getting the following messages

    URIError: Failed to decode param '%web_protocol%://192.168.1.74:%web_port%/vis/edit.html'
        at decodeURIComponent (<anonymous>)
        at decode_param (/opt/iobroker/node_modules/express/lib/router/layer.js:172:12)
        at Layer.match (/opt/iobroker/node_modules/express/lib/router/layer.js:148:15)
        at matchLayer (/opt/iobroker/node_modules/express/lib/router/index.js:585:18)
        at next (/opt/iobroker/node_modules/express/lib/router/index.js:226:15)
        at compression (/opt/iobroker/node_modules/compression/index.js:220:5)
        at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
        at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
        at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
        at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)
    
    HomoranH 1 Antwort Letzte Antwort
    0
    • A ap2017

      Not able to start VIS after recent power loss, getting the following messages

      URIError: Failed to decode param '%web_protocol%://192.168.1.74:%web_port%/vis/edit.html'
          at decodeURIComponent (<anonymous>)
          at decode_param (/opt/iobroker/node_modules/express/lib/router/layer.js:172:12)
          at Layer.match (/opt/iobroker/node_modules/express/lib/router/layer.js:148:15)
          at matchLayer (/opt/iobroker/node_modules/express/lib/router/index.js:585:18)
          at next (/opt/iobroker/node_modules/express/lib/router/index.js:226:15)
          at compression (/opt/iobroker/node_modules/compression/index.js:220:5)
          at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
          at trim_prefix (/opt/iobroker/node_modules/express/lib/router/index.js:328:13)
          at /opt/iobroker/node_modules/express/lib/router/index.js:286:9
          at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:346:12)
      
      HomoranH Nicht stören
      HomoranH Nicht stören
      Homoran
      Global Moderator Administrators
      schrieb am zuletzt editiert von
      #2

      @ap2017 Maybe that the filesystem is corrupted and nothing will work anymore.

      But we won't think of the worst case for now.

      please post iobroker list instances

      kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

      Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

      der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

      A 2 Antworten Letzte Antwort
      1
      • HomoranH Homoran

        @ap2017 Maybe that the filesystem is corrupted and nothing will work anymore.

        But we won't think of the worst case for now.

        please post iobroker list instances

        A Offline
        A Offline
        ap2017
        schrieb am zuletzt editiert von
        #3

        @homoran said in Not able to start VIS after recent power loss:

        iobroker list instances

        Here we go:

        ap@AP-Tiny:~$ iobroker list instances
        + system.adapter.accuweather.0            : accuweather           : AP-Tiny                                  -  enabled
        + system.adapter.admin.0                  : admin                 : AP-Tiny                                  -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        + system.adapter.backitup.0               : backitup              : AP-Tiny                                  -  enabled
          system.adapter.cloud.0                  : cloud                 : AP-Tiny                                  - disabled
          system.adapter.deconz.0                 : deconz                : AP-Tiny                                  - disabled, port: 8080
        + system.adapter.discovery.0              : discovery             : AP-Tiny                                  -  enabled
          system.adapter.echarts.0                : echarts               : AP-Tiny                                  -  enabled
          system.adapter.flot.0                   : flot                  : AP-Tiny                                  -  enabled
        + system.adapter.history.0                : history               : AP-Tiny                                  -  enabled
          system.adapter.icons-mfd-svg.0          : icons-mfd-svg         : AP-Tiny                                  -  enabled
        + system.adapter.info.0                   : info                  : AP-Tiny                                  -  enabled
        + system.adapter.javascript.0             : javascript            : AP-Tiny                                  -  enabled
          system.adapter.mysensors.0              : mysensors             : AP-Tiny                                  - disabled, port: 5003, bind: 0.0.0.0
        + system.adapter.simple-api.0             : simple-api            : AP-Tiny                                  -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
        + system.adapter.socketio.0               : socketio              : AP-Tiny                                  -  enabled, port: 8084, bind: 192.168.1.74, run as: admin
          system.adapter.sonoff.0                 : sonoff                : AP-Tiny                                  - disabled, port: 1883, bind: 0.0.0.0
        + system.adapter.telegram.0               : telegram              : AP-Tiny                                  -  enabled, port: 8443, bind: 0.0.0.0
          system.adapter.vis-google-fonts.0       : vis-google-fonts      : AP-Tiny                                  -  enabled
          system.adapter.vis-hqwidgets.0          : vis-hqwidgets         : AP-Tiny                                  -  enabled
          system.adapter.vis-jqui-mfd.0           : vis-jqui-mfd          : AP-Tiny                                  -  enabled
          system.adapter.vis-material-advanced.0  : vis-material-advanced : AP-Tiny                                  -  enabled
          system.adapter.vis-material-webfont.0   : vis-material-webfont  : AP-Tiny                                  -  enabled
          system.adapter.vis-material.0           : vis-material          : AP-Tiny                                  -  enabled
          system.adapter.vis-materialdesign.0     : vis-materialdesign    : AP-Tiny                                  -  enabled
          system.adapter.vis-metro.0              : vis-metro             : AP-Tiny                                  -  enabled
          system.adapter.vis-timeandweather.0     : vis-timeandweather    : AP-Tiny                                  -  enabled
          system.adapter.vis.0                    : vis                   : AP-Tiny                                  -  enabled
          system.adapter.web.0                    : web                   : AP-Tiny                                  - disabled, port: 8082, bind: 0.0.0.0, run as: admin
        + system.adapter.zigbee.0                 : zigbee                : AP-Tiny                                  -  enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_ba5ba26a021aec119f4c76e5f01c6278-if00-port0
        + system.adapter.zwave2.0                 : zwave2                : AP-Tiny                                  -  enabled
        
        + instance is alive
        ap@AP-Tiny:~$
        
        
        1 Antwort Letzte Antwort
        0
        • HomoranH Homoran

          @ap2017 Maybe that the filesystem is corrupted and nothing will work anymore.

          But we won't think of the worst case for now.

          please post iobroker list instances

          A Offline
          A Offline
          ap2017
          schrieb am zuletzt editiert von
          #4

          @homoran Actually, you got me thinking. Web.o was off. When I turned it on VIS started to work! Thanks

          HomoranH 1 Antwort Letzte Antwort
          0
          • A ap2017

            @homoran Actually, you got me thinking. Web.o was off. When I turned it on VIS started to work! Thanks

            HomoranH Nicht stören
            HomoranH Nicht stören
            Homoran
            Global Moderator Administrators
            schrieb am zuletzt editiert von
            #5

            @ap2017 sagte in Not able to start VIS after recent power loss. SOLVED:

            Web.o was off

            that was what I wanted to see. But

            @ap2017 sagte in Not able to start VIS after recent power loss. SOLVED:

            you got me thinking

            is the better way!

            kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

            der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

            1 Antwort Letzte Antwort
            0
            Antworten
            • In einem neuen Thema antworten
            Anmelden zum Antworten
            • Älteste zuerst
            • Neuste zuerst
            • Meiste Stimmen


            Support us

            ioBroker
            Community Adapters
            Donate

            994

            Online

            32.4k

            Benutzer

            81.5k

            Themen

            1.3m

            Beiträge
            Community
            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
            ioBroker Community 2014-2025
            logo
            • Anmelden

            • Du hast noch kein Konto? Registrieren

            • Anmelden oder registrieren, um zu suchen
            • Erster Beitrag
              Letzter Beitrag
            0
            • Home
            • Aktuell
            • Tags
            • Ungelesen 0
            • Kategorien
            • Unreplied
            • Beliebt
            • GitHub
            • Docu
            • Hilfe