Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rscp2mqtt no longer polled at 30 second intervals but at 3 second intervals #92

Open
jomifa opened this issue Dec 27, 2024 · 2 comments

Comments

@jomifa
Copy link

jomifa commented Dec 27, 2024

Hello,
I discovered today that the poll sequence has been reduced from 30 to 3 seconds. No change was made to the .config file.

Extract from the .config:

#-System
#--cycle interval in seconds (max 300 seconds)
INTERVAL=30

PS
RSCP2MQTT runs as version 3.23

Best regards,
Joachim

@pvtom
Copy link
Owner

pvtom commented Dec 27, 2024

Hello Joachim,
rscp2mqtt is implemented so that the wait time (set by the INTERVAL parameter) is interrupted when an MQTT command (a set command, e.g. e3dc/set/wallbox/xxx) is received so that it is processed immediately.
Are you using another tool that sends control commands to rscp2mqtt every 3 seconds?

Best regards,
Thomas

@jomifa
Copy link
Author

jomifa commented Dec 27, 2024

Hello Thomas,
no, I am not aware that I would send other E3DC commands via MQTT. I followed up on your hint and found a place in my flow that had written the status change via MQTT back into the MQTT (set). This then led to a loop condition.

Thank you for your support.

Greetings
Joachim

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

No branches or pull requests

2 participants