@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
@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
I just discover that if I comment the:
//#define MY_GATEWAY_MQTT_CLIENT
...then the Gateway is connect to the WiFi router.
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
1160 GWT:TIN:CONNECTING...
2162 GWT:TIN:CONNECTING...
3164 GWT:TIN:CONNECTING...
3166 GWT:TIN:IP: 192.168.1.199
3216 GWT:TIN:ETH OK
And then I have a lot of:
4139 GWT:TSA:ETH OK
4234 GWT:TSA:ETH OK
4307 GWT:TSA:ETH OK
4400 GWT:TSA:ETH OK
In my MQTT broker I can see the log:
1619521529: New connection from 192.168.1.199 on port 1883.
1619521529: Socket error on client <unknown>, disconnecting.
What this mean please ? ...can be a problem with my MQTT broker ?
It is work with all other topics around my home
Thanks again
Denis
Dear @mfalkvidd
on the same ESP32 Gateway board I write a simply web server schetch from here.
Then at the first reset the ESP32 take a new IP from DHCP server(router) without any problem.
So I think that there is something wrong in my schetch... but what can be ???
...because this GTW was working for weeks until now.
Just yesterday is stop working with always this error:
323366 GWT:TPC:CONNECTING...
324370 GWT:TPC:CONNECTING...
325374 GWT:TPC:CONNECTING...
326378 GWT:TPC:CONNECTING...
327382 GWT:TPC:CONNECTING...
328386 GWT:TPC:CONNECTING...
329390 GWT:TPC:CONNECTING...
330394 GWT:TPC:CONNECTING...
...
The unique thinks that I have changed yesterday,
it was the new PCB arrived for the sensor nodes:
I have mount one of this and test it for about one hour in order to understand better antenna.
It worked for some rounds and then boom... nothing arrived on my MQTT broker.
So I connect the gateway at the USB in order to debug and I so that the GTW can not take the IP.
I paste here my GTW schetch... maybe there is something that I can add in order to understand the problem.
/*
* The MySensors Arduino library handles the wireless radio link and protocol
* between your home built sensors/actuators and HA controller of choice.
* The sensors forms a self healing radio network with optional repeaters. Each
* repeater and gateway builds a routing tables in EEPROM which keeps track of the
* network topology allowing messages to be routed to nodes.
*
* Created by Henrik Ekblad <henrik.ekblad@mysensors.org>
* Copyright (C) 2013-2019 Sensnology AB
* Full contributor list: https://github.com/mysensors/MySensors/graphs/contributors
*
* Documentation: http://www.mysensors.org
* Support Forum: http://forum.mysensors.org
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
* version 2 as published by the Free Software Foundation.
*
*******************************
*
* REVISION HISTORY
* Version 1.0 - tekka
*
* DESCRIPTION
* The ESP32 gateway sends data received from sensors to the WiFi link.
* The gateway also accepts input on ethernet interface, which is then sent out to the radio network.
*
* Make sure to fill in your ssid and WiFi password below.
*/
/*
denis:
ESP32 pin out:
https://circuits4you.com/2018/12/31/esp32-devkit-esp32-wroom-gpio-pinout/
Radio wiring ESP32(GPIOxx): RFM69:
| RFM69| ESP32 |
|------|-------|
| MOSI | 23 |
| MISO | 19 |
| SCK | 18 |
| NSS | 5 |
| DIO0 | 16 |
*/
// Enable debug prints to serial monitor
#define MY_DEBUG
#define MY_BAUD_RATE 115200
// radio type (al meu ii RFM69HCW)
#define MY_RFM69_NETWORKID (45)
//#define MY_NODE_ID 39 // la gateway nu trebe node_id
#define MY_RADIO_RFM69
#define MY_IS_RFM69HW
#define MY_RFM69_FREQUENCY RFM69_433MHZ
#define MY_RFM69_NEW_DRIVER
//astea is pt. puterea radioului
#define MY_RFM69_ATC_TARGET_RSSI_DBM (-70) // target RSSI -70dBm
#define MY_RFM69_MAX_POWER_LEVEL_DBM (20) // max. TX power 10dBm = 10mW
//#define MY_REPEATER_FEATURE // denis: what is this ?
#define MY_GATEWAY_MQTT_CLIENT
#define MY_GATEWAY_ESP32
// Set this node's subscribe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "MySensors-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "MySensors-in"
// Set WIFI SSID and password
#define MY_WIFI_SSID "DaVinci"
#define MY_WIFI_PASSWORD "xxxxxxxxxxxxxx"
// Set the hostname for the WiFi Client. This is the hostname
// passed to the DHCP server if not static.
#define MY_HOSTNAME "MySensorsGTW"
// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
//#define MY_IP_ADDRESS 192,168,178,87
// denis: If using static ip you can define Gateway and Subnet address as well
//#define MY_IP_GATEWAY_ADDRESS 192,168,1,199
//#define MY_IP_SUBNET_ADDRESS 255,255,255,0
// MQTT broker
#define MY_MQTT_CLIENT_ID "MySensorsGTW"
#define MY_MQTT_USER "usr"
#define MY_MQTT_PASSWORD "pass"
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 1, 168
#define MY_PORT 1883
#define MY_SIGNAL_REPORT_ENABLED // denis: must undestand how is work
// Flash leds on rx/tx/err (Led pin on ESP32)
#define MY_DEFAULT_ERR_LED_PIN 2 // Error led pin
#define MY_DEFAULT_RX_LED_PIN 2 // Receive led pin
#define MY_DEFAULT_TX_LED_PIN 2 // the PCB, on board LED
// MySensors.h - must be after all #define
#include <MySensors.h>
void setup()
{
// Setup locally attached sensors
}
void presentation()
{
// Present locally attached sensors here
}
void loop()
{
// Send locally attech sensors data here
}
Thanks a lot again
Denis
@mfalkvidd said in GWT:TPC:CONNECTING:
Are other devices on the network able to get an ip address?
Yes I have a lot of device on my home lan, but not more than 50.
and I have a DHCP IP from 200 to 250.
I have try a fixed IP, but same think.
Is there some command in order to have more debug info please ?
Thanks a lot for the help.
Denis
Hi there all,
after a lot of days that my Gateway work, today it stop connecting, and I don't understand why.
It's still log a lot of:
510139 GWT:TPC:CONNECTING...
511143 GWT:TPC:CONNECTING...
512147 GWT:TPC:CONNECTING...
513151 GWT:TPC:CONNECTING...
514155 GWT:TPC:CONNECTING...
515159 GWT:TPC:CONNECTING...
516163 GWT:TPC:CONNECTING...
I try a WiFi connect to another router, but still same think.
I try a connection to my mobile phone WiFi (thetering) and same think.
Anyone can tell me why is not connecting anymore please ?
Thanks all in advance
Denis
I don't know... the link it's work on my side.
Anyway here is the pic:
Yes, I think will be ok... I hope
Thanks a lot
Denis
Thanks a lot Franz... I have buy this one... maybe is more little
Thanks again
Denis
Oh boys... a lot of information here.
Thanks so much... but I've already place the pcb order... I have make an order for 10 pieces.
Bun in the mean time I'll experiment and modify the schema thanks to you all
Anyway I have placed there this capacitor ... I hope will be ok for this time.
Thanks so much for all information
Denis
@skywatch said in New simply node sensor project - please some advise:
Measure the current drawn by the radio module in transmit. Small batteries may not last long if it is too high (say more than 20-30mA).2,
Do not use tantalum caps. They can have high ESR and have an ability to fail as a short circuit. Try ceramic SMD caps instead.
I just misure the power consume of the RFM69 radio and it's around 15mA max:
So you think it's ok ?
This is the develop project and here I use the 1000uF electrolytic capacitor (don't know if in this case help the radio power)
So for the cap please tell me... I must put a ceramic with out polarization ?
If yes, do you think this one it's ok please ? ...they have no disponibility for bigger than 220uF
Thanks a lot for your help
Denis
p.s. in the mean time I found this one that have only 7 mΩ MSR
Do you think it's ok please ?
Hi there all,
because I love a lot this great project MySensor, I begin to work on a simply node sensor
in order to have my one and make as I like.
Thi sensor will be a BME280 Temp/Humidity/Pressure sensor,
will work on ATMEGA328P and will transmit via RFM69 (cause I need big distances).
All will be power by 2 X 1.5 AAA battery, so I write the bootloader at 4 mHz in order to
suck more power from batts.
So I don't put a buster on this sensor.
Here I paste the sensor at this point:
And here is the schema:
Because I'm beginner, in Arduino, in Kicad and all this thinks,
I want to ask you all to give me some advise on this minimal hardware.
For example... I tested the sensor with a 10uF electrolytic capacitor
and I went at about 120 mt outside from my home. (gateway inside home)
Then I put a 1000uF (I have no other) capacitor and it work at about 150-170 mt.
So it'k ok the C1 at 470uF (!tantalum) on my schema ?
I also have read in some place that if the capacitor is bigger,
the sensor can use better the battery power every time that will wake up.
So please tell me if I can make some change before sending to Jlcpcb to make and assembly the pieces.
Thanks all in advance
Denis
@franz-unix
This is wonderful work... thanks for inspiring me
I know that this is an old thread,
but can you give me a link of the AAA battery holder please ?
I just make a node sensor and I want to use it.
Thanks a lot
Denis
@BearWithBeard said in Battery life calculator:
you'd wake up every 30 seconds instead of once every 2 minutes.
Whoawwww... I had entered wrong times
Now I take 409 days... great !!!
Thanks a lot again
Denis
@BearWithBeard said in Battery life calculator:
Did you measure the wake time of 2s?
No... I have inserted a wrong wake time,
cause now I have misure the wake time using millis() from initial LOOP
until before sleep command, and and I have only about 600 millis (sometime 300 sometime 900).
Then I send the data only when the temp have a difference of 0.3°C.
And the humidity only at 5% difference.
Also I put 2 minutes (really 128 sec because of 8s X 16 in order to use only thw WDT of 8Sec)
And now the tabel is like this:
But it give me only:
Yes... I have blinking LEDs as RX/TX but now I'll take off it and I'll blink only one time at every 2 minutes.
I'll see the measurements.
I will not discharge the batts too much because I dont buster for the voltage.
The 2 batts (3V) it's go directly to the Atmel and all the rest.
But I use an internal clock of 4mHz and If I understand correctly this will discharge the batts. until 1.8V of total.
Here I paste is the prototipe (cause I know you all like the pictures:-)
Thanks a lot
Denis
No... I must use 2 X AAA battery because of all project.
Thanks for the suggestion
Denis
I already have something like this, but this one have no misurement in uAh
Thanks a lot
Denis
Thanks a lot for the answer,
I think is not just 2 secs... I must do some variable and misure the time.
Also the temp/hum will be send only if delta difference is more than 0.5 Celsius.
So all the number I inserted is right...
I was hopping in some mistake
Thanks a lot for the answer.
Denis
Hi there all,
I just find this site that offer a battery life calculator.
My node sensor need 19mAh when work and about 9uAh in sleep mode.
I'll use 2 X AA (1,5V + 1,5V) battery and will send data every minute.
After I insert all the numbers it give me only 60 days.
So I want to ask, it's normal only 60 days or I'm wrong something on the inserted numbers please ?
Thanks all.
Denis.
Anyone can tell me if
Yes now I know
But the tester that I had before this one,
when it was switching from mA to uA, it was reseting the board.
Now all is greate
Thanks a lot
@Nca78 said in What I must buy in order to misure mAh please:
you have to unplug/re-plug before the nodes gets out of sleep and obviously this will make measurement impossible.
I use the multimeters in this mode:
-first I musure the work mA in the work session, with the switch on mA... this give me about 19 mA
-then I put the switch on uA but I also put a direct wire that is in paralel to the multimeters in order to have suficient current
...when the Arduino go in sleep mode, I take out the direct wire and the remained wire of multimeter will misure the uA
Thanks a lot for the answer.
Denis
I just retry with the newone and it give me about 9,1 uAmp
Thanks all
@Yveaux said in What really sleep() do please ?:
Sleeping for eg 30 seconds is divided into 3x8 seconds, 1x 4 seconds and 1x2 seconds.
Whoau... this is exact what I was think to do
But if MySensors is do this in automatic... well it's wonderful
Do you know ... is do an automatic sleep also for the RFM69 please ?
Thanks a lot.
Denis
Hi there all,
I just finish a simple node using a barebone Atmega328p.
I program the bootloader MiniCore at 8Mhz internal clock.
I use a BME280 for temp/humidity and RFM69HC for radio.
All work great
Now I'm on the software part of sleep.
I just use Sleep(30000) in order to test it.
What I receive in the log(parser) is:
Sleep node, duration 30000 ms, SmartSleep=0, Int1=255, Mode1=255, Int2=255, Mode2=255
Set transport to sleep
Node woke-up, reason/IRQ=-1 (-2=not possible, -1=timer, >=0 IRQ)
Set transport to standby
Sent Message ...etc...
So I wonder what sleep() do please ? ...it use a watchdog internal timer in order to wake up ?
I have try to use a "LowPower.h" lib but the compiler give me an error:
multiple definition of `__vector_6'
...like already have this piece of code in the MySensor lib.
So if I understand the watchdog internal timer is the best solution to make sleep all strange thinks inside Atmega328p.
Is I still understand it can't do it more than 8sec.
Can anyone please help me to understand ?
Thanks a lot
Denis
Usually I let it now 30 seconds in order to see the value in sleep mode.
Today I just buy this one... I'll try it tomorrow.
Thanks a lot
Denis
Thanks a lot... maybe I'll make one of this,
but now I need to buy one as soon is possible
Denis
Hi there all,
I make a test for a develop node and I just misure (a normal cinese tester)
how much mAh consume.
But when it will go in sleep I always take 0 mAh.
If I move the tester to uAh is not ok when it wake up.
So can anyone tell me what I must buy (maybe all ready on Amazon)
in order to misure mAh please from about 15 Mah to some uAh please ?
Thanks in advance
Denis
For now I spent all afternoon to program the 328 using an Arduino but I can't
I just buy from Amaz a ISP programmer and tomorow I'll retry.
I'll update the thread.
Thanks all again
Denis
@Yveaux said in Please give me an advice for a simple sensor node:
...so focus on sleeping current when trying to improve battery life.
Yeah you have right... I'll first program the 8Mhz bootloader first.
hen when all will work, I'll study also the 1Mhz one.
My node will sleep, and every minute (aprox 8 sec X 8 watchdog sleeps) will wake up for about 2 seconds.
Thanks a lot again
Denis
OK... thanks a lot.
Now I play with an old Arduino Mega and the AVR program in order to write the bootloader
A little question... how can I understand that the BME280 can work at 1MHz please ? ...maybe also the RFM69HC.
Thanks again
Denis
Thanks a lot all for the help.
So @evb you can confirm me that the internal 1 MHz it's still work on MySensors node ?
I ask this because in this thread (that I take from your link... thanks a lot)
at the first page I read:
"UPDATE 2: There have been reported issues with MySensors 2.x freezing on SlimNodes running at 1MHz, which I've confirmed. Recommended solution when using MyS 2.x, is to use 8MHz (internal) instead."
I'll begin to study the Minicore bootloader first... I have a lot to learn, and here in MySensors forum is a lot of page to read
Thanks a lot again
Denis
Hi there all,
I'm new on the MySensors and also Arduino world so please be pacient.
I just want to make a very simple Temp/Hum node sensor that can be powered
as long is possible from 2 X 1.5V AAA battery.
I decided for ATmega328 + BME280 + RFM69HW.
I have read a lot about battery power sensors and if I understand,
in order to make a 2 X AAA battery sensor, and suck as much juice is possible
from that battery, I'll need a Step up booster module.
But at the doc page is not specified witch one can I use.
I found/read a lot of post that is so old (about 3 to 6 or more years)
..so I want to gentle ask some low-power guru about what type of booster module regulator
I must use at this time please.
Or... maybe someone can give me a link of some similar (fresh) MySensors project that I can study.
Thanks a lot
Denis
Practically I receive the MQTT topics from the MySensors Gateway.
Then in Node-Red I have make a function that translate the MySensors MQTT topics in a personalized MQTT topics,
in order to have clear names of the sensors value.
In Node-Red you make a flow like this:
Then in the function node you make something like this... but personalized:
// add timestamp to every sensor reads
var dt = new Date();
var hh = dt.getHours();
var mm = dt.getMinutes();
var ss = dt.getSeconds();
var yy = dt.getFullYear();
var mo = dt.getMonth() + 1; // want 1 more
var dd = dt.getDate();
//var daynum = date.getDay();
timeST = (dd < 10 ? "0" : "") + dd + "-" + (mo < 10 ? "0" : "") + mo + "-" + yy +
" " + (hh < 10 ? "0" : "") + hh + ":" + (mm < 10 ? "0" : "") + mm + ":" + (ss < 10 ? "0" : "") + ss;
/* sensors ID
id SensGaraj: 11
id SensCame1:
id SensCame2:
id SensCame3:
id SensCucin:
id SensSerra: 12
id SensFuori:
id SensSalon:
type Temp : 51
type Hum : 52
type Press : 53
type BatVol: 54
type BatLev: 255
*/
ret = 0; // send the return or not
// sensor id (topic:MySensors-out/xx/)
var parts = msg.topic.split("/");
id = parts[1];
type = parts[2];
val = msg.payload;
if (id == 11 ){sname = "SensGaraj";ret = 1;}
if (id == 12 ){sname = "SensSerra";ret = 1;}
// if etc...
if (ret == 1){
if (type == 51 ){stype = "Temp"; }
if (type == 52 ){stype = "Hum";}
if (type == 53 ){stype = "Press";}
if (type == 54 ){stype = "BattVol";}
if (type == 255){stype = "BattLev";}
msg = {}; //initialize msg object
msg.measurement = "sensors"; // tabella/file > influxdb
msg.topic = "MySensors/" + sname + "/" + stype;
msg.payload = {value: val, timeST: timeST}
node.status({fill:"green",shape:"ring",text:sname});
return msg;
}
//////////////////////////////////////////////////////////////
If you need more help just let me know
Denis
I have try to install it but node-red give me some error.
But I have make a function that have a tabel that personalize all topics.
So I'll make all my future sensors in this mode.
Thanks again
Denis
Thanks a lot Yveaux... it's just what I work to from about 2 hours
I'll split all sensors in Node-Red with a new topic name.
I use something like:
/*
id SensGarag: 11
id SensCame1:
id SensCame2:
id SensCame3:
id SensCucin:
id SensFuori:
id SensSalon:
id SensSerra:
type Temp : 51
type Hum : 52
type Press: 53
*/
// sensor id (topic:MySensors-out/xx/)
var parts = msg.topic.split("/");
id = parts[1];
type = parts[2];
Thanks a lot again
Denis
Hi there all.
I finally finish to make work my first node and I'm very happy that it's work greate.
I just want to ask if it's possible to personalize the MQTT topics.
I mean, if it's possible in the GATEWAY code to intercept the NodeID, SensorID and value
and make a personalized topics in order to send it to MQTT broker.
I ask this because I make just a unique node and in my MQTT
it's already a lot of confusion...
There is a lot of number that I must translate every time I take a look.
What I would like is... use the MQTT code in order to make the broker connection,
stop the default update of topics, intercept the NodeID/SensorID/Value and give e personalized name.
Thanks all in advance
Denis
Hi there all,
I'm newbie in the world of MySensors and I try to make the first gateway (with MQTT client)
I so in the page here the pin mapping of the ESP8266
but I can't find the pin connection for the ESP32.
Then I find in this page a table with the pin for the ESP32 but I can't understand some pin.
* | IO | RF24 | RFM69 | RFM95 |
* |------|------|-------|-------|
* | MOSI | 23 | 23 | 23 |
* | MISO | 19 | 19 | 19 |
* | SCK | 18 | 18 | 18 |
* | CSN | 5 | 5 | 5 |
* | CE | 17 | - | - |
* | RST | - | 17 | 17 |
* | IRQ | 16* | 16 | 16 |
* * = optional
First of all this number is refer to the GPIO number of ESP32 ?
Then... I can't see the CSN and the IRQ on my RFM69HCW radio.
Here is a page that have the pinout of the RFM69HCW module.
I try some connections but I have an error like :
105 TSF:LRT:OK
148 TSM:INIT
188 TSF:WUR:MS=0
235 !TSM:INIT:TSP FAIL
283 TSM:FAIL:CNT=1
329 TSM:FAIL:DIS
374 TSF:TDI:TSL
Anybody can help me please ?
Thanks all in advance
Denis
Yes in the mean time I understand that MySensor have all the personalized ask/answer structure.
But I still study cause I like much this type of home network.
Anyway maybe there can be a personalized gateway part only for the incompatible sensors.
I'll try to study it when I'll be more "old" in this
Thanks a lot for the answer
Denis
I finally understand with was the problem...
My WiFi Mesh LAN accepted only 802.11.g+n radio... now that I have set 802.11.b+g+n it's ok
Strange this think cause an all other WiFi Arduino schetch the 802.11.g+n radio was always accepted.
Anyway... now it's work
Denis
Hi there all,
I know that usually all the node is maked by DIY... and there is some that are really greate.
But before knowing MySensore I have bought 8 pieces of Digoo DG-R8H sensors.
This one are really nice at less than 4 Euro. But have not display
I make it work using OpenMqttGateway but I want to try the MySensors also if possible.
So is there anyone that have use this sensors please ?
Thanks all
Denis
Hi there all,
I'm new here and for first think I'll like to thanks a lot for this wonderful MySensors
I just folow step-by-step the guide here: Building a WiFi Gateway using ESP8266
This is what I see on the NodeMcu log:
2216 GWT:TIN:CONNECTING...
scandone
state: 0 -> 2 (b0)
3982 GWT:TIN:CONNECTING...
state: 2 -> 3 (0)
state: 3 -> 0 (12)
reconnect
5068 GWT:TIN:CONNECTING...
6096 GWT:TIN:CONNECTING...
7124 GWT:TIN:CONNECTING...
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 0 (12)
This NodeMcu was always connecting on my WiFi LAN.
Someone can help me please ?
Thanks in advance
Denis
@MasMat said in 
Building a WiFi Gateway using ESP8266:
r usb + 800mA 5V charg
Sorry if I ask a noob question... I'm new and just arrived at MySensors
This screenshot, where is from please ? I mean What software you use ?
Thanks a lot
Denis
Great think this OpenMQTTGateway 
)
I'll post there.
Thanks a lot
Denis
Hi there all,
I just want to buy 8 pieces of the Digoo DG-R8H 433MHz
but before buy this I just want to ask someone... Can I link this sensor to the Sonoff RF Bridge please ?
If yes... what firmware I must put in the Sonoff ? (naw I have Tasmota)
Thanks in advance all
Denis