Releases, Bugs, Issues, Requests

OK, that's fixed for next release.

Using Release 0.2.5

When I press the Status Request button in the Indigo UI for my innr plugs, I get this response"

zigbee2mqtt:error 2020-02-24 18:07:40: Publish 'set' 'state' to 'innr_plug_1' failed: 'Error: Cluster 'genOnOff' has no command '''
zigbee2mqtt:info 2020-02-24 18:07:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'innr_plug_1' failed: 'Error: Cluster 'genOnOff' has no command '''","meta":{"friendly_name":"innr_plug_1"}}'
zigbee2mqtt:error 2020-02-24 18:08:20: Publish 'set' 'state' to 'innr_plug_1' failed: 'Error: Cluster 'genOnOff' has no command '''
zigbee2mqtt:info 2020-02-24 18:08:20: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"zigbee_publish_error","message":"Publish 'set' 'state' to 'innr_plug_1' failed: 'Error: Cluster 'genOnOff' has no command '''","meta":{"friendly_name":"innr_plug_1"}}'

The format of a Send Status Command is:

• Topic: zigbee2mqtt/device_name/get
• Payload: { "state": ""}

as tested by sending a direct message and as per the documentation here.

Would it be an idea to be able to specify a template for this command?

Apologies for adding to the list.

Yeah, that needs to be changed to a template. Or take out entirely.

Pre-release 0.2.6: https://github.com/FlyingDiver/Indigo-S ... /tag/0.2.6

Added templates for status requests

That's going to be the last feature add for a while. I'm leaving Friday for most of a month, so I'm only doing bug fixes between now and then. Please open a GitHub issue for anything other than a high priority bug fix.

Installed Release 0.2.6 and tested out the Status Request template.

It is all working as expected - Thank you.

Release 0.2.7 - https://github.com/FlyingDiver/Indigo-S ... /tag/0.2.7

Now supports toggle actions (again).
Misc bug fixes.

First release with device Template support.

Hi Joe,
Thanks for the update and adding Toggle - very useful.

With regard to templates, a couple of questions:

1. How do you select/use a template?
2. Are you collecting template definitions if users create them for new devices?

I see that there is a Templates folder in the plugin's Server Plugin folder with example templates.

If I have missed how to do this, can you point me in the right direction - Thanks.

I haven't gotten around to documenting the Templates yet. I pushed that update out early because of the Toggle action.

Yes, I'll be collecting templates to include in the plugin. Probably should just post them in the thread about the Templates.

There's two menu commands under the MQTT Shims plugin. One writes template data to the log, based on an existing Shim device. The other creates a new Shim device from a specified template.

There's also a field in the Plugin config dialog to specify which folder (under the Indigo base install directory) you want searched for personal templates.

So, short form is:

1. Write out template data to log using menu command
2. Create template file from that data, editing as necessary.
3. Repeat for additional device types
4. Use menu command to create new Shim devices from a template. You need to specify the unique-identifier for that particular device, and which Broker device it's associated with.
5. The plugin will also create a trigger for the device, based on the template data, if requested and needed. If a trigger already exists for the message_type specified in the template, a new trigger will not be created.

Hi, thanks for the awesome MQTT plugins.

Using MQTT Connector v. 0.4.0, I am not seeing an "End" option when setting up a Topic Component Match trigger:

Skjermbilde 2020-04-22 kl. 10.20.35.png (194.56 KiB) Viewed 1668 times

Topic Complete is End.
Choose it in "Match Type:" and "Add Match"

Great, thanks!