Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. (gelöst)USV

    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

    (gelöst)USV

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

      @ostseereiter sagte in USV:

      Error: no UPS definitions found in ups.conf

      und was steht da drin?

      Das hier? :

      @ostseereiter sagte in USV:

      Dann habe ich das eingegeben:

      [serverups]
      #       driver = usbhid-ups
      #         port = auto
      #       desc = "Eeaton UPS"
      

      incl. der #?

      Thomas Braun ostseereiter Homoran 3 Replies Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Homoran last edited by Thomas Braun

        @ostseereiter @homoran Vermutlich noch nix. 😄
        Außer Kommentarzeilen.

        @ostseereiter Der Gartenzaun leitet immer Kommentare ein, die nicht ausgelesen werden. Daher meldet der Dienst auch, das keine config gefunden werden kann.

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

          @thomas-braun sagte in USV:

          @ostseereiter Der Gartenzaun leitet immer Kommentare ein, die nicht ausgelesen werden. Daher meldet der Dienst auch, das keine config gefunden werden kann.

          und wenn ich mir die tolle Anleitung von @klassisch ansehe steht da:

          Einfügen:

          [ups]
          	driver = "usbhid-ups"
          	port = "auto"
          	desc = "CyberPower"
          	pollinterval = 30
          

          Bei Verwendung einer Synology muß [ups] verwendet werden.

          Sudo reboot

          Also feheln auch noch die Anführungszeichen

          1 Reply Last reply Reply Quote 0
          • ostseereiter
            ostseereiter @Homoran last edited by

            @homoran sagte in USV:

            ncl. der #?

            ja müssen die weg?

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @ostseereiter last edited by

              @ostseereiter
              Natürlich müssen die weg. Sonst ist die Zeile quasi 'nicht existent' für den Dienst.

              ostseereiter 1 Reply Last reply Reply Quote 0
              • ostseereiter
                ostseereiter @Thomas Braun last edited by

                @thomas-braun
                ok nun kommt diese ausgabe schon mal nicht schlecht aber wohl noch ein Fehler.

                andy@debian:~$ sudo upsdrvctl start
                Network UPS Tools - UPS driver controller 2.7.4
                Network UPS Tools - Generic HID driver 0.41 (2.7.4)
                USB communication driver 0.33
                
                Fatal error: 'maxretry' is not a valid variable name for this driver.
                
                Look in the man page or call this driver with -h for a list of
                valid variable names and flags.
                andy@debian:~$
                
                
                
                Thomas Braun Homoran 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @ostseereiter last edited by

                  @ostseereiter
                  Bist du sicher, dass du den richtigen Treiber für deine USV angegeben hast? Oder nur die gleichen Einstellungen aus dem HowTo 1:1 übernommen?
                  Das muss natürlich auf deine Situation angepasst werden.

                  ostseereiter 1 Reply Last reply Reply Quote 0
                  • ostseereiter
                    ostseereiter @Thomas Braun last edited by

                    @thomas-braun sagte in USV:

                    HowTo 1:1 übernommen
                    1:1 übernommen

                    ostseereiter Thomas Braun 2 Replies Last reply Reply Quote 0
                    • ostseereiter
                      ostseereiter @ostseereiter last edited by

                      @ostseereiter
                      was gibt man dann dort ein?

                      1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @ostseereiter last edited by

                        @ostseereiter

                        Und wer sagt dir, dass für deine Hardware nicht andere Einstellungen gelten?

                        ostseereiter 1 Reply Last reply Reply Quote 0
                        • ostseereiter
                          ostseereiter @Thomas Braun last edited by

                          @thomas-braun
                          das verstehe ich kann nicht gleich sein aber wie macht man das und wo finde ich das?

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @ostseereiter last edited by

                            @ostseereiter
                            Von der usbid her ist das die gleiche Hardware wie bei @foxriver76 .

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

                              @ostseereiter sagte in USV:

                              Fatal error: 'maxretry' is not a valid variable name for this driver.

                              wo hast du denn das maxretry eingegeben?

                              1 Reply Last reply Reply Quote 0
                              • ostseereiter
                                ostseereiter @Thomas Braun last edited by

                                @thomas-braun sagte in USV:

                                @ostseereiter
                                Von der usbid her ist das die gleiche Hardware wie bei @foxriver76 .

                                Der Hersteller zumindest ist gleich. Wie kann man dnn die USBID auslesen?

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

                                  hast du bereits!

                                  @ostseereiter sagte in USV:

                                  Bus 004 Device 002: ID 0463:ffff MGE UPS Systems UPS

                                  ostseereiter 1 Reply Last reply Reply Quote 0
                                  • ostseereiter
                                    ostseereiter @Homoran last edited by

                                    @homoran
                                    ja aber wo trägt man diese ein?

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

                                      @ostseereiter sagte in USV:

                                      ja aber wo trägt man diese ein?

                                      nirgends, damit meldet sich das Gerät.

                                      Aber

                                      @homoran sagte in USV:

                                      wo hast du denn das maxretry eingegeben?

                                      ostseereiter 1 Reply Last reply Reply Quote 0
                                      • ostseereiter
                                        ostseereiter @Homoran last edited by

                                        @homoran sagte in USV:

                                        wo hast du denn das maxretry eingegeben?

                                        garnicht

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

                                          @ostseereiter sagte in USV:

                                          garnicht

                                          steht außer der drei Zeilen nichts sonstiges in der conf?

                                          ostseereiter 1 Reply Last reply Reply Quote 0
                                          • ostseereiter
                                            ostseereiter @Homoran last edited by

                                            @homoran
                                            ja

                                            #
                                            # The section header ([upsname]) can be just about anything as long as
                                            # it is a single word inside brackets.  upsd uses this to uniquely
                                            # identify a UPS on this system.
                                            #
                                            # If you have a UPS called snoopy, your section header would be "[snoopy]".
                                            # On a system called "doghouse", the line in your upsmon.conf to monitor
                                            # it would look something like this:
                                            #
                                            #       MONITOR snoopy@doghouse 1 upsmonuser mypassword master
                                            #
                                            # It might look like this if monitoring in slave mode:
                                            #
                                            #       MONITOR snoopy@doghouse 1 upsmonuser mypassword slave
                                            #
                                            # Configuration directives
                                            # ------------------------
                                            #
                                            # These directives are used by upsdrvctl only and should be specified outside
                                            # of a driver definition:
                                            #
                                            #    maxretry: Optional.  Specify the number of attempts to start the driver(s),
                                            #              in case of failure, before giving up. A delay of 'retrydelay' is
                                            #              inserted between each attempt. Caution should be taken when using
                                            #              this option, since it can impact the time taken by your system to
                                            #              start.
                                            #
                                            #              The default is 1 attempt.
                                            #
                                            #  retrydelay: Optional.  Specify the delay between each restart attempt of the
                                            #              driver(s), as specified by 'maxretry'. Caution should be taken
                                            #              when using this option, since it can impact the time taken by your
                                            #              system to start.
                                            #
                                            #              The default is 5 seconds.
                                            #
                                            # These directives are common to all drivers that support ups.conf:
                                            #
                                            #  driver: REQUIRED.  Specify the program to run to talk to this UPS.
                                            #          apcsmart, bestups, and sec are some examples.
                                            of a driver definition:
                                            #
                                            #    maxretry: Optional.  Specify the number of attempts to start the driver(s),
                                            #              in case of failure, before giving up. A delay of 'retrydelay' is
                                            #              inserted between each attempt. Caution should be taken when using
                                            #              this option, since it can impact the time taken by your system to
                                            #              start.
                                            #
                                            #              The default is 1 attempt.
                                            #
                                            #  retrydelay: Optional.  Specify the delay between each restart attempt of the
                                            #              driver(s), as specified by 'maxretry'. Caution should be taken
                                            #              when using this option, since it can impact the time taken by your
                                            #              system to start.
                                            #
                                            #              The default is 5 seconds.
                                            #
                                            # These directives are common to all drivers that support ups.conf:
                                            #
                                            #  driver: REQUIRED.  Specify the program to run to talk to this UPS.
                                            #          apcsmart, bestups, and sec are some examples.
                                            #
                                            #    port: REQUIRED.  The serial port where your UPS is connected.
                                            #          /dev/ttyS0 is usually the first port on Linux boxes, for example.
                                            #
                                            # sdorder: optional.  When you have multiple UPSes on your system, you
                                            #          usually need to turn them off in a certain order.  upsdrvctl
                                            #          shuts down all the 0s, then the 1s, 2s, and so on.  To exclude
                                            #          a UPS from the shutdown sequence, set this to -1.
                                            #
                                            #          The default value for this parameter is 0.
                                            #
                                            #  nolock: optional, and not recommended for use in this file.
                                            #
                                            #          If you put nolock in here, the driver will not lock the
                                            #          serial port every time it starts.  This may allow other
                                            #          processes to seize the port if you start more than one by
                                            #          mistake.
                                            #
                                            #          This is only intended to be used on systems where locking
                                            #          absolutely must be disabled for the software to work.
                                            #
                                            # maxstartdelay: optional.  This can be set as a global variable
                                            #                above your first UPS definition and it can also be
                                            #                set in a UPS section.  This value controls how long
                                            sdorder: optional.  When you have multiple UPSes on your system, you
                                            #          usually need to turn them off in a certain order.  upsdrvctl
                                            #          shuts down all the 0s, then the 1s, 2s, and so on.  To exclude
                                            #          a UPS from the shutdown sequence, set this to -1.
                                            #
                                            #          The default value for this parameter is 0.
                                            #
                                            #  nolock: optional, and not recommended for use in this file.
                                            #
                                            #          If you put nolock in here, the driver will not lock the
                                            #          serial port every time it starts.  This may allow other
                                            #          processes to seize the port if you start more than one by
                                            #          mistake.
                                            #
                                            #          This is only intended to be used on systems where locking
                                            #          absolutely must be disabled for the software to work.
                                            #
                                            # maxstartdelay: optional.  This can be set as a global variable
                                            #                above your first UPS definition and it can also be
                                            #                set in a UPS section.  This value controls how long
                                            #                upsdrvctl will wait for the driver to finish starting.
                                            #                This keeps your system from getting stuck due to a
                                            #                broken driver or UPS.
                                            #
                                            #                The default is 45 seconds.
                                            #
                                            # synchronous: optional.  The driver work by default in asynchronous
                                            #              mode (i.e *synchronous=no*).  This means that all data
                                            #              are pushed by the driver on the communication socket to
                                            #              upsd (Unix socket on Unix, Named pipe on Windows) without
                                            #              waiting for these data to be actually consumed.  With
                                            #              some HW, such as ePDUs, that can produce a lot of data,
                                            #              asynchronous mode may cause some congestion, resulting in
                                            #              the socket to be full, and the driver to appear as not
                                            #              connected.  By enabling the 'synchronous' flag
                                            #              (value = 'yes'), the driver will wait for data to be
                                            #              consumed by upsd, prior to publishing more.  This can be
                                            #              enabled either globally or per driver.
                                            #
                                            #              The default is 'no' (i.e. asynchronous mode) for backward
                                            #              compatibility of the driver behavior.
                                            #
                                            # Anything else is passed through to the hardware-specific part of
                                                           This keeps your system from getting stuck due to a
                                            #                broken driver or UPS.
                                            #
                                            #                The default is 45 seconds.
                                            #
                                            # synchronous: optional.  The driver work by default in asynchronous
                                            #              mode (i.e *synchronous=no*).  This means that all data
                                            #              are pushed by the driver on the communication socket to
                                            #              upsd (Unix socket on Unix, Named pipe on Windows) without
                                            #              waiting for these data to be actually consumed.  With
                                            #              some HW, such as ePDUs, that can produce a lot of data,
                                            #              asynchronous mode may cause some congestion, resulting in
                                            #              the socket to be full, and the driver to appear as not
                                            #              connected.  By enabling the 'synchronous' flag
                                            #              (value = 'yes'), the driver will wait for data to be
                                            #              consumed by upsd, prior to publishing more.  This can be
                                            #              enabled either globally or per driver.
                                            #
                                            #              The default is 'no' (i.e. asynchronous mode) for backward
                                            #              compatibility of the driver behavior.
                                            #
                                            # Anything else is passed through to the hardware-specific part of
                                            # the driver.
                                            #
                                            # Examples
                                            # --------
                                            #
                                            # A simple example for a UPS called "powerpal" that uses the blazer_ser
                                            # driver on /dev/ttyS0 is:
                                            #
                                            # [powerpal]
                                            #       driver = blazer_ser
                                            #       port = /dev/ttyS0
                                            #       desc = "Web server"
                                            #
                                            # If your UPS driver requires additional settings, you can specify them
                                            # here.  For example, if it supports a setting of "1234" for the
                                            # variable "cable", it would look like this:
                                            #
                                            # [myups]
                                            #       driver = mydriver
                                            #       port = /dev/ttyS1
                                            #       cable = 1234
                                            #       desc = "Something descriptive"
                                             the driver.
                                            #
                                            # Examples
                                            # --------
                                            #
                                            # A simple example for a UPS called "powerpal" that uses the blazer_ser
                                            # driver on /dev/ttyS0 is:
                                            #
                                            # [powerpal]
                                            #       driver = blazer_ser
                                            #       port = /dev/ttyS0
                                            #       desc = "Web server"
                                            #
                                            # If your UPS driver requires additional settings, you can specify them
                                            # here.  For example, if it supports a setting of "1234" for the
                                            # variable "cable", it would look like this:
                                            #
                                            # [myups]
                                            #       driver = mydriver
                                            #       port = /dev/ttyS1
                                            #       cable = 1234
                                            #       desc = "Something descriptive"
                                            #
                                            # To find out if your driver supports any extra settings, start it with
                                            # the -h option and/or read the driver's documentation.
                                            
                                            # Set maxretry to 3 by default, this should mitigate race with slow devices:
                                            maxretry = 3
                                            
                                            
                                            Homoran 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            618
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            9
                                            135
                                            11195
                                            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