GWT:TPC:CONNECTING

[DenisJ]

Thanks a lot @electrik ... but I was on stable release when the problem has began.
For this reason I download the DEV version, but I have the same problem.

There is surely something stupid think that is wrong, but I don't know what is it.
This gateway was working for more than a month.

Thanks again
Denis

[electrik]

And if you change the lines like below now?

@smilvert said in GWT:TPC:CONNECTING:

it dosen't. But when I changed the delay to 3000
bool gatewayTransportConnect(void)
{
#if defined(MY_GATEWAY_ESP8266) || defined(MY_GATEWAY_ESP32)
if (WiFi.status() != WL_CONNECTED) {
GATEWAY_DEBUG(PSTR("GWT:TPC:CONNECTING...\n"));
delay(3000); // Was 1000
return false;
}
GATEWAY_DEBUG(PSTR("GWT:TPC:IP=%s\n"), WiFi.localIP().toString().c_str());

in MyGatewayTransportMQTTClient.cpp then it started to work!

[DenisJ]

@electrik said in GWT:TPC:CONNECTING:

gatewayTransportConnect

I changed it:

bool gatewayTransportConnect(void)
{
#if defined(MY_GATEWAY_ESP8266) || defined(MY_GATEWAY_ESP32)
	if (WiFi.status() != WL_CONNECTED) {
		GATEWAY_DEBUG(PSTR("GWT:TPC:CONNECTING...\n"));
		delay(3000); // denis: era 1000 dar l am schimbat pt. ca nu se lega la MQTT 
		return false;
	}
	GATEWAY_DEBUG(PSTR("GWT:TPC:IP=%s\n"), WiFi.localIP().toString().c_str());
#elif defined(MY_GATEWAY_LINUX)
#if defined(MY_IP_ADDRESS)
	_MQTT_ethClient.bind(_MQTT_clientIp);
#endif /* End of MY_IP_ADDRESS */
#elif defined(MY_GATEWAY_TINYGSM)
	GATEWAY_DEBUG(PSTR("GWT:TPC:IP=%s\n"), modem.getLocalIP().c_str());
#else
#if defined(MY_IP_ADDRESS)
	Ethernet.begin(_MQTT_clientMAC, _MQTT_clientIp);
#else /* Else part of MY_IP_ADDRESS */
	// Get IP address from DHCP
	if (!Ethernet.begin(_MQTT_clientMAC)) {
		GATEWAY_DEBUG(PSTR("!GWT:TPC:DHCP FAIL\n"));
		_MQTT_connecting = false;
		return false;
	}
#endif /* End of MY_IP_ADDRESS */
	GATEWAY_DEBUG(PSTR("GWT:TPC:IP=%" PRIu8 ".%" PRIu8 ".%" PRIu8 ".%" PRIu8 "\n"),
	              Ethernet.localIP()[0],
	              Ethernet.localIP()[1], Ethernet.localIP()[2], Ethernet.localIP()[3]);
	// give the Ethernet interface a second to initialize
	delay(1000);
#endif
	return true;
}

But in this case I get this error:

29 MCO:BGN:INIT GW,CP=RPNGF---,FQ=240,REL=0,VER=2.4.0-alpha
34 TSF:LRT:OK
35 TSM:INIT
37 TSF:WUR:MS=0
39 TSM:INIT:TSP OK
40 TSM:INIT:GW MODE
42 TSM:READY:ID=0,PAR=0,DIS=0
45 MCO:REG:NOT NEEDED
159 GWT:TPC:CONNECTING...
3162 MCO:BGN:STP
3164 MCO:BGN:INIT OK,TSP=1
3166 GWT:TPC:IP=192.168.1.170
3169 GWT:RMQ:CONNECTING...
3371 GWT:RMQ:OK
3372 GWT:TPS:TOPIC=MySensors-out/0/255/0/0/18,MSG SENT

Stack smashing protect failure!

abort() was called at PC 0x40134cef on core 1

ELF file SHA256: 0000000000000000

Backtrace: 0x40088620:0x3ffb1eb0 0x4008889d:0x3ffb1ed0 0x40134cef:0x3ffb1ef0 0x400d27e6:0x3ffb1f10 0x400d281e:0x3ffb1f50 0x400d2a23:0x3ffb1f70 0x400d2ff4:0x3ffb1f90 0x400d3105:0x3ffb1fb0 0x400898ae:0x3ffb1fd0

Rebooting...
ets Jun  8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:10944
load:0x40080400,len:6388
entry 0x400806b4
29 MCO:BGN:INIT GW,CP=RPNGF---,FQ=240,REL=0,VER=2.4.0-alpha
34 TSF:LRT:OK
36 TSM:INIT
37 TSF:WUR:MS=0
39 TSM:INIT:TSP OK
40 TSM:INIT:GW MODE
42 TSM:READY:ID=0,PAR=0,DIS=0
45 MCO:REG:NOT NEEDED
164 GWT:TPC:CONNECTING...
3166 MCO:BGN:STP
3168 MCO:BGN:INIT OK,TSP=1
3170 GWT:TPC:IP=192.168.1.170
3173 GWT:RMQ:CONNECTING...
6058 GWT:RMQ:OK
6059 GWT:TPS:TOPIC=MySensors-out/0/255/0/0/18,MSG SENT

Stack smashing protect failure!

abort() was called at PC 0x40134cef on core 1

ELF file SHA256: 0000000000000000
...from here it goes in LOOP

I'm near to become creasy :-(

Thanks again
Denis

[electrik]

Yes, but now use the 2.3.2 release with this modification

[DenisJ]

Yes... good idea :-)
I'll try now.

Thanks a lot
Denis

[DenisJ]

@electrik said in GWT:TPC:CONNECTING:

2.3.2 release

I can't believe... IT'S WOOOOOOORK !!!
Thanks a lot @electrik !!!

I don't know why, and I don't understand... but with 2.3.2 release it's work if I make that modify in the MyGatewayTransportMQTTClient.cpp file.
Also I don't like that I must modify that time... but for now it's ok.
Also I don't understand why 2 days ago it's change same hardware and same soft,
from work to no work (I don't know haw to tell this in english) :-)

Thanks so much again :-)
Denis

[electrik]

Good to hear! Perhaps a GitHub issue should be raised for these points...

[DenisJ]

@electrik said in GWT:TPC:CONNECTING:

Perhaps a GitHub issue should be raised for these points...

Well... if the DEV version is not work even if I make that change... I don't know.
I thinks this part is too sensibile. I'm not a programmer, but I think that this important part of communication must be renovate.

Tomorrow I can return to my node sensors test.
Thanks a lot all for the help.
Denis

[smilvert]

@electrik A ticket is raised quite long time ago, https://github.com/mysensors/MySensors/issues/1376

[DenisJ]

@smilvert said in GWT:TPC:CONNECTING:

A ticket is raised quite long time ago

Thanks a lot... I put my case there also, maybe can help.
That gui use same ESP32 DevKit V1 like me.

Strange that I didn't fount that page in this 2 days of research.

Thanks a lot
Denis