Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. English
    3. Scripting / Logic
    4. JavaScript
    5. JavaScript adapter wont detect modbus-serial

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    JavaScript adapter wont detect modbus-serial

    This topic has been deleted. Only users with topic management privileges can see it.
    • Homoran
      Homoran Global Moderator Administrators @Jack 3 last edited by

      @jack-3 sagte in JavaScript adapter wont detect modbus-serial:

      where do I need to download it to?

      nowhere!
      you just have to add it in the config.
      save and exit, the instance should restart and load it itself.

      Jack 3 1 Reply Last reply Reply Quote 1
      • Jack 3
        Jack 3 @Homoran last edited by

        @homoran Im still getting this error even after adding modbus-serial to the instance, are there perhaps other steps I can take to troubleshoot this?

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

          @jack-3 sagte in JavaScript adapter wont detect modbus-serial:

          are there perhaps other steps I can take to troubleshoot this?

          I think so, but I cannot tell which ones.

          maybe that @thomas-braun may help to find the issue if something went wrong by your installation method and is blocking the built in method

          oooh!
          is there a whitespace too much at the end? before the closing '

          1 Reply Last reply Reply Quote 1
          • F
            fastfoot @Jack 3 last edited by

            @jack-3 do something with ModbusRTU, the error might only be visually(because of some restriction the sandbox has). Only if yo get additional errors when using the module you can tell the module is not loaded

            Jack 3 1 Reply Last reply Reply Quote 2
            • Jack 3
              Jack 3 @fastfoot last edited by

              @fastfoot I tried this code which I copied and edited from the modbus serial documentation and I am getting these errors 48aac906-bd54-4c26-8cd4-eb3e6a7f5078-image.png

              F 1 Reply Last reply Reply Quote 0
              • F
                fastfoot @Jack 3 last edited by

                @jack-3 ok, thats a real error. Which version of JS-Adapter do you have? I think there is a bug in the newest Beta not installing modules that were entered in the instance config. Remove these lines, leave the config and enter them again. After leaving the config then have a look to the Log Tab, you schould see the that module(s) are getting installed.

                Workaround on the cli:

                • cd /opt/iobroker
                • npm i modbus-serial
                • js-adapter should recognize the module now, though the red underline might still be there

                let us know, there should be no need to install module in /opt/iobroker/node_modules/iobroker.javascript instead of /opt/iobroker

                Jack 3 1 Reply Last reply Reply Quote 0
                • Jack 3
                  Jack 3 @fastfoot last edited by

                  @fastfoot Thats the thing, I do not have an /opt/iobroker directory, it does not exist is what the terminal tells me

                  F 1 Reply Last reply Reply Quote 0
                  • F
                    fastfoot @Jack 3 last edited by

                    @jack-3 what system are you running iobroker, windows? There it schould be C:\iobroker. All Linux Systems use /opt/iobroker. Though not sure where tis is on a Mac

                    Jack 3 2 Replies Last reply Reply Quote 0
                    • Jack 3
                      Jack 3 @fastfoot last edited by

                      @fastfoot I use windows

                      F 1 Reply Last reply Reply Quote 0
                      • Jack 3
                        Jack 3 @fastfoot last edited by

                        @fastfoot I ran the command again using the directory you said and Im still getting the same errors, I can even see in the node_modules directory that I do have Modbus-serial installed

                        1 Reply Last reply Reply Quote 0
                        • F
                          fastfoot @Jack 3 last edited by

                          @jack-3 the try cd C:\iobroker and then npm i modbus-serial

                          F 1 Reply Last reply Reply Quote 0
                          • F
                            fastfoot @fastfoot last edited by

                            @fastfoot please log the error instead of the data, works fine here though i have no modbus hardware

                            1 Reply Last reply Reply Quote 0
                            • Jack 3
                              Jack 3 last edited by Jack 3

                              @fastfoot

                              2024-07-09 09:07:46.559 - error: modbus.0 (604) Socket Error
                              2024-07-09 09:07:46.564 - error: modbus.0 (604) Client in error state.
                              2024-07-09 09:07:46.564 - warn: modbus.0 (604) On error: {"errno":-4039,"code":"ETIMEDOUT","syscall":"connect","address":"131.246.75.233","port":5020}
                              2024-07-09 09:07:46.592 - error: modbus.1 (12848) Socket Error
                              2024-07-09 09:07:46.601 - error: modbus.1 (12848) Client in error state.
                              2024-07-09 09:07:46.601 - warn: modbus.1 (12848) On error: {"errno":-4078,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":502}
                              2024-07-09 09:08:47.615 - error: modbus.1 (12848) Socket Error
                              2024-07-09 09:08:47.615 - error: modbus.1 (12848) Client in error state.
                              2024-07-09 09:08:47.615 - warn: modbus.1 (12848) On error: {"errno":-4078,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":502}
                              2024-07-09 09:09:08.775 - error: modbus.0 (604) Socket Error
                              2024-07-09 09:09:08.775 - error: modbus.0 (604) Client in error state.
                              2024-07-09 09:09:08.775 - warn: modbus.0 (604) On error: {"errno":-4039,"code":"ETIMEDOUT","syscall":"connect","address":"131.246.75.233","port":5020}
                              2024-07-09 09:09:12.133 - info: admin.0 (5516) ==> Connected system.user.admin from ::1
                              2024-07-09 09:09:12.221 - error: host.PCRT49 cannot call visUtils: Not exists
                              2024-07-09 09:09:18.930 - info: admin.0 (5516) ==> Connected system.user.admin from ::1
                              2024-07-09 09:09:21.197 - info: javascript.0 (12652) Start JavaScript script.js.Test (Javascript/js)
                              2024-07-09 09:09:21.206 - error: javascript.0 (12652) script.js.Test compile failed:
                              at script.js.Test:4
                              

                              is that what you mean?

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

                              Support us

                              ioBroker
                              Community Adapters
                              Donate

                              929
                              Online

                              31.6k
                              Users

                              79.5k
                              Topics

                              1.3m
                              Posts

                              3
                              18
                              497
                              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