Introducing the Shims plugin

Hi, I am new to MQTT and struggling to get my first device setup in Shims.

Its an Aqara temp and humidity sensor and it publishes its payload like the attached from MQTT explorer , and I have set up my Shims device as per attached.

The broker devices shows its receiving the message but the Shims device is not updating. Is this to do with the format of the JSON, or likely my setup of the device.

Any pointers would be appreciated.

Thanks

Simon .

"Master" is the third field in the topic, so you need to change the "Topic Field" to 2.

If that still doesn't work, make sure you've got a trigger set up for that topic.

Cheers.. had tried 2 as well, and just changed to that, but no luck.

The trigger bit was where I was most confused. Yes I have one setup, but not entirely sure its correct. I only have trigger, no action set. I think thats correct? I have tried lots of combinations of Match strings here.

Your topic is 'zigbee2mqtt/Aqara/Master'. So you need:

Code: Select all

Match:  zigbee2mqtt
Match:  Aqara
Any:   
End:


You need a term in the list for each component of the topic, left to right --> top to bottom. Except you can skip trailing topic components using the 'End:' term.

Thanks... still no joy. How do I enter the End: terms. I only see Match or Any in the drop down?

Thanks... still no joy. How do I enter the End: terms. I only see Match or Any in the drop down?

Oops. That version was in pre-release state. I just updated the release version.

I dont see the End: option on the 0.1.3 version I just downloaded, but regardless , I have this working now.

Thanks, another amazing contribution the the Indigo world.

I now have a zigbee temp and humidity sensor reporting into Indigo via a zigbee USB stick on a Pi, talking to my MQTT broker on my NAS, to Indigo on the Mac, and reports in the blink of an eye!

I'll get a full write up done soon as this is a really easy (once you understand MQTT and Shims) setup that gives access to a new range of cheap sensors.

I dont see the End: option on the 0.1.3 version I just downloaded.

I think you want to update the MQTT Connector Plugin to 0.3.2 to get the update for the “End” Completion.

Good point, all working now.

What I dont seem to be able to work out is how to do the multi states, as it doesnt appear I have a dict in the payload json? Or is my lack of python knowledge showing?

Good point, all working now.

What I dont seem to be able to work out is how to do the multi states, as it doesnt appear I have a dict in the payload json? Or is my lack of python knowledge showing?

If there isn't a nested dict, then you can't do multi-states. There is an edge case where it might be useful to do multi-states with the top-level dict, but I didn't code it that way originally. I should do that one of these days.

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

Adds battery level support in Indigo UI
Adds multi-states support to all device types
Adds support for multi-states key at top level of message payload

If the payload looks like this:

Code: Select all

{ "battery":100, "voltage":3145, "temperature":24.95, "humidity":38.72, "pressure":1012, "linkquality":36}


Then putting a period (".") in the multi-states field will give you:

Awesome.. that works!

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

Added generic device (no state value).

Added capability to show energy usage in Indigo UI.
Energy UI (and now battery UI) are available for JSON payloads only.

Added info level logging of sent actions.

I have this working now.

May I ask how you got it to work? I believe I have set up Broker device, trigger and sensor devices correctly, but the sensor devices are not updating.

edit: Found it! I had a typo in the Topic Subscriptions settings of the Broker device

Controlling sonoff device (tasmota), works fine.

But the device status in Indigo UI is not changing (always staying "off") and the last update is always "2000-01-01 00:00"

What I'm doing wrong?