@OldSurferDude You are getting regular GWT:TSA:ETH OK message which i do not and you have no
MSG SENT lines

Which MQTT broker are you using?

my test setup which i hope matches yours is:
MySensors 2.3.2 & ESP8266 core 2.7.4
ESP8266 Node MCU with sketch GatewayESP8266MQTTClient
MY_BAUD_RATE 9600
MY_MQTT_USER & MQTT_PASSWORD commented out
MY_CONTROLLER_IP_ADDRESS 192, 168, 1, 195 address of the MQTT broker
MY_CONTROLLER_URL_ADDRESS "MQTT-TEST-W10" commented out Use IP or URL not Both
MY_PORT 1883

MQTT Broker
Mosquitto 2.0.15 running as a service on a windows 10 machine
listener 1883 anonymous access
URL MQTT-TEST-W10

When connected to the MQTT Broker and receiving messages from a node the gateway shows

09:48:18.962 -> 718935 TSF:MSG:READ,254-254-0,s=1,c=1,t=16,pt=2,l=2,sg=0:0
09:48:19.010 -> 718997 GWT:TPS:TOPIC=mygateway5-out/254/1/1/0/16,MSG SENT

09:48:19.104 -> 719059 TSF:MSG:READ,254-254-0,s=1,c=1,t=15,pt=1,l=1,sg=0:1
09:48:19.149 -> 719121 GWT:TPS:TOPIC=mygateway5-out/254/1/1/0/15,MSG SENT

09:48:19.198 -> 719182 TSF:MSG:READ,254-254-0,s=255,c=3,t=0,pt=1,l=1,sg=0:83
09:48:19.292 -> 719246 GWT:TPS:TOPIC=mygateway5-out/254/255/3/0/0,MSG SENT

if a message is sent to the broker the gateway shows

10:03:54.285 -> 1654209 GWT:IMQ:TOPIC=mygateway5-in/254/255/1/0/15, MSG RECEIVED
10:03:54.331 -> 1654279 TSF:MSG:SEND,0-0-254-254,s=255,c=1,t=15,pt=0,l=1,sg=0,ft=0,st=OK:1
10:03:54.423 -> 1654358 TSF:MSG:READ,254-254-0,s=1,c=1,t=16,pt=2,l=2,sg=0:1
10:03:54.471 -> 1654421 GWT:TPS:TOPIC=mygateway5-out/254/1/1/0/16,MSG SENT
10:03:54.565 -> 1654483 TSF:MSG:READ,254-254-0,s=1,c=1,t=15,pt=1,l=1,sg=0:1
10:03:54.611 -> 1654546 GWT:TPS:TOPIC=mygateway5-out/254/1/1/0/15,MSG SENT

@OldSurferDude You should leave them commented if not required.

I have just tested with a new install on windows of mosquitto with config file for anonymous access and it is working fine with them commented out.

what do your gateway debug logs look like?

@yourry for an example of array usage see Temperature Sensors build page.

MyMessage msgInA(0, V_WATT);     // only one message required
#define NSENSORS   6

//Read values and send to gateway
for (int i=0; i<NSENSORS; i++)
{
	watt[i] = (emon[i].calcIrms(1480))*230*0.9;
	send(msgInA.setSensor(i).set(watt[i], 1));        //setSensor(i) is the magic
       
}

@OldSurferDude have you set the MQTT user and MQTT passwords in the sketch and uncommented them as well?

// Enable these if your MQTT broker requires usenrame/password
//#define MY_MQTT_USER "username"
//#define MY_MQTT_PASSWORD "password"

// Enable these if your MQTT broker requires usenrame/password
#define MY_MQTT_USER "MQTTusername2022"
#define MY_MQTT_PASSWORD "MQTTpassword2022"

what does your debug log look like?
This sample is not connected correctly to the MQTT Broker

10:33:26.151 -> dhcp client start...
10:33:26.151 -> 341 TSM:INIT:GW MODE
10:33:26.199 -> 364 TSM:READY:ID=0,PAR=0,DIS=0
10:33:26.199 -> 396 MCO:REG:NOT NEEDED
10:33:26.339 -> 505 GWT:TPC:CONNECTING...
10:33:27.365 -> 1533 MCO:BGN:STP
10:33:27.365 -> 1551 MCO:BGN:INIT OK,TSP=1
10:33:27.412 -> 1579 TSM:READY:NWD REQ
10:33:27.412 -> 1606 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
10:33:28.671 -> scandone
10:33:35.993 -> pm open,type:2 0
10:33:44.664 -> 18861 TSF:MSG:READ,254-254-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
10:33:44.758 -> 18924 TSF:MSG:BC
10:33:44.758 -> 18942 TSF:MSG:FPAR REQ,ID=254
10:33:44.804 -> 18973 TSF:PNG:SEND,TO=0
10:33:44.804 -> 18998 TSF:CKU:OK
10:33:44.851 -> 19016 TSF:MSG:GWL OK
10:33:45.459 -> 19646 TSF:MSG:SEND,0-0-254-254,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
10:33:46.671 -> 20876 TSF:MSG:READ,254-254-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
10:33:46.766 -> 20939 TSF:MSG:PINGED,ID=254,HP=1
10:33:46.813 -> 20980 TSF:MSG:SEND,0-0-254-254,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
10:33:46.860 -> 21057 TSF:MSG:READ,254-254-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100

This is working correctly

10:36:34.908 -> dhcp client start...
10:36:37.655 -> ip:192.168.1.202,mask:255.255.255.0,gw:192.168.1.254
10:36:37.702 -> 7014 GWT:TPC:IP=192.168.1.202
10:36:37.702 -> 7100 GWT:RMQ:CONNECTING...
10:36:37.749 -> 7144 GWT:RMQ:OK
10:36:37.795 -> 7161 GWT:TPS:TOPIC=mygateway4-out/0/255/0/0/18,MSG SENT
10:36:44.792 -> pm open,type:2 0
10:38:56.629 -> 146027 TSF:MSG:READ,254-254-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
10:38:56.723 -> 146091 TSF:MSG:BC
10:38:56.723 -> 146109 TSF:MSG:FPAR REQ,ID=254
10:38:56.770 -> 146142 TSF:PNG:SEND,TO=0
10:38:56.770 -> 146168 TSF:CKU:OK
10:38:56.816 -> 146187 TSF:MSG:GWL OK
10:38:57.655 -> 147013 TSF:MSG:SEND,0-0-254-254,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
10:38:58.683 -> 148042 TSF:MSG:READ,254-254-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
10:38:58.730 -> 148105 TSF:MSG:PINGED,ID=254,HP=1
10:38:58.776 -> 148148 TSF:MSG:SEND,0-0-254-254,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
10:38:58.869 -> 148226 TSF:MSG:READ,254-254-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
10:38:58.916 -> 148294 TSF:MSG:SEND,0-0-254-254,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
10:38:59.010 -> 148375 TSF:MSG:READ,254-254-0,s=255,c=0,t=17,pt=0,l=11,sg=0:2.4.0-alpha
10:38:59.058 -> 148450 GWT:TPS:TOPIC=mygateway4-out/254/255/0/0/17,MSG SENT
10:38:59.151 -> 148515 TSF:MSG:READ,254-254-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
10:38:59.197 -> 148578 GWT:TPS:TOPIC=mygateway4-out/254/255/3/0/6,MSG SENT
10:39:00.923 -> 150319 TSF:MSG:READ,254-254-0,s=255,c=3,t=11,pt=0,l=14,sg=0:MockMySensors 
10:39:01.017 -> 150398 GWT:TPS:TOPIC=mygateway4-out/254/255/3/0/11,MSG SENT
10:39:01.064 -> 150462 TSF:MSG:READ,254-254-0,s=255,c=3,t=12,pt=0,l=4,sg=0:v0.5
10:39:01.157 -> 150529 GWT:TPS:TOPIC=mygateway4-out/254/255/3/0/12,MSG SENT
10:39:01.949 -> 151337 TSF:MSG:READ,254-254-0,s=1,c=0,t=0,pt=0,l=12,sg=0:Outside Door
10:39:02.044 -> 151410 GWT:TPS:TOPIC=mygateway4-out/254/1/0/0/0,MSG SENT
10:39:02.091 -> 151471 TSF:MSG:READ,254-254-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
10:39:02.184 -> 151542 TSF:MSG:SEND,0-0-254-254,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
10:39:02.699 -> 152055 TSF:MSG:READ,254-254-0,s=255,c=3,t=0,pt=1,l=1,sg=0:83

@OldSurferDude If connecting to a MQTT Broker i would have expected you to use the GatewayESP8266MQTTClient sketch.
as this is already setup with correct Port 1883 for MQTT and the publishing and subscription topics.

I did a quick test of a GatewayESP8266MQTTClient sketch with mosquitto and it works fine for me.

@OldSurferDude @dpcons Hi all,
The sample sketch could also be found using (File -> Examples -> MySensors -> Esp8266Gateway

As MySensors version 2.3.2 and ESP8266 core 3.0.2 combination does not work you need to change one or the other versions.

The simplest is to roll back the ESP8266 Core version to 2.7.4 and keep the MySensors 2.3.2 version
(Tools -> Board -> Board Manager)
Enter ESP8266 in search bar, then click within the ESP8266 data info box, click the select version pulldown.
Select 2.7.4 and then click Install.

Other option is to update the MySensors library to the development version 2.4.0-Alpha but that has to be done manually.

@dpcons I assembled a board copied from yours for testing.

I could replicate the problem. It is with the ESP core version and the MySensor Version
MySensors version 2.3.2 and ESP8266 core 3.0.2 does not work,

MySensors version 2.3.2 and ESP8266 core 2.7.4 works

Mysensors development version 2.4.0-Alpha and newest ESP8266 core 3.0.2 also works

So you can either update the esp core to older version 2.7.4, or install the development version of MySensors 2.4.0-Alpha

@dpcons As you are seeing no serial debug data. Have you checked that your serial data monitor is set for the same baud rate as set in the sketch (9600 on MySensors GatewayESP8266 sketch) as other sketches use default 115200

@Mati_Smart

What troubleshooting steps have you all ready taken?

I have loaded your sketch onto a mega2560 and looked at the serial output.
the binary switch child's 20 and 21 are switching.

0;20;1;0;16;1
0;21;1;0;16;1
0;21;1;0;16;0
0;20;1;0;16;0
0;21;1;0;16;1
0;20;1;0;16;1
0;21;1;0;16;0
0;21;1;0;16;1
0;21;1;0;16;0
0;21;1;0;16;1
0;20;1;0;16;0
0;20;1;0;16;1

have you checked this?

also why do you have all MY_INCLUSION defines active when there is no radio attached?

// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
#define MY_INCLUSION_BUTTON_FEATURE

// Inverses behavior of inclusion button (if using external pullup)
//#define MY_INCLUSION_BUTTON_EXTERNAL_PULLUP

// Set inclusion mode duration (in seconds)
#define MY_INCLUSION_MODE_DURATION 60 
// Digital pin used for inclusion mode button
#define MY_INCLUSION_MODE_BUTTON_PIN  3 

and you have the repeater function enabled

// Enable repeater functionality for this node
#define MY_REPEATER_FEATURE

this is sloppy programming and can cause problems.

Have you checked the basic things like the connections to the inputs?
You have the internal PULLUP enabled so the input signal should switch to ground.

@mrhutchinsonmn

try changing

 moistureLevels[i] = map(moistureLevel,0,650,0,99); // The maximum voltage output of the capacitive sensor is 3V, so since we're measuring 0-5v about 614 is the theoretical highest value we'll ever get.

to

 moistureLevels[i] = map(moistureLevel,325,650,99,0); // The maximum voltage output of the capacitive sensor is 3V, so since we're measuring 0-5v about 614 is the theoretical highest value we'll ever get.

Hi

Openhab and the MySensors binding use the HSTtype format (hue, saturation, brightness) for color information.
The binding automatically converts the HSBtype to the MySensors format of RRGGBB.
So you need to use the HSBType fromRGB(int R, int G, int B) function

items

Color   Mock_RGB_LED     "Mock RGB LED (HSB)     "  (test254) { channel = "mysensors:rgbLight:gatewayWIFI3:Mock_RGB_LED:rgb" } 
String  test_RGB_HexString "Test Color RGB hexS [0x%s]" (test254) 
Number  test_RGB_Red	" Test Colour Red    [%s]"  (test254)
Number  test_RGB_Green  " Test Colour Green  [%s]"  (test254)
Number  test_RGB_Blue   " Test Colour Blue   [%s]"  (test254)

Rules

val String filename = "rgb-light.rules"

rule "System startup"
        when
                System started
        then
/*Initial value of colors*/
    if (test_RGB_Red.state == NULL) test_RGB_Red.postUpdate(0)
	if (test_RGB_Green.state == NULL) test_RGB_Green.postUpdate(0)
    if (test_RGB_Blue.state == NULL) test_RGB_Blue.postUpdate(0)
end
rule "Test Colour Channels RGB to Mysensors"
when
	Item test_RGB_Red   changed or
	Item test_RGB_Green changed or
	Item test_RGB_Blue  changed
then
    val int r = (test_RGB_Red.state as Number).intValue
    val int g = (test_RGB_Green.state as Number).intValue
    val int b = (test_RGB_Blue.state as Number).intValue
    logInfo(filename, "Input Conversion: r:" + r + " g:" + g + " b:" + b)
   var HSBType hsb = HSBType.fromRGB(r, g, b)
    logInfo(filename, "Input Conversion: hsb" + hsb)	
    Mock_RGB_LED.sendCommand(hsb)
end


rule "RGB Hex -> HSB"
when
    Item test_RGB_HexString received update
then
    var rgb = test_RGB_HexString.state.toString

    var r = Integer::parseInt(rgb.substring(0, 2), 16)
    var g = Integer::parseInt(rgb.substring(2, 4), 16)
    var b = Integer::parseInt(rgb.substring(4, 6), 16)

    logInfo(filename, "Input Conversion: r" + r + " g" + g + " b" + b)
    var HSBType hsb = HSBType.fromRGB(r, g, b)
    logInfo(filename, "Input Conversion: hsb" + hsb)
    
    Mock_RGB_LED.sendCommand(hsb)	
end

/* I find this most useful for testing the node the Node */
rule "Test Colour Channels RGB to Mysensors"
when
    Item test_RGB_Red   changed or
    Item test_RGB_Green changed or
    Item test_RGB_Blue  changed
then
    var int r = (test_RGB_Red.state as Number).intValue
    var int g = (test_RGB_Green.state as Number).intValue
    var int b = (test_RGB_Blue.state as Number).intValue
    logInfo(filename, "Input Conversion: r:" + r + " g:" + g + " b:" + b)
    var HSBType hsb = HSBType.fromRGB(r, g, b)
    logInfo(filename, "Input Conversion: hsb" + hsb)	
    Mock_RGB_LED.sendCommand(hsb)
end	

I have tried this on my test system and i get the same results as you using the VAR1 -- VAR5 with the cover (RollerShutter) thing.

However if you add CustomSensor thing to your node then using the VAR1-VAR5 work as expected with the mapping. With numbers to and from the node.

things

cover    Mock_Cover        [nodeId=254, childId=6 ]
text     Mock_info         [nodeId=254, childId=7 ]

Items

Rollershutter	Mock_Cover_State       "Mock Cover State       [%s]"   <rollershutter>     (test254) { channel = "mysensors:cover:gatewayWIFI3:Mock_Cover:cover" } 

Number  Mock_Info_Var1			"Mock Info Variable 1 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" }
String  Mock_Info_Var1s			"Mock Info Variable 1 (string) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" }
Number  Mock_Info_Var1m			"Mock Info Variable 1 (number) [MAP(curtains.map):%s]"      (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var1" }
String  Mock_Info_Var1sm        "Mock Info Variable 1 (string map) [%s]" (test254) { channel="mysensors:text:gatewayWIFI3:Mock_Info:var1" [profile="transform:MAP", function="curtains.map"]  } 
Number  Mock_Info_Var2			"Mock Info Variable 2 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var2" }
Number  Mock_Info_Var3			"Mock Info Variable 3 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var3" }
Number  Mock_Info_Var4			"Mock Info Variable 4 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var4" }
Number  Mock_Info_Var5			"Mock Info Variable 5 (number) [%s]"                        (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:var5" }

Node

#define CHILD_ID_COVER 6
#define CHILD_ID_CUSTOM 7

present(CHILD_ID_COVER, S_COVER, "Roller Shutters");
present(CHILD_ID_CUSTOM, S_CUSTOM, "Reasons");

Or you if you want to send strings you could use

String  Mock_Info_Text			"Mock Info text sting [%s] "                                (test254) { channel = "mysensors:text:gatewayWIFI3:Mock_Info:text" }

Just use the V_Var1-5 to send a number to the node ( saves bandwidth) and back then use the MAP transform function to shown the human readable strings.

Make sure you have the Map Transformation installed in Transformations add-ons

The add a mapping file in the transformation folder

example file blinds.map

NULL=unknown Reason
-=unknown Reason
0=initial
1=Closed for Sunset
2=Closed for Sun Protection
3=Closed for Sleeping
4=Closed for Alexa Command
5=Closed for User Command
6=Closed for Security
7=Closed for Privacy
8=Closed for Migraine
9=Closed due to schedule
10 = Closed due to riots

33=Open for Sunrise
34=Open Ended Sun Protection
35=Open for Wakeup
36=Open for Alexa Command
37=Open for User Command
38=Open for Security
39=Open for No Privacy
40=Open for end of Migraine 
41=Open due to schedule

initial = 0
Closed for Sunset =1
Closed for Sun Protection = 2
Closed for Sleeping = 3
Closed for Alexa Command = 4
Closed for User Command = 5
Closed for Securitry = 6
Closed for Privacy = 7
Closed for Migraine = 8
Closed due to schedule = 9

Open for Sunrise = 33
Open Sun Protection Ended = 34
Open for Wakeup = 35
Open for Alexa Command = 36
Open for User Command = 37
Open for Securitry = 38
Open for No Privacy = 39
open end of Migraine = 40 
open due to schedule = 41

add the map transformation to item

Sample Items

// Blind Nodes 234,235,236
Number Blinds1_Reason	 "Bedroom 1 Blinds  [MAP(blinds.map):%s]"  (blinds, test1)  { channel = "mysensors:customSensor:gatewayWIFI2:Blinds234:var1" }
Number Blinds2_Reason	 "Bedroom 2 Blinds  [MAP(blinds.map):%s]"  (blinds, test1)  { channel = "mysensors:customSensor:gatewayWIFI2:Blinds235:var1" }
Number Blinds3_Reason	 "Bedroom 3 Blinds  [MAP(blinds.map):%s]"  (blinds, test1)  { channel = "mysensors:customSensor:gatewayW5100:Blinds236:var1" }

see https://www.openhab.org/addons/transformations/map/ for full details.

@yemesvee
If using a digital sensor mounted as per Kimot diagram you will receive a pulse stream, check the width of the pulsed to find if mesh or cable.

use the function pulseIn to determine the pulse width.

The simple example of the time duration of a pulse

int SensorPin = 3;
unsigned long duration = 0;
unsigned long CableDuration = 100;     // Set to suitable value
unsigned long CableCount = 0;

void setup()
{
  pinMode(SensorPin , INPUT);
}

void loop()
{

  duration = pulseIn(SensorPin , HIGH);
  Serial.print("Duration  : ");
  Serial.println(duration);
  if (duration >= CableDuration) {
    ++ CableCount;
    Serial.print("Cable detection  :");
    Serial.println(CableCount);
  }
}

@ek-wik you are describing sensor repeatability,

@dzjr To get the extra resolution sent to the controller try using

  send(msg.setSensor(i+21).set(temperature,2));

If the mesh moves at constant speed, How about a simple optical IR Sensor (break beam or Reflective), then checking pulse width of signal to detect mesh vs cable. Otherwise synchronize pulse width detection ratio in correlation to mesh speed.

Similar to this

@benhub Short answers, No, Yes, Yes

The regulator will use power if connected.
If your circuit is power hungry then removing the regulator will have limited effect.
The sparkfun schematic on the article that you listed notes to disconnect the regulator for low power, so the advice is consistent.
Unless you are using the genuine sparkfun versions of the pro-mini where the jumper can be cut then physically removing the regulator is recommended.

@dzjr you have the define

#define TEMPERATURE_PRECISION 12

In the github code this is not utilized, so the sensors are operating in 9 bit resolution.

You need to add the following in the before or setup

sensors.setResolution(TEMPERATURE_PRECISION);

@dzjr I also have various old meters, Some have a sealed movement so unable to change the scales.

Below is my meter showing time since last coffee.