Dtu settings : Missing values

[redridinghood314]

Hello !
First thanks for the work on opendtu. This IS really great project !
Here my problem , i have changed transmit power to try to extend range and disocver my new inverter. Then i have upgraded firmware (from 24.5.6 (if i remember well) ) to 24.9.21.
My New inverter is now working well, so i would like to see if i Can decrease transmit power, but when i change the value and save it indicates that some value are Missing, i do not understand why. Could you please help me on that ?thanks a lot !

[tbnobody]

Found the issue. will be fixed in the next release.

[redridinghood314]

Thanks a lot for this Quick return !!
May i ask you one question, my new inverter (hoymiles HMS 1000) is showing unknown event id 23 many Time (but seems to have stopped), do you know what is it or where i can search for explanation ?thanks !!

[tbnobody]

do you know what is it or where i can search for explanation ?

Unfortunatly not. All descriptions which are known are already shown. Only possibility would be the device manual (the previous id's where read from the manual)

[redridinghood314]

Ok, thanks, unfortunately error code starts at 121 in product documentation, i will try to contact hoymiles and give feedback to add it if i get an answer. Thanks !

[stefan123t]

@redridinghood314 the most concise list we found in warn_code.json of the S-Miles Installer Apps APK file.

#121 (comment)

Maybe they have added the alarm / event code the list lately? I have not checked or verified this since quite some time.

[tbnobody]

I have not checked or verified this since quite some time.

I've just checked versioin 1.1.29... Nothing regarding ID 23

[stefan123t]

Thanks we could only send a fake Event log to the S-Miles Cloud using the protobuf API that @rovo89 @DennisOSRM and others built.
Such a fake Event log may contain multiple of the yet unknown Event IDs like 23 and we could then check in the S-Miles Cloud how these unknown Event IDs get translated / interpreted.

[Zephalon]

I have the same issue in 24.9.22. A workaround is to export the config.json, adjust the values and re-import the file.

[tbnobody]

Thats absolutly ok as this issue was fixed in 24.9.23 and you are using an older version.