Repository navigation
Conversation
❌MegaLinter analysis: Error
Detailed Issues❌ CPP / clang-format - 2 errorsNotices
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
4 similar comments
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
4 similar comments
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
2 similar comments
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
5b4c852 to
a22f57d
Compare
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
1 similar comment
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
3 similar comments
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
1 similar comment
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 87829b282b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
Native Test Coverage
Report from native unit tests (ASan + gcov). |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fc1aaa211b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| settings.tempCircThreshold = command.value; | ||
| return saveSettings(); |
There was a problem hiding this comment.
Roll back circulation settings after save failures
When NVS cannot be opened, this branch returns rejection after leaving settings.tempCircThreshold changed; the factor and maximum-runtime branches have the same behavior. The MQTT adapter then calls publishStates(), which reports the rejected value, and any later successful configuration save persists it. Preserve the previous setting and restore it when saveSettings() fails, as the setpoint branches already do.
Useful? React with 👍 / 👎.
| settings.timezoneIndex = command.integerValue; | ||
| if (!saveSettings()) { | ||
| return false; |
There was a problem hiding this comment.
Restore the timezone setting when persistence fails
If ConfigManager::save() fails for an MQTT timezone command, the handler returns false but leaves settings.timezoneIndex at the requested value while skipping setTimezoneIndex(). Consequently Home Assistant is republished the new timezone label even though the running clock still uses the old timezone, and an unrelated later save can persist the rejected value. Save the previous index and restore it on this failure path.
Useful? React with 👍 / 👎.

Draft architecture migration
Incrementally migrates adapter boundaries to the Core-1 typed-command / immutable-snapshot architecture while preserving existing MQTT/Web contracts.
Target
ControllerCommandvaluesSystemSnapshotvalue copiesDependencies integrated in this branch
Implemented in this draft
ControllerCommandHandlercomposed inmain.cppControllerCommandon the Core-1 loopVerified so far
Still draft
SystemSnapshotfrom the Core-1 ownerNodes.hppaccess from migrated adaptersMqttCommandQueueafter typed hand-over equivalence is completeThe PR intentionally remains a draft until these migration steps and their contract tests are complete.