Opentherm Gateway NodeMCU terminal

[Daylights]

I've purchased the nodo-shop OTGW (https://www.nodo-shop.nl/en/opentherm-g ... teway.html), which is based on the open source version of OTGW. I didn't find any documentation on using or soldering it, but it wasn't too complicated. Then I put on a NodeMCU (ESP8266) and flashed ESP-Link to it (as I saw that most people were using this). When the OTGW is powered, my iSense thermostat is able to communicate with the Rehema Calenta boiler, so far so good. I just don't see anything coming in on the uC console. I set it to 9600 baud, fmt 8N1, but no show. I also tried sending something like PS=0 and PS=1, nada. I have tried the pin layout of ESP-12 and ESP-12 Swapped.

What am I missing here?

[sincze]

I've purchased the nodo-shop OTGW (https://www.nodo-shop.nl/en/opentherm-g ... teway.html), which is based on the open source version of OTGW. I didn't find any documentation on using or soldering it, but it wasn't too complicated. Then I put on a NodeMCU (ESP8266) and flashed ESP-Link to it (as I saw that most people were using this). When the OTGW is powered, my iSense thermostat is able to communicate with the Rehema Calenta boiler, so far so good. I just don't see anything coming in on the uC console. I set it to 9600 baud, fmt 8N1, but no show. I also tried sending something like PS=0 and PS=1, nada. I have tried the pin layout of ESP-12 and ESP-12 Swapped.

What am I missing here?

Try to connect to it with otmonitor for debugging maybe the debug firmware is still in the PIC.

[Daylights]

Thanks! Could you maybe guide me a little on how to use that, which pins do I need to query?

[sincze]

haha no pins to query. no worries.

Just enable the relay functionality in otmonitor and have domoticz connect to that.

In addition you could have a look at: viewtopic.php?t=12492 this allows full functionality of Otmonitor in mode PS=1 and Domoticz in PS=0 mode. You can spot the differences in realtime.

[Daylights]

As it turns out, I had my jumpers configured the wrong way

Thanks for your support!

[sincze]

Nice. Maybe share the correct jumper settings for future reference

[Daylights]

I also e-mail the seller at Nodo-shop.nl. He gave me an url to the manual:

https://www.nodo-shop.nl/nl/index.php?c ... achment=47

Page 9 explains how both jumpers need to be set towards the NodeMCU on TxP/RxP. I had them set for the FTDI connector, which I am not using.

Now only how to add it to Domoticz? I am seeing the same terminal events in Domoticz logs, but no new devices. Or do I need to configure MQTT for that?

[sincze]

I also e-mail the seller at Nodo-shop.nl. He gave me an url to the manual:

https://www.nodo-shop.nl/nl/index.php?c ... achment=47

Page 9 explains how both jumpers need to be set towards the NodeMCU on TxP/RxP. I had them set for the FTDI connector, which I am not using.

Now only how to add it to Domoticz? I am seeing the same terminal events in Domoticz logs, but no new devices. Or do I need to configure MQTT for that?

Did you allow new hardware for 5 minutes and connect domoticz via wlan to OTGW?
It should create the devices for you.

[Daylights]

I did try that, no new hardware is added. I also tried disabling/enabling it, no show. Even tried a fresh (release) install, since I thought I had some issues with the beta versions.

What caught my eye is that the shell events don't all show in the Domoticz log as they all show in the uC shell in ESP-Link. Sometimes Domoticz claims it cannot connect on port 23, then the connection is restored again and the events come in bunches, then no events for a few minutes...

[Daylights]

Ok, I just replaced the NodeMCU with another one flashed with ESPEasy. I've configured the Serial Server, now Domoticz gets a continues stream of terminal codes. Yet, no new hardware available?

[sincze]

As domoticz is showing the codes in the log... And OTmonitor is working correctly this is a strange thing indeed.
The only thing I can think of... is the allow for 5 minutes hardware, disbale otgw LAN (update), re-enable (update) it. Looks stupid but I managed to solve some Xiaomi devices in the same way that did not show up.

[Daylights]

That looks to have solved the issue indeed. By a bit disabling/enabling, restarting, all of a sudden the devices started to show up. Monitoring all works, even when I change the remote access setting on the thermostat, I am able to alter the temperature Now the flood of terminal codes are gone in the Domoticz log, I only see some errors are still appearing:

2018-04-30 09:35:39.766 Error: OTGW: Error received!
2018-04-30 09:35:39.766 (Opentherm Gateway) Temp (Control Setpoint)
2018-04-30 09:35:39.766 (Opentherm Gateway) General/Percentage (Maximum Relative Modulation Level)
2018-04-30 09:35:39.768 (Opentherm Gateway) Thermostat (Thermostaat temperatuur)
2018-04-30 09:35:39.768 (Opentherm Gateway) General/Percentage (Relative modulation level)
2018-04-30 09:35:39.769 (Opentherm Gateway) General/Pressure (Boiler Water druk)
2018-04-30 09:35:39.770 (Opentherm Gateway) Temp (Kamer temperatuur)
2018-04-30 09:35:39.771 (Opentherm Gateway) Temp (Boiler Water temparatuur)
2018-04-30 09:35:39.772 (Opentherm Gateway) Temp (DHW Temperature)
2018-04-30 09:35:39.772 (Opentherm Gateway) Temp (Outside Temperature)
2018-04-30 09:35:39.773 (Opentherm Gateway) Temp (Return Water Temperature)
2018-04-30 09:35:39.773 (Opentherm Gateway) Thermostat (DHW Setpoint)
2018-04-30 09:35:39.773 (Opentherm Gateway) Thermostat (Max_CH Water Setpoint)
2018-04-30 09:36:09.769 Error: OTGW: Error received!

Is there a way to debug log these?

[jejeti]

Hi, I know I'm late but I ended up here by searching "OTGW: Error received!" and I finally solved it.
So, just to help anyone having the same issue in Domoticz, here is what I did :
My setup :
- OTGW from Nodoshop
- NodeMCU with ESPEasy Mega configured as serial server
- Domoticz

Original post : https://gathering.tweakers.net/forum/li ... 1653967/12

"OTGW: Error received!" logged in Domoticz means "SE" (syntax error) code was received.
It is due to the serial log status request from the ESP.

To disable it, in ESP easy interface, go to "tools" tab, "system"/"advanced", "log settings"/"serial log level" = none