Hallo zusammen,
JSONMOD auf einer Fhem Instanz auf einem Proxmox X86 als Container (Debian) funktioniert. Exact identische JSONMOD Config auf einer Fhem Instanz auf einem Proxmox Raspberry Pi IV als Container (Debian) liefert invalid server response. Ich sehe zwar Sonderzeichen (Gradzeichen) im JSON und habe gelesen, dass es damit Probleme geben soll, finde aber keine Lösung und verstehe auch nicht warum es sich zwischen den Installationen unterschiedlich verhält. In den Fhem Logs habe ich auch bei Verbose 5 nichts gefunden (Kann ich gerne nachliefern).
Danke
Jürgen
Hier das List der "X86" Installation:
Internals:
API_LAST_MSG 200
API_LAST_RES 1728850920.307
DEF http://192.168.5.81/api/livedata/status
FUUID 65d5cdb2-f33f-0692-232d-c21f36d4e89f585f
NAME AUS.DACH.SOLAR
NEXT 2024-10-13 22:23:00
NR 136
SOURCE http://192.168.5.81/api/livedata/status (200)
STATE Tag: 1436 Wh / Gesamt: 1428.835938 KWh / Aktuell: 0 W
SVN 28481 2024-02-05 22:14:33 UTC
TYPE JsonMod
eventCount 12231
CONFIG:
IN_REQUEST 0
SOURCE http://192.168.5.81/api/livedata/status
SECRET:
Helper:
DBLOG:
inverters.0.0.Current.v:
logdb:
TIME 1728837600.29415
VALUE 0
inverters.0.0.Efficiency.v:
logdb:
TIME 1728837600.29415
VALUE 0
inverters.0.0.Frequency.v:
logdb:
TIME 1728838020.36173
VALUE 49.99000168
inverters.0.0.Power.v:
logdb:
TIME 1728837600.29415
VALUE 0
inverters.0.0.PowerFactor.v:
logdb:
TIME 1728837600.29415
VALUE 0
inverters.0.0.Power_DC.v:
logdb:
TIME 1728838020.36173
VALUE 0.5
inverters.0.0.ReactivePower.v:
logdb:
TIME 1728833580.25278
VALUE 0
inverters.0.0.Temperature.v:
logdb:
TIME 1728837960.37193
VALUE 11.10000038
inverters.0.0.Voltage.v:
logdb:
TIME 1728838020.36173
VALUE 222.8000031
inverters.0.0.YieldDay.v:
logdb:
TIME 1728837480.33569
VALUE 1436
inverters.0.0.YieldTotal.v:
logdb:
TIME 1728837480.33569
VALUE 1428.835938
inverters.0.1.Current.v:
logdb:
TIME 1728837600.29415
VALUE 0.02
inverters.0.1.Power.v:
logdb:
TIME 1728838020.36173
VALUE 0.200000003
inverters.0.1.Voltage.v:
logdb:
TIME 1728838020.36173
VALUE 14.60000038
inverters.0.1.YieldDay.v:
logdb:
TIME 1728837480.33569
VALUE 634
inverters.0.1.YieldTotal.v:
logdb:
TIME 1728837480.33569
VALUE 706.9680176
inverters.0.2.Current.v:
logdb:
TIME 1728837600.29415
VALUE 0.02
inverters.0.2.Power.v:
logdb:
TIME 1728838020.36173
VALUE 0.300000012
inverters.0.2.Voltage.v:
logdb:
TIME 1728838020.36173
VALUE 14.60000038
inverters.0.2.YieldDay.v:
logdb:
TIME 1728837360.38352
VALUE 802
inverters.0.2.YieldTotal.v:
logdb:
TIME 1728837360.38352
VALUE 721.867981
inverters.0.producing:
logdb:
TIME 1728850920.31885
VALUE 0
inverters.0.reachable:
logdb:
TIME 1728838020.36173
VALUE 0
total.Power.v:
logdb:
TIME 1728837600.29415
VALUE 0
total.YieldDay.v:
logdb:
TIME 1728837480.33569
VALUE 1436
total.YieldTotal.v:
logdb:
TIME 1728837480.33569
VALUE 1428.835938
READINGS:
2024-10-13 22:22:00 hints.default_password 0
2024-10-13 22:22:00 hints.radio_problem 0
2024-10-13 22:22:00 hints.time_sync 0
2024-10-13 22:22:00 inverters.0.0.Current.d 2
2024-10-13 22:22:00 inverters.0.0.Current.u A
2024-10-13 22:22:00 inverters.0.0.Current.v 0
2024-10-13 22:22:00 inverters.0.0.Efficiency.d 3
2024-10-13 22:22:00 inverters.0.0.Efficiency.u %
2024-10-13 22:22:00 inverters.0.0.Efficiency.v 0
2024-10-13 22:22:00 inverters.0.0.Frequency.d 2
2024-10-13 22:22:00 inverters.0.0.Frequency.u Hz
2024-10-13 22:22:00 inverters.0.0.Frequency.v 49.99000168
2024-10-13 22:22:00 inverters.0.0.Power.d 1
2024-10-13 22:22:00 inverters.0.0.Power.u W
2024-10-13 22:22:00 inverters.0.0.Power.v 0
2024-10-13 22:22:00 inverters.0.0.PowerFactor.d 3
2024-10-13 22:22:00 inverters.0.0.PowerFactor.u
2024-10-13 22:22:00 inverters.0.0.PowerFactor.v 0
2024-10-13 22:22:00 inverters.0.0.Power_DC.d 1
2024-10-13 22:22:00 inverters.0.0.Power_DC.u W
2024-10-13 22:22:00 inverters.0.0.Power_DC.v 0.5
2024-10-13 22:22:00 inverters.0.0.ReactivePower.d 1
2024-10-13 22:22:00 inverters.0.0.ReactivePower.u var
2024-10-13 22:22:00 inverters.0.0.ReactivePower.v 0
2024-10-13 22:22:00 inverters.0.0.Temperature.d 1
2024-10-13 22:22:00 inverters.0.0.Temperature.u °C
2024-10-13 22:22:00 inverters.0.0.Temperature.v 11.10000038
2024-10-13 22:22:00 inverters.0.0.Voltage.d 1
2024-10-13 22:22:00 inverters.0.0.Voltage.u V
2024-10-13 22:22:00 inverters.0.0.Voltage.v 222.8000031
2024-10-13 22:22:00 inverters.0.0.YieldDay.d 0
2024-10-13 22:22:00 inverters.0.0.YieldDay.u Wh
2024-10-13 22:22:00 inverters.0.0.YieldDay.v 1436
2024-10-13 22:22:00 inverters.0.0.YieldTotal.d 3
2024-10-13 22:22:00 inverters.0.0.YieldTotal.u kWh
2024-10-13 22:22:00 inverters.0.0.YieldTotal.v 1428.835938
2024-10-13 22:22:00 inverters.0.1.Current.d 2
2024-10-13 22:22:00 inverters.0.1.Current.u A
2024-10-13 22:22:00 inverters.0.1.Current.v 0.02
2024-10-13 22:22:00 inverters.0.1.Power.d 1
2024-10-13 22:22:00 inverters.0.1.Power.u W
2024-10-13 22:22:00 inverters.0.1.Power.v 0.200000003
2024-10-13 22:22:00 inverters.0.1.Voltage.d 1
2024-10-13 22:22:00 inverters.0.1.Voltage.u V
2024-10-13 22:22:00 inverters.0.1.Voltage.v 14.60000038
2024-10-13 22:22:00 inverters.0.1.YieldDay.d 0
2024-10-13 22:22:00 inverters.0.1.YieldDay.u Wh
2024-10-13 22:22:00 inverters.0.1.YieldDay.v 634
2024-10-13 22:22:00 inverters.0.1.YieldTotal.d 3
2024-10-13 22:22:00 inverters.0.1.YieldTotal.u kWh
2024-10-13 22:22:00 inverters.0.1.YieldTotal.v 706.9680176
2024-10-13 22:22:00 inverters.0.1.name.u
2024-10-13 22:22:00 inverters.0.2.Current.d 2
2024-10-13 22:22:00 inverters.0.2.Current.u A
2024-10-13 22:22:00 inverters.0.2.Current.v 0.02
2024-10-13 22:22:00 inverters.0.2.Power.d 1
2024-10-13 22:22:00 inverters.0.2.Power.u W
2024-10-13 22:22:00 inverters.0.2.Power.v 0.300000012
2024-10-13 22:22:00 inverters.0.2.Voltage.d 1
2024-10-13 22:22:00 inverters.0.2.Voltage.u V
2024-10-13 22:22:00 inverters.0.2.Voltage.v 14.60000038
2024-10-13 22:22:00 inverters.0.2.YieldDay.d 0
2024-10-13 22:22:00 inverters.0.2.YieldDay.u Wh
2024-10-13 22:22:00 inverters.0.2.YieldDay.v 802
2024-10-13 22:22:00 inverters.0.2.YieldTotal.d 3
2024-10-13 22:22:00 inverters.0.2.YieldTotal.u kWh
2024-10-13 22:22:00 inverters.0.2.YieldTotal.v 721.867981
2024-10-13 22:22:00 inverters.0.2.name.u
2024-10-13 22:22:00 inverters.0.data_age 12920
2024-10-13 22:22:00 inverters.0.events 4
2024-10-13 22:22:00 inverters.0.limit_absolute 600
2024-10-13 22:22:00 inverters.0.limit_relative 100
2024-10-13 22:22:00 inverters.0.name Balkon
2024-10-13 22:22:00 inverters.0.producing 0
2024-10-13 22:22:00 inverters.0.reachable 0
2024-10-13 22:22:00 inverters.0.serial 114182127298
2024-10-13 22:22:00 total.Power.d 1
2024-10-13 22:22:00 total.Power.u W
2024-10-13 22:22:00 total.Power.v 0
2024-10-13 22:22:00 total.YieldDay.d 0
2024-10-13 22:22:00 total.YieldDay.u Wh
2024-10-13 22:22:00 total.YieldDay.v 1436
2024-10-13 22:22:00 total.YieldTotal.d 2
2024-10-13 22:22:00 total.YieldTotal.u kWh
2024-10-13 22:22:00 total.YieldTotal.v 1428.835938
helper:
bm:
JsonMod_Set:
cnt 249
dmx -1000
dtot 0
dtotcnt 0
mTS 10.10. 11:38:00
max 3.814697265625e-05
tot 0.00267505645751953
mAr:
HASH(0x5cda92b4bfe8)
AUS.DACH.SOLAR
?
Attributes:
DbLogInclude .*.v,inverters.0.producing,inverters.0.reachable,SunAlt
event-min-interval inverters.0.producing:60
event-on-change-reading .*.v,inverters.0.producing,inverters.0.reachable
group Solar
interval * * * * *
readingList complete()
room SOLAR
stateFormat Tag: total.YieldDay.v Wh / Gesamt: inverters.0.0.YieldTotal.v KWh / Aktuell: inverters.0.0.Power.v W
und hier aus der "RASPI" Installation
nternals:
API_LAST_MSG invalid server response
API_LAST_RES 1728851480.82441
CFGFN
DEF http://192.168.5.81/api/livedata/status
FUUID 6707971a-f33f-f95b-27cc-b2ec16811251dd15
NAME AUS.DACH.SOLAR
NEXT 2024-10-13 20:32:00
NR 47
SOURCE http://192.168.5.81/api/livedata/status (200)
STATE Tag: total.YieldDay.v Wh / Gesamt: inverters.0.0.YieldTotal.v KWh / Aktuell: inverters.0.0.Power.v W
SVN 28481 2024-02-05 22:14:33 UTC
TYPE JsonMod
eventCount 9
CONFIG:
IN_REQUEST 0
SOURCE http://192.168.5.81/api/livedata/status
SECRET:
READINGS:
Attributes:
event-min-interval inverters.0.producing:60
event-on-change-reading .*.v,inverters.0.producing,inverters.0.reachable
group Solar
interval * * * * *
room SOLAR
stateFormat Tag: total.YieldDay.v Wh / Gesamt: inverters.0.0.YieldTotal.v KWh / Aktuell: inverters.0.0.Power.v W
Hier noch eine aktuelle API/JSON Abfrage:
{"inverters":[{"serial":"114182127298","name":"Balkon","data_age":13563,"reachable":false,"producing":false,"limit_relative":100,"limit_absolute":600,"0":{"Power":{"v":0,"u":"W","d":1},"Voltage":{"v":222.8000031,"u":"V","d":1},"Current":{"v":0,"u":"A","d":2},"Power DC":{"v":0.5,"u":"W","d":1},"YieldDay":{"v":1436,"u":"Wh","d":0},"YieldTotal":{"v":1428.835938,"u":"kWh","d":3},"Frequency":{"v":49.99000168,"u":"Hz","d":2},"Temperature":{"v":11.10000038,"u":"°C","d":1},"PowerFactor":{"v":0,"u":"","d":3},"ReactivePower":{"v":0,"u":"var","d":1},"Efficiency":{"v":0,"u":"%","d":3}},"1":{"name":{"u":""},"Power":{"v":0.200000003,"u":"W","d":1},"Voltage":{"v":14.60000038,"u":"V","d":1},"Current":{"v":0.02,"u":"A","d":2},"YieldDay":{"v":634,"u":"Wh","d":0},"YieldTotal":{"v":706.9680176,"u":"kWh","d":3}},"2":{"name":{"u":""},"Power":{"v":0.300000012,"u":"W","d":1},"Voltage":{"v":14.60000038,"u":"V","d":1},"Current":{"v":0.02,"u":"A","d":2},"YieldDay":{"v":802,"u":"Wh","d":0},"YieldTotal":{"v":721.867981,"u":"kWh","d":3}},"events":4}],"total":{"Power":{"v":0,"u":"W","d":1},"YieldDay":{"v":1436,"u":"Wh","d":0},"YieldTotal":{"v":1428.835938,"u":"kWh","d":2}},"hints":{"time_sync":false,"radio_problem":false,"default_password":false}}
Ich antworte mir jetzt mal selbst.
Ursache war die unterschiedliche Einstellung encoding in GLOBAL! Da die X86 Instanz wesentlich älter ist gab es dort das Attribut encoding gar nicht. Auf dem RASPI war es auf unicode eingestellt. Nach Umstellung von unicode auf bytestream funktioniert die Abfrage jetzt wieder.
Ob das schön und richtig ist kann ich nicht beurteilen.
Für mich ist das jetzt gelöst.