homematic-community / XML-API

HomeMatic CCU Addon implementing a xml request functionality
https://github.com/homematic-community/XML-API
GNU General Public License v3.0
123 stars 27 forks source link

fehlerhafte Ausgabe bei state.cgi #76

Closed ssbingo closed 11 months ago

ssbingo commented 11 months ago

Bei der Abfrage in V1.22 erhalte ich eine saubere Darstellung der Werte eines Geräte.

http://192.168.30.20/addons/xmlapi/state.cgi?device_id=32688

<state>
<device name="Hausanschluss-Strom" ise_id="32688" unreach="false" sticky_unreach="false" config_pending="false">
<channel name="Hausanschluss-Strom:0" ise_id="32689">
<datapoint name="BidCos-RF.MEQ0026056:0.UNREACH" type="UNREACH" ise_id="32709" value="false" valuetype="2" valueunit="" timestamp="1697468173"/>
<datapoint name="BidCos-RF.MEQ0026056:0.STICKY_UNREACH" type="STICKY_UNREACH" ise_id="32705" value="false" valuetype="2" valueunit="" timestamp="1697468173"/>
<datapoint name="BidCos-RF.MEQ0026056:0.CONFIG_PENDING" type="CONFIG_PENDING" ise_id="32691" value="false" valuetype="2" valueunit="" timestamp="1697468173"/>
<datapoint name="BidCos-RF.MEQ0026056:0.LOWBAT" type="LOWBAT" ise_id="32699" value="false" valuetype="2" valueunit="" timestamp="1697515201"/>
<datapoint name="BidCos-RF.MEQ0026056:0.RSSI_DEVICE" type="RSSI_DEVICE" ise_id="32703" value="-65535" valuetype="16" valueunit="" timestamp="1697468173"/>
<datapoint name="BidCos-RF.MEQ0026056:0.RSSI_PEER" type="RSSI_PEER" ise_id="32704" value="-85" valuetype="16" valueunit="" timestamp="1697468173"/>
<datapoint name="BidCos-RF.MEQ0026056:0.DEVICE_IN_BOOTLOADER" type="DEVICE_IN_BOOTLOADER" ise_id="32695" value="false" valuetype="2" valueunit="" timestamp="1697468173"/>
<datapoint name="BidCos-RF.MEQ0026056:0.UPDATE_PENDING" type="UPDATE_PENDING" ise_id="32713" value="false" valuetype="2" valueunit="" timestamp="1697468173"/>
</channel>
<channel name="Hausanschluss-Strom" ise_id="32717">
<datapoint name="BidCos-RF.MEQ0026056:1.IEC_ENERGY_COUNTER" type="IEC_ENERGY_COUNTER" ise_id="32722" value="6773.102798" valuetype="4" valueunit="kWh" timestamp="1697537831"/>
<datapoint name="BidCos-RF.MEQ0026056:1.IEC_POWER" type="IEC_POWER" ise_id="32723" value="1012.000000" valuetype="4" valueunit="W" timestamp="1697537831"/>
</channel>
<channel name="Hausanschluss-Strom(Lieferung)" ise_id="32725">
<datapoint name="BidCos-RF.MEQ0026056:2.IEC_ENERGY_COUNTER" type="IEC_ENERGY_COUNTER" ise_id="32726" value="169.390300" valuetype="4" valueunit="kWh" timestamp="1697537831"/>
<datapoint name="BidCos-RF.MEQ0026056:2.IEC_POWER" type="IEC_POWER" ise_id="32727" value="0.000000" valuetype="4" valueunit="W" timestamp="1697537831"/>
</channel>
</device>
</state>

Führe ich die gleiche Abfrage in V2.0 incl. dem generierten Token aus, erhalte ich eine Meldung über fehlerhaftes im xml

http://192.168.30.20/addons/xmlapi/state.cgi?sid=aaAAaaAAaAAaAAAA&device_id=32688

XML-Verarbeitungsfehler: nicht wohlgeformt
Adresse: http://192.168.30.20/addons/xmlapi/state.cgi?sid=aaAAaaAAaAAaAAAA&device_id=32688
Zeile Nr. 1, Spalte 379:
<?xml version='1.0' encoding='ISO-8859-1' ?><state><device name='Hausanschluss-Strom' ise_id='32688' unreach='false' sticky_unreach='false' config_pending='false' ><channel name='Hausanschluss-Strom:0' ise_id='32689'><datapoint name='BidCos-RF.MEQ0026056:0.UNREACH' type='UNREACH' ise_id='32709' value='false' valuetype='2' valueunit='' timestamp='1697468173' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.STICKY_UNREACH' type='STICKY_UNREACH' ise_id='32705' value='false' valuetype='2' valueunit='' timestamp='1697468173' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.CONFIG_PENDING' type='CONFIG_PENDING' ise_id='32691' value='false' valuetype='2' valueunit='' timestamp='1697468173' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.LOWBAT' type='LOWBAT' ise_id='32699' value='false' valuetype='2' valueunit='' timestamp='1697515201' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.RSSI_DEVICE' type='RSSI_DEVICE' ise_id='32703' value='-65535' valuetype='16' valueunit='' timestamp='1697468173' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.RSSI_PEER' type='RSSI_PEER' ise_id='32704' value='-85' valuetype='16' valueunit='' timestamp='1697468173' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.DEVICE_IN_BOOTLOADER' type='DEVICE_IN_BOOTLOADER' ise_id='32695' value='false' valuetype='2' valueunit='' timestamp='1697468173' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:0.UPDATE_PENDING' type='UPDATE_PENDING' ise_id='32713' value='false' valuetype='2' valueunit='' timestamp='1697468173' lastdpactiontime='</channel><channel name='Hausanschluss-Strom' ise_id='32717'><datapoint name='BidCos-RF.MEQ0026056:1.IEC_ENERGY_COUNTER' type='IEC_ENERGY_COUNTER' ise_id='32722' value='6773.226395' valuetype='4' valueunit='kWh' timestamp='1697538147' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:1.IEC_POWER' type='IEC_POWER' ise_id='32723' value='1020.000000' valuetype='4' valueunit='W' timestamp='1697538147' lastdpactiontime='</channel><channel name='Hausanschluss-Strom(Lieferung)' ise_id='32725'><datapoint name='BidCos-RF.MEQ0026056:2.IEC_ENERGY_COUNTER' type='IEC_ENERGY_COUNTER' ise_id='32726' value='169.390300' valuetype='4' valueunit='kWh' timestamp='1697538147' lastdpactiontime='<datapoint name='BidCos-RF.MEQ0026056:2.IEC_POWER' type='IEC_POWER' ise_id='32727' value='0.000000' valuetype='4' valueunit='W' timestamp='1697538147' lastdpactiontime='</channel></device></state>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------^

Das wiederrum führt daszu, dass die Ausgabe sich nicht weiter verarbeiten lässt.