Test Withings v0.0.x
-
@stoffel67 Bei mir ist z.B. bei 08 kein Gewicht sondern Pulswellengeschwindigkeit.
Ich hoffe, das ist es was du brauchst.
-
@patrickfro ,
bei mir wird immer 01 aktualisiert. Die anderen werden nach oben geschoben. Sonst könnte ich nicht damit in Vis arbeiten.... -
Wieviele Datenpunkte hast Du denn? Ich habe aktuell measuregrps01 bis measuregrps11. Vielleicht nutze ich es noch zu kurz, so dass z.b. 14 Datenpunkte vorhanden sein sollten und daher die Daten nicht mehr im selben Datenpunkt wie gestern zu finden sind.
-
@patrickfro , das hat nichts mit den Messpunkten zutun.....das ist eine Art Schieberegister nach unten.
Der aktuelleste Wert ist immer 01. Ich beziehe mich auf das Gewicht. Mehr kann meine Waage nicht. Das wird mit den anderen Geräten bzw. Messpunkten nicht anders sein.
Sonst lösch den ganzen Baum und starte den Adapter neu.....dann wird er neu aufgebaut. -
@patrickfro installier mal via github und schau ob die einträge nach datum sortiert sind
-
@tombox , bei mir liegt immer das Datum auf dem letzten Tag der Messung an erster Stelle. Derzeit Heute...
-
@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.
-
@esp8266 die änderung ist glaube schon älter einfach mal den ordner activity löschen und adapter neustarten
-
@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
-
@patrickfro Welcher wert hat denn das invalid date kannst ja den typ auf number oder so ändern
-
@tombox Hinterlegt ist Zeichenkette. Ändern auf Zahl etc. hat leider nichts gebracht..
-
@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.....gelöscht
-
@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. -
@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.
-
@patrickfro , ich habe jetzt auf Warnung gestellt, nun ist Ruhe....
-
@esp8266 es wurden unterschiedlich datum typen verwenden mal alle objekte löschen und via github installieren und schauen ob die fehler weg sind
-
@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 -
@tombox , alle 10 min das gleiche im log. Daten kommen keine mehr...
-
@esp8266 probier nochmal
