Navigation

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

    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

    R
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 35
    • Best 1
    • Groups 1

    Romantikus1977

    @Romantikus1977

    1
    Reputation
    103
    Profile views
    35
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Romantikus1977 Follow
    Starter

    Best posts made by Romantikus1977

    • RE: ioBroker Synology Adapter

      @lobomau

      Der Problematik schließe ich mich hiermit gerne an.
      Leider habe ich 5 Webcams von RLC, die ich seit dem Update auf DSM7 nicht mehr über den Adapter per Snapshot ansprechen kann.
      Über eine Korrektur würde ich mich sehr freuen.

      posted in ioBroker Allgemein
      R
      Romantikus1977

    Latest posts made by Romantikus1977

    • RE: Solarman PV, Bosswerk MI & Deye

      @rene55 done - kannst du mir irgendwie behilflich sein meinen WR in diesem Adapter zum Laufen zu bekommen ?
      https://forum.iobroker.net/topic/63899/adapter-cloudfreie-auslesung-von-deye-invertern

      posted in Tester
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      Der Support hat sich nun nach Wochen gemeldet - sie haben ihre Regularien geändert und wollen aktiv eine Zustimmung zu den neuen Developer Regularien:
      Ausschnitt der Mail:
      Thank you for your continued support and trust in the Solarman-OpenAPI service provided by Wuxi IGEN Technology Co! We are pleased to announce an important notice.

      Recently, in order to strengthen the implementation of security compliance, we have decided to adjust the Solarman-OpenAPI service and need to sign an API developer agreement with you and related parties. The developer agreement will detail the rules of use of the service, including but not limited to paid content, access rights, data use, security regulations and consequences of violations. We hope that through this agreement, we can ensure that the rights and interests of both parties are fully protected when using the API.

      You can view the new API Developer Agreement by downloading the attachment to this email. We recommend you to read the content of the agreement as soon as possible, and confirm the agreement by replying "I have understood all the contents of the Developer Agreement and agree to be bound by it" to this email address.

      After you complete the agreement confirmation, our service specialist will send you the account information and OpenAPI documentation by email.

      Before you start to call the service interface, please make sure that you have understood the call frequency and device limitations, for details, please refer to: SolarmanOpenAPI-global(v1.1.6) in the attachment. In addition, we will continue to update the relevant documents to provide you with a better service experience.

      If you have any questions on the content of the agreement or need further information, please feel free to ask us.

      Once again, thank you for your trust and support of IGEN Technology!

      Best Regard

      posted in Tester
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      @rene55 deyeidc

      posted in Tester
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      @rene55 nein leider keine app deswegen der umweg ueber die cloud dein adapter verbindet sich aber ich erhalte keine werte

      posted in Tester
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      @rene55 diesen WR habe ich am Start: Ein SolarMax Wechselrichter 1600SGA
      db9c8625-90ab-42e0-a270-e85dc96bbd68-image.png

      posted in Tester
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      @rene55 Danke - schreibe gleich mal den Support an. Gehe ich Recht der Annahme, dass ich deinen Adapter nur benutzen kann wenn es sich um einen DEYE oder Bosswerk WR handelt ? Ich habe aber ein anderes System für das ich bisher noch keine Adapter Alternative gefunden habe

      posted in Tester
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      Dann reihe ich mich heute mal ein - ich habe auch seit 3 Tagen das Problem mit dem Adapter.
      Keine Aktualisierung der Onjekte / Werte mehr
      Fehlermeldung : [initializeStation] error: undefined
      Mein System ist vollständig aktuell

      Im Debugmodus zeigt das Protokoll folgendes an:

      solarmanpv.0
      2024-05-13 20:32:38.578 info Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule

      solarmanpv.0
      2024-05-13 20:32:38.577 debug [onReady] finished - stopping instance

      solarmanpv.0
      2024-05-13 20:32:38.576 debug [main] catch "appId insufficient allowance"

      posted in Tester
      R
      Romantikus1977
    • RE: [Neuer Adapter] Reolink Kamera

      @cs Hi also ich hatte lange die gleichen Probleme - Lösung: Mein PW auf der Kamera hatte eine Sonderzeichen "#" das konnte der Adapter wohl nicht verarbeiten. Nun habe ich ein PW ohne Sonderzeichen und es funktioniert !

      posted in Entwicklung
      R
      Romantikus1977
    • RE: Solarman PV, Bosswerk MI & Deye

      @rene55 Erstmal vielen Dank, dass sich jemand der BOSSWERK Thematik annimmt. Schließe gerade meine Anlage an und werde den Adapter dann danken testen / nutzen.

      posted in Tester
      R
      Romantikus1977
    • RE: ioBroker Synology Adapter

      Hallo zusammen,
      seit einigen Wochen bekomme ich viele Fehlermeldung bei dem Adapter.
      U.a. kann ich die Snapshot Funktion meiner Kameras nicht mehr nutzen weil die Objekte nicht mehr up to date sind
      Hat noch jemand vgl. Probleme ?

      
      synology.0
      2022-03-18 16:57:26.249	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_1.used" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.248	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_1.used_size" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.247	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_1.total_size" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.246	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_2.used" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.245	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_2.used_size" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.204	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_2.total_size" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.171	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_3.used" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.162	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_3.used_size" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:26.160	info	State value to set for "synology.0.DiskStationManager.vol_info.volume_3.total_size" has to be type "number" but received type "string"
      
      synology.0
      2022-03-18 16:57:08.775	info	State value to set for "synology.0.FileStation.info.items.2" has to be stringified but received type "object"
      
      synology.0
      2022-03-18 16:57:08.774	info	State value to set for "synology.0.FileStation.info.items.1" has to be stringified but received type "object"
      
      synology.0
      2022-03-18 16:57:08.773	info	State value to set for "synology.0.FileStation.info.items.0" has to be stringified but received type "object"
      
      synology.0
      2022-03-18 16:57:08.772	info	State value to set for "synology.0.FileStation.info.enable_view_microsoft" has to be type "string" but received type "boolean"
      
      synology.0
      2022-03-18 16:57:08.771	info	State value to set for "synology.0.FileStation.info.enable_view_google" has to be type "string" but received type "boolean"
      
      synology.0
      2022-03-18 16:57:08.770	info	State value to set for "synology.0.FileStation.info.enable_send_email_attachment" has to be type "string" but received type "boolean"
      
      synology.0
      2022-03-18 16:57:07.962	info	DSM 3
      
      synology.0
      2022-03-18 16:57:04.540	info	Connecting to Synology 192.168.0.22:5001
      
      synology.0
      2022-03-18 16:57:04.494	info	starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.synology, node: v14.19.0, js-controller: 4.0.21
      
      synology.0
      2022-03-18 16:57:04.372	warn	This object will not be created in future versions. Please report this to the developer.
      
      synology.0
      2022-03-18 16:57:04.368	warn	Object synology.0.SurveillanceStation.getSnapshotCamera is invalid: Default value has to be type "string" but received type "number"
      

      Bin wohl nicht ganz alleine - für einen Teil gibt es schon ein Issue auf Git:
      bdcd5474-a7a5-49f8-bd19-e652526a11d8-image.png

      posted in ioBroker Allgemein
      R
      Romantikus1977
    Community
    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
    The ioBroker Community 2014-2023
    logo