Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Withings v0.0.x

    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

    Test Withings v0.0.x

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

      @tombox, das Log füllt sich jetzt unnötig....

      2022-02-10 14:36:19.005 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities01.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.007 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities02.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.009 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities03.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.010 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities04.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.012 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities05.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.035 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities06.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.038 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities07.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.040 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities08.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.042 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities09.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.046 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities10.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.048 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities11.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.050 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities12.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.052 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities13.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.054 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities14.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.056 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities15.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.058 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities16.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.060 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities17.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.062 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities18.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.064 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities19.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.065 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities20.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.131 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities21.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.133 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities22.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.135 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities23.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.138 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities24.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.140 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities25.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.157 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities26.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.160 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities27.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.163 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities28.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.165 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities29.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.167 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities30.date" has to be type "string" but received type "number"
      2022-02-10 14:36:19.169 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities31.date" has to be type "string" but received type "number" 
      

      Das war nach einem iob restart.

      T 1 Reply Last reply Reply Quote 0
      • T
        tombox @ESP8266 last edited by

        @esp8266 die änderung ist glaube schon älter einfach mal den ordner activity löschen und adapter neustarten

        1 Reply Last reply Reply Quote 0
        • P
          PatrickFro @tombox last edited by

          @tombox Nicht richtig. Bei Activitiy erscheint nun "Invalid Date" und bei Measures sind nun 86 Datenpunkte, 1-5 sind von heute, einer von gestern etc.

          Wenn es aber darum ging, dass alle Datenpunkte von heute hintereinander sind, dann passt es. In einem Datenpunkt von heute sind sie aber leider nicht alle enthalten

          T 1 Reply Last reply Reply Quote 0
          • T
            tombox @PatrickFro last edited by

            @patrickfro Welcher wert hat denn das invalid date kannst ja den typ auf number oder so ändern

            P ESP8266 2 Replies Last reply Reply Quote 0
            • P
              PatrickFro @tombox last edited by

              @tombox Hinterlegt ist Zeichenkette. Ändern auf Zahl etc. hat leider nichts gebracht..

              1 Reply Last reply Reply Quote 0
              • ESP8266
                ESP8266 @tombox last edited by ESP8266

                @tombox , Nein. Ich hatte vorher den ganzen Baum gelöscht, iob gestoppt dann rebootet, weil ich den Host aktualisiert habe.

                Das kommt jetzt alle 10 Min. Das Log ist schon voll....

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

                  @esp8266.....gelöscht

                  1 Reply Last reply Reply Quote 0
                  • ESP8266
                    ESP8266 @tombox last edited by ESP8266

                    @tombox , und weiter geht es.....glaubst du mir nicht?

                    2022-02-10 21:16:26.078 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities01.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.082 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities02.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.114 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities03.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.115 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities04.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.126 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities05.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.127 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities06.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.129 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities07.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.130 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities08.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.132 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities09.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.134 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities10.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.135 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities11.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.136 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities12.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.138 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities13.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.140 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities14.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.142 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities15.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.145 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities16.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.146 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities17.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.148 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities18.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.149 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities19.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.151 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities20.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.153 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities21.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.154 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities22.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.157 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities23.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.184 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities24.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.187 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities25.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.190 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities26.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.193 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities27.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.196 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities28.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.199 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities29.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.201 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities30.date" has to be type "string" but received type "number"
                    2022-02-10 21:16:26.203 - info: withings.0 (2703) State value to set for "withings.0.28587019.activity.activities31.date" has to be type "string" but received type "number" 
                    

                    Es wurde am Mittag der ganze Baum gelöscht!
                    Vielleicht solltest du mal selbst ins Log schauen und vorher auf Info stellen.

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      PatrickFro @ESP8266 last edited by

                      @esp8266 tombox hat glaub ich keine Withings-Geräte, weshalb wir sicherlich andere Stati und Datenpunkte / Fehlermeldungen erhalten.

                      @tombox Wenn Du zum Testen mal Login-Daten brauchst, sag gern bescheid.

                      ESP8266 1 Reply Last reply Reply Quote 0
                      • ESP8266
                        ESP8266 @PatrickFro last edited by

                        @patrickfro , ich habe jetzt auf Warnung gestellt, nun ist Ruhe....

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          tombox @ESP8266 last edited by tombox

                          @esp8266 es wurden unterschiedlich datum typen verwenden mal alle objekte löschen und via github installieren und schauen ob die fehler weg sind

                          ESP8266 2 Replies Last reply Reply Quote 1
                          • ESP8266
                            ESP8266 @tombox last edited by

                            @tombox , neu installiert.
                            hatte das im log und erstmal laufen lassen.....

                            2022-02-10 22:25:42.673 - info: withings.0 (21606) Please wait a few minutes.... clean old version
                            2022-02-10 22:25:42.802 - info: withings.0 (21606) Done with cleaning
                            2022-02-10 22:25:55.396 - warn: withings.0 (21606) State "withings.0.info.connection" has no existing object, this might lead to an error in future versions
                            2022-02-10 22:25:58.254 - warn: withings.0 (21606) State "withings.0.info.connection" has no existing object, this might lead to an error in future versions
                            2022-02-10 22:26:05.733 - error: withings.0 (21606) https://wbsapi.withings.net/measure
                            2022-02-10 22:26:05.734 - error: withings.0 (21606) TypeError: a.date.localeCompare is not a function
                            2022-02-10 22:26:12.910 - error: withings.0 (21606) https://wbsapi.withings.net/measure
                            2022-02-10 22:26:12.911 - error: withings.0 (21606) TypeError: a.date.localeCompare is not a function
                            
                            T 1 Reply Last reply Reply Quote 0
                            • ESP8266
                              ESP8266 @tombox last edited by

                              @tombox , alle 10 min das gleiche im log. Daten kommen keine mehr...

                              oberfragger 1 Reply Last reply Reply Quote 0
                              • T
                                tombox @ESP8266 last edited by

                                @esp8266 probier nochmal

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

                                  @tombox , alles wieder da. 👍

                                  1 Reply Last reply Reply Quote 0
                                  • oberfragger
                                    oberfragger @ESP8266 last edited by

                                    @esp8266 said in Test Withings v0.0.x:

                                    @tombox , alle 10 min das gleiche im log. Daten kommen keine mehr...

                                    Ich habe das gleiche "Problem".

                                    State value to set for "withings.0.20184649.activity.activities01.date" has to be type "string" but received type "number"
                                    
                                    ...
                                    
                                    State value to set for "withings.0.20184649.sleepSummary.series07.date" has to be type "string" but received type "number"
                                    
                                    ESP8266 1 Reply Last reply Reply Quote 0
                                    • ESP8266
                                      ESP8266 @oberfragger last edited by

                                      @oberfragger , alles löschen und vom Github neu installieren.

                                      oberfragger 1 Reply Last reply Reply Quote 0
                                      • oberfragger
                                        oberfragger @ESP8266 last edited by

                                        @esp8266 Okay. Wird gemacht.

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

                                          @tombox , hast du die Reihenfolge geändert. Warum? So kann man keinen festen Datenpunkt mehr definieren für z.B Vis, weil die aktuelle Messung jetzt hinten angehängt wird und sich jedes mal die Aufzählung ändert.

                                          1 Reply Last reply Reply Quote 0
                                          • T
                                            tombox last edited by

                                            @esp8266 Ich bin der Meinung dass die sortierung nach date ist? Ist created etwa besser?

                                            ESP8266 P 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            793
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            49
                                            516
                                            85013
                                            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