Skip to content

Use new ID for live reporting period to ensure reset#66

Merged
martinjaeger merged 1 commit intomainfrom
fix-live-reporting-period
Dec 19, 2025
Merged

Use new ID for live reporting period to ensure reset#66
martinjaeger merged 1 commit intomainfrom
fix-live-reporting-period

Conversation

@martinjaeger
Copy link
Contributor

The period was changed from seconds to milliseconds in b7b67f4. For devices which had their previous setting stored in flash or EEPROM, this led to publishing intervals of e.g. 1 ms instead of 1 s, which may completely block the MCU trying to publish the reports.

By using a new ID, the previously stored value is ignored and the default value is used instead.

CC @jalinei

The period was changed from seconds to milliseconds in b7b67f4. For
devices which had their previous setting stored in flash or EEPROM,
this led to publishing intervals of e.g. 1 ms instead of 1 s, which
may completely block the MCU trying to publish the reports.

By using a new ID, the previously stored value is ignored and the
default value is used instead.
@martinjaeger martinjaeger merged commit 83ad2ed into main Dec 19, 2025
2 checks passed
@martinjaeger martinjaeger deleted the fix-live-reporting-period branch December 19, 2025 09:54
martinjaeger added a commit to LibreSolar/bms-firmware that referenced this pull request Dec 19, 2025
The reason was that due to an update in the unit of the live reporting
period the BMS would try to send out reports in 1 ms intervals if it
had a reporting period from previous firmware versions stored in the
flash.

See also original ThingSet SDK PR:
ThingSet/thingset-zephyr-sdk#66
@jalinei
Copy link
Contributor

jalinei commented Dec 19, 2025

Sorry for the mess !

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.

2 participants