Ok. So my strange error was due to connecting GND to the wrong PIN.

I was connecting GND next to VCC on the side of the Pro Mini.
Accordning to pics on the MySensors homepage and to the marking of my Arduino that pin is GND.

But when connecting the FTDI with jumper cables I notice that PIN was marked with CTS.
So instead I connected GND to the pin one step out.
This PIN is also marked GND on my Arduino, and on the FTDI. But marked BLK on the pictures on MySensors home page.

So it seems that both these pins are GND on my board, because everything else was working fine except the reference for analogue pins.

So topic solved. Thanks for all input. And specally @gohan that made me use the jumper cables and therfore found the error.

Answering my self for info to others that finds this thread.

I finally did the upgrade anyway and:
It is NOT working in v4.970.

Update: It seems as heartbeat works in 4.9701 for S_DOOR, but not for S_MOTION or S_BINARY.

Ok... Sorry for bothering you... I have been testing several things now for an hour. And I found what was causing the errors, and it was my Asus router. A year ago when started this project apparently set up an dhcp rule for the gateway binding it to a certain ip when connecting. Some how this is the cause for not getting any IP at all.

Because now, when removing this rule, I am able to connect and receive IP adress in dynamic mode on.

It is strange because I have allot of other things that is getting manually assigned IP from the DHCP in the router, and they all works. But I guess this is to hard for me to find why the gateway is not working with this settings in the router..

Now I will get back to testing inclusion mode and traffic leds on the NodeMCU wifi gateway.

@mfalkvidd I have not started building it yet. Hopefully I will have some spare time tomorrow, otherwise it will be in a week or two. I will get back as soon as I have got it all up and running (with external radio traffic LED as well).

@gohan Well. I think I have found the problem. Investigating now. I will get back during the day when I have tested some more times.

I believed that adding this button to the gateway would set Domoticz to accept new hardware, when the button was pushed. But now that I have investigated some more it seems that this button is only used in Vera? Maybe there is a way to add this function in Domoticz, but that's for later.

Anyway; since I started this "issue" I want to finish it, even if I have no use of the button.

Is there any way to see if the gateway sends anything to the controller when I push the button?
I cant see anything on the serial output.

@zboblamont Yes. It looks like bad wiring. I am testing right now. And it looks like my Arduino clone has some bad markings of the pins.... I am documenting and posting the solution (if it is what I am suspecting right now) later today. Right now I am doing test cycles while doing some paid work..

@yveaux I'm a newbie when it comes to C++, but I have been coding for a long time in Python. I can't really see how I can change that code you are referring to to get the changes I am looking for.

But I found something in https://github.com/mysensors/MySensors/blob/development/core/MyGatewayTransportEthernet.cpp which I think is the code @mfalkvidd is reffering to.

So I think I someway need to change INDICATION_GW_TX and INDICATION_GW_RX in my sketch for my gateway.

Is that the way I should go if I don't change directly in the library code?

So. Forgot to get back.
But it was the Arduino it self that had gone bad. I switched the Arduino to a new, and everything was back to normal.

So I have been reading up alot. And yesterday I finally managed to upload a new bootloader to this ProMini. It was the optiboot that @bjacobse linked to. All worked fine without any errors.

But I must have been doing something wrong, because I am not able to upload any sketch to the Arduino after that. I only get not in sync errors.

Unfortunately I don't have time to continue on this until late next week...

Well. It was the radio that caused this false triggers. The final placement of the node must be in a radio shaddow.

I really "funny" thing is that I solved this problem by changing the radio. I had a NRF24L01+PA+LNA for better range. This was for future project (node in my greenhouse) which would need this node as a repeater for shore.
But by replacing the radio to a "normal" NRF24L01+ made the problem go away. I did not change the location!

@pjr I am still a noob when it comes to C. And I have not had the time to examine the Domoticz source code. But at first glance those lines seems as V_PERCENTAGE, V_SCENE_OFF, V_STOP and V_RGBW that updates the last seen on heartbeat.

I have had my node running now for 2 days just checking this heartbeat. And I can for shore sasy that is only working for the door sensor. Which presents it self as S_DOOR and sends V_TRIPPED messages.
It is not working for the motion sensor presenting it self as S_MOTION and also sends V_TRIPPED messages.

And one more really strange thing is that it is only working on the door sensor when the door is open. Not closed!

Update: It seems as heartbeat works in 4.9701 for S_DOOR, but not for S_MOTION or S_BINARY.

This is strange...

Last 24 hours I have had the node standing almost next to the gateway, and no false motion has been detected. So:

• Close to the gateway there is no false indication.
• Testing area in garage is no false indication.
• Final place in garage there is false indication.

PIR sensor is driven from 5V USB charger. All sensors are connected to the 5V charger as well as the Pro Mini. The radio is NRF24L01+PA+LNA connected to a AMS1117 5V-3.3V converter.
USB charger is capable to deliver 700mA. And if I calculate correct the node has a maximum of about 270 mA consumption.
So there should be more than enough power.

And why is it different due to location of the node? Does power consumption differs from radio depending on the quality of the radio connection to the gateway?

@yveaux Yes. I have understood that by reading up. But what I can't understand is that it not happens every time I use the radio. As it seems now it is only when the gateway is sending the discovery broadcast. Not when the node is sending data from the other sensors on the node, or when I send data to the node for operating the relays. Strange...

@electrik I disconnected the extender wires for reed. And it has been running all night like this. But no difference. So it can not be due to the extender wires.

@ahmedadelhosni Yes. This is a 5V sensor powered from a phone charger.

Hello,

I have been testing my latest node for a couple weeks. It's a node with a double relay, a DHT22, one reed switch and one motion sensor (HC-SR501), with repeater function. It is intended for maneuvering my garage door. And should be situated in my garage (of course) and the reason for repeater function is that I also have a temp node at my fridge in the garage that some times is not reaching my gateway. This new node is placed halfway between the gateway and fridge node.

It has been standing in the garage at the same distance as final mounting place and I have been logging the function. And all have been working perfectly.
But yesterday I mounted it and connected the garage door to the relay and extended the reed wires (4 meters), and now the motion sensor (not changed at all) is reporting motion every 20 minutes.

So last night I found this thread:
New nodes, new problems Motion sensor [Solved]
wich reports the exact same behavior.

But @xydix solved the problem with replacing the PIR from another model to the one I am using. Others suggest it is a power problem.
So I thought it was due to the reed switch. That was not tested at "closed" for a longer period under testing. Drawing current when the switch was closed.
But I disconnected it again, and no change. Still reporting motion every 20 minutes.

So:
Any one having any ideas what I should do next?
The only remaining differences from testing period is location. I was standing on a shelf before, and now it is placed in the sealing, with the same distance to the gateway (about 7 meters)

And if it is power issue due to radio radio transmissions (as suggested in the earlier mentioned thread) why is it only on discover request broadcast, and not when the node is sending data from DHT22 or reed, or when I send data to the node for maneuvering the relays?

@mfalkvidd Thanks! Don't think I found that page before. Found a lot of pages about this subject but not this page. But if I understand it correct I still need to buy a new Arduino. I only have a big supply of Pro Minis. No other models.