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

      @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
            • Homoran
              Homoran Global Moderator Administrators @ostseereiter last edited by Homoran

              @ostseereiter sagte in USV:

              # Set maxretry to 3 by default, this should mitigate race with slow devices:
              maxretry = 3

              und wo ist da deine Konfig?
              oder wo kommt der code jetzt her?

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

                @homoran
                Hier die komplette Config:

                
                # Network UPS Tools: example ups.conf
                #
                # --- SECURITY NOTE ---
                #
                # If you use snmp-ups and set a community string in here, you
                # will have to secure this file to keep other users from obtaining
                # that string.  It needs to be readable by upsdrvctl and any drivers,
                # and by upsd.
                #
                # ---
                #
                # This is where you configure all the UPSes that this system will be
                # monitoring directly.  These are usually attached to serial ports, but
                # USB devices and SNMP devices are also supported.
                #
                # This file is used by upsdrvctl to start and stop your driver(s), and
                # is also used by upsd to determine which drivers to monitor.  The
                # drivers themselves also read this file for configuration directives.
                #
                
                # This is where you configure all the UPSes that this system will be
                # monitoring directly.  These are usually attached to serial ports, but
                # USB devices and SNMP devices are also supported.
                #
                # This file is used by upsdrvctl to start and stop your driver(s), and
                # is also used by upsd to determine which drivers to monitor.  The
                # drivers themselves also read this file for configuration directives.
                #
                # The general form is:
                #
                 [serverups]
                       driver = usbhid-ups
                         port = auto
                        desc = "Eeaton UPS"
                #
                # 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.
                #
                #    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.
                 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
                #                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
                  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
                # the driver.
                #
                # Examples
                # --------
                #
                # A simple example for a UPS called "powerpal" that uses the blazer_ser
                # driver on /dev/ttyS0 is:
                #
                # [powerpal]
                         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"
                #
                # 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
                • Homoran
                  Homoran Global Moderator Administrators @ostseereiter last edited by

                  @ostseereiter sagte in USV:

                  Hier die komplette Config:

                  endlich!

                  Ob das korrekt ist mitten in der Anleitung die # zu entfernen und das als Config zu nehmen weiß ich nicht.

                  Ansonsten würde ich zum testen jetzt einfach die Zeile mit den maxretry auskommentieren.

                  EDIT:
                  das Problem wird die Zeile vor maxretry sein. Die war doch eben noch auskommentiert, oder?
                  Dort unbedingt ein # vorsetzen sonst ist das ein (ungültiger) Befehl -> set maxretry....

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

                    @homoran
                    habe ich auskommentiert jetzt sieht es so aus: das ist schon mal besser

                    
                    andy@debian:~$ sudo nano /etc/nut/ups.conf
                    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
                    Using subdriver: MGE HID 1.39
                    andy@debian:~$
                    
                    
                    Homoran 1 Reply Last reply Reply Quote 0
                    • Homoran
                      Homoran Global Moderator Administrators @ostseereiter last edited by

                      @ostseereiter sagte in USV:

                      habe ich auskommentiert

                      was?

                      • den Kommentar?
                      • den Wert?
                      • beides?
                      ostseereiter 1 Reply Last reply Reply Quote 0
                      • ostseereiter
                        ostseereiter @Homoran last edited by

                        @homoran
                        dies hier

                        # Set maxretry to 3 by default, this should mitigate race with slow devices:
                        # maxretry = 3
                        
                        
                        
                        Homoran 1 Reply Last reply Reply Quote 0
                        • Homoran
                          Homoran Global Moderator Administrators @ostseereiter last edited by

                          @ostseereiter sagte in USV:

                          dies hier

                          dann nimm das zweite vor maxretry=3 wieder weg

                          @ostseereiter sagte in USV:

                          das ist schon mal besser

                          ja, dann weiter im Text!
                          aber bitte wirklich

                          @ostseereiter sagte in USV:

                          1:1 übernommen

                          Wir müssen uns darauf verlassen könne, wenn du so etwas sagst, dass du nicht an anderen Stellen alles verstellt hast

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

                            @homoran
                            ja wenn ich den Gartenzaun wieder wegnehme dann kommt wieder die Fehlermeldung:

                            
                            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.
                            

                            Ich lese auch eure Beiträge zwei mal bevor ich was mache

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

                              @ostseereiter sagte in USV:
                              Das maxretry' muss aus kommentiert werden.

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

                                als nächstes habe ich das eingestellt:

                                # IMPORTANT NOTE:
                                #  This file is intended to be sourced by shell scripts.
                                #  You MUST NOT use spaces around the equal sign!
                                
                                MODE=netserver
                                
                                1 Reply Last reply Reply Quote 0
                                • ostseereiter
                                  ostseereiter last edited by

                                  nun kommt der Zugriff unter sudo nano /etc/nut/upsd.conf
                                  da ja auch Clients zufgreifen sollen,soll man dort LISTEN 0.0.0.0 eintragen.
                                  Nun stehe ich wieder wie der Ochse vor dem Scheunentor. wo hier?

                                   =======================================================================
                                  # STATEPATH <path>
                                  # STATEPATH /var/run/nut
                                  #
                                  # Tell upsd to look for the driver state sockets in 'path' rather
                                  # than the default that was compiled into the program.
                                  
                                  # =======================================================================
                                  # LISTEN <address> [<port>]
                                  # LISTEN 127.0.0.1 3493
                                  # LISTEN ::1 3493
                                  #
                                  # This defaults to the localhost listening addresses and port 3493.
                                  # In case of IP v4 or v6 disabled kernel, only the available one will be used.
                                  #
                                  # You may specify each interface 
                                  
                                  Homoran 1 Reply Last reply Reply Quote 0
                                  • Homoran
                                    Homoran Global Moderator Administrators @ostseereiter last edited by

                                    @ostseereiter sagte in USV:

                                    nun kommt der Zugriff unter sudo nano /etc/nut/upsd.conf

                                    ich möchte dir nochmals den Thread von @klassisch ans Herz legen (wenigstens parallel lesen!).
                                    https://forum.iobroker.net/topic/23688/howto-usv-nut-server-auf-sbc-installieren?_=1621345610029

                                    der macht nämlich vorher noch einen test:

                                    Eintragen:
                                    MODE=netserver
                                    Danach den Dienst starten:
                                    sudo upsd
                                    Wenn alles funktioniert hat, kann man jetzt Daten ausgeben:
                                    sudo upsc ups@localhost
                                    Hier muss eine sinnvolle Liste gelistet werden:

                                    Erst dann wird die /etc/nut/upsd.conf editiert und die IPs eingegeben.
                                    0.0.0.0 macht alles auf....

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

                                      @homoran
                                      ok ich lese erst mal melde mich wieder.

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

                                        beim ersten Befehl sudo upsd kommt

                                        Network UPS Tools upsd 2.7.4
                                        Fatal error: A previous upsd instance is already running!
                                        Either stop the previous instance first, or use the 'reload' command.
                                        

                                        beim zweiten Befehl: sudo upsc ups@localhost kommt dies

                                        andy@debian:~$ sudo upsc ups@localhost
                                        Init SSL without certificate database
                                        Error: Unknown UPS
                                        andy@debian:~$
                                        
                                        Homoran 1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @ostseereiter last edited by Homoran

                                          @ostseereiter sagte in USV:

                                          beim ersten Befehl sudo upsd kommt

                                          klar du hast ja schon gestartet

                                          @ostseereiter sagte in USV:

                                          beim zweiten Befehl: sudo upsc ups@localhost kommt dies

                                          aber du hast alles an deine Bezeichnungen angepasst?

                                          EDIT:
                                          eher nicht:

                                          @ostseereiter sagte in USV:

                                          Error: Unknown UPS

                                          heisst deine nicht serverups?

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

                                            @homoran sagte in USV:

                                            heisst deine nicht serverups?

                                            ja so heißt sie

                                            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

                                            942
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

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