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
Is your feature request related to a problem? Please describe.
The Dev console cannot be used to arbitrarly probe a device, leading to:
Unbelievable epic failure to support a device while THE MANUFACTURER PROVIDED THE FULL REGISTER MAPPING (in the manual!!) because this person couldn't probe their device in order to build an understanding of how specific parameters work. Note they were motivated enough to write 2 long posts and follow up.
Community effort is prevented by the virtual limitation to the predefined list of clusters and attributes. (that isn't even on par with what the converter is exposing!) It's too bad.
Describe the solution you'd like
Let us input endpoint, cluster ID, attribute ID and r/w arbitrary value.
Additional context
Edit Removed all the "can't do it" stuff because yes you can, through MQTT. For anyone finding this while searching: the command is sent via MQTT BUT the result is in the log, it isn't published!
The text was updated successfully, but these errors were encountered:
toine512
changed the title
Dev console: Please allow inputing endpoint/cluster/attribute (the Dev console is useless / virtual limitations are aweful)
Dev console: Please allow inputing endpoint/cluster/attribute (the Dev console is useless)
Jan 7, 2025
Is your feature request related to a problem? Please describe.
The Dev console cannot be used to arbitrarly probe a device, leading to:
Unbelievable epic failure to support a device while THE MANUFACTURER PROVIDED THE FULL REGISTER MAPPING (in the manual!!) because this person couldn't probe their device in order to build an understanding of how specific parameters work. Note they were motivated enough to write 2 long posts and follow up.
Exploitation of network capture going nowhere. (2 upvotes)
People as clueless as I am: Reddit - How can I send a low-level Zigbee command using the zigbee2mqtt dev console?
Maybe the Dev console can do what I want, but nobody knows.
Community effort is prevented by the virtual limitation to the predefined list of clusters and attributes. (that isn't even on par with what the converter is exposing!) It's too bad.
Describe the solution you'd like
Let us input endpoint, cluster ID, attribute ID and r/w arbitrary value.
Describe alternatives you've considered
It can be done with a MQTT client https://www.zigbee2mqtt.io/guide/usage/mqtt_topics_and_messages.html#directly-reading-writing-zcl-attributes
Additional context
Edit Removed all the "can't do it" stuff because yes you can, through MQTT. For anyone finding this while searching: the command is sent via MQTT BUT the result is in the log, it isn't published!
The text was updated successfully, but these errors were encountered: