Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] Synology Adapter startet nicht mehr

    NEWS

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    • Wir empfehlen: Node.js 22.x

    [gelöst] Synology Adapter startet nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • Holger Etzel
      Holger Etzel last edited by Holger Etzel

      Hallo,

      der Synology-Adapter ist die ganze Zeit gelaufen.
      IObroker läuft in einer VM auf der Synology.

      Nach dem letzten Update von 0.1.20 auf 1.0.0 startet der Adapter nicht mehr und bleibt gelb.
      Im Log stehen dann folgende Fehlermeldungen

      synology.1	2021-04-28 19:53:59.600	warn	(1710020) get state error: Connection is closed.
      synology.1	2021-04-28 19:53:59.599	warn	(1710020) Could not check object existence of state synology.1.info.connection: Cannot check object existence of "synology.1.info.connection": Connection is closed.
      synology.1	2021-04-28 19:53:59.599	error	(1710020) Cannot check object existence of "synology.1.info.connection": Connection is closed.
      synology.1	2021-04-28 19:53:59.597	warn	(1710020) redis get synology.1.info.connection, error - Connection is closed.
      synology.1	2021-04-28 19:53:59.596	debug	(1710020) * Get info from (firstPoll) api: DSM method: getPollingData params: {}
      synology.1	2021-04-28 19:53:59.596	debug	(1710020) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}}
      synology.1	2021-04-28 19:53:59.596	debug	(1710020) -----------------------------------------------------------------------------------------------------
      synology.1	2021-04-28 19:53:59.596	debug	(1710020) Error: Reconnection after 10s
      synology.1	2021-04-28 19:53:59.596	debug	(1710020) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password
      synology.1	2021-04-28 19:53:59.595	debug	(1710020) * No response, read next.
      synology.1	2021-04-28 19:53:59.510	warn	(1710020) get state error: Connection is closed.
      synology.1	2021-04-28 19:53:59.509	warn	(1710020) Could not check object existence of state synology.1.info.connection: Cannot check object existence of "synology.1.info.connection": Connection is closed.
      synology.1	2021-04-28 19:53:59.508	error	(1710020) Cannot check object existence of "synology.1.info.connection": Connection is closed.
      synology.1	2021-04-28 19:53:59.505	warn	(1710020) redis get synology.1.info.connection, error - Connection is closed.
      synology.1	2021-04-28 19:53:59.505	debug	(1710020) * Get info from (firstPoll) api: DSM method: getPollingData params: {}
      synology.1	2021-04-28 19:53:59.505	debug	(1710020) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}}
      synology.1	2021-04-28 19:53:59.505	debug	(1710020) -----------------------------------------------------------------------------------------------------
      synology.1	2021-04-28 19:53:59.504	debug	(1710020) Error: Reconnection after 10s
      synology.1	2021-04-28 19:53:59.504	debug	(1710020) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password
      synology.1	2021-04-28 19:53:59.504	debug	(1710020) * No response, read next.
      synology.1	2021-04-28 19:53:59.475	warn	(1710020) get state error: Connection is closed.
      synology.1	2021-04-28 19:53:59.429	warn	(1710020) get state error: Connection is closed.
      synology.1	2021-04-28 19:53:59.429	warn	(1710020) get state error: Connection is closed.
      synology.1	2021-04-28 19:53:59.428	warn	(1710020) get state error: Connection is closed.
      synology.1	2021-04-28 19:53:59.400	warn	(1710020) redis get synology.1.info.connection, error - Connection is closed.
      synology.1	2021-04-28 19:53:59.399	debug	(1710020) * Get info from (firstPoll) api: DSM method: getPollingData params: {}
      synology.1	2021-04-28 19:53:59.399	debug	(1710020) * sendPolling. namePolling = firstPoll | iteration = 0 | typeof poll = object | poll = {"api":"dsm","method":"getPollingData","params":{}}
      synology.1	2021-04-28 19:53:59.399	debug	(1710020) -----------------------------------------------------------------------------------------------------
      synology.1	2021-04-28 19:53:59.399	debug	(1710020) Error: Reconnection after 10s
      synology.1	2021-04-28 19:53:59.399	debug	(1710020) *** ERROR : src: sendPolling syno[dsm][getPollingData] To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password
      synology.1	2021-04-28 19:53:59.398	debug	(1710020) * No response, read next.
      synology.1	2021-04-28 19:53:59.373	warn	(1710020) redis get synology.1.info.connection, error - DB closed
      synology.1	2021-04-28 19:53:59.373	warn	(1710020) redis get synology.1.info.connection, error - DB closed
      synology.1	2021-04-28 19:53:59.372	warn	(1710020) redis get synology.1.info.connection, error - Connection is closed.
      

      Die Datenpunkte scheinen aber da zu sein. Mit meiner zweiten Synology läuft der Adapter.

      finde es komisch, da der Adapter vor dem Update gelaufen ist. User und PW habe ich nicht geändert und auch schon neu eingegeben.
      Auf die Synology komme ich mit den Anmeldedaten.

      Hat jemand eine Idee

      Gruß
      Holger

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

        @holger-etzel sagte in Synology Adapter startet nicht mehr:

        Nach dem letzten Update von 0.1.20 auf 1.0.0 startet der Adapter nicht mehr und bleibt gelb.
        ... und auch schon neu eingegeben.

        Eventuell blockiert .

        https://forum.iobroker.net/topic/44484/gelöst-synology-ist-nicht-erreichbar/2
        https://forum.iobroker.net/topic/44260/synology-adapter-keine-verbindung-mehr-gelb/4

        Sonst sind hier viele Beiträge und Lösungen zu :

        To use the adapter, the user must be in the Administrators group! code: 400 message: No such account or incorrect password
        

        https://forum.iobroker.net/topic/33224/iobroker-synology-adapter

        Holger Etzel 1 Reply Last reply Reply Quote 0
        • Holger Etzel
          Holger Etzel @Glasfaser last edited by

          @glasfaser

          danke, der Tip war richtig.
          IP war blockiert.

          Danke für die schnelle hilfe

          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

          920
          Online

          32.1k
          Users

          80.6k
          Topics

          1.3m
          Posts

          2
          3
          388
          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