Strange behavior of connection Node => Gateway

dakky

Hello

EDIT: I posted this thread to General diskussions, because I don't know if there is somethink to troubleshoot or bugreport ...

I have the following behavior:
When starting a node after it's off some time, it fails to connect to the gateway:

Starting sensor (RNNNA-, 1.6.0-beta)
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=fail:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=fail:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=fail:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=fail:0.1
find parent
send: 99-99-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:

Erm .. ok: 0/6 messages are ok. Powering it off and on (and mybe pressing the reset buttin once or twice) results in partial st=ok:

Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=fail:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=fail:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=fail:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:0.1
Init complete, id=99, parent=0, distance=1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=ok:1

Strange ... 2/6 messages are ok ok lets reset the node again:

Starting sensor (RNNNA-, 1.6.0-beta)
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=fail:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=ok:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=ok:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=ok:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:0.1
Init complete, id=99, parent=0, distance=1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1

Hmm .. almost ... 4/6 messages are ok ... reset again:

Starting sensor (RNNNA-, 1.6.0-beta)
Radio init successful.
send: 99-99-0-0 s=255,c=3,t=15,pt=1,l=1,sg=0,st=ok:0
send: 99-99-0-0 s=255,c=0,t=17,pt=0,l=10,sg=0,st=ok:1.6.0-beta
send: 99-99-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,st=ok:0
send: 99-99-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,st=ok:
send: 99-99-0-0 s=255,c=3,t=11,pt=0,l=11,sg=0,st=ok:Test Sensor
send: 99-99-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,st=ok:0.1
Init complete, id=99, parent=0, distance=1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=ok:1

Here we are 6/6 messages are ok ... but i can image, that's not the way it's inted to be, isn't it? I did not change the wiring or something on the code between the power cycles/resets.

** Some time went by trying to get more infos **

Ah i could narrow it down: It's the gateway causing the problem: When the GW was off some time (simple unplug/plug does not cause this problem) it takes some time until the nodes could connect again.

Times:
GW offline: ~7m
Node can reconnect: ~1m20s

Not shure if this is a real world problem or not ... maybe i should think about a mini usv for the gateway

dakky

**EDIT: can someone move thes thread to the troubleshoot section? **
hmm maybe it's more of a problem than i thought: the first connection of the node to the ggateway does still require one or two resets of the node :(

I turned off and on the gateway and simply waited in order to have the node reconnected to the gw. But this does not happen:

Every 6 "actions/sendings" from the node to the gw i can see:

send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
find parent
send: 99-99-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:0
send: 99-99-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0,st=fail:1
find parent
send: 99-99-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,st=bc:

Only resetting the node connects it to the network again.

dakky

recap:
after a longer downtime of the gw the nodes need

some time (~1-2min) after the startup of the GW
a reset

in order to reconnect

EDIT. Code attached

/**
 * 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-2015 Sensnology AB
 * Full contributor list: https://github.com/mysensors/Arduino/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 - Henrik Ekblad
 * 
 * DESCRIPTION
 * The W5100 MQTT gateway sends radio network (or locally attached sensors) data to your MQTT broker.
 * The node also listens to MY_MQTT_TOPIC_PREFIX and sends out those messages to the radio network
 *
 * LED purposes:
 * - To use the feature, uncomment WITH_LEDS_BLINKING in MyConfig.h
 * - RX (green) - blink fast on radio message recieved. In inclusion mode will blink fast only on presentation recieved
 * - TX (yellow) - blink fast on radio message transmitted. In inclusion mode will blink slowly
 * - ERR (red) - fast blink on error during transmission error or recieve crc error  
 * 
 * See http://www.mysensors.org/build/esp8266_gateway for wiring instructions.
 * nRF24L01+  ESP8266
 * VCC        VCC
 * CE         GPIO4          
 * CSN/CS     GPIO15
 * SCK        GPIO14
 * MISO       GPIO12
 * MOSI       GPIO13
 *            
 * Not all ESP8266 modules have all pins available on their external interface.
 * This code has been tested on an ESP-12 module.
 * The ESP8266 requires a certain pin configuration to download code, and another one to run code:
 * - Connect REST (reset) via 10K pullup resistor to VCC, and via switch to GND ('reset switch')
 * - Connect GPIO15 via 10K pulldown resistor to GND
 * - Connect CH_PD via 10K resistor to VCC
 * - Connect GPIO2 via 10K resistor to VCC
 * - Connect GPIO0 via 10K resistor to VCC, and via switch to GND ('bootload switch')
 * 
  * Inclusion mode button:
 * - Connect GPIO5 via switch to GND ('inclusion switch')
 * 
 * Hardware SHA204 signing is currently not supported!
 *
 * Make sure to fill in your ssid and WiFi password below for ssid & pass.
 */

// Custom Settings
#define SKETCH_NAME "mqttClientGateway"
#define SKETCH_MAJOR_VERSION "1"
#define SKETCH_MINOR_VERSION "0"

#include <EEPROM.h>
#include <SPI.h>

// Enable debug prints to serial monitor
#define MY_DEBUG 

// Enables and select radio type (if attached)
#define MY_RADIO_NRF24
//#define MY_RADIO_RFM69

#define MY_GATEWAY_MQTT_CLIENT

// Set this nodes subscripe and publish topic prefix
#define MY_MQTT_PUBLISH_TOPIC_PREFIX "sensor-gw1-out"
#define MY_MQTT_SUBSCRIBE_TOPIC_PREFIX "sensor-gw1-in"

// Set MQTT client id
#define MY_MQTT_CLIENT_ID "sensor-gw1"

// W5100 Ethernet module SPI enable (optional if using a shield/module that manages SPI_EN signal)
//#define MY_W5100_SPI_EN 4  

// Enable Soft SPI for NRF radio (note different radio wiring is required)
// The W5100 ethernet module seems to have a hard time co-operate with 
// radio on the same spi bus.
#if !defined(MY_W5100_SPI_EN)
  #define MY_SOFTSPI
  // Arduino Uno
  //#define MY_SOFT_SPI_SCK_PIN 14
  //#define MY_SOFT_SPI_MISO_PIN 16
  //#define MY_SOFT_SPI_MOSI_PIN 15
  // Arduino Mega
  #define MY_SOFT_SPI_SCK_PIN A0
  #define MY_SOFT_SPI_MISO_PIN A2
  #define MY_SOFT_SPI_MOSI_PIN A1
#endif  

// When W5100 is connected we have to move CE/CSN pins for NRF radio
#define MY_RF24_CE_PIN 5
#define MY_RF24_CS_PIN 6

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

// Enable MY_IP_ADDRESS here if you want a static ip address (no DHCP)
#define MY_IP_ADDRESS 192,168,100,10

// If using static ip you need to define Gateway and Subnet address as well
#define MY_IP_GATEWAY_ADDRESS 192,168,100,1
#define MY_IP_SUBNET_ADDRESS 255,255,0,0


// MQTT broker ip address.  
#define MY_CONTROLLER_IP_ADDRESS 192, 168, 100, 3

// The MQTT broker port to to open 
#define MY_PORT 1883      

 /*
// Flash leds on rx/tx/err
#define MY_LEDS_BLINKING_FEATURE
// Set blinking period
#define MY_DEFAULT_LED_BLINK_PERIOD 300

// Enable inclusion mode
#define MY_INCLUSION_MODE_FEATURE
// Enable Inclusion mode button on gateway
#define MY_INCLUSION_BUTTON_FEATURE
// 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 

#define MY_DEFAULT_ERR_LED_PIN 16  // Error led pin
#define MY_DEFAULT_RX_LED_PIN  16  // Receive led pin
#define MY_DEFAULT_TX_LED_PIN  16  // the PCB, on board LED
*/

#include <Ethernet.h>
#include <MySensor.h>

void setup() { 
}

void presentation() {
  // Present locally attached sensors here    
    sendSketchInfo(SKETCH_NAME, SKETCH_MAJOR_VERSION"."SKETCH_MINOR_VERSION);
}


void loop() {
  // Send locally attech sensors data here
}

m26872

I don't know any MQTT but apart from that I guess that it could be a problem with nRF, power or routing.

How's your MySensors net(s) look like? How many Nodes? Repeaters? Gateways?
As I understand it, you've now ruled out down to that it's a Gateway issue? Any other to test with? MQTT, Serial and Ethernet.
What does your Gateway etc look like i.e. What's your power source? Tried another? Filter (capacitors up to 200uF)? Battery (2AA) to nRF only, just for a test?
Tried different nRF radio modules? Tried another PA level (low) in the config file?
Have you cleared eeprom (routing table) of Nodes, Repeaters and Gateways? Any difference?
Tried to add delay (100-500ms) before and in between begin and presentation messages? (This could be an easy first step).

dakky

I'll try to answer as much as possible :D

My Network is quite simple at the moment: one gateway, one testnode
the reconnect problem seems to come from the gateway. when powering off the node for a while, reconnection goes out of the box
not really some other gateways for testing
my gateway is power via USB from my pc. Filter capacitor is at 4,7nF. I try to increase it.
Changed nrf already with no improvements. i'll try to set pa level to low. whats the impact of this? lower range? speed?
nope have not cleared any eeprom ... musst search for a howto
the delay in the gateway i assume?

thx ;) again

sundberg84

Hi dakky!

I would also guess power problems - but its just a guess.
I would try different power sources if possible.

dakky

hmmm i changed the filter cap to 100nF and powered off the gateway over night: today the node connected at once. I will test again later.

dakky

retested ... works.
Does the cap size has any "disadvantages"?

mfalkvidd

Larger caps react slower, so you might want to use both caps. The small will take care of small quick dips and the large will take care of larger slower dips.

dakky

ok i think this can be regarded as solved: have tested very many on/of roundtrips and with an 100nf and an additional 4,7nf cap it's rocking stable. Maybe this would be worth a sidenote here: http://www.mysensors.org/build/connect_radio

Strange behavior of connection Node => Gateway

8

11.7k

11.2k

113.0k