Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request]Monitor the connection quality between OpenDTU and Inverter(s) #1963

Open
Manos1966 opened this issue May 4, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@Manos1966
Copy link

Is your feature request related to a problem? Please describe.

I place this point for discussion, not sure whether it is relevant under normal conditions...
I had the experience of testing in an environment with many DTUs (original HM DTUs + OpenDTU) are active.

Depending on the transmition strength and distance between OpenDTU and the inverter, you may experience a lot of "re-transmissions" (You can notice this by monitoring the messsages in the Console).

When such "re-transmissions" occur, there are delays to reaction-time of other processes. This gives the impression that OpenDTU reacts slowly (whereas the slow reaction-time has nothing to do with OpenDTU).

Not many users (in my opinion) are aware of this transmission-quality problem.

Describe the solution you'd like

An visual indicator that could give an idea how good (fast, number of re-transmits) communication of these two areas is.
Something like calculate the ratio of successful transmissions and (retransmits + failures).
Individually for every inverter, of course.

Describe alternatives you've considered

I know it sounds funny but, it happened: Putting a brick between the OpenDTUonBattery and the inverter solves the problem.
Same as putting the OpenDTUonBattery in another room.

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant