mfalkvidd
Please stand down, problem is resolved. When I return to a peaceful place, I will fill in the details.

BTW... Thank you for your quick responses... your suggestion re: look behind the hardware kept the boards off the target range.

Issue resolution: When the W5100 card silkscreen says +5V, it means it! Disconnected W5100 +5 pin from 3.3 Arduino and connected +5V and GND directly to power supply.... a glorious city of lights!

I reviewed the guides to see if this was something I had missed but 3.3V is clearly stated as the proper connection. If these boards have version numbers on the silkscreen, I can't find it.

I would like to suggest that you change this topic description to something more fitting so when someone else is presented with this same opportunity a port closure issue doesn't confuse the problem. I looked for an "edit" menu but, again, I can't find it.

As always, the solution is simple. Finding the actual problem is what is complex. It ain't what you don't know, it is what you're absolutely certain of that just ain't so what get's ya!

Thanks for you help, mfalkvidd. In spite of this rough start, being able to get assistance like yours encourages me about this adventure.

I restarted Domoticz for a non-related reason and the issue ceased. I have tried to create the sequence of events that led to the problem the first time but at present Domoticz logs are quite and things are working as they should.

I have the following setup:

Domoticz controller
Ethernet gateway/W5100/NRF24L01+
Prototyped Relay Controller

All hardware(Arduino, W5100, NRF24L01+) is powered from a power bus with stepdown regulators for the radio. The power supply is a converted AT 300W supply so I would say the power is clean and current is not constrained. The MySensors code is 1.6 and not altered in any way.

According to the Domoticz log, the TCP connection to the gateway is reset after connecting for only about 500 msec. Domoticz then "says" it will re-establish the connection in 30 seconds, although this timeline does not seem to be supported by the log. The physical 30 second delay occurs between these two lines:

2016-05-28 09:07:24.715 MySensors: Gateway Version: 1.5.4
2016-05-28 09:07:52.423 TCP: Reconnecting...

After re-establishing the connection it will be reset again in ~500 msec. This repeats ad infinitum

Domoticz log:

2016-05-28 07:08:15.273 MySensors: connected to: 192.168.1.65:5003
2016-05-28 07:08:16.273 MySensors: Gateway Ready...
2016-05-28 07:08:16.273 MySensors: Gateway Version: 1.5.4
2016-05-28 07:08:17.274 MySensors: Gateway Version: 1.5.4
2016-05-28 07:08:35.669 MySensors: trying to connect to: 192.168.1.65:5003
2016-05-28 07:08:36.669 MySensors: connected to: 192.168.1.65:5003
2016-05-28 07:08:37.278 MySensors: Connection reset!
2016-05-28 07:08:37.278 TCP: Reconnecting in 30 seconds...
2016-05-28 07:08:38.670 MySensors: Gateway Ready...
2016-05-28 07:08:38.670 MySensors: Gateway Version: 1.5.4
2016-05-28 07:08:39.671 MySensors: Gateway Version: 1.5.4
2016-05-28 07:09:07.277 User: Admin initiated a switch command
2016-05-28 07:09:07.278 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:09:07.285 TCP: Reconnecting...
2016-05-28 07:09:08.285 MySensors: connected to: 192.168.1.65:5003
2016-05-28 07:09:08.676 MySensors: Connection reset!
2016-05-28 07:09:08.677 TCP: Reconnecting in 30 seconds...
2016-05-28 07:09:10.286 MySensors: Gateway Ready...
2016-05-28 07:09:10.286 MySensors: Gateway Version: 1.5.4
2016-05-28 07:09:11.287 MySensors: Gateway Version: 1.5.4
2016-05-28 07:09:15.348 User: Admin initiated a switch command
2016-05-28 07:09:15.349 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:09:19.908 User: Admin initiated a switch command
2016-05-28 07:09:19.909 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:09:22.707 User: Admin initiated a switch command
2016-05-28 07:09:22.708 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:09:25.207 User: Admin initiated a switch command
2016-05-28 07:09:25.208 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:09:38.683 TCP: Reconnecting...
2016-05-28 07:09:39.683 MySensors: connected to: 192.168.1.65:5003
2016-05-28 07:09:40.293 MySensors: Connection reset!
2016-05-28 07:09:40.293 TCP: Reconnecting in 30 seconds...
2016-05-28 07:09:41.684 MySensors: Gateway Ready...
2016-05-28 07:09:41.684 MySensors: Gateway Version: 1.5.4
2016-05-28 07:09:42.685 MySensors: Gateway Version: 1.5.4

The led representing the relay continues to operate (affirmed visually) from Domoticz throughout this trauma as indicated by this log section:

2016-05-28 07:13:57.352 TCP: Reconnecting...
2016-05-28 07:13:58.353 MySensors: connected to: 192.168.1.65:5003
2016-05-28 07:13:58.739 MySensors: Connection reset!
2016-05-28 07:13:58.739 TCP: Reconnecting in 30 seconds...
2016-05-28 07:14:00.353 MySensors: Gateway Ready...
2016-05-28 07:14:00.354 MySensors: Gateway Version: 1.5.4
2016-05-28 07:14:01.354 MySensors: Gateway Version: 1.5.4
2016-05-28 07:14:07.971 User: Admin initiated a switch command
2016-05-28 07:14:07.973 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:10.151 User: Admin initiated a switch command
2016-05-28 07:14:10.153 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:11.630 User: Admin initiated a switch command
2016-05-28 07:14:11.631 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:13.871 User: Admin initiated a switch command
2016-05-28 07:14:13.872 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:15.498 User: Admin initiated a switch command
2016-05-28 07:14:15.499 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:17.683 User: Admin initiated a switch command
2016-05-28 07:14:17.684 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:19.470 User: Admin initiated a switch command
2016-05-28 07:14:19.471 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:21.391 User: Admin initiated a switch command
2016-05-28 07:14:21.392 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:23.030 User: Admin initiated a switch command
2016-05-28 07:14:23.031 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:25.238 User: Admin initiated a switch command
2016-05-28 07:14:25.239 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:27.337 User: Admin initiated a switch command
2016-05-28 07:14:27.338 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:28.745 TCP: Reconnecting...
2016-05-28 07:14:29.050 User: Admin initiated a switch command
2016-05-28 07:14:29.051 (Mysensors Gateway) Lighting 2 (Light)
2016-05-28 07:14:29.745 MySensors: connected to: 192.168.1.65:5003
2016-05-28 07:14:30.360 MySensors: Connection reset!
2016-05-28 07:14:30.361 TCP: Reconnecting in 30 seconds...
2016-05-28 07:14:31.746 MySensors: Gateway Ready...
2016-05-28 07:14:31.746 MySensors: Gateway Version: 1.5.4
2016-05-28 07:14:32.747 MySensors: Gateway Version: 1.5.4

This is strange since the log indicates that there is no TCP connection!

Based on recent experiences with this forum and the below referenced similar issues I am not banking on a helpful response here but I thought I would try before tossing all this hardware in the trash.

1. Is the TCP connection actually reset or is the code reporting non-issues?

2. Which code, Domoticz or MySensors, would report Connection Reset when there seems to be an established connection?

See similar issues not responded to :

https://forum.mysensors.org/topic/3567/wifi-gateway-nodemcu-0-9-always-reset

https://forum.mysensors.org/topic/3256/reset-problem-with-ethernet-gateway-and-a-sensor

https://forum.mysensors.org/topic/3222/arduino-mysensors-w5100-gateway-closing-tcp-connection-2us-not-2ms-after-each-sending-of-data

Just echoing the 12V fried silicon. Specs don't really apply to these components, that is why they are not published. I smoked a Nano on 12V in less time than it takes to think "This might work"

I have 10 radios. Two were prototyped to verify and then soldered into enclosures. Three days ago I could not sleep and decided to work on this issue for a bit. Going over the same steps I have gone over multiple times, suddenly, miraculously, the communications started to work. For 15 glorious minutes I clicked an icon on the computer and the relay operated. Then the clock struck midnight and they turned back into pumpkins! I am not making any of this up.

Of the remaining 8 radios and 4 or 5 arduinos I have used every software library I can find to try to figure this out. None are diagnostic. Each presumes that the radios, arduinos and stars align and they just work OoB. GettingStarted seems to be the most universally used for radio validation. Using this code and the wiring recommended for it, I can get none of the 8 radios to get past these lines of code:

unsigned long start_time = micros(); // Take the time, and send it. This will block until complete
if (!radio.write( &start_time, sizeof(unsigned long) )){
Serial.println(F("failed"));

This means to me that none of the radio's and/or none of the arduino's and/or none of the power configurations work.

Respectfully, if this is a wiring issue, then you can tie me up and paint me blue! I will be blue-fully happy to have finally been shown the truth.

Is there anyone still in here or should I just turn out the lights when I leave?

Radio wiring photo crapped out:


I get 405 Error Not Allowed each time I try to upload this image.

Update:18:30hrs
GettingStarted.ino from this site https://arduino-info.wikispaces.com/Nrf24L01-2.4GHz-HowTo runs the radio just fine utilizing the arduino pin hookup TMRh20 RF24 Library. This is looking like a software issue or a pin out error.

I am working this problem from the prototype board since the relay components are now soldered in and mounted in a case. The same issue exists with each set of components... i.e. soldered in and prototype have the same serial debut outputs.

This is the prototype. I have replaced the leads according to the color coding at https://www.mysensors.org/build/connect_radio for trace-ability. I confirmed that the serial debug responses are the same after the rewire. The cap on the radio power is 10uF, this is all I have. I have also tried 68uF with the same results. Recommendations for the size of this component vary by 4 orders of magnitude across MySensors forum. In my uneducated opinion, cap should not matter for initialization.


Closeup of the Mini wired for the RelayActuator.ino.

Closeup of the radio connections:

Serial Debug output of this configuration:radio init fail

Mini rewired for EthernetGateway.ino

Enable soft_spi in myconfig.h and flash the Mini with EthernetGateway.ino, this is the Serial Debug output:
0;0;3;0;9;gateway started, id=0, parent=0, distance=0

Same hardware... same wires... same power supply... different software and wiring for software.

Please instruct on method for uploading images. Please be specific as I can find no instructions.

I have two modules:

1. Ethernet Gateway w/Clone Nano, W5100 and NRF24L01+
   Flashing this module with EthernetGateway.ino and opening serial debug I get this:

0;0;3;0;9;gateway started, id=0, parent=0, distance=0
0;0;3;0;14;Gateway startup complete.
Finished
0;0;3;0;2;0;0;3;0;2;1.5.4
Finished
0;0;3;0;2;Get Version0;0;3;0;2;1.5.4
Finished
0;0;3;0;18;PINGFinished
0;0;3;0;18;PINGFinished

Which I think means everything is working and the PING is a response to Domoticz request for setup.

1. Relay Module w/Clone Mini Pro, NRF24L01+ and 5/3.3 voltage regulator
   Flashing the module with RelayActuator.ino and stating Serial monitor I get:

radio init fail

So, after two days of checking power, wiring, re-flowing solder, changing radios and researching issues, I decide to flash the Relay Module with EthernetGateway.ino, since I can't think of anything else to do. Rearranging radio wiring for the EthernetGateway(since it is different) and using the EXACT SAME HARDWARE, I flash it with EthernetGateway.ino and get this:

0;0;3;0;9;gateway started, id=0, parent=0, distance=0

Which I think means the radio is working.

I then reflash the EXACT SAME HARDWARE using the EthernetGateway radio wiring with the RelayActuator.ino and I get this:

radio init fail

Which I expected. All hardware was prototyped and verified to work with Domoticz before soldering onto PCB. Only change was to the Ethernet Gateway Nano which lasted about 3 seconds on the 12V power I had planned to run it with.

Ideas?