@sindrome73 assuming you have executed the personalizer sketch with your generated keys on both the gateway and the node(s), then yes. You can always see in the log if signing is being used. There is a parser for the log on the homepage.
@gohan Maybe: RFM69 and RFM95 have a software-based packet engine responsible for the ACK handling, i.e. with extreme clock differences between node and GW, TX from (fast) GW may occur before the radio of the (slow) node is in RX, that's why we introduced additional delays for faster CPUs. I had no issues running the code on RPI1 (0.7GHz) and RPI2 (0.9GHz), but I do not have a RPI3(1.2GHz) where additional timing optimizations may be needed.
@mario64 It does not work as a repeater, it registers via Domoticz as a node with a child ID of 255 (Internal effectively) under Setup/Hardware/Nodes, sometimes listed as a Repeater.
It baffled me originally as I have no repeaters nor a need for them, but that is what Domoticz does. Since you can activate which child sensors are active under Domoticz, you can simply ignore them anyway.
Not sure if you have figured this out yet without reading back to confirm it, but until you send a sensor reading after presentation the device will not show up within Domoticz and remains in the background....
I beg your pardon if i took long to reappear, but i spent a long time trying to complete the board design. Even today it's still a work in progress thing, i had to resort to 3 layer autorouting to get it "finished", and i say "finished" because i'm still aware it needs some further development, but now it's a matter of building it.
The problem i have is: ended into a 3 layer pcb, but the goal of this project is to be a single layer bridged by wire linking board, so it can be made using normal electronic tools and not technology from outer space. i could even get the drawings of each layer wich i published into the github repository as svg files.
The problem i need to discuss is: how could 4 layers of wires be turned into a single one cutting the traces that would cross so they can be resolved by wire links?
You can see the svg layers here: https://github.com/temporaryuser132/wakameboard/tree/master/gerbertosvg
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.
I'm afraid I don't know enough about the hardware to answer. I didn't have any luck with the RFM69 on the Nano, so I switched to the 3.3V ProMini. I used a Moteino USB for my serial gateway. It's a more expensive option, but it was easy to implement and has been very reliable.
@mfalkvidd , yes, I see. As I wrote in the first post I was using https://github.com/mysensors/MySensors/tree/development/examples/SecurityPersonalizer code.
I checked with the Personizer code in the Library examples - it does compile, thanks.
What I find a bit confusing - in the sketch in exampla library you have to make two keys - USER_SOFT_KEY and USER_KEY (when you do not use hw hashing, and when you do).
I have mixed configurations. Should those keys be the same in my network for mixed configuration to work?
thanks for help and sorry for confusion