Thank you! I had seen that example before – but wasn’t sure how to use it since I had the MQTT publishing “device” installed and didn’t have the temperature device.
I get it now, and after hydrating a virtual “mqtt temperature” device, I was able to use the exact rule text to call the setvTemp command and publish the update, which I have confirmed using MQTTX as a subscriber.
So, note to others who find this (and I didn’t even after reviewing all the threads / topics), you need to create a new virtual/child device using the mqtt parent first, plus create a matching copy for every one of the temperatures you want to publish to mqtt (our house has 8 or so). I’ll create a virtual “room” for them to hide them away.
Thanks again. Would have been nice to have a single mqtt bridge device, but I get it now based on what you said, the types cannot be converted in the rules engine.
The MQTT Devices driver crashes if a numeric value NaN is received via MQTT.
My RPi Python program sends the temperature values using MQTT to the ST Hub.
From the source of the temperature values became a NaN value
and the Python program sent it with the MQTT Retain flag.
This caused the driver to crash constantly. The driver received a NaN value as a response immediately after driver started and started to update MQTT topics’ values.
Figuring out the fault was really challenging because the situation looked like a network failure.