Hi,
I have installed configured a NoDo Opentherm (latest firmware) which works fine.
Used to Otmonitor application (windows) and I can read out / set all the parameters I Need and the graphs are showing the right info.
Now I configured in domoticz :
OpenTherm GateWay with LAN interface Version: 6.3 Setup
So far so good the logging is transferred into domoticz
The problem is now that there's np logging anymore visible in otmonitor
Am I doing something wrong?
Do I have to change the operating mode
I have a Heating Elcoo Thison25 + Siemens QAA73 thermostat
by the way, what is the diffrence between a QAA73 Siemens QAA73 and a Siemens QAA73.210
How Can I check what is used here at home?
It does do some logging, which looks like :
12:25:20.255794 00010000/00100000,...
12:25:49.973774 SC: 12:19/4
12:25:50.222313 PR: G=00
12:25:50.224388 PR: I=11
12:25:50.227103 PR: O=N
12:25:50.228196 PS: 1
12:25:50.229125 00010000/00100000,...
Domoticz
Version: 2022.2 (build 14792)
Build Hash: d8c71540c
Compile Date: 2022-12-02 14:00:20
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Oct 31 2022, 14:04:00) [GCC 8.3.0]
otmonitor stops graph logging combined with domoticz
Moderator: hvxl
Re: otmonitor stops graph logging combined with domoticz
Disclaimer: I don't use domoticz myself, so the information below may not be completely accurate.
The basic domoticz OTGW binding uses the PS=1 command to obtain information from the OTGW. This command stops the normal reporting of opentherm messages. As a result, otmonitor no longer receives the information it uses for logging and creating the graph.
If you have the WiFi enabled OTGW from the Nodo shop, you can install rvdbreemen's OTGW-firmware onto the Wemos D1 mini and have it publish MQTT messages. Then use a domoticz plugin for the OTGW integration, instead of the classic OTGW binding. This alternative OTGW integration doesn't use the PS=1 command, so the graph in OTmonitor will continue to be updated.
The basic domoticz OTGW binding uses the PS=1 command to obtain information from the OTGW. This command stops the normal reporting of opentherm messages. As a result, otmonitor no longer receives the information it uses for logging and creating the graph.
If you have the WiFi enabled OTGW from the Nodo shop, you can install rvdbreemen's OTGW-firmware onto the Wemos D1 mini and have it publish MQTT messages. Then use a domoticz plugin for the OTGW integration, instead of the classic OTGW binding. This alternative OTGW integration doesn't use the PS=1 command, so the graph in OTmonitor will continue to be updated.
Schelte