Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[ESP8266]

@esp8266.....gelöscht

[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.

[PatrickFro]

@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]

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

[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]

@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

[ESP8266]

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

[tombox]

@esp8266 probier nochmal

[ESP8266]

@tombox , alles wieder da. :+1:

[oberfragger]

@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]

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

[oberfragger]

@esp8266 Okay. Wird gemacht.

[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.

[tombox]

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

[ESP8266]

@tombox , ich weiss nicht was du geändert hast. Wenn sollte das Datum immer an erster Stelle stehen. Nicht an letzter. So ist die Messung 01 immer Aktuell und die 02 wäre die vorletzte Messung. So hat man einen festen Datenpunkt der Auswertbar ist um sich in der Vis die aktuelle Messung anzeigen zu lassen.

Dieser Datenpunkt wechselt zwischen meinem Gewicht und meiner Frau alle 15 Sek.
Das ist nicht die Waage sondern die Vis....:blush:

[tombox]

@esp8266 ich habs wieder rausgenommen

[ESP8266]

@tombox , Super :+1: ....neu installieren? Gehe ich von aus.

[ESP8266]

@tombox , ist immer noch das aktuelle Datum an letzter Stelle. Habe vor der Aktualisierung den ganzen Datenpunktbaum gelöscht.
Dann alles gelöscht und neu installiert noch immer das Datum an letzter Stelle. Aber nicht vom Github, sondern regulär.

[ESP8266]

@tombox , die Version 0.0.6 vom Github funzt wieder, Danke.

[PatrickFro]

@tombox Ich muss nochmal nerven. Beim Thema Gewicht: Noch immer klappt es bei mir nicht wirklich. Es ist jeden Tag ein anderer Datenpunkt, gestern war es measures4, heute measures1. Ich wiege mich nicht jeden Tag, liegt es vielleicht hieran?

Die Daten werden mit InfluxDB geloggt. Ich schreibe sie in einen anderen Datenpunkt und logge sie von dort, damit das runterrutschen des measures-Datenpunkt kein Problem macht.

Nachdem es auch mit der Version von Git nicht recht klappte, bin ich wieder auf die in IoBroker (0.0.3) zurückgewechselt, aber auch hier ist es weiterhin nicht möglich.

Ich verzweifle etwas.