Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Einbindung von Geräten
    5. Solax WR zeigt teils keine aktuellen Daten in den Objekten

    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

    Solax WR zeigt teils keine aktuellen Daten in den Objekten

    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Chris999 @wendy2702 last edited by

      @wendy2702 Habe ich gemacht.
      Er holt dann tatsächlich die aktuellen Daten..die sind kurz grün und werden dann schwarz

      Ich probiere mal eben, das in Putty zu ziehen

      1 Reply Last reply Reply Quote 0
      • C
        Chris999 @wendy2702 last edited by

        @wendy2702 So..nochmal...
        Was muss ich jetzt genau in Putty eingeben?
        Ich logge mich doch erst auf dem Pi ein...oder?
        Da kann er aber mit dem Kommando nichts anfangen

        1 Reply Last reply Reply Quote 0
        • C
          Chris999 @simatec last edited by wendy2702

          @simatec Ich habe jetzt mal bei Protokolle den Log heruntergeladen...

          2022-02-28 22:00:40.896 - info: host.raspberrypi "system.adapter.solax.0" enabled
          2022-02-28 22:00:40.969 - info: host.raspberrypi instance system.adapter.solax.0 started with pid 16308
          2022-02-28 22:00:42.119 - debug: solax.0 (16308) Redis Objects: Use Redis connection: 127.0.0.1:9001
          2022-02-28 22:00:42.156 - debug: solax.0 (16308) Objects client ready ... initialize now
          2022-02-28 22:00:42.158 - debug: solax.0 (16308) Objects create System PubSub Client
          2022-02-28 22:00:42.160 - debug: solax.0 (16308) Objects create User PubSub Client
          2022-02-28 22:00:42.183 - debug: solax.0 (16308) Objects client initialize lua scripts
          2022-02-28 22:00:42.189 - debug: solax.0 (16308) Objects connected to redis: 127.0.0.1:9001
          2022-02-28 22:00:42.214 - debug: solax.0 (16308) Redis States: Use Redis connection: 127.0.0.1:9000
          2022-02-28 22:00:42.223 - debug: solax.0 (16308) States create System PubSub Client
          2022-02-28 22:00:42.224 - debug: solax.0 (16308) States create User PubSub Client
          2022-02-28 22:00:42.237 - debug: solax.0 (16308) States connected to redis: 127.0.0.1:9000
          2022-02-28 22:00:42.287 - debug: solax.0 (16308) Plugin sentry Initialize Plugin (enabled=true)
          2022-02-28 22:00:42.641 - warn: solax.0 (16308) Object solax.0.suninfo.Altitude is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.642 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.646 - warn: solax.0 (16308) Object solax.0.suninfo.Altitude is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.646 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.656 - info: solax.0 (16308) State value to set for "solax.0.suninfo.Altitude" has to be type "number" but received type "string"
          2022-02-28 22:00:42.663 - warn: solax.0 (16308) Object solax.0.suninfo.Azimut is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.663 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.666 - warn: solax.0 (16308) Object solax.0.suninfo.Azimut is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.667 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.673 - info: solax.0 (16308) State value to set for "solax.0.suninfo.Azimut" has to be type "number" but received type "string"
          2022-02-28 22:00:42.679 - warn: solax.0 (16308) Object solax.0.history.yield_1_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.680 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.683 - warn: solax.0 (16308) Object solax.0.history.yield_1_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.683 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.733 - info: solax.0 (16308) State value to set for "solax.0.history.yield_1_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.739 - warn: solax.0 (16308) Object solax.0.history.yield_2_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.739 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.742 - warn: solax.0 (16308) Object solax.0.history.yield_2_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.743 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.749 - info: solax.0 (16308) State value to set for "solax.0.history.yield_2_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.755 - warn: solax.0 (16308) Object solax.0.history.yield_3_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.756 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.759 - warn: solax.0 (16308) Object solax.0.history.yield_3_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.759 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.768 - info: solax.0 (16308) State value to set for "solax.0.history.yield_3_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.774 - warn: solax.0 (16308) Object solax.0.history.yield_4_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.775 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.777 - warn: solax.0 (16308) Object solax.0.history.yield_4_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.778 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.784 - info: solax.0 (16308) State value to set for "solax.0.history.yield_4_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.790 - warn: solax.0 (16308) Object solax.0.history.yield_5_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.791 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.793 - warn: solax.0 (16308) Object solax.0.history.yield_5_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.794 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.843 - info: solax.0 (16308) State value to set for "solax.0.history.yield_5_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.849 - warn: solax.0 (16308) Object solax.0.history.yield_6_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.849 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.852 - warn: solax.0 (16308) Object solax.0.history.yield_6_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.852 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.859 - info: solax.0 (16308) State value to set for "solax.0.history.yield_6_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.865 - warn: solax.0 (16308) Object solax.0.history.yield_7_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.865 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.868 - warn: solax.0 (16308) Object solax.0.history.yield_7_days_ago is invalid: Default value has to be type "number" but received type "string"
          2022-02-28 22:00:42.869 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.876 - info: solax.0 (16308) State value to set for "solax.0.history.yield_7_days_ago" has to be type "number" but received type "string"
          2022-02-28 22:00:42.891 - warn: solax.0 (16308) Object solax.0.info.success is invalid: Default value has to be type "boolean" but received type "string"
          2022-02-28 22:00:42.892 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.894 - warn: solax.0 (16308) Object solax.0.info.success is invalid: Default value has to be type "boolean" but received type "string"
          2022-02-28 22:00:42.895 - warn: solax.0 (16308) This object will not be created in future versions. Please report this to the developer.
          2022-02-28 22:00:42.901 - info: solax.0 (16308) State value to set for "solax.0.info.success" has to be type "boolean" but received type "string"
          2022-02-28 22:00:42.963 - info: solax.0 (16308) starting. Version 0.3.7 in /opt/iobroker/node_modules/iobroker.solax, node: v14.19.0, js-controller: 4.0.15
          2022-02-28 22:00:42.989 - debug: solax.0 (16308) Solax is started
          2022-02-28 22:00:43.010 - debug: solax.0 (16308) System longitude: 9.205442731944252 System latitude: 52.80312946030813
          2022-02-28 22:00:43.011 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:00:43.012 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:00:43.013 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:00:43.013 - debug: solax.0 (16308) current local Time: 22:00
          2022-02-28 22:00:43.015 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:00:43.015 - debug: solax.0 (16308) Sun Altitude: -35.1°
          2022-02-28 22:00:43.015 - debug: solax.0 (16308) Sun Azimut: 310.5°
          2022-02-28 22:00:43.157 - debug: solax.0 (16308) Request Interval: 1 minute(s)
          2022-02-28 22:00:43.398 - debug: solax.0 (16308) API Request successfully completed
          2022-02-28 22:00:45.473 - debug: solax.0 (16308) solaxRequest: {"success":true,"exception":"Query success!","result":{"inverterSN":"H3UE10H1011006","sn":"SWFFTM5RNN","acpower":196,"yieldtoday":34.4,"yieldtotal":4904.1,"feedinpower":-30,"feedinenergy":7436.06,"consumeenergy":1127.73,"soc":68,"inverterType":"5","inverterStatus":"102","uploadTime":"2022-02-28 21:59:11","batPower":-212}}
          2022-02-28 22:01:43.159 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:01:43.162 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:01:43.163 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:01:43.164 - debug: solax.0 (16308) current local Time: 22:01
          2022-02-28 22:01:43.165 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:01:43.166 - debug: solax.0 (16308) Sun Altitude: -35.2°
          2022-02-28 22:01:43.167 - debug: solax.0 (16308) Sun Azimut: 310.8°
          2022-02-28 22:01:43.191 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:02:43.160 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:02:43.161 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:02:43.162 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:02:43.162 - debug: solax.0 (16308) current local Time: 22:02
          2022-02-28 22:02:43.163 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:02:43.164 - debug: solax.0 (16308) Sun Altitude: -35.3°
          2022-02-28 22:02:43.164 - debug: solax.0 (16308) Sun Azimut: 311.1°
          2022-02-28 22:02:43.188 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:03:43.160 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:03:43.162 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:03:43.162 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:03:43.163 - debug: solax.0 (16308) current local Time: 22:03
          2022-02-28 22:03:43.164 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:03:43.165 - debug: solax.0 (16308) Sun Altitude: -35.5°
          2022-02-28 22:03:43.165 - debug: solax.0 (16308) Sun Azimut: 311.3°
          2022-02-28 22:03:43.183 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:04:43.160 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:04:43.161 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:04:43.162 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:04:43.163 - debug: solax.0 (16308) current local Time: 22:04
          2022-02-28 22:04:43.163 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:04:43.164 - debug: solax.0 (16308) Sun Altitude: -35.6°
          2022-02-28 22:04:43.165 - debug: solax.0 (16308) Sun Azimut: 311.6°
          2022-02-28 22:04:43.181 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:05:43.160 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:05:43.162 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:05:43.163 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:05:43.164 - debug: solax.0 (16308) current local Time: 22:05
          2022-02-28 22:05:43.165 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:05:43.166 - debug: solax.0 (16308) Sun Altitude: -35.7°
          2022-02-28 22:05:43.167 - debug: solax.0 (16308) Sun Azimut: 311.9°
          2022-02-28 22:05:43.189 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:06:43.161 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:06:43.162 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:06:43.162 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:06:43.163 - debug: solax.0 (16308) current local Time: 22:06
          2022-02-28 22:06:43.164 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:06:43.164 - debug: solax.0 (16308) Sun Altitude: -35.8°
          2022-02-28 22:06:43.165 - debug: solax.0 (16308) Sun Azimut: 312.2°
          2022-02-28 22:06:43.187 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:07:43.161 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:07:43.162 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:07:43.163 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:07:43.164 - debug: solax.0 (16308) current local Time: 22:07
          2022-02-28 22:07:43.165 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:07:43.166 - debug: solax.0 (16308) Sun Altitude: -35.9°
          2022-02-28 22:07:43.166 - debug: solax.0 (16308) Sun Azimut: 312.4°
          2022-02-28 22:07:43.189 - debug: solax.0 (16308) is Night: true
          2022-02-28 22:08:43.161 - debug: solax.0 (16308) nightCalc started ...
          2022-02-28 22:08:43.162 - debug: solax.0 (16308) nauticalDusk: 19:14
          2022-02-28 22:08:43.163 - debug: solax.0 (16308) nauticalDawn: 06:00
          2022-02-28 22:08:43.164 - debug: solax.0 (16308) current local Time: 22:08
          2022-02-28 22:08:43.165 - debug: solax.0 (16308) calculate astrodata ...
          2022-02-28 22:08:43.165 - debug: solax.0 (16308) Sun Altitude: -36°
          2022-02-28 22:08:43.166 - debug: solax.0 (16308) Sun Azimut: 312.7°
          2022-02-28 22:08:43.196 - debug: solax.0 (16308) is Night: true
          

          Mod Edit: log in Code Tags gesetzt

          wendy2702 simatec 2 Replies Last reply Reply Quote 0
          • wendy2702
            wendy2702 @Chris999 last edited by

            @chris999 Hast du den Adapter mal gestoppt, alle Objekte gelöscht und Adapter neu gestartet?

            Ist das log von nach dieser Aktion?

            C 1 Reply Last reply Reply Quote 0
            • simatec
              simatec Developer Most Active @Chris999 last edited by

              @chris999 sagte in Solax WR zeigt teils keine aktuellen Daten in den Objekten:

              is Night: true

              In der Nacht holt er keine daten.
              Wenn gewünscht, kann ich das konfigurierbar machen

              C 1 Reply Last reply Reply Quote 0
              • C
                Chris999 @wendy2702 last edited by

                @wendy2702 Ja...gestoppt, gelöscht und neu gestartet. Dann den log gezogen

                1 Reply Last reply Reply Quote 0
                • C
                  Chris999 @simatec last edited by Chris999

                  @simatec Er holt tagsüber auch nicht alle Daten
                  Aktuell ist:
                  acpower vom 1.3. 07:24
                  batpower vom 1.3. 19:16
                  consumeenergy vom 1.3. 19:16
                  feedinenergy vom 1.3. 19:16
                  feedinpower vom 28.2. 22:00
                  soc vom 1.3. 19:16

                  Aktuelle Uhrzeit ist 20:05

                  ist schon seltsam, dass er so unterschiedlich die Daten holt...oder nicht holt..
                  zumindest soc wäre auch nachts interessant.
                  Aber am wichtigsten für mich ist feedinpower, um meine Klimaanlagen bedarfsgerecht schalten zu können.

                  Bekommen wir das irgendwie hin?

                  simatec 1 Reply Last reply Reply Quote 0
                  • simatec
                    simatec Developer Most Active @Chris999 last edited by

                    @chris999 Das hört sich sehr komisch an.
                    Hab meine Anlage gerade mal auf Cloud umgestellt und alle Daten kommen im 5 Minuten Intervall.

                    Mache mal folgendes.
                    Hole dir mal die Daten parallel zur Abfrage über den browser und vergleiche diese mal.
                    Somit können wir ausschließen, ob das Problem beim adapter oder bei deiner Cloudabfrage liegt.

                    https://www.eu.solaxcloud.com:9443/proxy/api/getRealtimeInfo.do?tokenId=XXXXXXXXXXXXXXXXXXXXX&sn=XXXXXXXX

                    C 1 Reply Last reply Reply Quote 0
                    • C
                      Chris999 @simatec last edited by

                      @simatec Habe ich jetzt gerade mal gemacht.
                      Da passen die Werte genau. Der Adapter zieht die bei mir aber aus der Cloud..oder?
                      Kann ich das umstellen, dass er die Werte direkt vom WR bekommt?

                      simatec 1 Reply Last reply Reply Quote 0
                      • simatec
                        simatec Developer Most Active @Chris999 last edited by

                        @chris999 Das sind die Daten aus der Cloud.
                        Zeige mir mal bitte die Ausgabe im Browser und die Werte im Adapter.

                        Welche Version vom Solax Adapter ist installiert?

                        C 1 Reply Last reply Reply Quote 0
                        • C
                          Chris999 @simatec last edited by Chris999

                          @simatec
                          Werte im Browser:

                          success true
                          exception "Query success!"
                          result
                          inverterSN "H3UE10H1011006"
                          sn "SWFFTM5RNN"
                          acpower 1164
                          yieldtoday 1.1
                          yieldtotal 4962.7
                          feedinpower -18
                          feedinenergy 7517.11
                          consumeenergy 1140.14
                          feedinpowerM2 0
                          soc 52
                          peps1 0
                          peps2 0
                          peps3 0
                          inverterType "5"
                          inverterStatus "102"
                          uploadTime "2022-03-03 08:54:31"
                          batPower 1406
                          powerdc1 299
                          powerdc2 2259
                          powerdc3 null
                          powerdc4 null

                          Werte Cloud.jpg

                          Installierte Adapterversion ist 0.3.7

                          EDIT: Werte weichen etwas ab, da wohl nicht exakt zeitgleich erfasst

                          simatec 1 Reply Last reply Reply Quote 0
                          • simatec
                            simatec Developer Most Active @Chris999 last edited by

                            @chris999 sagte in Solax WR zeigt teils keine aktuellen Daten in den Objekten:

                            EDIT: Werte weichen etwas ab, da wohl nicht exakt zeitgleich erfasst

                            Das ist nicht relevant, da die daten in der Cloud nur alle 5 Minuten aktualisiert werden.
                            Mir sind aber die Daten in der Browserausgabe und die Daten im iobroker wichtig.

                            Die muss ich vergleichen
                            D.h. Wenn der Adapter die Daten abgerufen hat, dann hole dir parallel die daten vom Browser
                            Und genau die benötige ich.

                            Ein Tipp wäre noch, die aktuelle latest zu installieren und nach Anleitung den Expertenmodus aktivieren, den Wifi Stick auf die Firmwareversion laut Anleitung zu flashen und sekundengenaue Daten direkt und lokal ohne Cloud zu bekommen.

                            Wenn du weiterhin lieber die Cloud nutzen willst, dann mache trotzdem mal bitte ein Update des Adapters auf die aktuelle latest Version.

                            C 1 Reply Last reply Reply Quote 0
                            • C
                              Chris999 @simatec last edited by

                              @simatec
                              Browser:
                              success true
                              exception "Query success!"
                              result
                              inverterSN "H3UE10H1011006"
                              sn "SWFFTM5RNN"
                              acpower 1407
                              yieldtoday 1.5
                              yieldtotal 4963.1
                              feedinpower -103
                              feedinenergy 7517.5
                              consumeenergy 1140.54
                              feedinpowerM2 0
                              soc 54
                              peps1 0
                              peps2 0
                              peps3 0
                              inverterType "5"
                              inverterStatus "102"
                              uploadTime "2022-03-03 09:09:31"
                              batPower 1295
                              powerdc1 329
                              powerdc2 2346
                              powerdc3 null
                              powerdc4 null

                              iobroker:
                              iobroker.jpg

                              Wenn ich die Daten direkt vom Stick in ioBroker bekommen will...läuft die Cloud dann nicht mehr?
                              Das würde ich schon gerne weiter nutzen...sonst kann ich von unterwegs ja nicht mehr auf die Anlage zugreifen...

                              Beim ioBroker wird die 0.3.7 als neueste Version angezeigt

                              1 Reply Last reply Reply Quote 0
                              • simatec
                                simatec Developer Most Active last edited by

                                @chris999 Du musst deine Repo von Stable auf Beta umstellen.
                                5f5cce53-7477-46f6-8ac2-a72cf29ed395-image.png

                                Die Cloud funktioniert auch mit lokaler Abfrage

                                Was du genau machen musst, um lokal abfragen zu können, steht in der Doku

                                C 1 Reply Last reply Reply Quote 0
                                • C
                                  Chris999 @simatec last edited by

                                  @simatec Danke..werde ich mal machen.
                                  Das ist für mich alle noch extremes Neuland. Aber ich gebe mein Bestes, diese Sachen zu lernen.

                                  Die Anleitung zum lokalen Abfragen hatte ich schon gelesen...aber gehofft, das nicht anwenden zu müssen 😉

                                  Danke schonmal für deine Geduld mit mir... mit 50 lernt man nicht mehr so schnell neue Dinge 😉

                                  simatec 1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active @Chris999 last edited by

                                    @chris999 Die lokale Abfrage ist auch kein muss. Die Daten aus der Cloud sind im Grunde ausreichend.
                                    Nachteil bei der Cloud ist halt, dass man vor Störungen in der Cloud nicht geschützt ist und der Abruf nur alle 5 Minuten passieren kann.

                                    Teste bitte erstmal die aktuelle Beta Version.

                                    C 1 Reply Last reply Reply Quote 0
                                    • C
                                      Chris999 @simatec last edited by

                                      @simatec So.. ich hatte ja heute Vormittag die Beta Version geladen. Leider hat sich am Verhalten nichts geändert.
                                      Ich habe dann die Firmware auf dem Stick auf die Version dowgraded, die du in der Doku hinterlegt hast und in den Experteneinstellungen auf Lokal gestellt.
                                      In der Doku steht, die Firmware darf nicht höher, als 2.30.20 sein. Die hinterlegte Firmware ist allerding 2.33.20.
                                      Ist das so korrekt?
                                      Jedenfalls kommen jetzt gar keine Daten mehr rein. in den Objekten
                                      Oder habe ich einen Fehler gemacht?
                                      Der Adapter ist jedenfalls grün.

                                      simatec 1 Reply Last reply Reply Quote 0
                                      • simatec
                                        simatec Developer Most Active @Chris999 last edited by

                                        @chris999
                                        Ja in der Doku ist noch ein Schreibfehler. Ist mir auch gerade aufgefallen.
                                        Die Firmware ist richtig.

                                        Zeige mal deine Einstellungen im Adapter und ein Screenshot des Webinterfaces vom Stick

                                        C 1 Reply Last reply Reply Quote 0
                                        • C
                                          Chris999 @simatec last edited by

                                          @simatec Einstellungen Adapter.jpg Stick1.jpg Stick2.jpg Stick3.jpg

                                          simatec 1 Reply Last reply Reply Quote 0
                                          • simatec
                                            simatec Developer Most Active @Chris999 last edited by

                                            @chris999 Die lokale IP (192.168.188.105) in den Adaptereinstellungen fehlt.
                                            Des Weiteren musst du auch dein Passwort (Passwort des Wifi Sticks >>> Standard admin) in den Adaptereinstellungen setzen.

                                            d5f0ea82-bdb3-4276-910c-c3de485dc186-image.png

                                            C 2 Replies Last reply Reply Quote 1
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            866
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            4
                                            52
                                            4661
                                            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