@barrymoules Hi there,
yes I still have about 8 of this sensors, but I don't use it anymore.
It's not work with MySensors... only with OpenMqttGateway (or maybe else software)
If you need it I can send you 8 of this sensors
Obviously we make a less price then the official (and if you are in Europe for shipping cost).
Denis
@tbowmo said in node-red-contrib-mysensors release thread:
e-assistant and their spe
Thanks a lot @tbowmo
Denis
Sorry if I reopen this page... can I use MySController on e gateway with ESP32 please ?
I can't find any installation doc.
Thanks a lot
Denis
No problem @electrik I have already set the Node-Red to translate my node sensor in human leggibile data :-)
And now I can see it like this:
All ok and thanks a lot for the help
Denis
@electrik said in node-red-contrib-mysensors release thread:
build-essentials
I try it but it give me same errore.
I think that that package must be here in this link like the error log tell
Do you have Home Assistant installed ? if yes... do you have this "essentials" installed also ?
Thanks again
Denis
@electrik said in node-red-contrib-mysensors release thread:
system_packages
I have try to insert in the system_packages like this:
But it give me errore when start:
I think I'll make some translate node by my self
Thanks a lot again
Denis
@tbowmo said in node-red-contrib-mysensors release thread:
apt install build-essentials
I think I have not the apt inside of Node_red docker.
Can I install it from outside in this case.
Sorry but I'm very beginner so I need some basic info in this case.
Thanks a lot again
Denis
@tbowmo said in node-red-contrib-mysensors release thread:
ed 1.1.2, without problem
Thanks for the answer.
I have now Node-Red 1.3.3 under Home Assistant installed.
But I must search on net how can I install the build-essentials from the docker console.
Do you know if is there some other node that I can install from the palette that maybe incluse the build-essentials please ?
Thanks again
Denis
@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
Hi there all,
I just try to install the node in my Node-Red (Home Assistant)
and I got error:
-----------------------------------------------------------
2021-04-30T07:18:09.293Z Install : node-red-contrib-mysensors 3.3.1
2021-04-30T07:18:07.624Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production node-red-contrib-mysensors@3.3.1
2021-04-30T07:18:11.638Z [err] npm WARN deprecated @types/moment-timezone@0.5.30: This is a stub types definition. moment-timezone provides its own type definitions, so you do not need this installed.
2021-04-30T07:18:14.813Z [err] npm WARN
2021-04-30T07:18:14.813Z [err] deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
2021-04-30T07:18:19.176Z [out]
2021-04-30T07:18:19.176Z [out] > sqlite3@4.2.0 install /config/node-red/node_modules/sqlite3
2021-04-30T07:18:19.176Z [out] > node-pre-gyp install --fallback-to-build
2021-04-30T07:18:19.176Z [out]
2021-04-30T07:18:19.551Z [err] node-pre-gyp
2021-04-30T07:18:19.552Z [err] WARN Using request for node-pre-gyp https download
2021-04-30T07:18:20.511Z [err] node-pre-gyp
2021-04-30T07:18:20.512Z [err] WARN Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v4.2.0/node-v83-linux-x64.tar.gz
2021-04-30T07:18:20.512Z [err] node-pre-gyp WARN Pre-built binaries not found for sqlite3@4.2.0 and node@14.16.1 (node-v83 ABI, musl) (falling back to source compile with node-gyp)
2021-04-30T07:18:21.714Z [err] gyp
2021-04-30T07:18:21.715Z [err]
2021-04-30T07:18:21.715Z [err] ERR!
2021-04-30T07:18:21.715Z [err]
2021-04-30T07:18:21.716Z [err] build error
2021-04-30T07:18:21.716Z [err]
2021-04-30T07:18:21.716Z [err] gyp
2021-04-30T07:18:21.717Z [err]
2021-04-30T07:18:21.717Z [err] ERR!
2021-04-30T07:18:21.717Z [err]
2021-04-30T07:18:21.717Z [err] stack
2021-04-30T07:18:21.717Z [err] Error: not found: make
2021-04-30T07:18:21.717Z [err] gyp
2021-04-30T07:18:21.717Z [err]
2021-04-30T07:18:21.717Z [err] ERR!
2021-04-30T07:18:21.717Z [err]
2021-04-30T07:18:21.717Z [err] stack
2021-04-30T07:18:21.717Z [err] at getNotFoundError (/usr/lib/node_modules/npm/node_modules/which/which.js:13:12)
2021-04-30T07:18:21.718Z [err] gyp
2021-04-30T07:18:21.718Z [err]
2021-04-30T07:18:21.718Z [err] ERR!
2021-04-30T07:18:21.718Z [err]
2021-04-30T07:18:21.718Z [err] stack
2021-04-30T07:18:21.718Z [err] at F (/usr/lib/node_modules/npm/node_modules/which/which.js:68:19)
2021-04-30T07:18:21.718Z [err] gyp
2021-04-30T07:18:21.718Z [err]
2021-04-30T07:18:21.718Z [err] ERR!
2021-04-30T07:18:21.718Z [err]
2021-04-30T07:18:21.718Z [err] stack
2021-04-30T07:18:21.719Z [err] at E (/usr/lib/node_modules/npm/node_modules/which/which.js:80:29)
2021-04-30T07:18:21.719Z [err] gyp
2021-04-30T07:18:21.719Z [err]
2021-04-30T07:18:21.719Z [err] ERR!
2021-04-30T07:18:21.719Z [err]
2021-04-30T07:18:21.719Z [err] stack
2021-04-30T07:18:21.719Z [err] at /usr/lib/node_modules/npm/node_modules/which/which.js:89:16
2021-04-30T07:18:21.719Z [err] gyp
2021-04-30T07:18:21.719Z [err]
2021-04-30T07:18:21.719Z [err] ERR!
2021-04-30T07:18:21.720Z [err]
2021-04-30T07:18:21.720Z [err] stack
2021-04-30T07:18:21.720Z [err] at /usr/lib/node_modules/npm/node_modules/isexe/index.js:42:5
2021-04-30T07:18:21.720Z [err] gyp
2021-04-30T07:18:21.720Z [err]
2021-04-30T07:18:21.720Z [err] ERR!
2021-04-30T07:18:21.720Z [err]
2021-04-30T07:18:21.720Z [err] stack
2021-04-30T07:18:21.720Z [err] at /usr/lib/node_modules/npm/node_modules/isexe/mode.js:8:5
2021-04-30T07:18:21.720Z [err] gyp
2021-04-30T07:18:21.720Z [err]
2021-04-30T07:18:21.721Z [err] ERR!
2021-04-30T07:18:21.721Z [err]
2021-04-30T07:18:21.721Z [err] stack
2021-04-30T07:18:21.721Z [err] at FSReqCallback.oncomplete (fs.js:183:21)
2021-04-30T07:18:21.721Z [err] gyp
2021-04-30T07:18:21.721Z [err]
2021-04-30T07:18:21.721Z [err] ERR!
2021-04-30T07:18:21.721Z [err]
2021-04-30T07:18:21.721Z [err] System
2021-04-30T07:18:21.722Z [err] Linux 5.0.0-27-generic
2021-04-30T07:18:21.722Z [err] gyp
2021-04-30T07:18:21.722Z [err]
2021-04-30T07:18:21.722Z [err] ERR!
2021-04-30T07:18:21.722Z [err]
2021-04-30T07:18:21.722Z [err] command
2021-04-30T07:18:21.722Z [err] "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/config/node-red/node_modules/sqlite3/lib/binding/node-v83-linux-x64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/config/node-red/node_modules/sqlite3/lib/binding/node-v83-linux-x64" "--napi_version=7" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v83"
2021-04-30T07:18:21.722Z [err] gyp
2021-04-30T07:18:21.722Z [err]
2021-04-30T07:18:21.722Z [err] ERR!
2021-04-30T07:18:21.723Z [err]
2021-04-30T07:18:21.723Z [err] cwd
2021-04-30T07:18:21.723Z [err] /config/node-red/node_modules/sqlite3
2021-04-30T07:18:21.723Z [err] gyp
2021-04-30T07:18:21.723Z [err]
2021-04-30T07:18:21.723Z [err] ERR!
2021-04-30T07:18:21.723Z [err]
2021-04-30T07:18:21.723Z [err] node -v
2021-04-30T07:18:21.724Z [err] v14.16.1
2021-04-30T07:18:21.724Z [err] gyp
2021-04-30T07:18:21.724Z [err]
2021-04-30T07:18:21.724Z [err] ERR!
2021-04-30T07:18:21.724Z [err]
2021-04-30T07:18:21.724Z [err] node-gyp -v
2021-04-30T07:18:21.725Z [err] v5.1.0
2021-04-30T07:18:21.725Z [err] gyp
2021-04-30T07:18:21.725Z [err]
2021-04-30T07:18:21.725Z [err] ERR!
2021-04-30T07:18:21.725Z [err]
2021-04-30T07:18:21.725Z [err] not ok
2021-04-30T07:18:21.725Z [err]
2021-04-30T07:18:21.730Z [err] node-pre-gyp
2021-04-30T07:18:21.730Z [err] ERR! build error
2021-04-30T07:18:21.731Z [err] node-pre-gyp ERR!
2021-04-30T07:18:21.731Z [err] stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/config/node-red/node_modules/sqlite3/lib/binding/node-v83-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/config/node-red/node_modules/sqlite3/lib/binding/node-v83-linux-x64 --napi_version=7 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v83' (1)
2021-04-30T07:18:21.731Z [err] node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/config/node-red/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
2021-04-30T07:18:21.731Z [err] node-pre-gyp
2021-04-30T07:18:21.731Z [err] ERR! stack at ChildProcess.emit (events.js:315:20)
2021-04-30T07:18:21.731Z [err] node-pre-gyp ERR!
2021-04-30T07:18:21.731Z [err] stack at maybeClose (internal/child_process.js:1048:16)
2021-04-30T07:18:21.731Z [err] node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
2021-04-30T07:18:21.731Z [err] node-pre-gyp ERR!
2021-04-30T07:18:21.731Z [err] System Linux 5.0.0-27-generic
2021-04-30T07:18:21.731Z [err] node-pre-gyp
2021-04-30T07:18:21.731Z [err] ERR! command "/usr/bin/node" "/config/node-red/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
2021-04-30T07:18:21.731Z [err] node-pre-gyp
2021-04-30T07:18:21.731Z [err] ERR! cwd /config/node-red/node_modules/sqlite3
2021-04-30T07:18:21.731Z [err] node-pre-gyp
2021-04-30T07:18:21.731Z [err] ERR! node -v v14.16.1
2021-04-30T07:18:21.732Z [err] node-pre-gyp ERR! node-pre-gyp -v v0.11.0
2021-04-30T07:18:21.732Z [err] node-pre-gyp ERR! not ok
2021-04-30T07:18:21.732Z [out] Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/config/node-red/node_modules/sqlite3/lib/binding/node-v83-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/config/node-red/node_modules/sqlite3/lib/binding/node-v83-linux-x64 --napi_version=7 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v83' (1)
2021-04-30T07:18:22.158Z [err] npm ERR!
2021-04-30T07:18:22.158Z [err] code ELIFECYCLE
2021-04-30T07:18:22.158Z [err] npm ERR! errno 1
2021-04-30T07:18:22.164Z [err] npm ERR!
2021-04-30T07:18:22.164Z [err] sqlite3@4.2.0 install: `node-pre-gyp install --fallback-to-build`
2021-04-30T07:18:22.164Z [err] npm ERR! Exit status 1
2021-04-30T07:18:22.164Z [err] npm ERR!
2021-04-30T07:18:22.164Z [err] npm
2021-04-30T07:18:22.164Z [err] ERR! Failed at the sqlite3@4.2.0 install script.
2021-04-30T07:18:22.164Z [err] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-04-30T07:18:22.178Z [err]
2021-04-30T07:18:22.178Z [err] npm ERR! A complete log of this run can be found in:
2021-04-30T07:18:22.178Z [err] npm ERR! /root/.npm/_logs/2021-04-30T07_18_22_169Z-debug.log
2021-04-30T07:18:22.201Z rc=1
Is there still possibility to install it please ?
Thanks a lot
Denis
@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
@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
Yes... good idea :-)
I'll try now.
Thanks a lot
Denis
@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
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 said in GWT:TPC:CONNECTING:
Do you have the latest ESP32 framework installed?
I use Ardiono IDE and I have Espressif Systems version 1.0.6 installed on boards manager.
It tell me that is the last.
Do I must install other please ?
Thanks a lot
Denis
@smilvert said in GWT:TPC:CONNECTING:
in MyGatewayTransportMQTTClient.cpp then it started to work!
Thanks a lot @smilvert ...for me it's a big step forward, cause is 2 days that I'm so angry with this connections
I don't understand why I test a lot of Arduino schetch that use ETH+MQTT and was work all,
but MySensors use something that is not work always...
Now my GTW is connect (eth and mqtt) but then it goes in error:
E (46) psram: PSRAM ID read error: 0xffffffff
32 MCO:BGN:INIT GW,CP=RPNGF---,FQ=240,REL=0,VER=2.4.0-alpha
38 TSF:LRT:OK
39 TSM:INIT
40 TSF:WUR:MS=0
42 TSM:INIT:TSP OK
44 TSM:INIT:GW MODE
46 TSM:READY:ID=0,PAR=0,DIS=0
49 MCO:REG:NOT NEEDED
171 GWT:TPC:CONNECTING...
3173 MCO:BGN:STP
3175 MCO:BGN:INIT OK,TSP=1
3177 GWT:TPC:IP=192.168.1.170
3180 GWT:RMQ:CONNECTING...
3234 GWT:RMQ:OK
3235 GWT:TPS:TOPIC=MySensors-out/0/255/0/0/18,MSG SENT
Stack smashing protect failure!
abort() was called at PC 0x401353af on core 1
ELF file SHA256: 0000000000000000
Backtrace: 0x4008c6a8:0x3ffb1eb0 0x4008c921:0x3ffb1ed0 0x401353af:0x3ffb1ef0 0x400d2a56:0x3ffb1f10 0x400d2a91:0x3ffb1f50 0x400d2cb3:0x3ffb1f70 0x400d32f6:0x3ffb1f90 0x400d3429:0x3ffb1fb0 0x4008d926: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
E (46) psram: PSRAM ID read error: 0xffffffff
32 MCO:BGN:INIT GW,CP=RPNGF---,FQ=240,REL=0,VER=2.4.0-alpha
37 TSF:LRT:OK
39 TSM:INIT
40 TSF:WUR:MS=0
42 TSM:INIT:TSP OK
44 TSM:INIT:GW MODE
46 TSM:READY:ID=0,PAR=0,DIS=0
48 MCO:REG:NOT NEEDED
168 GWT:TPC:CONNECTING...
3170 MCO:BGN:STP
3172 MCO:BGN:INIT OK,TSP=1
3174 GWT:TPC:IP=192.168.1.170
3177 GWT:RMQ:CONNECTING...
11960 GWT:RMQ:OK
11962 GWT:TPS:TOPIC=MySensors-out/0/255/0/0/18,MSG SENT
Stack smashing protect failure!
Do you think is a hardware problem ?
Thank you so much for the help
Denis
I understand that I forget the "#define MY_GATEWAY_MQTT_CLIENT" was commented out.
So when I uncommented it, all return back with the:
169206 GWT:TPC:CONNECTING...
170210 GWT:TPC:CONNECTING...
171214 GWT:TPC:CONNECTING...
172218 GWT:TPC:CONNECTING...
173222 GWT:TPC:CONNECTING...
174226 GWT:TPC:CONNECTING...
So if I take out all the MQTT story, the GTW is connect to WiFi and I can ping it.
When I put back the MQTT rows the GTW is not connected and I always have the GWT:TPC:CONNECTING
I try with another ESP32, I try with another MQTT broker... I don't know anymore what to try :-(
A little help will be so appreciated
Thanks again
Denis
I take out the MySensors official distro
and I put on line the 2.4.0-alpha version.
Now I have the eth connect but I have a lot (too much and too quick) "GWT:TSA:ETH OK" messages
28 MCO:BGN:INIT GW,CP=RPNGF---,FQ=240,REL=0,VER=2.4.0-alpha
34 TSF:LRT:OK
35 TSM:INIT
36 TSF:WUR:MS=0
38 TSM:INIT:TSP OK
40 TSM:INIT:GW MODE
41 TSM:READY:ID=0,PAR=0,DIS=0
44 MCO:REG:NOT NEEDED
1165 GWT:TIN:CONNECTING...
2167 GWT:TIN:CONNECTING...
3169 GWT:TIN:CONNECTING...
3171 GWT:TIN:IP: 192.168.1.170
3197 GWT:TIN:ETH OK
3200 MCO:BGN:STP
3202 MCO:BGN:INIT OK,TSP=1
3205 TSM:READY:NWD REQ
3217 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
3238 GWT:TSA:ETH OK
3254 GWT:TSA:ETH OK
3282 GWT:TSA:ETH OK
3303 GWT:TSA:ETH OK
3319 GWT:TSA:ETH OK
3341 GWT:TSA:ETH OK
3368 GWT:TSA:ETH OK
3388 GWT:TSA:ETH OK
3410 GWT:TSA:ETH OK
3461 GWT:TSA:ETH OK
3495 GWT:TSA:ETH OK
3524 GWT:TSA:ETH OK
3541 GWT:TSA:ETH OK
3556 GWT:TSA:ETH OK
3576 GWT:TSA:ETH OK
3592 GWT:TSA:ETH OK
3613 GWT:TSA:ETH OK
3632 GWT:TSA:ETH OK
Any help with this messages ?
Thanks again
Denis
@DenisJ said in GWT:TPC:CONNECTING:
Socket error on client
I have try another time with commented out the define of MY_GATEWAY_MQTT_CLIENT.
and I so that the GTW get the IP but after there is fail log on eth.
Here is all log of connection with out MY_GATEWAY_MQTT_CLIENT
29 MCO:BGN:INIT GW,CP=RPNGF---,FQ=240,REL=255,VER=2.3.2
34 TSF:LRT:OK
35 TSM:INIT
36 TSF:WUR:MS=0
38 TSM:INIT:TSP OK
40 TSM:INIT:GW MODE
42 TSM:READY:ID=0,PAR=0,DIS=0
44 MCO:REG:NOT NEEDED
1164 GWT:TIN:CONNECTING...
2166 GWT:TIN:CONNECTING...
3168 GWT:TIN:CONNECTING...
3170 GWT:TIN:IP: 192.168.1.199
3279 !GWT:TIN:ETH FAIL
3281 MCO:BGN:STP
3283 MCO:BGN:INIT OK,TSP=1
3289 !GWT:TSA:ETH FAIL
3291 TSM:READY:NWD REQ
3797 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
3810 !GWT:TSA:ETH FAIL
3815 !GWT:TSA:ETH FAIL
!GWT:TIN:ETH FAIL is not parse, but I so in another page that is simply "ETH Connection failed"
Anyone any idea on this please ?
Thanks again
Denis