Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Basti81

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    B
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 28
    • Best 1
    • Groups 1

    Basti81

    @Basti81

    Starter

    1
    Reputation
    9
    Profile views
    28
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Basti81 Follow
    Starter

    Best posts made by Basti81

    • RE: iot Adapter und Shelly 2.5

      @cinimod hab es hinbekommen:
      Rollos rekalibriert und eine Gruppe in Alexa angelegt mit beiden Rollos. Anschließend eine Routine in Alexa angelegt mit der ich die Gruppe steuere (Prozentwert).

      Lg
      Basti

      posted in Cloud Dienste
      B
      Basti81

    Latest posts made by Basti81

    • RE: Hue statuswert sofort per push aktualisieren

      @basti81 Mein Fehler, hatte kein SSL eingeschaltet. Danach geht es.

      posted in ioBroker Allgemein
      B
      Basti81
    • Hue statuswert sofort per push aktualisieren

      Hi Leute,

      ich nutze einen Senic Friends for Hue Schalter. Mit diesem möchte ich eine Shelly schalten.
      Leider sind die Aktualisierungen im Hue adapter immer an die Aktualisierungs-Einstellung gebunden (bspw. alle 10 Sekunden).

      Ich habe auch von dem push api script gelesen, ist das immer noch notwendig?

      Ich würde gerne, dass der Statuswert direkt beim iobroker ankommt (Taste gedrückt), sodass ich keine Verzögerung beim Schalten der Shelly habe.

      Wie mache ich das am Besten?

      lg
      Basti

      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser danke dir. Habe die Container sauber neu aufgesetzt wie hier erläutert:
      https://smarthome.buanet.de/2020/12/iobroker-docker-container-mit-redis-db-verbinden/

      Alles läuft nun wie es soll und der Restore hat geklappt da die redis Verbindung von Anfang an funktionierte. Bridged Network war hier der Schlüssel. Mit Host network hat es nicht geklappt.

      Danke dir!!!

      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser hab jetzt den 6379 versucht und ich bekomme den gleichen Fehler:

      -----------------------------------------------
      -----             Step 3 of 5: Checking ioBroker installation              -----
      --------------------------------------------------------------------------------
       
      (Re)setting permissions (This might take a while! Please be patient!)... Done.
       
      Fixing "sudo-bug" by replacing sudo with gosu... Done.
       
      [DEBUG] Checking multihost settings... 
      [DEBUG] No multihost settings detected.
      [DEBUG] Done.
       
      Configuring custom objects db...
      IOB_OBJECTSDB_TYPE is available and value meets detected ioBroker installation.
      IOB_OBJECTSDB_HOST is available and value meets detected ioBroker installation.
      IOB_OBJECTSDB_PORT is available but value is different from detected ioBroker installation.
      Setting port of objects db to "6379"... Done.
      Done.
       
      Configuring custom states db...
      IOB_STATESDB_TYPE is available and value meets detected ioBroker installation.
      IOB_STATESDB_HOST is available and value meets detected ioBroker installation.
      IOB_STATESDB_PORT is available but value is different from detected ioBroker installation.
      Setting port of states db to "6379"... Done.
      Done.
       
      Checking Database connection... Failed.
      [DEBUG] Error message: 
      [DEBUG] No connection to objects 127.0.0.1:6379[redis]
      Please check your configuration and try again.
      For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
       
      [DEBUG] Debug mode prevents the container from exiting on errors.
      [DEBUG] This enables you to investigate or fix your issue on the command line.
      [DEBUG] If you want to stop or restart your container you have to do it manually.
      [DEBUG] IoBroker is not running!
      

      Soll ich mal:
      apt-get install redis-sentinel

      im Container ausführen? Mich wundert das hier im Container:

      root@iobrokerpi:/opt/iobroker# redis-server -v                                                        
      bash: redis-server: command not found
      
      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser wir kommen der Sache näher 🙂

      -------------------------------------------------
      -----             Step 3 of 5: Checking ioBroker installation              -----
      --------------------------------------------------------------------------------
       
      (Re)setting permissions (This might take a while! Please be patient!)... Done.
       
      Fixing "sudo-bug" by replacing sudo with gosu... Done.
       
      [DEBUG] Checking multihost settings... 
      [DEBUG] No multihost settings detected.
      [DEBUG] Done.
       
      Configuring custom objects db...
      IOB_OBJECTSDB_TYPE is available and value meets detected ioBroker installation.
      IOB_OBJECTSDB_HOST is available and value meets detected ioBroker installation.
      IOB_OBJECTSDB_PORT is available and value meets detected ioBroker installation.
      Done.
       
      Configuring custom states db...
      IOB_STATESDB_TYPE is available and value meets detected ioBroker installation.
      IOB_STATESDB_HOST is available and value meets detected ioBroker installation.
      IOB_STATESDB_PORT is available but value is different from detected ioBroker installation.
      Setting port of states db to "9000"... Done.
      Done.
       
      Checking Database connection... Failed.
      [DEBUG] Error message: 
      [DEBUG] No connection to objects 127.0.0.1:9001[redis]
      Please check your configuration and try again.
      For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
       
      [DEBUG] Debug mode prevents the container from exiting on errors.
      [DEBUG] This enables you to investigate or fix your issue on the command line.
      [DEBUG] If you want to stop or restart your container you have to do it manually.
      [DEBUG] IoBroker is not running!
      

      Unbenannt2.png

      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser den Container habe ich über die GUI aktiviert und das gibt es nur diese ENV:
      Unbenannt.png

      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser auf dem Pi:

      pi@iobrokerpi:~ $ sudo redis-server -v
      Redis server v=5.0.14 sha=00000000:0 malloc=libc bits=32 build=ddd3b1f304a7d4d5
      

      In dem Container:

      root@iobrokerpi:/opt/iobroker# redis-server -v                                                        
      bash: redis-server: command not found
      
      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser ah ok, anbei das Log:

      --------------------------------------------------
      -----                   Step 1 of 5: Preparing container                   -----
      --------------------------------------------------------------------------------
       
      This is not the first run of this container. Skipping first run preparation.
       
      --------------------------------------------------------------------------------
      -----             Step 2 of 5: Detecting ioBroker installation             -----
      --------------------------------------------------------------------------------
       
      Existing installation of ioBroker detected in "/opt/iobroker".
       
      --------------------------------------------------------------------------------
      -----             Step 3 of 5: Checking ioBroker installation              -----
      --------------------------------------------------------------------------------
       
      (Re)setting permissions (This might take a while! Please be patient!)... Done.
       
      Fixing "sudo-bug" by replacing sudo with gosu... Done.
       
      [DEBUG] Checking multihost settings... 
      [DEBUG] No multihost settings detected.
      [DEBUG] Done.
       
      [DEBUG] Checking custom objects db settings... 
      [DEBUG] No custom objects db settings detected.
      [DEBUG] Done.
       
      [DEBUG] Checking custom states db settings... 
      [DEBUG] No custom states db settings detected.
      [DEBUG] Done.
       
      Checking Database connection... Failed.
      [DEBUG] Error message: 
      [DEBUG] No connection to states 0.0.0.0:6379[redis]
      Please check your configuration and try again.
      For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
       
      [DEBUG] Debug mode prevents the container from exiting on errors.
      [DEBUG] This enables you to investigate or fix your issue on the command line.
      [DEBUG] If you want to stop or restart your container you have to do it manually.
      [DEBUG] IoBroker is not running!
      
      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @homoran nach dem restore mit Backitup startet der Container durch. Dann sehe ich im Protokoll folgendes:

      --------------------------------------
      -----                   Step 1 of 5: Preparing container                   -----
      --------------------------------------------------------------------------------
       
      This is not the first run of this container. Skipping first run preparation.
       
      --------------------------------------------------------------------------------
      -----             Step 2 of 5: Detecting ioBroker installation             -----
      --------------------------------------------------------------------------------
       
      Existing installation of ioBroker detected in "/opt/iobroker".
       
      --------------------------------------------------------------------------------
      -----             Step 3 of 5: Checking ioBroker installation              -----
      --------------------------------------------------------------------------------
       
      (Re)setting permissions (This might take a while! Please be patient!)... Done.
       
      Fixing "sudo-bug" by replacing sudo with gosu... Done.
       
      Checking Database connection... Failed.
      Please check your configuration and try again.
      For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
       
      This Script will exit now.
      
      posted in ioBroker Allgemein
      B
      Basti81
    • RE: Migration Pi4 > Synology Docker

      @glasfaser hatte ich auch versucht mit dem gleichen Ergebnis nur dann startet das System autom. durch und ich komme gar nicht mehr an den Container ran per ssh da er andauernd von selbst neu startet (wahrscheinlich wegen des Startup bash scripts von buanet.

      posted in ioBroker Allgemein
      B
      Basti81
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo