HMS-800-2T

[Vicio88]

What happened?

Buon giorno. Ho un problema con la mia dtu. Non riconosce il mio inverter HMS-800-2T. Ho fatto anche l’ultimo aggiornamento ma non va

To Reproduce Bug

Buon giorno. Ho un problema con la mia dtu. Non riconosce il mio inverter HMS-800-2T. Ho fatto anche l’ultimo aggiornamento ma non va

Expected Behavior

v4.4.7-dirtyI

Install Method

Pre-Compiled binary from GitHub

What git-hash/version of OpenDTU?

v4.4.7-dirty

Relevant log/trace output

No response

Anything else?

No response

Please confirm the following

• I believe this issue is a bug that affects all users of OpenDTU, not something specific to my installation.
• I have already searched for relevant existing issues and discussions before opening this report.
• I have updated the title field above with a concise description.

[broth-itk]

Please provide more information like S/N of your inverter and the correct OpenDTU version.
Screenshot would be nice.
v4.4.7-dirtyI is no version from an OpenDTU release

[Vicio88]

[Vicio88]

Inverte hoymiles HMS-800-2T

[stefan123t]

@Vicio88 we need at least the first seven digits of your inverter serial id.
The last five are unique and can be ommitted.

Do you have two different serial IDs on the sticker, ie the model number ( first four digits ) may differ for HMS-800W-2T Models as they have a built-in DTUBI as well.

[Vicio88]

[stefan123t]

Your first inverter is a HMS-800W model. The second most likely too, given the same model prefix.
You can use any of the other projects for DTUBI and HMS-xxxW HMS-WiFi-Series Models or directly use the S-Miles Installer App / S-Miles Cloud from Hoymiles itself.

[Vicio88]

Dove lo trovo ?

[stefan123t]

Ciao Vicio, the most known is this one written in RUST from DennisOSRM https://github.com/DennisOSRM/hms-mqtt-publisher
At the moment it does support only a single HMS-WiFi-Series, though there is a pull request # 94 to support multiple inverters too.

I do prefer the Python implementation by rovo89 as it is more promising, but I do not own an HMS-WiFi-Series inverter so this is only my personal point of view.

[broth-itk]

Maybe it's good idea to add all known serial number prefixes to the list and name them "Unsupported" or "WIFI Unsupported"

[tbnobody]

I added a open topic to the documentation project and will close this issue.

[stefan123t]

@tbnobody so we can not identify them based on the Serial ID users enter ?
This would allow us to show an alert / warning in the add/edit inverter dialog to notify users

I answer several reports / discussions per week and have to explain the distinction between vanilla HMS and HMS-xxxW again and again.

Maybe it would be good to hint at this fact also in the Bug template or pose it as a checkbox / question ?

Kind regards, Stefan

[tbnobody]

I will add a checkbox to the issue template. I'm not really willing to add a blacklist to the WebGUI, especially as an "Unknown" etc. is also displayed in the inverter overview. It will be also mentioned in the documentation. I mean, in how many other places can people ignore it?

[stefan123t]

Well if they can ignore it, they will. 🤣
Even if a clear Warning its there they will try to ignore it if possible.

One last thought, though you are reluctant to add support for those built-in DTUBI HMS WiFi series inverters, they are not Unknown but just Unsupported at the moment.

Maybe we should add a stub for a protobuf implementation via a separate AP network link.
Once the Setup AP has been closed we could use its connection to connect to at least one of the DTUBI APs.
I wonder if we would have to connect to each AP in case we want to query multiple such DTUBI based inverters ?

[broth-itk]

IMHO I agree to stefan123t, there should be a "Unsupported" message in the GUI when adding a W inverter.
Since asking questions is always easier as reading documentaton or even the text beside of checkboxes, this change will help keeping motivation up for all involved in OpenDTU development and support (via Issues).

Just my 2 cents

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.