search

hvxl / otmonitor

Monitor tool for the OTGW (http://otgw.tclcode.com/)
GNU Lesser General Public License v3.0
27 stars 10 forks source link

duplication of MQTT messages #11

Closed antst closed 3 years ago

antst commented 3 years ago

If you override things like chenable or controlsetpoint (by ctrlsetpt) it results in 2 messages send in MQTT, one for what thermostat sends, and one for what otgw sends to boiler. Example. 

18:45:28.825097  T10010A00  Write-Data  Control setpoint: 10.00
18:45:28.831854  R90013700  Write-Data  Control setpoint: 55.00
18:45:29.185726  B50013700  Write-Ack   Control setpoint: 55.00
18:45:29.186737  AD0010A00  Write-Ack   Control setpoint: 10.00

results in 

events/central_heating/otmonitor/controlsetpoint 10.00
events/central_heating/otmonitor/controlsetpoint 55.00

It is VERY annoying. And confuses any automation which is based on those topics.

I think everything which might be overridden should have two separate MQTT topics, one for what come to OTGW, and one for what goes further.

hvxl commented 3 years ago

This seems a repeat of issue #7. You still don't indicate at what time the MQTT events happen.

OTmonitor delays change reports for 50ms in case the message is changed by the OTGW. Your OT messages arrive less than 7ms apart. So only the second one will be reported.

Which version of OTmonitor are you using?

hvxl commented 3 years ago

Any follow-up on this issue? Otherwise I will close it again.

hvxl commented 3 years ago

No response (again) from reporter.