3diy
/
moonraker
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: update the mqtt documentation 

Signed-off-by:  Eric Callahan <arksine.code@gmail.com>
This commit is contained in:
Eric Callahan 2021-10-10 18:08:25 -04:00
parent 25f9800f77
commit 562f971c3d
1 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/configuration.md
View File

@ -563,19 +563,26 @@ status_objects:
# A newline separated list of Klipper objects whose state will be # A newline separated list of Klipper objects whose state will be
# published in the payload of the following topic: # published in the payload of the following topic:
# {instance_name}/klipper/status # {instance_name}/klipper/status
# For example, to track the "webhooks" and "toolhead" objects this # For example, this option could be set as follows:
# option would be set as follows: #
# status_objects: # status_objects:
# webhooks # webhooks
# toolhead # toolhead=position,print_time,homed_axes
# See the "Printer Objects" section of the documentation for an # extruder=temperature
# overview of the most common objects available. Note that Klipper #
# will only push an update to an object/field if the field has changed. # In the example above, all fields of the "webhooks" object will be tracked
# An object with no fields that have changed will not be part of the # and changes will be published. Only the "position", "print_time", and
# payload. Object state is checked and published roughly every # "homed_axes" fields of the "toolhead" will be tracked. Likewise, only the
# 250 ms. # "temperature" field of the extruder will be tracked. See the
# "Printer Objects" section of the documentation for an overview of the most
# common objects available.
#
# Note that Klipper will only push an update to an object/field if the field
# has changed. An object with no fields that have changed will not be part
# of the payload. Object state is checked and published roughly every 250 ms.
#
# If not configured then no objects will be tracked and published to # If not configured then no objects will be tracked and published to
# the status topic. # the klipper/status topic.
default_qos: 0 default_qos: 0
# The default QOS level used when publishing or subscribing to topics. # The default QOS level used when publishing or subscribing to topics.
# Must be an integer value from 0 to 2. The default is 0. # Must be an integer value from 0 to 2. The default is 0.