Skip to content

Avoid_Timesync_AlarmID_#2: - #3302

Open
xX-nichtlachen-Xx wants to merge 1 commit into
tbnobody:masterfrom
xX-nichtlachen-Xx:Avoid_Timesync_AlarmID_#2
Open

xX-nichtlachen-Xx wants to merge 1 commit into
tbnobody:masterfrom
xX-nichtlachen-Xx:Avoid_Timesync_AlarmID_#2

Conversation

@xX-nichtlachen-Xx

Copy link
Copy Markdown
Contributor

Avoid_Timesync_AlarmID_#2:
Occurs when many commands are queued at the same time.me.

@xX-nichtlachen-Xx
xX-nichtlachen-Xx force-pushed the Avoid_Timesync_AlarmID_#2 branch from f0ba00f to 575684c Compare October 22, 2026 19:12
@SW-Niko

SW-Niko commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

That explains why ID_2 disappeared from my system after I drastically reduced the number of re-requests.
👍 very good.

@xX-nichtlachen-Xx
xX-nichtlachen-Xx force-pushed the Avoid_Timesync_AlarmID_#2 branch from 575684c to 75aed9c Compare October 25, 2026 03:43
@elmr91

elmr91 commented Oct 25, 2026

Copy link
Copy Markdown

@mathieucarbou, this is what we saw with zero-export firmware: large increase of alarm_#2 when zero export is active.
zero-export is sending lots of powercontrol commands.

@mathieucarbou

Copy link
Copy Markdown
Contributor

@mathieucarbou, this is what we saw with zero-export firmware: large increase of alarm_#2 when zero export is active. zero-export is sending lots of powercontrol commands.

I though this was finally fixed by another pr ?

@SW-Niko @elmr91 : did you test his PR ? Want me to include it in the Zero-export firmware ?

@SW-Niko

SW-Niko commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

@mathieucarbou
No, I didn't test this PR.
The ID_2 warnings disappeared from my system already after I drastically reduced the number of re-requests.
I just didn't know why. But this PR seams to be the explanation.
No re-requests, No commands with identical time stamp, No ID_2 warnings. 😄

@mathieucarbou

Copy link
Copy Markdown
Contributor

@mathieucarbou No, I didn't test this PR. The ID_2 warnings disappeared from my system already after I drastically reduced the number of re-requests. I just didn't know why. But this PR seams to be the explanation. No re-requests, No commands with identical time stamp, No ID_2 warnings. 😄

Isn’t the right approach would be to keep requesting again, but instead with a different time stamp?

@SW-Niko

SW-Niko commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

@mathieucarbou

isn’t the right approach would be to keep requesting again, but instead with a different time stamp?

That's the right approach, and that's exactly what this PR achieves.

by the way .. the powercontrol command returns only one packet. If we don't get an answer from the inverter, we do not re-request the missing packet, we request the complete powercontrol command again. 🤔

@elmr91

elmr91 commented Oct 28, 2026 •

Copy link
Copy Markdown

by the way .. the powercontrol command returns only one packet. If we don't get an answer from the inverter, we do not re-request the missing packet, we request the complete powercontrol command again. 🤔

I don't see any drawback to send twice the same PowerControl command:

  • either the first command has been lost: it is then useful to resend it
  • or the answer from the previous command has been lost. In this case a new command with the same power settings will reach the inverter again. It should not produce any unwanted effect as inverter should have already taken into account the new power.

@xX-nichtlachen-Xx

Copy link
Copy Markdown
Contributor Author

I'm glad to see that you're having fun here, but please try to stay on topic.

If you want to discuss temporary power limits on the HMS-4T, that's fine. However, the HMS-4T FW > 2.x does not mirror those limits, so please don't mix everything together.

@tbnobody

Copy link
Copy Markdown
Owner

Thank you. Will include it in the next release

Occurs when many commands are queued at the same time.
@xX-nichtlachen-Xx
xX-nichtlachen-Xx force-pushed the Avoid_Timesync_AlarmID_#2 branch from 75aed9c to 11eeea6 Compare November 11, 2026 16:43
@xX-nichtlachen-Xx

Copy link
Copy Markdown
Contributor Author

rebased to v26.11.11

@mathieucarbou

Copy link
Copy Markdown
Contributor

Note: commit added in latest OpenDTU Zero-Export release v26.11.11-ze1 rebased on latest OpenDTU version v26.11.11

@elmr91

elmr91 commented Nov 13, 2026 •

Copy link
Copy Markdown

Note: commit added in latest OpenDTU Zero-Export release v26.11.11-ze1 rebased on latest OpenDTU version v26.11.11

I'm testing this fix using @mathieucarbou build: I can confirm it completely solves the AlarmID 2 problems.
No alarm at all except the initial AlarmID 1 at start in the morning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants