[Solved] Internal message I_DISCOVER_RESPONSE is handed over to the controller
-
When the internal message I_DISCOVER_RESPONSE is received in the gw it's sent to the controller. I'm using an Ethernet MQTT client GW with Mosquitto. Is this message used by some controller? Or should it be kept internally? In my case it messes up with my controller functions.
Debug messages captured in the gw:
0;255;3;0;9;TSM:READY:NWD REQ 0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 0;255;3;0;9;TSF:MSG:READ,26-26-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0 0;255;3;0;9;Sending message on topic: mygateway1-out/26/255/3/0/21
I added the following lines to MyTransport.cpp after:
https://github.com/mysensors/MySensors/blob/development/core/MyTransport.cpp#L705if (type == I_DISCOVER_RESPONSE) { // don't send to controller return; }
With the patch added it looks like this:
0;255;3;0;9;TSM:READY:NWD REQ 0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK: 0;255;3;0;9;TSF:MSG:READ,26-26-0,s=255,c=3,t=21,pt=1,l=1,sg=0:0
Pls. confirm if this is correct.
-
@jpaulin No, this is correct - the I_DISCOVER_RESPONSE messages can be used by the controller to reveal the network topology.
-
@tekka ok, I'll fix it on the controller side, thanks!
1 out of 3
Suggested Topics
-
Code for beta-testing?
Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44 -
ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • 6 Apr 2020, 18:43 • Technovation 7 Mar 2022, 10:37 -
some differences between serial- and tcp-gateways.
Bug Reports • 15 Mar 2023, 09:26 • Branther 30 Mar 2023, 15:40 -
sleep(0) in V2.1 doesn't sleep indefinitely anymore. Used to powerdown and sleep in V1.5
Bug Reports • 22 Nov 2019, 00:35 • GaryStofer 15 Apr 2023, 05:50 -
Sensor presentation failure
Bug Reports • 31 Jul 2016, 19:23 • Sergio Rius 3 Mar 2021, 18:48 -
NRF51-52 PA not support ???
Bug Reports • 23 Feb 2019, 16:40 • berkseo 8 Jul 2021, 11:42