Huawei: panic: runtime error: index out of range [3] with length 2 #3222
Replies: 3 comments 12 replies
-
|
Bitte Sufu benutzen. Fehler in der Modbuskommunikation vom Huawei. Schön wäre auch Posting lesbar zu formatieren ;) /cc @RTTTC |
Beta Was this translation helpful? Give feedback.
-
|
Hmm nothing like that ever happens to me. One thing that I noticed is that in your error there is
|
Beta Was this translation helpful? Give feedback.
-
|
Dass die Kommunikation mit dem Huawei nicht einfach ist, habe ich schon verstanden. Blöd nur, wenn deswegen der EVCC komplett abschmiert. Mit einem Check der übergebenen Daten, könnte man das ja abfangen?!? Übrigens gibt es hier neue Erkenntnisse dazu... |
Beta Was this translation helpful? Give feedback.
-
|
@olloESP have you seen this? What do you have set up as decode? Post your Huawei meter config. |
Beta Was this translation helpful? Give feedback.
-
|
Doesn‘t matter. The problem is not the sign but missing bytes. The data is invalid form what I could guess from the message as far as it is readable. |
Beta Was this translation helpful? Give feedback.
-
|
Well then, besides old firmware, and poor wifi - I'm out of ideas. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using latest FW v127 for the SDongle. It is connected through WiFi. The signal strength is fine while the connection drops occationally but recovers quickly. The connection to the FusionSlar as well as to my local OpenHAB server works fine. If you know about the problem, why don't you drop such incomplete data and wait for the next good one instead of crash? Isn't it good practice to verify data before processing it? Such crash might become a security issue, no? |
Beta Was this translation helpful? Give feedback.
-
|
Why not address the root cause, that is a broken Huawei Modbus implementation? Did you open a ticket with Huawei? |
Beta Was this translation helpful? Give feedback.
-
|
Should be solved #2994 (comment) |
Beta Was this translation helpful? Give feedback.
-
Hallo,
bei meiner Installation (v0.90 Docker Container auf Synology) kommt es häufiger zu einem Crash mit der genannten Fehlermeldung. Das liegt wahrscheinlich daran, dass die Kommunikation zu meinem Huawei WR recht "wacklich" ist und manchmal unplausible Daten gesendet werden - extrem große Zahlen für den Verbrauch. Das wird bei der Konvertierung nicht abgefangen?!
panic: runtime error: index out of range [3] with length 2 goroutine 119 [running]: encoding/binary.bigEndian.Uint32(...) /usr/local/go/src/encoding/binary/binary.go:112 github.com/volkszaehler/mbmd/meters/rs485.RTUInt32ToFloat64({0xc0001a3569?, 0xc000ac1ac8?, 0xe700eb?}) /go/pkg/mod/github.com/volkszaehler/[email protected]/meters/rs485/transform.go:65 +0x3b github.com/evcc-io/evcc/provider.(*Modbus).floatGetter(0xc000a94c00) /build/provider/modbus.go:171 +0x52b github.com/evcc-io/evcc/meter.(*Meter).CurrentPower(0xc000ac1b10?) /build/meter/meter.go:122 +0x1a github.com/evcc-io/evcc/core.(*Site).updateMeter.func1() /build/core/site.go:242 +0x2b github.com/avast/retry-go/v3.Do(0xc000a58440, {0x2b39ee0, 0x2, 0xc0002704a0?}) /go/pkg/mod/github.com/avast/retry-go/[email protected]/retry.go:107 +0x12c github.com/evcc-io/evcc/core.(*Site).updateMeters(0xc0005de900) /build/core/site.go:299 +0x618 github.com/evcc-io/evcc/core.(*Site).sitePower(0xc0005de900, 0x0) /build/core/site.go:341 +0x65 github.com/evcc-io/evcc/core.(*Site).update(0xc0005de900, {0x1e96480, 0xc000364380}) /build/core/site.go:406 +0x12f github.com/evcc-io/evcc/core.(*Site).Run(0xc0005de900, 0xc0006e6ba0, 0x2540be400) /build/core/site.go:490 +0x1ea github.com/evcc-io/evcc/cmd.run.func1() /build/cmd/root.go:263 +0x31 created by github.com/evcc-io/evcc/cmd.run /build/cmd/root.go:262 +0x12e5Danke!
Beta Was this translation helpful? Give feedback.
All reactions