Polling interval
#1452
Replies: 1 comment
-
|
If you can read, you have a clear advantage. I put the numbers behind the R in the csv an all went good. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
in addition to #1446 (comment) I would like to now how the polling of values works.
Everything is loaded fine and I look into the deamon with tcp via putty.
so my 'find' list is filled with "Names":
As you can see: for many "Names" there are no values yet.
I can read "Names" with "r -V Name" (e.g. r -V z1SFMode). The answer is the Value of z1SFMode and the log description (-V).
Afterwards the value is also found in the 'find' list (and in HomeAssistant, i can see the value with MQTTExplorer). E.g "ctlv2 WaterPressure" and "bai WaterPressure" in the code above.
That leads me to my question: how is the "Names"-List polled on the eBUS? Is there somewhere a variable, how often an how many "Names" are polled (e.g. from top to bottom 5 "Names" every 10 sec., so a a list of 30 "Names" will be filled with (new) values every 2 Minutes)?
How does eBUSd (especially the HomeAssistant add-on (Lukas Grebe)) get all the values in order to work with them?
I 'reloaded' the csv and after 2 hours there are almost all "Names" still in "no data stored".
Regards Sebastian
Beta Was this translation helpful? Give feedback.
All reactions