This could be related to how you have the associations setup.
If you mapped a Topic received into an existing HS device then the plugin uses CAPI to try to control the device. The pluign that owns the device is then responsible for setting Devicevalue and DeviceString. Since mcsMQTT does not know how a plugin setup its CAPI interface it does a search using some criteria. There is debug output when debug is enabled to help understand the CAPI setup for the target plugin. It seems that two now are using the Zwave plugin with mcsMQTT. I do not have Zwave so need to work with somebody and that is the purpose of the debug.
If you mapped a Topic into a mcsMQTT device then mcsMQTT will set the DeviceValue if the Payload is a number or it will set the DeviceString with the payload. It has special cases of case-insensitive ON, OFF, OPEN, CLOSE that it maps into 1 and 0 and updates the DeviceValue.
If you mapped a Topic received into an existing HS device then the plugin uses CAPI to try to control the device. The pluign that owns the device is then responsible for setting Devicevalue and DeviceString. Since mcsMQTT does not know how a plugin setup its CAPI interface it does a search using some criteria. There is debug output when debug is enabled to help understand the CAPI setup for the target plugin. It seems that two now are using the Zwave plugin with mcsMQTT. I do not have Zwave so need to work with somebody and that is the purpose of the debug.
If you mapped a Topic into a mcsMQTT device then mcsMQTT will set the DeviceValue if the Payload is a number or it will set the DeviceString with the payload. It has special cases of case-insensitive ON, OFF, OPEN, CLOSE that it maps into 1 and 0 and updates the DeviceValue.
Comment