while reading the MQTT topics from Shelly 2.5 and ShellyPlug usig Telegraf 1.22.4 is working fine for me, I am not able to get Telegraf to read it from the Shelly 1 PM MQTT topic.
My topic is “shellies/Shelly1PM-Office/status/switch:0” which make a JSON string available like this:
Although I have tried to comment out already bits and pieces, I get not output nor erros when running like this “telegraf.exe --config configs\mqtt_shelly1.conf --test”.
My output look likes this
hmm, can you send me your full Telegraf config, please? I cannot see why it’s looking for a tag as based on the config you have shown me you haven’t defined one. Could you also humour me and comment out the topic parsing and see if that changes the result?
#--------------------------------------------------------------------------------------------------
# Global tags can be specified here in key="value" format.
#--------------------------------------------------------------------------------------------------
[global_tags]
site = "all"
#--------------------------------------------------------------------------------------------------
# Configuration for telegraf agent
#--------------------------------------------------------------------------------------------------
[agent]
## Default data collection interval for all inputs
## we do a check every 5 minutes
interval = "300s"
## Rounds collection interval to 'interval'
## ie, if interval="10s" then always collect on :00, :10, :20, etc.
round_interval = true
## Telegraf will send metrics to outputs in batches of at most
## metric_batch_size metrics.
## This controls the size of writes that Telegraf sends to output plugins.
metric_batch_size = 1000
## Maximum number of unwritten metrics per output.
## Increasing this value allows for longer periods of output downtime without
## dropping metrics at the cost of higher maximum memory usage.
metric_buffer_limit = 10000
## Collection jitter is used to jitter the collection by a random amount.
## Each plugin will sleep for a random time within jitter before collecting.
## This can be used to avoid many plugins querying things like sysfs at the
## same time, which can have a measurable effect on the system.
collection_jitter = "60s"
## Default flushing interval for all outputs.
## Maximum flush_interval will be flush_interval + flush_jitter
flush_interval = "300s"
## Jitter the flush interval by a random amount. This is primarily to avoid
## large write spikes for users running a large number of telegraf instances.
## ie, a jitter of 5s and interval 10s means flushes will happen every 10-15s
flush_jitter = "60s"
## By default or when set to "0s", precision will be set to the same
## timestamp order as the collection interval, with the maximum being 1s.
## ie, when interval = "300s", precision will be "1s"
## when interval = "250ms", precision will be "1ms"
## Precision will NOT be used for service inputs.
## It is up to each individual service input to set the timestamp at the appropriate precision.
## Valid time units are "ns", "us" (or "µs"), "ms", "s".
precision = "0s"
## Log at debug level.
debug = true
## Log only error level messages.
quiet = false
## Log target controls the destination for logs and can be one of "file",
## "stderr" or, on Windows, "eventlog". When set to "file", the output file
## is determined by the "logfile" setting.
# logtarget = "file"
## Name of the file to be logged to when using the "file" logtarget. If set to
## the empty string then logs are written to stderr.
# logfile = ""
## The logfile will be rotated after the time interval specified. When set
## to 0 no time based rotation is performed. Logs are rotated only when
## written to, if there is no log activity rotation may be delayed.
# logfile_rotation_interval = "0d"
## The logfile will be rotated when it becomes larger than the specified
## size. When set to 0 no size based rotation is performed.
# logfile_rotation_max_size = "0MB"
## Maximum number of rotated archives to keep, any older logs are deleted.
## If set to -1, no archives are removed.
# logfile_rotation_max_archives = 5
## Override default hostname, if empty use os.Hostname()
hostname = ""
## If set to true, do no set the "host" tag in the telegraf agent.
omit_hostname = true
#--------------------------------------------------------------------------------------------------
# Processors
#--------------------------------------------------------------------------------------------------
[[processors.strings]]
[[processors.strings.lowercase]]
tag = "host"
[[processors.enum]]
[[processors.enum.mapping]]
## Name of the tag to map
tag = "url"
## Destination tag or field to be used for the mapped value. By default the
## source tag or field is used, overwriting the original value.
dest = "url_name"
## Default value to be used for all values not contained in the mapping
## table. When unset and no match is found, the original field will remain
## unmodified and the destination tag or field will not be created.
default = ""
#--------------------------------------------------------------------------------------------------
# Output
#--------------------------------------------------------------------------------------------------
[[outputs.influxdb]]
urls = ["http://localhost:8086"]
username = "admin"
password = "*****"
database = "mqtt"
#--------------------------------------------------------------------------------------------------
# Inputs
#--------------------------------------------------------------------------------------------------
[[inputs.mqtt_consumer]]
name_override = "shelly"
## MQTT broker URLs to be used. The format should be scheme://host:port,
## schema can be tcp, ssl, or ws.
servers = ["tcp://mqtt.home:1883"]
## Connection timeout for initial connection in seconds
connection_timeout = "60s"
## If unset, a random client ID will be generated.
client_id = "telegraf-shelly1"
topics = ["shellies/Shelly1PM-Office/status/switch:0"]
[[inputs.mqtt_consumer.topic_parsing]]
topic = "+/+/+/+"
measurement = "_/_/_/switch_id"
data_format = "json_v2"
[[inputs.mqtt_consumer.json_v2]]
[[inputs.mqtt_consumer.json_v2.field]]
path = "apower"
rename = "power"
type = "float"
[[inputs.mqtt_consumer.json_v2.field]]
path = "aenergy.total"
rename = "energy"
type = "float"
[[inputs.mqtt_consumer.json_v2.field]]
path = "voltage"
type = "float"
[[inputs.mqtt_consumer.json_v2.field]]
path = "current"
type = "float"
# telegraf.exe --config configs\mqtt_shelly1.conf --test
# telegraf.exe --config configs\mqtt_shelly1.conf --debug
Sorry @mengrie,
I had a google and bad use of the saying “can you humour me” . I meant no offence. I was just asking you to do something silly so meant with that context . I am now glad you have data but lets see if we can get your topic parsing working
. I meant no offence. I was just asking you to do something silly so meant with that context 
. I am now glad you have data but lets see if we can get your topic parsing working 
(Because my native language is Dutch, I wondering if it meant something special …)
