Closed Manos1966 closed 5 months ago
Good idea, I had it for months now. My approach would be to calculate the ratio of successful transmissions and (retransmits + failures). However, this was never important enough for me attempt, especially since we would need to touch the upstream code.
This request might actually be better placed upstream? All OpenDTU Users could benefit from such an indicator.
Good Idea, I will place it upstream.
Would upstream also solve the DPL transmition-quality monitoring as well or, does this have to be done here?
Why would we need a separate indicator for the DPL? An no, upstream cannot do something related to the DPL, as the DPL is not an upstream feature.
We need to know how many re-transmits were needed to send the updated Watt-Limit to the Inverter.
ALTHOUGH, we could deduce that, if the quality of Data Transmission from Upstream is poor, the same poor quality will be the case for the transmission of data from the DPL.
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.
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 have the experience of testing in environments where many DTUs (Hoymiles DTUs + OpenDTUonBattery) are active.
Depending on the transmition strength and the (shiort) distance between DTU 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 could lead to the impression that OpenDTUonBattery has slow reaction time.
As most users keep the Battery near the inverter and the OpenDTUonBattery is connected to the Battery and Victron, the OpenDTUonBattery is very close to the inverter.
Not many users (in my opinion) are aware of this transmission-quality problem.
Describe the solution you'd like
Open to suggestions. I see two key areas:
Describe alternatives you've considered
I know it is 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