Skip to content

Conversation

@pylonsoft
Copy link

If continuous mode is activated most SEN5X readings went wrong because the already read values weren't returned but get_reading() returned an error state. By checking if update() failed because of no new values available in continuous mode (SEN54 and SEN55) we can return the stored values safely.

If continuous mode is activated most SEN5X readings went wrong because
the already read values weren't returned but get_reading() returned an
error state. By checking if update() failed because of no new values
available in continuous mode (SEN54 and SEN55) we can return the stored
values safely.
@oscgonfer
Copy link
Collaborator

oscgonfer commented Sep 9, 2025

Thank you so much @pylonsoft ! I add a minor addition to your check for the forcedContinuousMode.

If you want/can test this last change, I'll merge!

@oscgonfer oscgonfer self-assigned this Sep 9, 2025
@oscgonfer oscgonfer added the bug Something isn't working label Sep 9, 2025
@oscgonfer
Copy link
Collaborator

Also, if working with SEN55, probably take a look at #88 too

@pylonsoft
Copy link
Author

Your addition for the forcedContinousMode works for me. I deactivated the SEN55 sensors and set the reading interval to 20 secs (both in config and for the SEN5X temperature sensor). This way the forcedContinousMode flag was activated but the continousMode flag wasn't. The readings came in as expected.

@oscgonfer oscgonfer merged commit 803d3f2 into fablabbcn:master Sep 9, 2025
4 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants