search

zivillian / ism7mqtt

GNU General Public License v3.0
57 stars 11 forks source link

Fehler #61

Closed wartungsmonteur closed 11 months ago

wartungsmonteur commented 1 year ago

Hallo

ich bekomme nach dem Start des Plugin folgende Fehlermeldung: s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started ++ cd /app Creating initial configuration /config/ism7-parameters-Wolf.json ++ parameters=/config/ism7-parameters-Wolf.json ++ '[' -f /config/ism7-parameters-Wolf.json ']' ++ echo 'Creating initial configuration /config/ism7-parameters-Wolf.json' ++ /app/ism7config -t /config/ism7-parameters-Wolf.json 2023-06-29 13:22:32.0172|INFO|LuCon.WebPortal.StandaloneService.NetworkConnector|Try IP-resolve for host:192.168.178.84 2023-06-29 13:22:32.0846|INFO|LuCon.WebPortal.StandaloneService.NetworkConnector|Try connect destination server -> 192.168.178.84:9092, Timeout:1000 ms 2023-06-29 13:22:37.3709|ERROR|LuCon.WebPortal.StandaloneService.NetworkConnector|DoConnect Unhandled exception. LuCon.Common.Declarations.BusinessServiceException: Die Verbindung zur Anlage kann nicht hergestellt werden. Aktualisieren Sie die Anlagenliste und versuchen Sie es nochmal. at LuCon.WebPortal.StandaloneService.NetworkConnector.DoConnect(String server, IPAddress localIp, Int32 port, String password, IStreamHandler streamHandler) at ism7config.Program.Main(String[] args) in /app/ism7config/Program.cs:line 120 at ism7config.Program.

(String[] args) /run.sh: line 28: 125 Aborted (core dumped) /app/ism7config -t $parameters s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

sniesen commented 1 year ago

Are you using the most recent version?

zivillian commented 1 year ago

I've published a new version with increased timeouts. As soon as the HA Addon is updated, you can try again.

wartungsmonteur commented 1 year ago

Hallo

Läuft länger aber stoppt dann wieder.

log ``` 2023-07-17 19:38:47.9200|TRACE|GW-1| ReadTelegramAsync !! 2023-07-17 19:38:47.9200|TRACE|GW-1| Got 6 bytes from stream, elapsedMs=0 2023-07-17 19:38:47.9200|TRACE|GW-1| lenToRead: 86 2023-07-17 19:38:47.9200|TRACE|GW-1| telegrType TgrBundleResponse 2023-07-17 19:38:47.9200|TRACE|GW-1| Try to complete msg, bytesMissing:86 [6/86] 2023-07-17 19:38:47.9643|TRACE|GW-1| Got 86 bytes from stream, elapsedMs=44 2023-07-17 19:38:47.9643|INFO|GW-1| Got XML msg:??? 2023-07-17 19:39:07.2592|TRACE|GW-1| ReadTelegramAsync !! 2023-07-17 19:39:07.2592|TRACE|GW-1| Got 6 bytes from stream, elapsedMs=0 2023-07-17 19:39:07.2592|TRACE|GW-1| lenToRead: 1450 2023-07-17 19:39:07.2592|TRACE|GW-1| telegrType TgrBundleResponse 2023-07-17 19:39:07.2592|TRACE|GW-1| Try to complete msg, bytesMissing:1450 [6/1450] 2023-07-17 19:39:07.2641|TRACE|GW-1| Got 249 bytes from stream, elapsedMs=4 2023-07-17 19:39:07.2641|TRACE|GW-1| Try to complete msg, bytesMissing:1201 [255/1450] 2023-07-17 19:39:07.2722|TRACE|GW-1| Got 66 bytes from stream, elapsedMs=12 2023-07-17 19:39:07.2722|TRACE|GW-1| Try to complete msg, bytesMissing:1135 [321/1450] 2023-07-17 19:39:07.2743|TRACE|GW-1| Got 225 bytes from stream, elapsedMs=15 2023-07-17 19:39:07.2743|TRACE|GW-1| Try to complete msg, bytesMissing:910 [546/1450] 2023-07-17 19:39:07.2769|TRACE|GW-1| Got 64 bytes from stream, elapsedMs=17 2023-07-17 19:39:07.2769|TRACE|GW-1| Try to complete msg, bytesMissing:846 [610/1450] 2023-07-17 19:39:07.2821|TRACE|GW-1| Got 197 bytes from stream, elapsedMs=22 2023-07-17 19:39:07.2821|TRACE|GW-1| Try to complete msg, bytesMissing:649 [807/1450] 2023-07-17 19:39:07.2836|TRACE|GW-1| Got 64 bytes from stream, elapsedMs=24 2023-07-17 19:39:07.2836|TRACE|GW-1| Try to complete msg, bytesMissing:585 [871/1450] 2023-07-17 19:39:07.2879|TRACE|GW-1| Got 194 bytes from stream, elapsedMs=28 2023-07-17 19:39:07.2879|TRACE|GW-1| Try to complete msg, bytesMissing:391 [1065/1450] 2023-07-17 19:39:07.2896|TRACE|GW-1| Got 65 bytes from stream, elapsedMs=30 2023-07-17 19:39:07.2896|TRACE|GW-1| Try to complete msg, bytesMissing:326 [1130/1450] 2023-07-17 19:39:07.3013|TRACE|GW-1| Got 188 bytes from stream, elapsedMs=42 2023-07-17 19:39:07.3013|TRACE|GW-1| Try to complete msg, bytesMissing:138 [1318/1450] 2023-07-17 19:39:07.3033|TRACE|GW-1| Got 65 bytes from stream, elapsedMs=44 2023-07-17 19:39:07.3033|TRACE|GW-1| Try to complete msg, bytesMissing:73 [1383/1450] 2023-07-17 19:39:07.3482|TRACE|GW-1| Got 73 bytes from stream, elapsedMs=88 2023-07-17 19:39:07.3482|INFO|GW-1| Got XML msg:??? 2023-07-17 19:39:07.3538|INFO|GW-1| Written XML, bytes:1041, msg: Timeout waiting for GW Parameter file creation seems to have failed. Please report to the ism7mqtt project: https://github.com/zivillian/ism7mqtt/issues/new ++ '[' -f /config/ism7-parameters-Wolf.json ']' ++ echo 'Parameter file creation seems to have failed. Please report to the ism7mqtt project: https://github.com/zivillian/ism7mqtt/issues/new' ++ exit -1 s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping ```
zivillian commented 1 year ago

magst du einmal das vollständige Log hochladen? Und es wäre super, wenn du das einmal ohne den Docker Container mit den Binaries aus dem Release ausprobieren könntest. Dadurch können wir ausschließen, dass es irgendwas im HomeAssistant oder dem Addon ist.

wartungsmonteur commented 1 year ago 
    <ird se="A;52" ba="0x86" in="9028" is="60" />
    <ird se="A;45" ba="0x85" in="9024" is="60" />
    <ird se="A;57" ba="0x87" in="9028" is="60" />
    <ird se="A;50" ba="0x86" in="9024" is="60" />
    <ird se="A;55" ba="0x87" in="9024" is="60" />
    </tbreq>
2023-07-17 20:21:16.3484|TRACE|GW-1|<GW:1,0> ReadTelegramAsync !!
2023-07-17 20:21:16.3484|TRACE|GW-1|<GW:1,0> Got 6 bytes from stream, elapsedMs=0
2023-07-17 20:21:16.3484|TRACE|GW-1|<GW:1,0> lenToRead: 784
2023-07-17 20:21:16.3484|TRACE|GW-1|<GW:1,0> telegrType TgrBundleResponse
2023-07-17 20:21:16.3484|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:784 [6/784]
2023-07-17 20:21:16.3914|TRACE|GW-1|<GW:1,0> Got 192 bytes from stream, elapsedMs=42
2023-07-17 20:21:16.3914|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:592 [198/784]
2023-07-17 20:21:16.3981|TRACE|GW-1|<GW:1,0> Got 43 bytes from stream, elapsedMs=49
2023-07-17 20:21:16.3981|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:549 [241/784]
2023-07-17 20:21:16.3999|TRACE|GW-1|<GW:1,0> Got 150 bytes from stream, elapsedMs=51
2023-07-17 20:21:16.3999|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:399 [391/784]
2023-07-17 20:21:16.4018|TRACE|GW-1|<GW:1,0> Got 62 bytes from stream, elapsedMs=53
2023-07-17 20:21:16.4018|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:337 [453/784]
2023-07-17 20:21:16.4071|TRACE|GW-1|<GW:1,0> Got 153 bytes from stream, elapsedMs=58
2023-07-17 20:21:16.4071|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:184 [606/784]
2023-07-17 20:21:16.4088|TRACE|GW-1|<GW:1,0> Got 44 bytes from stream, elapsedMs=60
2023-07-17 20:21:16.4088|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:140 [650/784]
2023-07-17 20:21:16.4140|TRACE|GW-1|<GW:1,0> Got 132 bytes from stream, elapsedMs=65
2023-07-17 20:21:16.4140|TRACE|GW-1|<GW:1,0> Try to complete msg, bytesMissing:8 [782/784]
2023-07-17 20:21:16.4157|TRACE|GW-1|<GW:1,0> Got 8 bytes from stream, elapsedMs=67
2023-07-17 20:21:16.4160|INFO|GW-1|<GW:1,0> Got XML msg:???<?xml version="1.0" encoding="utf-8"?>
    <tbres bn="11" gw="1" st="OK" ts="2166-01-01T00:00:33" emsg="">
    <irs se="A;48" ba="0x86" in="5266" st="ER"/>
    <irs se="A;53" ba="0x87" in="5266" st="ER"/>
    <irs se="A;30" ba="0x51" in="410" st="ER"/>
    <irs se="A;31" ba="0x52" in="410" st="ER"/>
    <irs se="A;32" ba="0x53" in="410" st="ER"/>
    <irs se="B;17;23" ba="0x8" in="410" dl="0xE6" dh="0x0" st="OK"/>
    <irs se="A;19" ba="0x8" in="10878" dl="0x0" dh="0x0" st="OK"/>
    <irs se="B;38;37" ba="0x76" in="2476" dl="0x1" dh="0x0" st="OK"/>
    <irs se="A;47" ba="0x85" in="9028" st="ER"/>
    <irs se="A;52" ba="0x86" in="9028" st="ER"/>
    <irs se="A;45" ba="0x85" in="9024" st="ER"/>
    <irs se="A;57" ba="0x87" in="9028" st="ER"/>
    <irs se="A;50" ba="0x86" in="9024" st="ER"/>
    <irs se="A;55" ba="0x87" in="9024" st="ER"/>
    </tbres>
2023-07-17 20:21:16.4160|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;48, Ba:0x86, TelegrNr:5266, State:ER, set value to null
2023-07-17 20:21:16.4160|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;53, Ba:0x87, TelegrNr:5266, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;30, Ba:0x51, TelegrNr:410, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;31, Ba:0x52, TelegrNr:410, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;32, Ba:0x53, TelegrNr:410, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;47, Ba:0x85, TelegrNr:9028, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;52, Ba:0x86, TelegrNr:9028, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;45, Ba:0x85, TelegrNr:9024, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;57, Ba:0x87, TelegrNr:9028, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;50, Ba:0x86, TelegrNr:9024, State:ER, set value to null
2023-07-17 20:21:16.4169|WARN|GW-1|<GW:1,-1> - Response state:ER !!! entry:Resp -> Seq:A;55, Ba:0x87, TelegrNr:9024, State:ER, set value to null
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36013600001, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36013600002, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36013600003, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36006600001, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36006600002, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36006600003, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:4009300001, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:4009300002, state:Error
2023-07-17 20:21:16.4181|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:4009300003, state:Error
2023-07-17 20:21:16.4189|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36014500001, state:Error
2023-07-17 20:21:16.4189|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36014500002, state:Error
2023-07-17 20:21:16.4189|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36013200001, state:Error
2023-07-17 20:21:16.4189|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36014500003, state:Error
2023-07-17 20:21:16.4189|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36013200002, state:Error
2023-07-17 20:21:16.4189|ERROR|GW-1|<GW:1,-1> - Missing device answer - ParameterId:36013200003, state:Error
2023-07-17 20:21:16.4232|INFO|GW-1|<GW:1,-1> - FinishBusconfig
2023-07-17 20:21:16.4542|DEBUG|GW-1|<GW:1,-1> BundleType:push, deviceVisibleReadAddresses:0x8,0x35,0x51,0x52,0x53,0x76
2023-07-17 20:21:16.4542|INFO|GW-1|<GW:1,0> Written XML, bytes:142, msg:<?xml version="1.0" encoding="utf-8"?>
    <tbreq bn="3" gw="1" ae="false" ty="push">
    <erd se="3" li="0x8,0x35,0x51,0x52,0x53,0x76" />
    </tbreq>
2023-07-17 20:21:16.4966|DEBUG|GW-1|<GW:1,-1> Detect SmartHome-System...
2023-07-17 20:21:16.4977|DEBUG|GW-1|<GW:1,-1> SmartHome = 0
2023-07-17 20:21:16.6426|INFO|GW-1|<GW:1,0> Written XML, bytes:1079, msg:<?xml version="1.0" encoding="utf-8"?>
    <tbreq bn="1000" gw="1" ae="true" ty="push">
    <ird se="B;60;59;61;62" ba="0x8" in="371" is="60" />
    <ird se="B;459;453;451" ba="0x87" in="10109" is="60" />
    <ird se="A;160" ba="0x35" in="10148" is="60" />
    <ird se="C;264;135;136;137" ba="0x76" in="135" is="60" />
    <ird se="C;264;135;136;137" ba="0x76" in="136" is="60" />
    <ird se="C;264;135;136;137" ba="0x76" in="137" is="60" />
    <ird se="A;187" ba="0x35" in="5250" is="60" />
    <ird se="A;42" ba="0x35" in="10134" is="60" />
    <ird se="B;162;155" ba="0x35" in="10161" is="60" />
    <ird se="A;389" ba="0x85" in="10159" is="60" />
    <ird se="A;435" ba="0x86" in="10159" is="60" />
    <ird se="A;481" ba="0x87" in="10159" is="60" />
    <ird se="B;214;213" ba="0x51" in="82" is="60" />
    <ird se="B;226;225" ba="0x52" in="82" is="60" />
    <ird se="B;244;243" ba="0x53" in="82" is="60" />
    <ird se="A;77" ba="0x8" in="10010" is="60" />
    <ird se="A;76" ba="0x8" in="10071" is="60" />
    <ird se="A;228" ba="0x52" in="2701" is="60" />
    <ird se="A;358" ba="0x85" in="10179" is="60" />
    <ird se="A;404" ba="0x86" in="10179" is="60" />
    </tbreq>

Das steht im Logfile des Addon, das andere verstehe ich leider nicht. Das Addon läuft jetzt ohne zu stoppen, nur gibt es keine Entitäten unter Mqtt 

Hat jetzt doch wieder gestoppt.

Timeout waiting for GW
Parameter file creation seems to have failed. Please report to the ism7mqtt project: https://github.com/zivillian/ism7mqtt/issues/new
++ '[' -f /config/ism7-parameters-Wolf.json ']'
++ echo 'Parameter file creation seems to have failed. Please report to the ism7mqtt project: https://github.com/zivillian/ism7mqtt/issues/new'
++ exit -1
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
wartungsmonteur commented 1 year ago

Hallo zivillian

Kannst du mir eine PM senden an info@wartungsmonteur.de

Ich könnte dir einen Zugang per VPN einrichten um den Fehler eventuell zu finden. Auch könnte ich dir einen Zugang zum Wolfportal einrichten.

Könntest du bitte eventuell die Zeit die das Addon zum einlesen benötigt auf mindestens 10 Minuten erhöhen ?

Meine Anlage ist so komplex das dies ewig dauert bis alle Parameter eingelesen wurden.

Vielen Dank und viele Grüße.

Tomoene commented 1 year ago

Konntet ihr das Problem lösen? Ich frage, weil bei mir das Gleiche auftritt.

wartungsmonteur commented 1 year ago

Hallo Nein, das Addon läuft bei mir leider nicht. Für große komplexe Anlagen wahrscheinlich nicht geeignet. Schade.

Tomoene commented 1 year ago

Hi! Ich habe nur eine kleine Heizung dran hängen. Also weiß ich nicht, ob es an der Größe der Anlage liegt.

zivillian commented 11 months ago

@wartungsmonteur Funktioniert die Wolf Smartset App (Android oder iOS) mit deiner Anlage?

wartungsmonteur commented 11 months ago

Guten Morgen

Leider nein, immer noch der gleiche Fehler wie zuletzt gemeldet.

zivillian commented 11 months ago

Dann fürchte ich musst du dich an Wolf wenden.

wartungsmonteur commented 11 months ago

Ich bin Kundendiensttechniker für Wolf Heizungsanlagen

zivillian commented 11 months ago

@wartungsmonteur Ich kann mit deiner Antwort leider nichts anfangen. Wenn ich den Verlauf und deine Antwort richtig verstanden habe kannst du mit der offiziellen App von Wolf nicht auf deine Heizung zugreifen. Was ist deine Erwartung, was jetzt hier auf github passiert? Welche Rolle spielt es was du für einen Beruf hast? Was willst du erreichen?

Ich würde meine Software gern auch mit deiner Anlage zum Laufen bringen, aber mir fehlt leider die Zeit mich in meiner Freizeit darum zu kümmern, dass deine Anlage überhaupt so funktioniert wie vom Hersteller vorgesehen (nämlich zumindest mit der offiziellen App vom Hersteller).

Bitte versteh mich nicht falsch - ich versuche deinen Standpunkt zu verstehen und dir irgendwie weiterzuhelfen. Wenn du eine Idee oder einen Lösungsansatz für dein Problem hast, können wir hier gern drüber diskutieren, aber da dieses Projekt von Freiwilligen in ihrer Freizeit umgesetzt, erweitert und verbessert wird, musst du dich da auch entsprechend einbringen.