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. ioBroker general
  4. Node.js update

NEWS

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    11
    1
    534

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    24
    1
    1.7k

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

Node.js update

Geplant Angeheftet Gesperrt Verschoben ioBroker general
node.js
39 Beiträge 3 Kommentatoren 6.0k Aufrufe 3 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.
  • Thomas BraunT Thomas Braun

    @ap2017

    i stall vis if you use it, because of an actual bug

    You have to install vis prior to restoring your backup. Known issue.

    1. Error 25 ist very generic, it can have a lot of causes for this error.

    Try

    iob stop
    iob fix
    iob start
    
    A Offline
    A Offline
    ap2017
    schrieb am zuletzt editiert von
    #25

    @thomas-braun

    1. Assuming that I have to delete VIS adapter and add it back. Will all my screens stay in the system?
    2. Tried this, did not help.
    iob stop
    iob fix
    iob start
    
    

    Here is detailed error message

    $ ./iobroker upgrade echarts
    Update echarts from @1.4.15 to @1.5.1
    NPM version: 8.19.4
    Installing iobroker.echarts@1.5.1... (System call)
    ERROR: npm ERR! code 6npm ERR! path /opt/iobroker/node_modules/iobroker.visnpm ERR! command failednpm ERR! command sh -c -- node main.js --installnpm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T20_57_44_562Z-debug-0.log
    ERROR: host.AP-Tiny Cannot install iobroker.echarts@1.5.1: 6
    ERROR: process exited with code 25
    
    HomoranH 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von
      #26

      @ap2017
      Do it via command line interface and debug option:

      iobroker upgrade echarts --debug
      

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      A 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @ap2017
        Do it via command line interface and debug option:

        iobroker upgrade echarts --debug
        
        A Offline
        A Offline
        ap2017
        schrieb am zuletzt editiert von
        #27

        @thomas-braun

        ap@AP-Tiny:/opt/iobroker$ iobroker upgrade echarts --debug
        
        This upgrade of "echarts" will introduce the following changes:
        ==========================================================================
        -> 1.5.1:
        Error handling in JSON data was improved
        
        -> 1.5.0:
        Implemented raw data export
        ==========================================================================
        
        Would you like to upgrade echarts from @1.4.15 to @1.5.1 now? [(y)es, (n)o]: y
        Update echarts from @1.4.15 to @1.5.1
        NPM version: 8.19.4
        Installing iobroker.echarts@1.5.1... (System call)
        npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
        npm WARN deprecated har-validator@5.1.5: this library is no longer supported
        npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
        npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
        npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
        npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
        npm ERR! code 6
        npm ERR! path /opt/iobroker/node_modules/iobroker.vis
        npm ERR! command failed
        npm ERR! command sh -c -- node main.js --install
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T21_31_07_618Z-debug-0.log
        npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
        npm WARN deprecated har-validator@5.1.5: this library is no longer supported
        npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
        npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
        npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
        npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
        npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
        npm ERR! code 6
        npm ERR! path /opt/iobroker/node_modules/iobroker.vis
        npm ERR! command failed
        npm ERR! command sh -c -- node main.js --install
        
        npm ERR! A complete log of this run can be found in:
        npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T21_31_07_618Z-debug-0.log
        host.AP-Tiny Cannot install iobroker.echarts@1.5.1: 6
        ap@AP-Tiny:/opt/iobroker$
        
        
        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • A ap2017

          @thomas-braun

          ap@AP-Tiny:/opt/iobroker$ iobroker upgrade echarts --debug
          
          This upgrade of "echarts" will introduce the following changes:
          ==========================================================================
          -> 1.5.1:
          Error handling in JSON data was improved
          
          -> 1.5.0:
          Implemented raw data export
          ==========================================================================
          
          Would you like to upgrade echarts from @1.4.15 to @1.5.1 now? [(y)es, (n)o]: y
          Update echarts from @1.4.15 to @1.5.1
          NPM version: 8.19.4
          Installing iobroker.echarts@1.5.1... (System call)
          npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
          npm WARN deprecated har-validator@5.1.5: this library is no longer supported
          npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
          npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
          npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
          npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
          npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
          npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
          npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
          npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
          npm ERR! code 6
          npm ERR! path /opt/iobroker/node_modules/iobroker.vis
          npm ERR! command failed
          npm ERR! command sh -c -- node main.js --install
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T21_31_07_618Z-debug-0.log
          npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
          npm WARN deprecated har-validator@5.1.5: this library is no longer supported
          npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
          npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
          npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
          npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
          npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
          npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
          npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
          npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
          npm ERR! code 6
          npm ERR! path /opt/iobroker/node_modules/iobroker.vis
          npm ERR! command failed
          npm ERR! command sh -c -- node main.js --install
          
          npm ERR! A complete log of this run can be found in:
          npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T21_31_07_618Z-debug-0.log
          host.AP-Tiny Cannot install iobroker.echarts@1.5.1: 6
          ap@AP-Tiny:/opt/iobroker$
          
          
          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #28

          @ap2017 sagte in Node.js update:

          npm ERR! code 6
          npm ERR! path /opt/iobroker/node_modules/iobroker.vis
          npm ERR! command failed
          npm ERR! command sh -c -- node main.js --install
          

          The broken vis install blocks any other npm actions.
          Try

          iobroker upgrade vis@1.4.10
          

          Restore your backup again.
          And avoid the beta Repository!

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          A 2 Antworten Letzte Antwort
          0
          • Thomas BraunT Thomas Braun

            @ap2017 sagte in Node.js update:

            npm ERR! code 6
            npm ERR! path /opt/iobroker/node_modules/iobroker.vis
            npm ERR! command failed
            npm ERR! command sh -c -- node main.js --install
            

            The broken vis install blocks any other npm actions.
            Try

            iobroker upgrade vis@1.4.10
            

            Restore your backup again.
            And avoid the beta Repository!

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

            @thomas-braun

            ap@AP-Tiny:~$ iobroker upgrade vis@1.4.10
            
            This downgrade of "vis" will at least remove the following changes:
            ==========================================================================
            -> 1.4.16
            Corrected connection with "only port" URLs
            
            -> 1.4.15
            Better check of the offline license
            
            -> 1.4.14
            Corrected GUI bug
            
            -> 1.4.13
            The group attributes will be replaced recursively
            
            -> 1.4.12
            Fixed bug with the export of specific widgets
            
            -> 1.4.11
            Removed ES6 commands to be supported by older browsers
            Fixed problem with update of grouped widgets
            Added web manifest to be able to handle vis as the web app
            ==========================================================================
            
            Would you like to downgrade vis from @1.4.16 to @1.4.10 now? [(y)es, (n)o]: y
            Update vis from @1.4.16 to @1.4.10
            NPM version: 8.19.4
            Installing iobroker.vis@1.4.10... (System call)
            npm ERR! code 6
            npm ERR! path /opt/iobroker/node_modules/iobroker.vis
            npm ERR! command failed
            npm ERR! command sh -c -- node main.js --install
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T22_28_10_906Z-debug-0.log
            host.AP-Tiny Cannot install iobroker.vis@1.4.10: 6
            ap@AP-Tiny:~$
            
            
            1 Antwort Letzte Antwort
            0
            • Thomas BraunT Thomas Braun

              @ap2017 sagte in Node.js update:

              npm ERR! code 6
              npm ERR! path /opt/iobroker/node_modules/iobroker.vis
              npm ERR! command failed
              npm ERR! command sh -c -- node main.js --install
              

              The broken vis install blocks any other npm actions.
              Try

              iobroker upgrade vis@1.4.10
              

              Restore your backup again.
              And avoid the beta Repository!

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

              @thomas-braun said in Node.js update:

              Restore your backup again.

              What do you mean by "Restore your backup again."? I did not do nor restore backup

              Thomas BraunT 1 Antwort Letzte Antwort
              0
              • A ap2017

                @thomas-braun said in Node.js update:

                Restore your backup again.

                What do you mean by "Restore your backup again."? I did not do nor restore backup

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #31

                @ap2017

                I thought you did change your operating system?

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                A 1 Antwort Letzte Antwort
                0
                • Thomas BraunT Thomas Braun

                  @ap2017

                  I thought you did change your operating system?

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

                  @thomas-braun Not yet, it will take me a while

                  Thomas BraunT 1 Antwort Letzte Antwort
                  0
                  • A ap2017

                    @thomas-braun Not yet, it will take me a while

                    Thomas BraunT Online
                    Thomas BraunT Online
                    Thomas Braun
                    Most Active
                    schrieb am zuletzt editiert von
                    #33

                    @ap2017

                    Then take your time and come again when done.

                    Linux-Werkzeugkasten:
                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                    NodeJS Fixer Skript:
                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                    A 1 Antwort Letzte Antwort
                    0
                    • A ap2017

                      @thomas-braun

                      1. Assuming that I have to delete VIS adapter and add it back. Will all my screens stay in the system?
                      2. Tried this, did not help.
                      iob stop
                      iob fix
                      iob start
                      
                      

                      Here is detailed error message

                      $ ./iobroker upgrade echarts
                      Update echarts from @1.4.15 to @1.5.1
                      NPM version: 8.19.4
                      Installing iobroker.echarts@1.5.1... (System call)
                      ERROR: npm ERR! code 6npm ERR! path /opt/iobroker/node_modules/iobroker.visnpm ERR! command failednpm ERR! command sh -c -- node main.js --installnpm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2023-06-14T20_57_44_562Z-debug-0.log
                      ERROR: host.AP-Tiny Cannot install iobroker.echarts@1.5.1: 6
                      ERROR: process exited with code 25
                      
                      HomoranH Nicht stören
                      HomoranH Nicht stören
                      Homoran
                      Global Moderator Administrators
                      schrieb am zuletzt editiert von
                      #34

                      @ap2017 sagte in Node.js update:

                      Assuming that I have to delete VIS adapter and add it back

                      NO!!
                      Don't delete the vis adapter!

                      Just install a "blank" version before restoring.

                      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
                      • Thomas BraunT Thomas Braun

                        @ap2017

                        Then take your time and come again when done.

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

                        @thomas-braun Installed latest Ubuntu, restored ioBroker from backup (had to use latest beta controller to match with backup), but new installation of ioBroker is set for stable repositories. Everything seems to be working, including VIS. Having a bit of an issue with info adapter. It works for few seconds then turns red with error messages

                        2023-06-16 16:09:19.354 - info: info.0 (3352) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                        2023-06-16 16:09:20.660 - info: info.0 (3352) starting. Version 1.9.26 in /opt/iobroker/node_modules/iobroker.info, node: v18.16.0, js-controller: 5.0.4
                        2023-06-16 16:09:21.033 - info: info.0 (3352) Reading/updating systemdata.
                        2023-06-16 16:09:22.167 - info: info.0 (3352) State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number"
                        2023-06-16 16:09:22.323 - info: info.0 (3352) State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string"
                        2023-06-16 16:09:22.583 - info: info.0 (3352) cpu Temp res = {"main":62,"cores":[62,61],"max":62,"socket":[],"chipset":null}
                        2023-06-16 16:09:25.284 - info: admin.0 (1913) ==> Connected system.user.admin from ::ffff:192.168.1.244
                        2023-06-16 16:09:27.785 - info: host.ap-EB1033 Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                        2023-06-16 16:09:31.423 - info: info.0 (3352) State value to set for "info.0.sysinfo.disks.diskLayout.dev0.size" has to be type "string" but received type "number"
                        

                        Should I change Info objects types to match received vs. set?

                        Thomas BraunT 1 Antwort Letzte Antwort
                        0
                        • A ap2017

                          @thomas-braun Installed latest Ubuntu, restored ioBroker from backup (had to use latest beta controller to match with backup), but new installation of ioBroker is set for stable repositories. Everything seems to be working, including VIS. Having a bit of an issue with info adapter. It works for few seconds then turns red with error messages

                          2023-06-16 16:09:19.354 - info: info.0 (3352) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system
                          2023-06-16 16:09:20.660 - info: info.0 (3352) starting. Version 1.9.26 in /opt/iobroker/node_modules/iobroker.info, node: v18.16.0, js-controller: 5.0.4
                          2023-06-16 16:09:21.033 - info: info.0 (3352) Reading/updating systemdata.
                          2023-06-16 16:09:22.167 - info: info.0 (3352) State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number"
                          2023-06-16 16:09:22.323 - info: info.0 (3352) State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string"
                          2023-06-16 16:09:22.583 - info: info.0 (3352) cpu Temp res = {"main":62,"cores":[62,61],"max":62,"socket":[],"chipset":null}
                          2023-06-16 16:09:25.284 - info: admin.0 (1913) ==> Connected system.user.admin from ::ffff:192.168.1.244
                          2023-06-16 16:09:27.785 - info: host.ap-EB1033 Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json"
                          2023-06-16 16:09:31.423 - info: info.0 (3352) State value to set for "info.0.sysinfo.disks.diskLayout.dev0.size" has to be type "string" but received type "number"
                          

                          Should I change Info objects types to match received vs. set?

                          Thomas BraunT Online
                          Thomas BraunT Online
                          Thomas Braun
                          Most Active
                          schrieb am zuletzt editiert von
                          #36

                          @ap2017

                          Usually this would be reported as 'Issue' at the GitHub:

                          https://github.com/iobroker-community-adapters/ioBroker.info/issues

                          This may be due to the beta-version of the js-controller. Have seen similar errors with different adapters.

                          Linux-Werkzeugkasten:
                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                          NodeJS Fixer Skript:
                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                          A 1 Antwort Letzte Antwort
                          0
                          • Thomas BraunT Thomas Braun

                            @ap2017

                            Usually this would be reported as 'Issue' at the GitHub:

                            https://github.com/iobroker-community-adapters/ioBroker.info/issues

                            This may be due to the beta-version of the js-controller. Have seen similar errors with different adapters.

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

                            @thomas-braun Would it make sense to downgrade controller?

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • A ap2017

                              @thomas-braun Would it make sense to downgrade controller?

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von Thomas Braun
                              #38

                              @ap2017 To avoid the errors that come with a beta-js-contoller I 'd recommend to downgrade. But it's not that trivial
                              Instructions on how to do a downgrade are only available in German, afaics.

                              https://forum.iobroker.net/topic/66108/js-controller-5-0-x-jetzt-in-der-beta

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              A 1 Antwort Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @ap2017 To avoid the errors that come with a beta-js-contoller I 'd recommend to downgrade. But it's not that trivial
                                Instructions on how to do a downgrade are only available in German, afaics.

                                https://forum.iobroker.net/topic/66108/js-controller-5-0-x-jetzt-in-der-beta

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

                                @thomas-braun Here is what I have in my records to downgrade. This from https://forum.iobroker.net/topic/19885/probleme-nach-js-controller-1-5-6-1-4-2-downgrade?_=1686947115238

                                cd /opt/iobroker
                                iobroker stop
                                npm i iobroker.js-controller@x.x.x --production
                                iobroker start
                                
                                
                                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

                                597

                                Online

                                32.5k

                                Benutzer

                                81.8k

                                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