Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. English
    3. Visualization
    4. Not able to start VIS after recent power loss. SOLVED

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Not able to start VIS after recent power loss. SOLVED

    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      ap2017 last edited by 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)
      
      Homoran 1 Reply Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @ap2017 last edited by

        @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 2 Replies Last reply Reply Quote 1
        • A
          ap2017 @Homoran last edited by

          @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 Reply Last reply Reply Quote 0
          • A
            ap2017 @Homoran last edited by

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

            Homoran 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @ap2017 last edited by

              @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!

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Support us

              ioBroker
              Community Adapters
              Donate

              578
              Online

              31.8k
              Users

              80.0k
              Topics

              1.3m
              Posts

              vis
              2
              5
              453
              Loading More Posts
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes
              Reply
              • Reply as topic
              Log in to reply
              Community
              Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
              The ioBroker Community 2014-2023
              logo