MQTTShims setup - feel really dump right now

[roquej]

I got Home Assistant devices publishing to MQTT and Indigo devices publishing to MQTT. I can access and create interactions with all those devices using with Node-Red. However, for the life of me, can't get MQTTShims to work. The first image is the MQTT Explorer with the topic I want to use with MQTTShims.

The process I attempted, with the images in sequence, was:

- Configured the broker with the Topic Subscription
- Configure the trigger
- Configure the device

I am sure is something simple, but as I said, it's just not working for me. Please, any suggestions would be appreciated.

JP

[FlyingDiver]

MQTT Explorer is messing with you.

The topic for the pool temperature is: homeassistant/sensor/pool_temp/state
And it's a raw payload type.

Your subscription is fine.

Your Component Match is wrong because you're not accounting for the "state" component after the unique ID. Add a "state" term before the end term.

Your Unique ID location is correct as "Topic", but the value is 2 not 12. It's the third component in the topic string, and it's a zero-based count.

The State Value Location is Payload, not Topic. And it's a RAW payload (not JSON).

I think that's all.

[roquej]

Thank you for the quick response.

I got the Component Match fixed with your suggestion. However, I still can't get the device to work. is the "Unique Value ID" correct the way I have it? That is the only thing that you didn't mention.

Thank you again.

JP

[roquej]

My system is afraid of you! No sooner I had sent the post, it started working.

Thank you!!

JP

[FlyingDiver]

I am the MQTT Whisperer.

[roquej]

Sir MQTT Whisperer, another quick question.

I have configured an MQTT switch device. It all seems to work, except that the on/off is erratic when the topic is updated by another system. The topic changes and it works, sometimes.

Any way to make this more reliable?

JP

[FlyingDiver]

You need to make sure you're updating the state of the shim based on the status update from the device, NOT the command sent to it. I'd have to see all the traffic to/from that device to be more specific.