This is likely more work than we should probably expect from a plugin, and maybe better as a more native indigo functionality, however, thought I would throw this out for discussion.
With the great work you have done on the shims templates for the zigbee2mqtt devices the ideal end goal would be an automated discovery of devices reported by zigbee2mqtt over mqtt.
I see this sort of functionality has been built into homeassistant, based on presumably standard templates.
The zigbee2mqtt even outputs standard messages for each of the zigbee devices into the various types.
Lights for instance report
- Code: Select all
{"availability":[{"topic":"zigbee2mqtt/bridge/state"},{"topic":"zigbee2mqtt/HueBulb/Hall/availability"}],
"brightness":true,
"brightness_scale":254,
"color_temp":true,
"command_topic":"zigbee2mqtt/HueBulb/Hall/set",
"device":{"identifiers":["zigbee2mqtt_0x00158d0004f86f25"],
"manufacturer":"Innr","model":"E27 bulb RGBW (RB 285 C)","name":"HueBulb/Hall","sw_version":"Zigbee2MQTT 1.16.1"},
"hs":true,
"json_attributes_topic":"zigbee2mqtt/HueBulb/Hall",
"name":"HueBulb/Hall_light",
"schema":"json",
"state_topic":"zigbee2mqtt/HueBulb/Hall",
"unique_id":"0x00158d0004f86f25_light_zigbee2mqtt",
"xy":true}
Sensors are broken into the various types
Using this strcuture and the Shims templates, it should be possible to simplify, and even automate creation, of indigo Shims devices?
What do you think?