Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. English
    3. ioBroker general
    4. Update System iobroker failed

    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

    Update System iobroker failed

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tiger @mickym last edited by Tiger

      @mickym
      Sorry, didn't see your post before doing it...

      So I took the package.json and replace in the node-red and made npm install in the directory

      Error with alexa node, seems that the node used before doesn't exist now

      pi@raspberrypi:/opt/iobroker/iobroker-data/node-red $ npm install
      npm ERR! code ENOVERSIONS
      npm ERR! No versions available for node-red-node-alexa
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /home/iobroker/.npm/_logs/2022-08-16T14_59_56_194Z-debug-0.log
      
      

      log file 2022-08-16T14_59_56_194Z-debug-0.log

      Do you want that I tryed with copy af all the directory? there is a lot of files... more than 60.000

      mickym 1 Reply Last reply Reply Quote 0
      • mickym
        mickym Most Active @Tiger last edited by mickym

        @tiger sagte in Update System iobroker failed:

        node-red-node-alexa

        So this node is no longer supported. As said you can rename the existing directory and copy the whole directory to the original place - but I do not recommend this. So better is to look for an replacement.

        If you want to try if the old one is running copying the old directory in total - you should first rename the exiting one before you copy the old one. But better is to remove the alexa node. If this is the only error then you should have all except the alexa node.

        to test if the old one will run. you can do

        cd /opt/iobroker/iobroker-data
        mv node-red node-red.new
        

        and then copy the old directory into the iobroker-data directory. But I am not sure if this old alexa node will work at all.

        T 1 Reply Last reply Reply Quote 0
        • T
          Tiger @mickym last edited by Tiger

          @mickym

          I'm Trying to understand 🙂

          1 I've to test with your command

          cd /opt/iobroker/iobroker-data
          mv node-red node-red.new
          

          once made, (depending of the result)

          • change the name of the directory to have backup I supposed
          • Copy all the directory from the old SD Card (lots of files... more than 60.000....) to the new SD Card at same place

          and after?

          mickym 1 Reply Last reply Reply Quote 0
          • T
            Tiger @crunchip last edited by

            @crunchip

            don't remember if socketio is used but it was installed.
            Web.0 is not configured, And I didn't reached to change the Ip adress.

            Configuration of VIS, nothing, lincence key is show and when checking licence it's OK

            Configuration of Web.0
            67924ee0-c9eb-412f-9045-0bf1aa712fc3-image.png

            No ip Adress, supposed is the reason

            crunchip 1 Reply Last reply Reply Quote 0
            • mickym
              mickym Most Active @Tiger last edited by

              @tiger sagte in Update System iobroker failed:

              @mickym

              I'm Trying to understand 🙂

              1 I've to test with your command

              cd /opt/iobroker/iobroker-data
              mv node-red node-red.new
              

              once made, (depending of the result)

              • change the name of the directory to have backup I supposed
              • Copy all the directory from the old SD Card (lots of files... more than 60.000....) to the new SD Card at same place

              and after?

              after you copied the old directory under /opt/iobroker/iobroker-data make sure that the rights are adapted.

              go to the /opt/iobroker/iobroker-data directory and execute:

              cd /opt/iobroker/iobroker-data
              sudo chown -R iobroker:iobroker node-red
              

              this will ensure that user iobroker has access to all files and you can try to start the adapter. If this will not work - you have to use again the backup (node-red.new) and delete the reference of the old alexa node in the package.json file. However I guess all other nodes should have been installed.

              I have to go off now and can only support you on my mobile. But this is very limited. But these are standard procedures all others should be familiar with. 😉

              T 1 Reply Last reply Reply Quote 0
              • T
                Tiger @mickym last edited by

                @mickym said in Update System iobroker failed:

                make sure that the rights are adapted.

                What do you mean by that?

                mickym 1 Reply Last reply Reply Quote 0
                • mickym
                  mickym Most Active @Tiger last edited by

                  @tiger If you copy with user pi - all files are owned by this user. As iobroker runs under user iobroker you need to change the owner of the files and directories.

                  T 1 Reply Last reply Reply Quote 0
                  • T
                    Tiger @mickym last edited by

                    @mickym
                    ok I've same user name as before

                    mickym 1 Reply Last reply Reply Quote 0
                    • mickym
                      mickym Most Active @Tiger last edited by

                      @tiger So but I am not sure if the old node will work at all with the new node version. You should better think about a replacement.

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        Tiger @mickym last edited by

                        @mickym
                        So... if I'm understanding well...
                        I've to let like that without copy the directory...
                        install the new node of Alexa...
                        and made a new programmation?

                        as i wanted to have an installation up to date... if it's your recommandation... i'll do like that...

                        mickym 1 Reply Last reply Reply Quote 0
                        • T
                          Tiger @Homoran last edited by

                          @homoran

                          No problem Now that I'd understood Filezilla 🙂

                          I'm going to have all working, and after we'll see to the update.

                          After Node-red.. that if I understand well I've to reprogram... for alexa
                          I've to check VIS
                          RFXCOM it seems that I've to pair everything as I've the devices but seems not connected
                          Zigbee, probably same, I've to pair everything

                          Homoran 1 Reply Last reply Reply Quote 0
                          • crunchip
                            crunchip Forum Testing Most Active @Tiger last edited by

                            @tiger sagte in Update System iobroker failed:

                            don't remember if socketio is used but it was installed.

                            Not currently, you can switch and test it or use pure web sockets
                            69379e9f-cd05-4e19-ae30-5939c76d2576-image.png

                            T 1 Reply Last reply Reply Quote 0
                            • mickym
                              mickym Most Active @Tiger last edited by

                              @tiger sagte in Update System iobroker failed:

                              @mickym
                              So... if I'm understanding well...
                              I've to let like that without copy the directory...
                              install the new node of Alexa...
                              and made a new programmation?

                              as i wanted to have an installation up to date... if it's your recommandation... i'll do like that...

                              Yes my recommendation is to do not copy the old stuff. Edit your package.json and delete the line in the dependencies section which refers to the old- alexa node. Run npm install hopefully without errors. Activate in the node red adapter configuration that you use the pallet manager and install a different node. Then you need to rework all alexa flows

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

                                @tiger sagte in Update System iobroker failed:

                                Zigbee, probably same, I've to pair everything

                                i don't use zigbee and therefore I'm very sorry if there is a pitfall too.
                                But @Thomas-Braun may know wether there will be a solution.

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  Tiger @mickym last edited by

                                  @mickym said in Update System iobroker failed:

                                  package.json

                                  ok I'll do it...
                                  but, how do you edit the package.json?

                                  mickym 1 Reply Last reply Reply Quote 0
                                  • T
                                    Tiger @Homoran last edited by

                                    @homoran

                                    No it seems everything is working well...
                                    Zigbee and Rfxcom... good news...

                                    1 Reply Last reply Reply Quote 0
                                    • T
                                      Tiger @crunchip last edited by

                                      @crunchip

                                      it seems it's due to my version of iobroker.admin...

                                      I thing we'll be able to solve it after upgrading system...

                                      2022-08-16 18:10:28.357	error	startInstance system.adapter.web.0 Adapter dependency not fulfilled on any host: required adapter "admin" has wrong version. Installed "4.0.10", required ">=5.1.0"!
                                      crunchip 1 Reply Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @Tiger last edited by

                                        @tiger I do not understand all the problems, that was a backup with the backitup adapter? Why admin 4

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

                                          @crunchip sagte in Update System iobroker failed:

                                          that was a backup with the backitup adapter?

                                          no manually by iobroker backup

                                          the admin had been downgraded by the restore

                                          crunchip 1 Reply Last reply Reply Quote 0
                                          • crunchip
                                            crunchip Forum Testing Most Active @Homoran last edited by crunchip

                                            @homoran

                                            @tiger sagte in Update System iobroker failed:

                                            Vis installed
                                            Backup with --force done...
                                            ADmin version has beenn downgrade to 4.0 as before...

                                            Why
                                            itself or through backup

                                            @tiger sagte in Update System iobroker failed:

                                            Installed "4.0.10", required ">=5.1.0"

                                            then do the upgrade

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            882
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            update iobroker
                                            7
                                            164
                                            15684
                                            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