Fehlermeldung bei Twilight nach httputils-update vom 10.12.16

Begonnen von habl, 10 Dezember 2016, 08:42:05

Vorheriges Thema - Nächstes Thema

habl

Hallo Rudi,

nach update heute Morgen erhalte ich minütlich folgende Einträge im Log:

2016.12.10 08:02:23 1: PERL WARNING: Number found where operator expected at (eval 706) line 1, near "1.0 200"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 1, near "200 OK"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 2, near "3ff4ef57"
2016.12.10 08:02:23 1: PERL WARNING: (Missing operator before ff4ef57?)
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 2, near "89c9"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 6, near "8
Cache"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 7, near "10 Dec"
2016.12.10 08:02:23 1: PERL WARNING: Number found where operator expected at (eval 706) line 7, near "Dec 2016"
2016.12.10 08:02:23 1: PERL WARNING: Number found where operator expected at (eval 706) line 7, near "2016 07"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 7, near "23 GMT"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 9, near "0
Via"
2016.12.10 08:02:23 1: PERL WARNING: Bareword found where operator expected at (eval 706) line 9, near "1.1 a26"
2016.12.10 08:02:23 1: PERL WARNING: (Missing operator before a26?)
2016.12.10 08:02:23 1: PERL WARNING: Semicolon seems to be missing at (eval 706) line 9.
2016.12.10 08:02:23 3: [myTwilight] error syntax error at (eval 706) line 1, near "1.0 200"
syntax error at (eval 706) line 2, near "3ff4ef57"
syntax error at (eval 706) line 6, near "8
Cache"
"no" not allowed in expression at (eval 706) line 6, near ": "
syntax error at (eval 706) line 12, near "}}"
parsing HTTP/1.0 200 OK
X-YQL-Host: prod_bf1_1;paas.yql;queryyahooapiscomproductionbf1;3ff4ef57-bd18-11e6-89c9-d4ae5297450a
X-Content-Type-Options: nosniff
Access-Control-Allow-Origin: *
Content-Type: application/json;charset=utf-8
Cache-Control: no-cache
Date: Sat, 10 Dec 2016 07:02:23 GMT
Age: 0
Via: http/1.1 a26.ue.bf1.yahoo.net (ApacheTrafficServer [cMsSf ])
Server: ATS

{"query":{"count":1,"created":"2016-12-10T07:02:23Z","lang":"en-US","results":{"channel":{"units":{"distance":"km","pressure":"mb","speed":"km/h","temperature":"C"},"title":"Yahoo! Weather - Timbuktu, NI, DE","link":"http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-XXXXXXXX/","description":"Yahoo! Weather for Timbuktu, NI, DE","language":"en-us","lastBuildDate":"Sat, 10 Dec 2016 08:02 AM CET","ttl":"60","location":{"city":"Timbuktu","country":"Germany","region":" NI"},"wind":{"chill":"39","direction":"235","speed":"35.40"},"atmosphere":{"humidity":"90","pressure":"34541.18","rising":"0","visibility":"25.91"},"astronomy":{"sunrise":"8:34 am","sunset":"4:12 pm"},"image":{"title":"Yahoo! Weather","width":"142","height":"18","link":"http://weather.yahoo.com","url":"http://l.yimg.com/a/i/brand/purplelogo//uh/us/news-wea.gif"},"item":{"title":"Conditions for Timbuktu, NI, DE at 07:00 AM CET","lat":"XX.125801","long":"XX.5479","link":"http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-XXXXXXXX/","pubDate":"Sat, 10 Dec 2016 07:00 AM CET","condition":{"code":"26","date":"Sat, 10 Dec 2016 07:00 AM CET","temp":"7","text":"Cloudy"},"forecast":[{"code":"39","date":"10 Dec 2016","day":"Sat","high":"10","low":"5","text":"Scattered Showers"},{"code":"11","date":"11 Dec 2016","day":"Sun","high":"9","low":"5","text":"Showers"},{"code":"28","date":"12 Dec 2016","day":"Mon","high":"8","low":"5","text":"Mostly Cloudy"},{"code":"26","date":"13 Dec 2016","day":"Tue","high":"6","low":"3","text":"Cloudy"},{"code":"28","date":"14 Dec 2016","day":"Wed","high":"6","low":"1","text":"Mostly Cloudy"},{"code":"28","date":"15 Dec 2016","day":"Thu","high":"3","low":"0","text":"Mostly Cloudy"},{"code":"28","date":"16 Dec 2016","day":"Fri","high":"3","low":"-1","text":"Mostly Cloudy"},{"code":"28","date":"17 Dec 2016","day":"Sat","high":"4","low":"0","text":"Mostly Cloudy"},{"code":"28","date":"18 Dec 2016","day":"Sun","high":"5","low":"0","text":"Mostly Cloudy"},{"code":"28","date":"19 Dec 2016","day":"Mon","high":"5","low":"1","text":"Mostly Cloudy"}],"description":"<![CDATA[<img src=\"http://l.yimg.com/a/i/us/we/52/26.gif\"/>\n<BR />\n<b>Current Conditions:</b>\n<BR />Cloudy\n<BR />\n<BR />\n<b>Forecast:</b>\n<BR /> Sat - Scattered Showers. High: 10Low: 5\n<BR /> Sun - Showers. High: 9Low: 5\n<BR /> Mon - Mostly Cloudy. High: 8Low: 5\n<BR /> Tue - Cloudy. High: 6Low: 3\n<BR /> Wed - Mostly Cloudy. High: 6Low: 1\n<BR />\n<BR />\n<a href=\"http://us.rd.yahoo.com/dailynews/rss/weather/Country__Country/*https://weather.yahoo.com/country/state/city-XXXXXXXX/\">Full Forecast at Yahoo! Weather</a>\n<BR />\n<BR />\n(provided by <a href=\"http://www.weather.com\" >The Weather Channel</a>)\n<BR />\n]]>","guid":{"isPermaLink":"false"}}}}}}


Ursache ist das Update von httputlis.pm, nach Rücksicerung der Datei tauchen die Fehlermeldungen nicht mehr auf.

wenn Du noch mehr Infos benötigst, lass es mich wissen.

VG
habl

stromer-12

FHEM (SVN) auf RPi1B mit HMser | ESPLink
FHEM (SVN) virtuell mit HMLAN | HMUSB | CUL

rudolfkoenig

Ich habe die Aenderungen von gestern wieder zurueckgedreht.
Kann bitte einer von euch mir einen (einfach nachzustellenden) Testafll bauen?

stromer-12

einfach mal ein
define test_tw Twilight 54.179 13.467 2 654035
eingeben und die Fehler kommen ca. 1 Minute später
FHEM (SVN) auf RPi1B mit HMser | ESPLink
FHEM (SVN) virtuell mit HMLAN | HMUSB | CUL

habl

#4
bei mir ist es nur auf mein Produktivsystem, 2 Testsysteme aufgesetzt, bei beiden funktioniert es.

Wo und wie kann ich das jetzt weiter eingrenzen, bin Ratlos?!


Alles zurück, Fehler ist wie stromer-12 angegeben hat reproduzierbar, die alte Version wird ja wieder per update verteilt.

Invers

#5
Bei mir läuft es mit DECT 200 und Wetter nicht.

2016.12.10 10:47:48 3: fb2: unexpected reply from device: HTTP/1.0 200 OK
Connection: close
Content-Type: text/xml; charset=utf-8

<devicelist version="1"><device identifier="08761 0087783" id="18" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>TV Licht hinten</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>99623</energy></powermeter><temperature><celsius>205</celsius><offset>-15</offset></temperature></device><device identifier="08761 0149529" id="24" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Stehlampe</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>4730</energy></powermeter><temperature><celsius>185</celsius><offset>-20</offset></temperature></device><device identifier="08761 0091342" id="22" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Balkon</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>1688</energy></powermeter><temperature><celsius>220</celsius><offset>-5</offset></temperature></device><device identifier="08761 0101811" id="23" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Trockner</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>122433</energy></powermeter><temperature><celsius>190</celsius><offset>0</offset></temperature></device><device identifier="08761 0087573" id="20" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Luefter</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>6184</energy></powermeter><temperature><celsius>235</celsius><offset>0</offset></temperature></device><device identifier="08761 0002297" id="16" functionbitmask="896" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>PC</name><switch><state>1</state><mode>auto</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>123660</power><energy>981766</energy></powermeter><temperature><celsius>245</celsius><offset>-5</offset></temperature></device><device identifier="08761 0172730" id="25" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>PC Kunlaya</name><switch><state>0</state><mode>auto</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>38323</energy></powermeter><temperature><celsius>200</celsius><offset>-20</offset></temperature></device><device identifier="08761 0087570" id="26" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Lampe Korridor</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>14981</energy></powermeter><temperature><celsius>215</celsius><offset>-15</offset></temperature></device><device identifier="08761 0243162" id="27" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>TV</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>394804</energy></powermeter><temperature><celsius>225</celsius><offset>-5</offset></temperature></device><device identifier="08761 0245609" id="28" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Schreibtisch</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>1140</energy></powermeter><temperature><celsius>225</celsius><offset>0</offset></temperature></device><device identifier="08761 0091219" id="29" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>Led Kueche</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>32727</energy></powermeter><temperature><celsius>205</celsius><offset>0</offset></temperature></device><device identifier="08761 0087781" id="31" functionbitmask="2944" fwversion="03.83" manufacturer="AVM" productname="FRITZ!DECT 200"><present>1</present><name>TV Licht vorne</name><switch><state>0</state><mode>manuell</mode><lock>0</lock><devicelock>0</devicelock></switch><powermeter><power>0</power><energy>138803</energy></powermeter><temperature><celsius>235</celsius><offset>0</offset></temperature></device></devicelist>

2016.12.10 10:47:59 3: Wetter: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "HTTP/1.0 200 OK\r\nX...") at FHEM/YahooWeatherAPI.pm line 247.

2016.12.10 10:49:06 3: Wetter: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "HTTP/1.0 200 OK\r\nX...") at FHEM/YahooWeatherAPI.pm line 247.

2016.12.10 10:49:48 3: fb2: unexpected reply from device: HTTP/1.0 200 OK
Connection: close
Content-Type: text/xml; charset=utf-8

Pi3B+ mit SSD/ Bullseye | FB7590 AX | 12 x Dect200 | CUL433+868 | SDuino | HM-LAN | 3 x Heizung FHT + FKontakte | KeyMatic + 4 FB | HM Wandtaster 2-fach m. LED | 6 x Türkont. TFK-TI | HM-Bew.-Melder innen | 3 x Smoked. HM-SEC-SD-2

rudolfkoenig

Ich habe verpasst, Http Antworten ohne Content-Length als solche zu erkennen. Das habe ich geaendert, und mit twilight und FBAHAHTTP getestet, beide funktionieren jetzt bei mir. Ab morgen gibt es eine neue Variante per update, wenn jemand das vorher testen kann, waere ich dankbar.

habl

bei mir funktioniert es auch mit der neuen Version aus SVN, keine Einträge im Log mehr.

vielen Dank fürs schnelle reparieren!

habl

cheanrod

Hallo zusammen,

ich habe mit der neuesten Version der HttpUtils leider noch Probleme im Zusammenspiel mit HTTPMOD. Folgende Einträge finden sich im Log-File:


2016.12.11 11:03:13 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at FHEM/HttpUtils.pm line 660.
2016.12.11 11:03:13 3: Bremen4_Verkehr: Read response to update didn't match any Reading
2016.12.11 11:07:10 3: Bremen4_Verkehr: Read response to update didn't match any Reading
2016.12.11 11:13:31 3: Bremen4_Verkehr: Read response to update didn't match any Reading


Mit einer älteren Version von HttpUtils.pm aus dem Backup funktioniert das HTTPMOD-Device noch.

Hier ein Listing des HTTPMOD-Devices zum Nachstellen des Problems (buf habe ich gekürzt):


Internals:
   BUSY       0
   CFGFN
   CHANGED
   DEF        http://www.radiobremen.de/bremenvier/programm/vier-news/verkehr130.html 900
   Interval   900
   LASTSEND   1481451211.38931
   MainURL    http://www.radiobremen.de/bremenvier/programm/vier-news/verkehr130.html
   MaxAgeEnabled 1
   ModuleVersion 3.3.5 - 29.9.2016
   NAME       Bremen4_Verkehr
   NR         37
   STATE      Achtung Blitzer!
   TRIGGERTIME 1481452111.38811
   TRIGGERTIME_FMT 2016-12-11 11:28:31
   TYPE       HTTPMOD
   addr       http://www.radiobremen.de:80
   buf        HTTP/1.0 200 OK

   code       200
   conn
   data
   displayurl http://www.radiobremen.de/bremenvier/programm/vier-news/verkehr130.html
   header
   host       www.radiobremen.de
   httpheader HTTP/1.0 200 OK

Server: Apache/2.4.7 (Ubuntu)

Content-Type: text/html; charset=utf-8

Date: Sun, 11 Dec 2016 09:58:31 GMT

Connection: close
   httpversion 1.0
   hu_blocking 0
   hu_filecount 4
   ignoreredirects 0
   loglevel   4
   path       /bremenvier/programm/vier-news/verkehr130.html
   protocol   http
   redirects  0
   timeout    2
   url        http://www.radiobremen.de/bremenvier/programm/vier-news/verkehr130.html
   value      0
   Helper:
     Dblog:
       State:
         Logdb:
           TIME       1481450829.29897
           VALUE      reread
   QUEUE:
   Readings:
   Request:
     data
     header
     ignoreredirects 0
     retryCount 0
     type       update
     url        http://www.radiobremen.de/bremenvier/programm/vier-news/verkehr130.html
     value      0
   Sslargs:
Attributes:
   enableControlSet 1
   group      Straße
   reading01MaxAge 900
   reading01MaxAgeReplacementMode delete
   reading01Name Blitzer
   reading01RegOpt gs
   reading01Regex <div class='blitz'>(.*?)<\/div>
   stateFormat { if (ReadingsVal($name, "Blitzer", "") eq 'Aktuell liegen uns keine Blitzermeldungen vor.') {
sprintf 'Keine Blitzer';
} else {
sprintf 'Achtung Blitzer!';
}
}
   userattr   reading01MaxAge reading01MaxAgeReplacementMode reading01MaxAgeReplacementMode:text,reading,internal,expression,delete reading01Name reading01RegOpt reading01Regex


Viele Grüße
Cheanrod

CoolTux

Muss ich leider bestätigen. RegEx und Readings klappen aber korrekt.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rudolfkoenig

Koennt ihr mir bitte was Nachstellbares hier anhaengen?

CoolTux


DEF        http://www.clever-tanken.de/tankstelle_details/1374 1800

Attributes:
   event-on-change-reading .*
   group      Spritpreise,
   reading01Name SuperE10
   reading01Regex <span>Super E10[^0-9]+([0-9\.]+)
   reading02Name Diesel
   reading02Regex <span>Diesel[^0-9]+([0-9\.]+)
   room       Info
   stateFormat Liter_Diesel: Diesel
   timeout    5
   userattr   reading01Name reading01Regex reading02Name reading02Regex


Geht das so oder brauchst was ganz bestimmtes?
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rudolfkoenig

Copy & Paste von "Raw definition" waere fuer mich etwas einfacher :), aber so geht es auch.
Haken: ich bekomme keine Fehlermeldung, habs jetzt 10* gestartet. Muss man laenger warten?
Was sieht man mit "attr global verbose 5" ?

CoolTux

Stimmt da gab es ja sowas neues. Lach


defmod ELANKlm HTTPMOD http://www.clever-tanken.de/tankstelle_details/1374 1800
attr ELANKlm userattr reading01Name reading01Regex reading02Name reading02Regex
attr ELANKlm event-on-change-reading .*
attr ELANKlm group Spritpreise,
attr ELANKlm reading01Name SuperE10
attr ELANKlm reading01Regex <span>Super E10[^0-9]+([0-9\.]+)
attr ELANKlm reading02Name Diesel
attr ELANKlm reading02Regex <span>Diesel[^0-9]+([0-9\.]+)
attr ELANKlm room Info
attr ELANKlm stateFormat Liter_Diesel: Diesel
attr ELANKlm timeout 5

setstate ELANKlm Liter_Diesel: 1.20
setstate ELANKlm 2016-12-11 12:01:34 Diesel 1.20
setstate ELANKlm 2016-12-11 12:01:34 SuperE10 1.35


Mach mal am Ende der defmod Zeile aus der 1800 eine 30 dann sollte er alle 30s einen Aufruf machen.
Mit verbose 5 schaue ich gleich mal.
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

CoolTux

Verbose 5


2016.12.11 13:33:59 4: ELANKlm: GetUpdate called (update)
2016.12.11 13:33:59 4: ELANKlm: update timer modified: will call GetUpdate in 30.0 seconds at 2016-12-11 13:34:29
2016.12.11 13:33:59 4: ELANKlm: AddToQueue adds update, initial queue len: 0
2016.12.11 13:33:59 5: ELANKlm: AddToQueue adds type update to URL http://www.clever-tanken.de/tankstelle_details/1374, no data, no headers, retry 0
2016.12.11 13:33:59 5: ELANKlm: HandleSendQueue called, qlen = 1
2016.12.11 13:33:59 4: ELANKlm: HandleSendQueue sends request type update to URL http://www.clever-tanken.de/tankstelle_details/1374, No Data, No Header,
timeout 5
2016.12.11 13:33:59 4: HttpUtils url=http://www.clever-tanken.de/tankstelle_details/1374
2016.12.11 13:33:59 4: http://www.clever-tanken.de/tankstelle_details/1374: HTTP response code 200
2016.12.11 13:33:59 4: HttpUtils http://www.clever-tanken.de/tankstelle_details/1374: Got data, length:
2016.12.11 13:33:59 4: HttpUtils http://www.clever-tanken.de/tankstelle_details/1374: Zero length data, header follows:
2016.12.11 13:33:59 4:   Date: Sun, 11 Dec 2016 11:01:30 GMT
2016.12.11 13:33:59 4:   Server: Apache/2.2.22 (Ubuntu)
2016.12.11 13:33:59 4:   Vary: Accept-Encoding
2016.12.11 13:33:59 4:   Content-Type: text/html; charset=utf-8
2016.12.11 13:33:59 4:   X-Cache: MISS from pi-proxy01
2016.12.11 13:33:59 4:   X-Cache-Lookup: MISS from pi-proxy01:3128
2016.12.11 13:33:59 4:   Connection: close
2016.12.11 13:33:59 4: ELANKlm: Read callback: request type was update retry 0,
Header: HTTP/1.1 200 OK
Date: Sun, 11 Dec 2016 11:01:30 GMT
Server: Apache/2.2.22 (Ubuntu)
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
X-Cache: MISS from pi-proxy01
X-Cache-Lookup: MISS from pi-proxy01:3128
Connection: close, body emptyno error
2016.12.11 13:33:59 5: ELANKlm: ExtractSid called, context reading, num
2016.12.11 13:33:59 4: ELANKlm: CheckAuth decided no authentication required
2016.12.11 13:33:59 5: ELANKlm: Read starts parsing response to update with defined readings: 01,02
2016.12.11 13:33:59 5: ELANKlm: ExtractReading SuperE10 with regex /<span>Super E10[^0-9]+([0-9\.]+)/...
2016.12.11 13:33:59 5: ELANKlm: ExtractReading SuperE10 did not match
2016.12.11 13:33:59 5: ELANKlm: ExtractReading Diesel with regex /<span>Diesel[^0-9]+([0-9\.]+)/...
2016.12.11 13:33:59 5: ELANKlm: ExtractReading Diesel did not match
2016.12.11 13:33:59 3: ELANKlm: Read response to update didn't match any Reading
2016.12.11 13:33:59 5: ELANKlm: HandleSendQueue called, qlen = 0
Du musst nicht wissen wie es geht! Du musst nur wissen wo es steht, wie es geht.
Support me to buy new test hardware for development: https://www.paypal.com/paypalme/MOldenburg
My FHEM Git: https://git.cooltux.net/FHEM/
Das TuxNet Wiki:
https://www.cooltux.net

rudolfkoenig


cheanrod


fume

Hallo ich habe leider noch immer eim Problem im zusammenhang mit HTTPMOD.

Loglevel 5 nach update 10.12
2016.12.11 21:21:41 4: PV_Meter: Read callback: request type was update retry 0, no headers,
Body: HTTP/1.0 200 OK
Content-Type: text/javascript
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0
Connection: close
Date: Sun, 11 Dec 2016 20:19:58 GMT
Server: webserver

{
"Head" : {
"RequestArguments" : {
"DeviceClass" : "Meter",
"DeviceId" : "1",
"Scope" : "Device"
},
"Status" : {
"Code" : 0,
"Reason" : "",
"UserMessage" : ""
},
"Timestamp" : "2016-12-11T21:19:58+01:00"
},
"Body" : {
"Data" : {
"Details" : {
"Serial" : "n.a.",
"Model" : "S0 Meter at inverter 1",
"Manufacturer" : "Fronius"
},
"TimeStamp" : 1481487597,
"Enable" : 1,
"Visible" : 1,
"PowerReal_P_Sum" : -294.64724,
"Meter_Location_Current" : 1,
"EnergyReal_WAC_Minus_Relative" : 37.5
}
}
}no error
2016.12.11 21:21:41 3: PV_Meter: error while parsing JSON data: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "HTTP/1.0 200 OK\r\nC...") at (eval 11537) line 1.

2016.12.11 21:21:41 5: PV_Meter: ExtractSid called, context reading, num
2016.12.11 21:21:41 4: PV_Meter: CheckAuth decided no authentication required
2016.12.11 21:21:41 5: PV_Meter: Read starts parsing response to update with defined readings: 01
2016.12.11 21:21:41 5: PV_Meter: ExtractReading Stromverbrauch with json Body_Data_PowerReal_P_Sum ...
2016.12.11 21:21:41 5: PV_Meter: ExtractReading Stromverbrauch did not match
2016.12.11 21:21:41 3: PV_Meter: Read response to update didn't match any Reading
2016.12.11 21:21:41 5: PV_Meter: HandleSendQueue called, qlen = 0


Nach dem lesen diese in diesem Threat habe ich natürlich gleich nochmal ein Update gemacht. Nach Neustart von fhem
hat sich mein Wert genau einmal geändert (sollte alle 60sec aktualisieren) und ist dann wieder festgefroren. Ein erneuter Verbose 5 brachte dieses Ergebnis.
Den link habe ich in Chromium geprüft, wo die volle JSON Ausgabe angezeigt wird.

2016.12.11 21:56:51 4: http://fronius.fume.lan/solar_api/v1/GetMeterRealtimeData.cgi?Scope=Device&DeviceId=1: HTTP response code 200
2016.12.11 21:56:51 4: HttpUtils http://fronius.fume.lan/solar_api/v1/GetMeterRealtimeData.cgi?Scope=Device&DeviceId=1: Got data, length:
2016.12.11 21:56:51 4: HttpUtils http://fronius.fume.lan/solar_api/v1/GetMeterRealtimeData.cgi?Scope=Device&DeviceId=1: Zero length data, header follows:
2016.12.11 21:56:51 4:   Content-Type: text/javascript
2016.12.11 21:56:51 4:   Cache-Control: no-cache, no-store, must-revalidate
2016.12.11 21:56:51 4:   Pragma: no-cache
2016.12.11 21:56:51 4:   Expires: 0
2016.12.11 21:56:51 4:   Connection: close
2016.12.11 21:56:51 4:   Date: Sun, 11 Dec 2016 20:46:08 GMT
2016.12.11 21:56:51 4:   Server: webserver
2016.12.11 21:56:51 4: PV_Meter: Read callback: request type was update retry 0,
Header: HTTP/1.0 200 OK
Content-Type: text/javascript
Cache-Control: no-cache, no-store, must-revalidate
Pragma: no-cache
Expires: 0
Connection: close
Date: Sun, 11 Dec 2016 20:46:08 GMT
Server: webserver, body emptyno error
2016.12.11 21:56:51 5: PV_Meter: ExtractSid called, context reading, num
2016.12.11 21:56:51 4: PV_Meter: CheckAuth decided no authentication required
2016.12.11 21:56:51 5: PV_Meter: Read starts parsing response to update with defined readings: 01
2016.12.11 21:56:51 5: PV_Meter: ExtractReading Stromverbrauch with json Body_Data_PowerReal_P_Sum ...
2016.12.11 21:56:51 5: PV_Meter: ExtractReading Stromverbrauch did not match
2016.12.11 21:56:51 3: PV_Meter: Read response to update didn't match any Reading
2016.12.11 21:56:51 5: PV_Meter: HandleSendQueue called, qlen = 0


Habe jetzt mal die letzte backup HttpUtils.pm von 5.12 reinkopiert und alles läuft wieder einwandfrei.

rudolfkoenig

Bitte beachten:
ZitatHabs gefixt, eingecheckt, ab morgen per update.

fume