Hi,
I have a number of Homeseer managed devices that I also need to control via an external management server (that supports mqtt). The external server needs to know about status changes that are initiated by Homeseer for those devices as well. With that, I've set up this (excellent!) plugin to facilitate, and it's working very well.
The only side effect of this configuration is that mcsMQTT effectively echoes back to the publish topic (which the external server is subscribed to) device status changes that are received from the external server. While the external server does use mySQL to track device change events, fortunately it does not add another entry to the DB if the device status hasn't actually changed from it's last known state, so there's no major issue at this point... just some redundant traffic.
I've chosen to configure mcsMQTT devices and the external server devices to use the same topic for both subscribe and publish. Is there a way to prevent publishing device status changes if received from a topic, when the same topic is used for publishing? Alternatively, can a global (or per device) configuration option be added to only publish device changes that are initiated by Homeseer (vs. received from a subscribed topic)? Or is there some other option that I should consider?
I'm more curious than anything, nothing at all urgent here. As mentioned, everything works great and does what I need. And thanks very much for mcsMQTT... it really is excellent!
I have a number of Homeseer managed devices that I also need to control via an external management server (that supports mqtt). The external server needs to know about status changes that are initiated by Homeseer for those devices as well. With that, I've set up this (excellent!) plugin to facilitate, and it's working very well.
The only side effect of this configuration is that mcsMQTT effectively echoes back to the publish topic (which the external server is subscribed to) device status changes that are received from the external server. While the external server does use mySQL to track device change events, fortunately it does not add another entry to the DB if the device status hasn't actually changed from it's last known state, so there's no major issue at this point... just some redundant traffic.
I've chosen to configure mcsMQTT devices and the external server devices to use the same topic for both subscribe and publish. Is there a way to prevent publishing device status changes if received from a topic, when the same topic is used for publishing? Alternatively, can a global (or per device) configuration option be added to only publish device changes that are initiated by Homeseer (vs. received from a subscribed topic)? Or is there some other option that I should consider?
I'm more curious than anything, nothing at all urgent here. As mentioned, everything works great and does what I need. And thanks very much for mcsMQTT... it really is excellent!
Comment