You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing a CODESYS library to interface with a Zigbee2MQTT gateway over MQTT. My goal is to automatically discover and configure Zigbee devices (type, model, exposed properties, manufacturer, etc.) without manual configuration files.
Currently, the only way to retrieve device metadata seems to be zigbee2mqtt/bridge/devices, but this topic returns a very large JSON payload (~9KB+ for just 3 devices) which is problematic for memory-constrained environments like PLCs or embedded systems with limited MQTT buffer sizes.
Feature request:
Would it be possible to know how to achieve one of the following options ?
A lightweight device list topic : e.g. zigbee2mqtt/bridge/devices/summary that returns only essential fields per device: friendly_name, ieee_address, model, vendor, type — without the full definition, endpoints, clusters, and configured_reportings details.
A per-device query : e.g. publishing to zigbee2mqtt/bridge/request/device/info with payload {"id": "<friendly_name_or_ieee>"} to retrieve metadata for a single device on demand, rather than fetching the entire device list.
Either option would significantly reduce payload sizes and make Zigbee2MQTT much more accessible for resource-constrained MQTT clients.
Thank you for the great work on this project and thank you for your help!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm developing a CODESYS library to interface with a Zigbee2MQTT gateway over MQTT. My goal is to automatically discover and configure Zigbee devices (type, model, exposed properties, manufacturer, etc.) without manual configuration files.
Currently, the only way to retrieve device metadata seems to be
zigbee2mqtt/bridge/devices, but this topic returns a very large JSON payload (~9KB+ for just 3 devices) which is problematic for memory-constrained environments like PLCs or embedded systems with limited MQTT buffer sizes.Feature request:
Would it be possible to know how to achieve one of the following options ?
A lightweight device list topic : e.g.
zigbee2mqtt/bridge/devices/summarythat returns only essential fields per device:friendly_name,ieee_address,model,vendor,type— without the fulldefinition,endpoints,clusters, andconfigured_reportingsdetails.A per-device query : e.g. publishing to
zigbee2mqtt/bridge/request/device/infowith payload{"id": "<friendly_name_or_ieee>"}to retrieve metadata for a single device on demand, rather than fetching the entire device list.Either option would significantly reduce payload sizes and make Zigbee2MQTT much more accessible for resource-constrained MQTT clients.
Thank you for the great work on this project and thank you for your help!
Beta Was this translation helpful? Give feedback.
All reactions