Domoticz

A lot of information can be found on this link:
https://www.domoticaforum.eu/viewtopic. ... 93&start=0
And since my suggested serial to ethernet adapter can only handle ttl, you must not use the max232, but connect the converter directly to the pic. You can use the connections on the place where the max232 should normally be placed. Check pinouts for ground, 5 volt, rx ttl and tx ttl.

bryan241 wrote: ↑Thursday 28 December 2017 11:24 A lot of information can be found on this link:
https://www.domoticaforum.eu/viewtopic. ... 93&start=0
And since my suggested serial to ethernet adapter can only handle ttl, you must not use the max232, but connect the converter directly to the pic. You can use the connections on the place where the max232 should normally be places. Check pinouts for ground, 5 volt, rx ttl and tx ttl.

Yeah, I found that forum, but not yet that specific topic in it, Thanks! I also found this pdf (https://www.kiwi-electronics.nl/downloa ... ctions.pdf) and with some other info from http://otgw.tclcode.com I put together a little bit how I think it should work. Could someone look at these and tell me if I'm correct or not?

To start off: since the TCP232 goes from TTL to Ethernet, I can skip the following components:

• MAX232 (IC2) (including the fitting it sits in that gets added to the Conrad shopping-cart when using the button on otgw.tclcode.com)

• 4x 1µF Capacitor (C3, C4, C5 and C6)

• 10 pin male header connector (SV1, but marked RS232 on the PCB) (including the Sub-D and 10-wire ribbon cable that gets added to the Conrad shopping-cart when using the button on otgw.tclcode.com)

The USR TCP232 should then be connected to the following points on the PCB. I indicated the "removed" components with a red X in this image.

Hobbybob wrote: ↑Thursday 28 December 2017 12:27

bryan241 wrote: ↑Thursday 28 December 2017 11:24 A lot of information can be found on this link:
https://www.domoticaforum.eu/viewtopic. ... 93&start=0
And since my suggested serial to ethernet adapter can only handle ttl, you must not use the max232, but connect the converter directly to the pic. You can use the connections on the place where the max232 should normally be places. Check pinouts for ground, 5 volt, rx ttl and tx ttl.

Yeah, I found that forum, but not yet that specific topic in it, Thanks! I also found this pdf (https://www.kiwi-electronics.nl/downloa ... ctions.pdf) and with some other info from http://otgw.tclcode.com I put together a little bit how I think it should work. Could someone look at these and tell me if I'm correct or not?

To start off: since the TCP232 goes from TTL to Ethernet, I can skip the following components:

• MAX232 (IC2) (including the fitting it sits in that gets added to the Conrad shopping-cart when using the button on otgw.tclcode.com)

• 4x 1µF Capacitor (C3, C4, C5 and C6)

• 10 pin male header connector (SV1, but marked RS232 on the PCB) (including the Sub-D and 10-wire ribbon cable that gets added to the Conrad shopping-cart when using the button on otgw.tclcode.com)

The USR TCP232 should then be connected to the following points on the PCB. I indicated the "removed" components with a red X in this image.
OTGW Ethernet.jpg

You are using the wrong tx and rx connections. The ones you are using are the output tx and rx from the max 232. You need to use pin 11 and 12.
I can remember connecting pin 11 to 14 and pin 12 to 13 and use the male header to connect the USR TCP232.

bryan241 wrote: ↑Thursday 28 December 2017 23:40 You are using the wrong tx and rx connections. The ones you are using are the output tx and rx from the max 232. You need to use pin 11 and 12.
I can remember connecting pin 11 to 14 and pin 12 to 13 and use the male header to connect the USR TCP232.

Aaah, you are right! Since I abandon the max232 I have to use the other connectors indeed! Just like the PDF showed that I found (see link in post above).

Thanks for the pointers! I think I have everything now

Yesterday I have bought my new boiler and Thermostat, and halfway through January it should be installed. Now I can order the stuff for the OTGW, and then the fun can begin!

Keep us posted and pictures always welcome

sincze wrote: ↑Friday 29 December 2017 11:42 Keep us posted and pictures always welcome

Will do! It will take a while I think, but I will certainly get back with my experiences!

The otgw from nodo-shop works great!

Here as well

I am using the Nodo shop OTG now for a few days and it works fine.
Soldering was easy (expert) and following the instructions it worked right away.
I used the transparant casing and the wifi module. Looks great.

I also just build the Nodo OTG version this week with an USR TCP232-T2 ethernet module.

The on-board voltage regulator was running to hot when I added the ethernet module directly to the 5V connection where you can place the NodoMCU. So I added an second voltage regulator to the OTG board. There are 2 holes (see attached image) free at the 19-24V side at the board so I wired there an extra 7805 with an output of 5V/1A with heat sink.

I found out that with the USR TCP232-T2 ethernet module powered from the OTG board you need to add the reset button if you wanna flash firmware. Power cycling in this case will also reboot the ethernet module and flashing from the otmonitor software will stop updating the firmware because it lost the connection. With the reset button you can set the OTG in programming mode without power cycling.

It works perfectly with Homeseer and Domoticz here, can communicate simultaneously to the OTG with the USR TCP232-T2. I'm now thinking of modifying my RFXTRX433 also with this ethernet module so I can connect to this interface also simultaneously with both systems. Ethernet will also make my move to one virtual machine (Citrix Xenserver) with domotica servers posible because USB support on virtual machines is not (good) supported.

vasco wrote: ↑Friday 09 March 2018 9:16 I also just build the Nodo OTG version this week with an USR TCP232-T2 ethernet module.

The on-board voltage regulator was running to hot when I added the ethernet module directly to the 5V connection where you can place the NodoMCU. So I added an second voltage regulator to the OTG board. There are 2 holes (see attached image) free at the 19-24V side at the board so I wired there an extra 7805 with an output of 5V/1A with heat sink.

I found out that with the USR TCP232-T2 ethernet module powered from the OTG board you need to add the reset button if you wanna flash firmware. Power cycling in this case will also reboot the ethernet module and flashing from the otmonitor software will stop updating the firmware because it lost the connection. With the reset button you can set the OTG in programming mode without power cycling.

It works perfectly with Homeseer and Domoticz here, can communicate simultaneously to the OTG with the USR TCP232-T2. I'm now thinking of modifying my RFXTRX433 also with this ethernet module so I can connect to this interface also simultaneously with both systems. Ethernet will also make my move to one virtual machine (Citrix Xenserver) with domotica servers posible because USB support on virtual machines is not (good) supported.

Nice one! In the meantime I have soldered away at a OTGW-board. Some other things came up in everyday life that have prohibited me from testing it, but when I do, I'll post my experiences here (as promised before).

Hello all,

Last week I was able to connect the Nodo Shop OTGW with NodeMCU. All went pretty smoothly. I found some instructions on how to change my boiler to the OpenTherm protocol. Some hardware modifications to the boiler were mentioned, but when the OTGW lost connection (yesterday afternoon when we were not at home ) the boiler turned on instead of off, making it rather warm when we returned, So I changed the hardware modification and now it's off instead of on when the connection is lost.

The only trouble I discover is that the OTGW loses connection at least 10x a day. I read this in the Domoticz log with the hardware time-out setting set to 5 minutes. Nevertheless was the connection lost permanently last night causing the thermostat (Honeywell Chronothern Touch Modulation) to lose connection with the boiler. Because the temperature was still high from last afternoon no harm was done, but the connection seems rather unreliable.

Last restart: 13:33:31 but the NodeMCU says (at 13:55) that the uptime is 265 minutes.

Any suggestions/help are highly appreciated.

Skippy

I ran into a small problem... I hope anybody can help.

I finished soldering my OTGW, and I can connect to it using the USB-cable. otmonitor shows a green connection-symbol and when I plug in the power-cable, it shows the version (4.2.5) of the OTGW-software running. I have not yet pued my thermostat off the wall, as I want to test the connections before I make any adjustments to the house-installation (I don't live alone, so I want to minimize the disruption of the heating-system).

After that, I removed the USB-cable, and connected the USR-TCP232-T2 I bought. It's working fine, since I can access the device through my network on 192.168.0.7 (the default fixed IP of this device). I can configure a lot of things, but I cannot find a configuration so get otmonitor to connect to it.

Does anybody know what I should change in the settings to get this to work? In the meantime I have restored the default-settings. Since I suspect it should be the "Serial"-settings, I included a screenshot of those settings below. What should be changed? I already tried several things (change port-numbers, baud-rate to 9600, remote IP, but to be honest I don't know what combinations I have tried...). Or perhaps I have to change the settings of otmonitor (I just put in the ip-address without any prefices or anything, and the port-numbers shown in the screenshot below).

vasco wrote: ↑Friday 09 March 2018 9:16I also just build the Nodo OTG version this week with an USR TCP232-T2 ethernet module.

Hey vasco (or anybody else with this ethernet-module), could you send me screenshots or info on the settings of the USR TCP232-T2? As stated in my last post, I cannot reach the OTGW through this module, but I am able to reach the module itself. Thanks very much!

Sorry read your message just today.
Hope you already find the solution but if not here are my settings of the USR TCP232-T2 to help you and others.

I did some communication with Remco from Nodo Shop past months about adding an USR TCP232-T2 possibility directly to the board. We did exchange ideas about this and how I did it. I received a message today from Remco of Nodo Shop that they now have a version of the OTGW where you can also directly connect the USR TCP232-T2 board. They also selling the USR TCP232-T2 at there shop too.

I'm not involved with the Nodo Shop what soever but would let others know that they have made my idea into a great new OTGW board so it is easy for others to make an ethernet (USR TCP232-T2) or WiFi (NodoMCU) version now.

vasco wrote: ↑Monday 14 May 2018 16:17 I did some communication with Remco from Nodo Shop past months about adding an USR TCP232-T2 possibility directly to the board. We did exchange ideas about this and how I did it. I received a message today from Remco of Nodo Shop that they now have a version of the OTGW where you can also directly connect the USR TCP232-T2 board. They also selling the USR TCP232-T2 at there shop too.

I'm not involved with the Nodo Shop what soever but would let others know that they have made my idea into a great new OTGW board so it is easy for others to make an ethernet (USR TCP232-T2) or WiFi (NodoMCU) version now.

Okay, that's great! Another option for communication is always good!

However, I've soldered my own OTGW in the meantime. I'm just running into problems with the communication between the OTGW and Domoticz. I've made a new topic about this, but nobody seems to know the answer. Communicating with otmonitor.exe works perfectly, but when Domoticz gets involved it starts giving errors.
I've also posted on domoticaforum.eu about this, and Schelte reacted that the log indicated that Domoticz is bombarding the OTGW with messages without waiting for a response, and in that way is overloading the OTGW. I'd like to get some more help on this, but I'm afraid I'm on my own here, and this is not something I can figure out by myself. As it stands now this is the end of the road for OTGW for me.

Hello guys,

Maybe I didn't search good enough, but I also use the OTGW from NODO with Ethernet connection.
Thanks to Remco from NODO shop I got the right settings to get it communicating.
I was only wondering what model to choose in Hardware settings?
Obviously I chose OpenTherm Gateway with LAN interface, but in version V3.9587 you have to choose a model out of 7 options.
Wich one should I pick, at the moment I use DAEnet IP4 and this works.
But some values like DHW temperature stay 0. So maybe it has something to do with it?

Last weeks i had many problems regarding lost connection/no display on thermostat.
This always happend at warm days en i suppose the circuit board or one or more components get to hot.
As a solution i drlled many holes in the side and on the top side of the acrylic casing but that didn't help a lot.
Stil disconnections occur and no display on thermostat on hot days...

Next thing i wil try is to mount a bigger heatsink on the voltage regulator, en also try to improve the ventilaton of the casing.

The extra ventilation holes i drilled:

Hi
I installed this in March (when it was cold) and it I experienced frequent dropouts. I suspected it had to do with overheating. My (crude) solution: an old fashioned timer in the wall socket which turns off the OTGW every 4 hours for 15 minutes. This solved the problem, although the you will see error messages in the log...
Skippy