NEWS
[gelöst] Netatmo Adapter aktualisiert nicht mehr nach Update
-
@tombir Zeig nochmal den Stand jetzt:
uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
-
pi@raspberrypi:~ $ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SES SION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sud o apt update && apt policy nodejs armv7l Kein Docker /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.18.1 v16.18.1 8.19.2 4.0.23 pi pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker tty /home/pi Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 http://archive.raspberrypi.org/debian buster InRelease Hit:3 https://repos.influxdata.com/debian buster InRelease Hit:4 https://deb.nodesource.com/node_16.x buster InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. nodejs: Installed: 16.18.1-deb-1nodesource1 Candidate: 16.18.1-deb-1nodesource1 Version table: *** 16.18.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u2 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
-
-
@thomas-braun said in Netatmo Adapter aktualisiert Daten nicht mehr nach Update:
iobroker update
sagt?
Used repository: stable Adapter "admin" : 6.2.23 , installed 6.2.23 Adapter "backitup" : 2.5.4 , installed 2.5.4 Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "echarts" : 1.0.12 , installed 1.0.12 Adapter "flot" : 1.11.0 , installed 1.11.0 Adapter "fritzdect" : 2.2.3 , installed 2.2.3 Adapter "fronius" : 1.1.3 , installed 1.1.6 Adapter "history" : 2.2.0 , installed 2.2.0 Adapter "homekit-controller": 0.5.1, installed 0.5.1 Adapter "influxdb" : 3.1.8 , installed 3.1.8 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "javascript" : 6.0.3 , installed 6.0.3 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "netatmo" : 2.0.5 , installed 2.0.5 Adapter "ocpp" : 0.4.0 , installed 0.4.0 Adapter "onvif" : 0.4.4 , installed 0.4.4 Adapter "parser" : 1.1.8 , installed 1.1.8 Adapter "ping" : 1.5.3 , installed 1.5.3 Adapter "simple-api" : 2.7.0 , installed 2.7.0 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "tr-064" : 4.2.16 , installed 4.2.16 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-hqwidgets": 1.3.0 , installed 1.3.0 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0
-
-
@thomas-braun said in Netatmo Adapter aktualisiert Daten nicht mehr nach Update:
Gut.
Dann exerzier nochmal die Anmeldung bei netatmo durch.Ist alles durch gelaufen ohne Fehlermeldung.
Unter Objekte ist jetzt ein zweites Gerät aufgetaucht mit einer kryptischen Bezeichnung.
Leider werden noch immer die alten Werte angezeigt und nicht aktualisiert.Im Protokoll finde ich diese debug-Angaben, aber keine error
code_textnetatmo.0 2022-11-13 22:32:25.691 debug stateChange netatmo.0.5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.LastUpdate {"val":"Sun Nov 13 2022 22:26:09 GMT+0100 (Central European Standard Time)","ack":true,"ts":1668375145688,"q":0,"from":"system.adapter.netatmo.0","user":"system.user.admin","lc":1668375145688} netatmo.0 2022-11-13 22:32:25.637 debug Update object 5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.LastUpdate ...{"type":"state","common":{"name":"Last update","type":"string","role":"value.date","read":true,"write":false},"from":"system.adapter.netatmo.0","user":"system.user.admin","ts":1668374545463} => {"type":"state","common":{"name":"Last update","type":"string","role":"value.date","read":true,"write":false}} netatmo.0 2022-11-13 22:32:25.636 debug stateChange netatmo.0.5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.RfStatus {"val":"bad","ack":true,"ts":1668375145634,"q":0,"from":"system.adapter.netatmo.0","user":"system.user.admin","lc":1668374511774} netatmo.0 2022-11-13 22:32:25.626 debug Update object 5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.RfStatus ...{"type":"state","common":{"name":"Radio status","type":"string","role":"value.rf","read":true,"write":false},"from":"system.adapter.netatmo.0","user":"system.user.admin","ts":1668374545450} => {"type":"state","common":{"name":"Radio status","type":"string","role":"value.rf","read":true,"write":false}} netatmo.0 2022-11-13 22:32:25.622 debug stateChange netatmo.0.5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.BatteryStatus {"val":84,"ack":true,"ts":1668375145608,"q":0,"from":"system.adapter.netatmo.0","user":"system.user.admin","lc":1668374511706} netatmo.0 2022-11-13 22:32:25.553 debug Update object 5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.BatteryStatus ...{"type":"state","common":{"name":"Battery status","type":"number","role":"value.battery","read":true,"write":false,"min":0,"max":100,"unit":"%"},"from":"system.adapter.netatmo.0","user":"system.user.admin","ts":1668374545437} => {"type":"state","common":{"name":"Battery status","type":"number","role":"value.battery","read":true,"write":false,"min":0,"max":100,"unit":"%"}} netatmo.0 2022-11-13 22:32:25.544 debug Update object 5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.Rain.SumRain24MaxDate ...{"type":"state","common":{"name":"Absolute rain in 24 hours maximum date","type":"string","role":"value.date","read":true,"write":false},"from":"system.adapter.netatmo.0","user":"system.user.admin","ts":1668374545429} => {"type":"state","common":{"name":"Absolute rain in 24 hours maximum date","type":"string","role":"value.date","read":true,"write":false}} netatmo.0 2022-11-13 22:32:25.537 debug Update object 5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.Rain.SumRain24Max ...{"type":"state","common":{"name":"Absolute rain in 24 hours maximum","type":"number","role":"value","read":true,"write":false,"unit":"mm"},"from":"system.adapter.netatmo.0","user":"system.user.admin","ts":1668374545422} => {"type":"state","common":{"name":"Absolute rain in 24 hours maximum","type":"number","role":"value","read":true,"write":false,"unit":"mm"}} netatmo.0 2022-11-13 22:32:25.536 debug stateChange netatmo.0.5e9d7bc0a91a645c33155601.70-ee-50-15-df-22.05-00-00-05-40-16.Rain.SumRain24 {"val":0.2,"ack":true,"ts":1668375145534,"q":0,"from":"system.adapter.netatmo.0","user":"system.user.admin","lc":1668374511671}
-
Objekte mal löschen.
Adapterneustart sieht wie aus?
Und bitte das log ausiob logs --watch | uniq
nehmen. Das liest sich besser (wenn du das puTTY-Fenster aufziehst). Ich mag nicht von unten nach oben lesen.
-
@tombir said in Netatmo Adapter aktualisiert Daten nicht mehr nach Update:
Leider werden noch immer die alten Werte angezeigt und nicht aktualisiert.
Ich glaube ich habe in den falschen Zeilen gesucht.
Hier finde ich aktuelle Daten!
Ich muss wohl in vis nur neue Datenpunkte verknüpfen.
Vielen Dank, Thomas, für deine Hilfe!!!
-
@tombir said in Netatmo Adapter aktualisiert Daten nicht mehr nach Update:
Ich glaube ich habe in den falschen Zeilen gesucht.
Mit den falschen Zeilen meine ich, dass ich wie üblich unter Luckyweather gesucht hatte, und nicht unter dem darüber stehenden neuen "kryptischen" Eintrag.
-
Die alten Objekte kannst du löschen. Offenbar werden die jetzt neustrukturiert.