Just a followup thought here: might it be useful to change these in specific circumstances? Like if:
- a user has a particularly flaky network, "i know my wifi drops daily and it takes 2 minutes for the network to reboot"
- a user needs a tighter disconnect period, "5 seconds is make or break, kick my device at 7 seconds without heartbeat!"
...if they could control these values they could self-help wrt disconnect behavior
We could allow these values to be overridden by, for instance:
- user controls in the frontend
- special
secrets.json vars
Originally posted by @lorennorman in #900 (comment)
For now we can relatively easily update the keep alive interval, potentially via config/secrets, as it's a full blown property:
|
uint16_t _brokerKeepAliveIntervalSeconds = |
|
0; /*!< Cached MQTT broker keepalive interval, in seconds. */ |
Just a followup thought here: might it be useful to change these in specific circumstances? Like if:
...if they could control these values they could self-help wrt disconnect behavior
We could allow these values to be overridden by, for instance:
secrets.jsonvarsOriginally posted by @lorennorman in #900 (comment)
For now we can relatively easily update the keep alive interval, potentially via config/secrets, as it's a full blown property:
Adafruit_Wippersnapper_Arduino/src/Wippersnapper.h
Lines 481 to 482 in c212b86