Replies: 4 comments 1 reply
-
JSON is a convenient format so that one's can pickup what it needs |
Beta Was this translation helpful? Give feedback.
-
Thanks for sharing your ideas. Most automation softwares like OpenHab, Homeassistant, etc, parse JSON messages without issues. Sorry, this change don't have any advantage for most users and make a more intensive use of MQTT Broker. Sorry, that is not going to be added. |
Beta Was this translation helpful? Give feedback.
-
Thanx for sharing your visions. It's not a big problem to me but I just wanted to share my ideas and to hear how others think about it. |
Beta Was this translation helpful? Give feedback.
-
Because values aren't separated into different topics I bump into this issue: #11103 |
Beta Was this translation helpful? Give feedback.
-
At this moment STATE and INFO for example is one json payload containing all state information.
I think it is more versatile to split the json data into different topics. This way a mqtt client can receive exactly the information it is interested in and the json doesn't have to be parsed anymore before processing in for example nodered.
I know this is a very big change, and maybe it has to be an additional feature.
Example:
home/TASMOTA_ZIGBEE/tele/INFO1 = {"Module":"Sonoff ZbBridge","Version":"9.3.0(zbbridge)","FallbackTopic":"cmnd/DVES_9BA274_fb/","GroupTopic":"home/tasmotas/cmnd/"}
Becomes:
home/TASMOTA_ZIGBEE/tele/INFO/module = "Sonoff ZbBridge"
home/TASMOTA_ZIGBEE/tele/INFO/version = "9.3.0(zbbridge)"
home/TASMOTA_ZIGBEE/tele/INFO/fallbacktopic = "cmnd/DVES_9BA274_fb/"
home/TASMOTA_ZIGBEE/tele/INFO/grouptopic = "home/tasmotas/cmnd/"
Beta Was this translation helpful? Give feedback.
All reactions