Firmware version 4.0 has been released.

Post by **mike7** » Sun Jun 22, 2014 8:47 pm

hvxl wrote:The type of the value is always the same for a particular parameter, so it's a waste of bandwidth to transmit that information every time (I understand MQTT was designed to keep the messages small). But obviously JSON isn't the most appropriate format if bandwidth is a consideration. So I've added two more JSON formats to otmonitor 4.1b1.

Small messages are for not powerful platform to save energy and cpu, for example for gateway itself. Thank you for more formats, will test.

hvxl wrote:Re: Prefix for the topic: I'm not sure that's allowed. The DomoMQTT specification says "The events topic has the following format: events/device_type/device_id/property".

Currently it's not actual for me, but we can expand the standard a bit, prefix can be empty

.

hvxl wrote:I don't understand what you are trying to say regarding the unprocessed messages and using http interface for command. If you want me to change something there, please explain a bit more.

I just want to get messages in the following form:
T00110000
BC0110000
T9014A73B
R80190000
B40191B00
T80001300

otmonitor is processing messages very well, but other applications can use messages from gateway for additional processing, for ex. if chsetpoint is overwritten. That topic should be not persistent.

About http command interface, I just use it and I don't need mqtt interface for it. With "http get" request I have got report in transactional way in time of request.

Thank you very much, I can't expect such high level of support.

Post by **sincze** » Thu Jun 26, 2014 1:22 pm

Would it be possible to add "http://cmdirect.nl/nl/registreren" as an SMS Gateway as well to the OpenTherm Monitor?

Connection can be made via

HTTP GET

example: https://secure.cm.nl/smssgateway/cm/gat ... My+company

or POST,

HTTPS://secure.cm.nl/smssgateway/cm/gateway.ashx

<?xml version="1.0"?>
<MESSAGES>
<AUTHENTICATION>
<PRODUCTTOKEN>de7c7df3-81ca-4d1e-863d-95a252120321</PRODUCTTOKEN>
</AUTHENTICATION>
<MSG>
<FROM>My company</FROM>
<TO>+31600000000</TO>
<BODY>Example message text</BODY>
</MSG>
</MESSAGES>

So seems not that dificult.

And If you register with "Bedrijfsnaam" OTGW you'll receive 100 free text messages.

Sandor

Post by **hvxl** » Sat Jun 28, 2014 4:34 pm

sincze wrote:Would it be possible to add "http://cmdirect.nl/nl/registreren" as an SMS Gateway as well to the OpenTherm Monitor?

This has been added to otmonitor 4.1b2. I have not fully tested it because I couldn't find any information on how they may (ab)use the mobile phone numbers they receive through this service, so I was hesitant to provide mine.

Post by **mike7** » Sun Jun 29, 2014 1:48 pm

Schelte,

thank you for the "Message" mqtt topic. Now I have a what to do on my vacation

Post by **Dickuk** » Mon Jun 30, 2014 3:48 pm

Hi Schelte,

A while back you added the functionality to retain the ignored commands during an upgrade using otmonitor, mine were put in so long ago that I can't remember what ones are in there !

Is there any chance of having the otmonitor software report these to the screen or a logfile after/during the upgrade process as I presume it must read them in to put them into the new software?

Thanks and keep up the good work !

Richard

Post by **mike7** » Mon Jun 30, 2014 8:48 pm

Schelte,

"GatewayReset" signal doesn't rise after GW=R command.

Post by **hvxl** » Mon Jun 30, 2014 9:49 pm

mike7 wrote:"GatewayReset" signal doesn't rise after GW=R command.

It does, except when you have the data format set to "Standard JSON". Will fix that.

mqtt.patch.zip: Patch; (434 Bytes) Downloaded 375 times

Post by **mike7** » Wed Jul 02, 2014 6:26 am

Schelte,

I can't to set working configuration with SR, UI pairs for ids 48 and 49, I've got "Unk-DataId" response:

Code: Select all

07:57:35.606245  Command (via websocket from 192.168.7.24:50156): PR=A
07:57:35.644649  PR: A=OpenTherm Gateway 4.0.1

07:57:53.396780  Command (via websocket from 192.168.7.24:50156): SR=48:65,35
07:57:53.425729  SR: 48:65/35

07:57:55.830245  T00300000  Read-Data   DHW setpoint boundaries: 0 0
07:57:56.006625  B40304123  Read-Ack    DHW setpoint boundaries: 65 35

07:58:00.831687  T80310000  Read-Data   Max CH setpoint boundaries: 0 0
07:58:01.014204  B4031551E  Read-Ack    Max CH setpoint boundaries: 85 30

07:58:14.584192  Command (via websocket from 192.168.7.24:50156): UI=48
07:58:14.599679  UI: 48

07:58:55.832924  T00300000  Read-Data   DHW setpoint boundaries: 0 0
07:58:55.858676  R80190000  Read-Data   Boiler water temperature: 0.00
07:58:56.013932  B40194200  Read-Ack    Boiler water temperature: 66.00
07:58:56.044430  AF0300000  Unk-DataId  DHW setpoint boundaries: 0 0

07:59:00.832772  T80310000  Read-Data   Max CH setpoint boundaries: 0 0
07:59:01.001270  B4031551E  Read-Ack    Max CH setpoint boundaries: 85 30

07:59:38.697252  Command (via websocket from 192.168.7.24:50158): SR=49:85,30
07:59:38.725827  SR: 49:85/30

07:59:53.596742  Command (via websocket from 192.168.7.24:50158): UI=49
07:59:53.612557  UI: 49

07:59:55.834364  T00300000  Read-Data   DHW setpoint boundaries: 0 0
07:59:55.864399  R80190000  Read-Data   Boiler water temperature: 0.00
07:59:56.019465  B40194200  Read-Ack    Boiler water temperature: 66.00
07:59:56.041428  AF0300000  Unk-DataId  DHW setpoint boundaries: 0 0

08:00:00.833613  T80310000  Read-Data   Max CH setpoint boundaries: 0 0
08:00:00.864347  R801A0000  Read-Data   DHW temperature: 0.00
08:00:01.008174  B401A3300  Read-Ack    DHW temperature: 51.00
08:00:01.032872  A70310000  Unk-DataId  Max CH setpoint boundaries: 0 0

08:00:55.835855  T00300000  Read-Data   DHW setpoint boundaries: 0 0
08:00:55.864358  R801A0000  Read-Data   DHW temperature: 0.00
08:00:56.006939  B401A3300  Read-Ack    DHW temperature: 51.00
08:00:56.034373  AF0300000  Unk-DataId  DHW setpoint boundaries: 0 0

08:01:00.835186  T80310000  Read-Data   Max CH setpoint boundaries: 0 0
08:01:00.859613  R80190000  Read-Data   Boiler water temperature: 0.00
08:01:01.014902  BC0194300  Read-Ack    Boiler water temperature: 67.00
08:01:01.039794  A70310000  Unk-DataId  Max CH setpoint boundaries: 0 0

For id 10 it's working fine.

BTW, otmonitor Summary page shows correct values

Post by **mike7** » Thu Jul 03, 2014 9:39 am

Returning to GatewayReset signal, I think this signal shouldn't be set to be retained.

Post by **hvxl** » Thu Jul 03, 2014 11:58 am

mike7 wrote:Returning to GatewayReset signal, I think this signal shouldn't be set to be retained.

I agree. That's why it isn't. This is what mosquitto -v reports (note the r0):

1404380828: Received PUBLISH from xxxxxx (d0, q1, r0, m5, 'events/central_heating/otmonitor/gatewayreset', ... (28 bytes))

Post by **mike7** » Thu Jul 03, 2014 12:25 pm

hvxl wrote: I agree. That's why it isn't. This is what mosquitto -v reports (note the r0):

Sorry, I can't check that, can't rise the signal

Thank you

Post by **hvxl** » Thu Jul 03, 2014 12:36 pm

mike7 wrote:I can't to set working configuration with SR, UI pairs for ids 48 and 49, I've got "Unk-DataId" response

That's correct. I initially only implemented the SR command for message IDs the gateway didn't handle specially. Since it is using the values from MsgID 48 and 49, the SR function doesn't work for these message IDs. You may be able to add this functionality by replacing the 2nd and 3rd "return" of the MessageID48 and MessageID49 subroutines by "goto WordResponse" (untested).

Post by **hvxl** » Thu Jul 03, 2014 12:40 pm

mike7 wrote:Sorry, I can't check that, can't rise the signal

Why not? Haven't you applied the patch I provided?

You can also use a different format than "Standard JSON" and then it's just a matter of sending a "GW=R" command.

Post by **mike7** » Thu Jul 03, 2014 2:27 pm

hvxl wrote: You may be able to add this functionality by replacing the 2nd and 3rd "return" of the MessageID48 and MessageID49 subroutines by "goto WordResponse" (untested).

hvxl wrote:Why not? Haven't you applied the patch I provided?

Moment to start to lean how to install build system for gateway and tcl for raspbian ... will try

Post by **hvxl** » Thu Jul 03, 2014 3:22 pm

mike7 wrote:Moment to start to lean how to install build system for gateway and tcl for raspbian ... will try

You make it sound complicated. You are aware that instructions are available in the readme.txt file included in the gateway sources and at http://otgw.tclcode.com/otmonsrc.html?

Home Automation Domotica Forum Europe, Bwired Forum

Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.

Re: Firmware version 4.0 has been released.