Best posts made by Strixx

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.

Did some more research. And it seems to me now that it was Domoticz that somehow messed up the ID. Even after clearing the EEPROM and flashed the node with a new sketch specifying what ID to use, it did not show up in Domoticz. So I had a look in Domoticz database. And in the table "MySenors" everything looked as it should, but in table "MySensorsChilds" there was children to nodes not existing in the first table or in reality.
By removing those lines in the database, it started working again.

Can be that I have been adding children to this new node between tests?

Anyway; my conclusion is that it is safer to manually assign ID myself, when building and testing new nodes.