Opentherm Gateway 4.0 alpha/beta testers wanted

[RedNax]

Hi Schelte,

Would it be possible to add an outside temperature offset? ie OO=-1.5 ? The placement of the dallas probe isn't optimal in my case and it allways reads the temp too high.

A minor thing, the new otmonitor lists the otm option for gba (however it doesn't allow you to actually choose it, which is correct).


RedNax

[Dickuk]

I have loaded the new otmonitor but when I select my new firmware file the 'Program' button is greyed out.

That was a bug. Try otmonitor 4.0b1.

Perfect, that's done the trick. Uploaded 4.0b0 of firmware now, so far all good.

[hvxl]

The specs say no valid response for 1 min. should be considered a communications fault. So I'm planning to go with that.

This has been implemented in the proposed way in firmware 4.0b1. With this firmware the gateway will also no longer reset itself repeatedly when the boiler is switched off (e.g. for maintenance). The communication failure detection isn't activated again until successful communication has been observed after the reset.

[Warwar]

Hi, hvxv.
How can one list Alternative Data ID stored in EEPROM?
How can one find out, what Alternative Data ID functon is active/worked?
I've setup AA=18, and got response "AA: 18".
I have Unk Msg with ID 128, which i suppose to use.
On "Log" tab i see messages with ID 128 as usual: T80800000 Read Data / B70800000 Unk-DataId
On "Statistics" tab i can't see messages with ID 18.
I want watch for the CH pressure, it can be displayed on thermostat by pressing corresponding key.

firmware: gateway-4.0b0.hex
otmonitor: otmonitor-4.0b0 / otmonitor-4.0b1 - the same

new features request:
cat you add "load dump" feature to the otmonitor? with timestamps will be perfect!
i want to save, for example, a day of boiler work and load it to otmonitor.
i was trying to do it with current version (released one) through socat - it works, but... first i tried to load whole file - time scale was terrible, otmonitor reads messages in realtime, for 9600 it's about 150 messages in a second (actually must be about 4 messages / second) - timescale about x40 faster - useless.
then i try to feed otmonitor 4 messages per second - time scale close to real, but it takes 24 hours for 24 hours dump! still useless...
in linux, i can add predefined format timestamp through minicom, i even can write "a programm" to write such "dump" file - it's easy, all i need - "load dump" function in otmonitor.

Thanks for your work.

[hvxl]

There is no command that lists the configured alternative data ID's. But you can infer them by looking for the messages prefixed with 'R' in the log. You can also test it using the DA command. If that returns NF, then the ID wasn't in the list. Of course, if it was in the list, the DA command has now removed it.

Due to space restrictions, only MsgID's below 128 are being tracked for boiler support. So, indeed MsgID 128 will never be replaced by the gateway. But there must be some MsgID's below 128 that the boiler doesn't process. Some boilers may simply acknowledge all messages instead of returning unknown for messages they don't support. In that case you can use the UI command to inform the gateway of MsgID's it doesn't need to send to the boiler. Good candidates are MsgID's 9, 16, 20, 24. Boilers don't normally have any use for the information in those messages.

What format dump file did you want to load in otmonitor and what do you expect to happen when it has been loaded? Normally otmonitor only keeps track of the last two hours of data. If your dump is older, otmonitor would forget everything immediately after reading the file. Or do you expect otmonitor not to consider the current time when loading a dump? In that case, if the file contains more than two hours worth of data, what should be shown? The last two hours? The first two hours?

[Warwar]

There is no command that lists the configured alternative data ID's. But you can infer them by looking for the messages prefixed with 'R' in the log. You can also test it using the DA command. If that returns NF, then the ID wasn't in the list. Of course, if it was in the list, the DA command has now removed it.

Due to space restrictions, only MsgID's below 128 are being tracked for boiler support. So, indeed MsgID 128 will never be replaced by the gateway. But there must be some MsgID's below 128 that the boiler doesn't process. Some boilers may simply acknowledge all messages instead of returning unknown for messages they don't support. In that case you can use the UI command to inform the gateway of MsgID's it doesn't need to send to the boiler. Good candidates are MsgID's 9, 16, 20, 24. Boilers don't normally have any use for the information in those messages.

i see...
i don't see any messages prefixed with 'R', and now i know why.
ID 9 - thermostat doesn't send request for it
ID 16 - well, actually, boiler responds for this message, but i don't know how this information may be used by boiler, maybe as for ID 24 (i don't know at this moment if boiler can show room setpoint at it's display)
ID 20 - the same as ID 9
ID 24 - boiler responds for this message, and it can be used by boiler to show room temperature at boiler's display

What format dump file did you want to load in otmonitor and what do you expect to happen when it has been loaded? Normally otmonitor only keeps track of the last two hours of data. If your dump is older, otmonitor would forget everything immediately after reading the file. Or do you expect otmonitor not to consider the current time when loading a dump? In that case, if the file contains more than two hours worth of data, what should be shown? The last two hours? The first two hours?

i'm expecting otmonitor to show/navigate me 24 hours of data. is it possible? after some patching, of course.
about timestamp format
simplest form is `date +%s.%N` - like 1387251888.153641352 (seconds since 1970-01-01 00:00:00 UTC and nanoseconds)
just a bit 'human readable' - 'date +%Y%m%d-%H%M%S.%N' - like 20131217-074805.135096813
second will be prefer.

[Warwar]

In that case you can use the UI command to inform the gateway of MsgID's it doesn't need to send to the boiler.

Could you give description/show how to use "UI" and "KI" commands, because i don't seen it on home page of "alpha/beta fw" on OTGW site.
And how to delete IDs inserted with UI or KI commands?

[Warwar]

Well... It's a *magic*!
i suppose... UI - marks message as been used for get additional info from boiler, KI - "unmarks"...
AA adds some messages, i want to get report to...
as i see, OTGW want to know some infos by itself, it's send some message it thinks bouiler can support... so, next questions:
- can you provide message IDs OTGW is searched for if it has "timeslot" (enabled/blacklisted messages through UI or natively researched Unk IDs)?
- can i force OTGW not to research supported messages by itself, but only which ones i specified through AA?
- my thermostat have buildin "clock" - time & day of the week, which it uses for timesheduling. my boiler does not have any clock at all (it responds UnkID to the message 20, sent by OTGW). So tell me if i'm wrong: there is no possibility in OpenThern spec to force message being send from slave (boiler) to the master (thermostat)? i just want to syncronise time/date through OTGW to thermostat, but if it's not reqesting time/date, one can't force to do it...

[Warwar]

sorry for posting too many messages, i can't edit messages, which was not approved by moderator yet...
i guess it's not only my "Problem"...
about "as i see, OTGW want to know some infos by itself, it's send some message it thinks bouiler can support..." - i was wrong, sorry...
i'm set too many messages with 'AA' command and forget which i was set sorry, ti's my fault...
i'm using message ID 16 now to get a message 18 (CH water pressure).
it's seems like OTGW works perfect!
i was exploring some other messages - most of them unsupported by boiler.
next i want to monitor starting of communication between thermostat & boiler, then send you logs, at last...
and i want to press thermostat keys and watch messages through OTGW.
Now i can say Ferroli Romeo W by default send commands with ID: 0, 1, 3, 5, 10, 12, 16, 17, 24, 25, 26, 27, 48, 49, 56, 57 and 128.
Boiler Ferroli Pegasus D responds with useful data to all thermostat commands mentioned above, except ID 128, which is Unk ID.
In addition, boiler support next commands: 6, 11, 13, 18, 120, 121.
Messages related to cooling and 2nd CH i did not test, because boiler does not have any.

So i have next question, sorry...
how can i read data from ID 11, 13? Just for interest.
It's "iterator" messages, you should increment an index and send request a few times. Does it in your "todo" list?
In common, it's will be helpful, if one can send any command to boiler by providing all 4 bytes in a row.

[hvxl]

my thermostat have buildin "clock" - time & day of the week, which it uses for timesheduling. my boiler does not have any clock at all (it responds UnkID to the message 20, sent by OTGW). So tell me if i'm wrong: there is no possibility in OpenThern spec to force message being send from slave (boiler) to the master (thermostat)? i just want to syncronise time/date through OTGW to thermostat, but if it's not reqesting time/date, one can't force to do it...

The thermostat is the master, so it decides which messages it will send. The slave can only respond to the requests, but can not influence which message ID's will be exchanged.

[Warwar]

For long term statistics i decided to use rrdtool, so if no one needs "load dump" feature ... skip it.
Sill interested in sending random messages to boiler by specifying all 4 bytes.

[sappien]

I've got a problem with the setpoint setting. When I send a TT= to the gateway, the setpoint is correctly adjusted. But after 30/40 minutes the iSense restores the setpoint.
(iSense program is 07:00 21C - 21:00 15C) (using OTC+Eco mode setting)

14:00 i've send TT=15
14:40 Setpoint is set back to 19

[Warwar]

In addition...
hvxl, if you implement sending random command through com/usb interface to boiler AND implement one else OTGW mode, then OTGW can cut off thermostat line and act as thermostat by itself, gatewaying messages from com/usb to boiler. Then it will be possible to do something like "soft thermostat of your dream"
And, at the end, there wiil be no need to buy "HW" thermostat, just OTGW!
I like this idea!

upd: as read from other thread "Opentherm Gateway", if i disconnect thermostat from OTGW, then OTGW already wiil be acting like thermostat. But it's not so easy, as set "GW=2", for example. especially if you far away from thermostat, OTGW and boiler.

[hvxl]

I've got a problem with the setpoint setting. When I send a TT= to the gateway, the setpoint is correctly adjusted. But after 30/40 minutes the iSense restores the setpoint.
(iSense program is 07:00 21C - 21:00 15C) (using OTC+Eco mode setting)

14:00 i've send TT=15
14:40 Setpoint is set back to 19

The 19 degrees didn't come from the thermostat schedule or a serial command to the gateway. Maybe someone manually adjusted the setpoint on the thermostat? Do you have a log?

[hvxl]

as read from other thread "Opentherm Gateway", if i disconnect thermostat from OTGW, then OTGW already wiil be acting like thermostat. But it's not so easy, as set "GW=2", for example. especially if you far away from thermostat, OTGW and boiler.

I expect people will either want to use the gateway with or without a thermostat all the time. Remotely disconnecting the thermostat when you're far away doesn't sound like a common use-case to me. Furthermore it's already possible to take over control of the boiler from the connected thermostat by overriding the control commands the thermostat sends (using the CS and MM commands).

If your aim is to use the gateway as a simple opentherm to serial converter, it makes more sense to do that with dedicated firmware rather than trying to cram that function into the very limited remaining space left in the current firmware.