Home Automation Domotica Forum Europe, Bwired Forum

hvxl wrote:You know you can click on a point of interest in the graph and get a tooltip with the time and value of the parameter?

Thanks, I will try

hvxl wrote:You keep mentioning what kind of boiler you have, but whether it's possible to override the temperature setting depends on the thermostat. Which one do you use?

Appologies, thought the boiler was leading... I am using the Bosch TF30 as thermostat.

According to the equipment matrix, the TF30 never asks for a setpoint override (MsgID 9). So, unless it has some setting to enable it, the gateway won't be able to override the setpoint on that thermostat.

hvxl wrote:According to the equipment matrix, the TF30 never asks for a setpoint override (MsgID 9).

Starting to learn more and more. Did not realise the thermostat was leading, not the boiler. So that means that the gateway mode is useless for this thermostat and monitor mode is what I should use (monitor is also not reporting the Error 01 errors)?

OTGvis wrote:So that means that the gateway mode is useless for this thermostat and monitor mode is what I should use (monitor is also not reporting the Error 01 errors)?

It doesn't mean that at all. Even if your thermostat doesn't support remote setpoint override, gateway mode still allows you to do other things, like:

• Override the hot water option and other settings of your boiler
• Provide the outside temperature to your thermostat
• Obtain additional information from your boiler

None of that is possible in monitor mode.

Also, both modes use the same routines to decode the opentherm signal, so any difference you think you observe in the number of errors reported is either due to something else (e.g.: IT=1 vs IT=0) or superstition.

Chriskras wrote:I have this error on my pc with windows xp

Does your USERNAME environment variable not match a real user on your system?
I put some improvements for this in otmonitor 4.0b4.

Hi,

Yesterday i upgraded the firmware to 4.0b1 because with the stable version i got error 01 and 03 sometimes, but now the following happends:
at first it was during a very long time and a lot of error 03 codes before the OTGW was working.
When it was working it all looked ok, and i could change the temp. with the otgateway tool, so i left it for the night.

When i awake the day after the connection between my wireless thermostat and OTGW was lost. Also there where error 03 codes again.

I use the OTGW with at one side a remeha tzerra M24C boiler and at thermostat side the Honeywell Opentherm RF module (type: R8810A1018) which is connected wirelessly to the Honeywell Round Wireless (type: T87RF1003)

With the stable firmware it was working ok, but the temp. change could take up to half an hour or so. The beta version seems to be working faster, untill now when i got error03 errors after one night.
yesterday at around 22hour everything was ok with beta firmware, but around 04:00 today the thermostat was stopping working because the connection was lost for some weird reason.

Known problem?


Edit: now i downgraded to the stable version again, this seems to go better, but the error 01 and 03 are back again, also it is taking a long time when i set a new temperature before it gets to the thermostat. mostly i need to send it more then once to get it working.

Why did you upgrade to 4.0b1 instead of the latest 4.0 beta version (4.0b3)?

Which version of otmonitor did you use to upgrade? If you didn't use a 4.0 beta version of the application, your settings will not have been preserved during the upgrade.

On which side do you see the errors? If it's on the thermostat side, you may have lost the voltage reference adjustment with the upgrade. That would also explain why you still see the errors after downgrading again.

Because updating of the temprature was taking a long time. So i thought lets upgrade. Also i got a lot of error 01 and 03 messages with the latest stable version.
I would try to upgrade to the latest firmware in some days from now, you say that when i adjust the Voltage Reference my erros will be gone? How do i know what i need to set there?

Thanks!

That's not what I said at all. Your story suggested that you got more errors after you upgraded, and they stayed even when you downgraded again. I was only offering a possible reason for that. To be able to better diagnose what is going on I need more information, which is why I asked some questions.

Which version of otmonitor did you use to upgrade? If you didn't use a 4.0 beta version of the application, your settings will not have been preserved during the upgrade.
It was the latest stable one, so not a beta.

On which side do you see the errors?
On the thermostat side.

In my experience the opentherm signal from Honeywell thermostats is well within the specifications. So if you see errors from the thermostat side, that may well be correctable by tuning the VR setting. Any tweaks you did on the old firmware will have been lost by the upgrade you did.

Started using 4.0b3 firmware and noticed the DHW SetPoint is always 0, while firmware 3.4 reported the correct DHW SetPoint.

Using:
Honeywell Chronotherm Vision Modulation
EMS-OT converter
Nefit Smartline HRC24/CW4

Did you happen to pull the plug of the gateway to reset it at the start of the upgrade process? That will also have powered off the thermostat. At startup the thermostat checks whether the boiler supports the DHW setpoint message via the Remote-parameter transfer-enable flags message. Normally the gateway will simulate at least read support, but during a firmware upgrade the thermostat talks directly to the boiler or, in your case, the EMS-OT converter. According to the equipment matrix the EMS-OT converter doesn't support the DHW Setpoint message, so it may have indicated that to the thermostat. The thermostat then probably refrains from requesting that information. This can be fixed by resetting the thermostat once more, either by pulling the plug on the gateway again, or by temporarily disconnecting the thermostat.

Note: Since the EMS-OT converter doesn't actually support the DHW Setpoint message, you will only get a virtual value at best (whatever you specified with the SW command, or the gateway's default value of 80).

I have just published firmware version 4.0b4 for the opentherm gateway. In addition to a number of fixes, it has the following new features:

• New CH command to control the central heating enable status bit when the control setpoint is manipulated by serial commands.
• New PM command to specify a one-time priority message to be sent to the
  boiler at the first opportunity.
• The PM command can also be used to retrieve Transparent Slave Parameters and Fault History Buffers from the boiler.
• When the boiler indicates a problem, the gateway will ask for details if the thermostat doesn't.
• When an on/off thermostat generates a heat demand, the gateway will use the setpoint set with the SH command, if available.

Hopefully this will be the final beta before I release 4.0, so please report any issues you encounter with it.