in your IDE go to tools -> boards: "..." -> board manager and there select Arduino AVR board in the correct version.

Hey there,

I'm planing to use mysensors a litte 'off-label':
instead of monitoring sensors I try to build a counting system for sports. My brother is organizing sports tournaments with several matches running simultaneous. At the moment I'm trying to get the electronics working, but thats another point.
We want to see the status of all matches at a central laptop and get the final status (points, statistics,...) after the match has finished. He has a software doing the organisation of players, matchmaking and online statistics. This data might get exported as xml or similar (has to be discussed with the software developer yet).
My idea was to get a controller that is able to store a big amount of string entries for the database (player names) and the matches to play all imported from xml (maybe with some kind of import script?). Then the controller should be able to start a specific match (with unique ID) at one specific node (counting unit at the playside). Optional it would also transfer some strings maybe for announcement ("Player 1 vs Player 2 --- game starts") on the display of the unit.
As I don't know most of the controllers my question is if there is one (or more) capable of doing something like that? I know transmitting points is not the problem, thats just sending integers. I think the tricky thing is assigning a match ID to a node and get the reported points back to the right match.
I'm using pimatic at the moment and could not thing about a solution with this controller. I though about having one device for each match with associated string entries for names and integer values for points, but getting the data from the node (wich is running one match at a time) to the correct match seems difficult to me. If someone knows a good way that would be fine, as I know how to use pimatic and it has good scripting support.

Best would be if this controller is running on windows, so it could run on the already existing laptop. If it's linux only I would have to add a RPi and connect to that.

I'm grateful for any kind of tips/hints.

@ndiwan you can check what kind of usb interface chip your nano clone uses: look at the bottom side of your nano, there should be only one chip. If it is a ch340 you will need the drivers given by Al.

ok, what is the behavior if there is no ACK coming back? Trying again for several times before discarding the message? How long is the timeout?

@robosensor you could try nodered. It can connect multiple inputs (mqtt, tcp,...) and merge it to a single serial output and vice versa. You might have to add some logic, but that shouldn't be a problem.

Could you please post the versions of your ESP8266 library and MySensors library? As mfalkvidd said I had a similar problem and could fix it with newest versions for the ESP8266 gateway (no need to upgrade the nodes if not wanted).

OK i found the problem, I misunderstood something. I thought I have to add the keys to the enabling command of USER_SOFT_KEY. but there are the real keys some lines below that with correct example how to look like. Now it works and I personalized my first node. Thanks a lot @Anticimex

to my last knowledge this feature is implemented but not working. If you want to see the serial monitor you have to connect physically.

@mfalkvidd you have to open pcbnew pcb designer first. That's the third icon in the row on the right side of your screenshot.

I updated my gateway to newest dev version and now my nodes are communicating correctly (not updated, still 1.5.3). So the problem seems to be gone in 2.0, but I think it would still be nice to know what caused it for those not willing to upgrade to dev branch.
For @netram and @kr0815 (and maybe others) who had similiar problems: dev branch fixes this issue.

Hey there,

I hope someone can help. I have a simple test setup with only one gateway and one node at the moment. I want them to communication with encryption enabled. As one of them has no easy access to serial lines I want to first set it up with #define MY_ENCRYPTION_SIMPLE_PASSWD "Test" I have this activated in both sketches.
The result is the node asking for an ID in loop all the time, but with different sensor numbers (why is there a sensor number in the ID_REQUEST, shouldn't it be 255?). But there is a pattern (tried multiple time with reboot on node and gateway), so it's not random... first I see 6 requests for ID with sensor 102, followed by sensor 4, 163, 67, 12, 176 (6 times each). My controller (MYSController) answers them all the time and I see the sending messages in the serial console of the gateway...
here the complete gateway log:

dhcp client start...
ip:192.168.38.131,mask:255.255.255.0,gw:192.168.38.1
7778 GWT:TIN:CONNECTING...
7939 GWT:TIN:IP: 192.168.38.131
7973 MCO:BGN:STP
7991 MCO:BGN:INIT OK,TSP=1
8019 TSM:READY:NWD REQ
8048 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
pm open,type:2 0
107269 GWT:TSA:C=0,CONNECTED
186214 TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
186278 TSF:MSG:BC
186297 TSF:MSG:FPAR REQ,ID=255
186329 TSF:PNG:SEND,TO=0
186355 TSF:CKU:OK
186374 TSF:MSG:GWL OK
186431 ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
202842 TSF:MSG:READ,255-255-0,s=102,c=3,t=3,pt=0,l=0,sg=0:
202912 GWT:RFC:C=0,MSG=255;102;3;0;4;2
202958 ?TSF:MSG:SEND,0-0-255-255,s=102,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
204480 TSF:MSG:READ,255-255-0,s=102,c=3,t=3,pt=0,l=0,sg=0:
204546 GWT:RFC:C=0,MSG=255;102;3;0;4;2
204592 ?TSF:MSG:SEND,0-0-255-255,s=102,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
206120 TSF:MSG:READ,255-255-0,s=102,c=3,t=3,pt=0,l=0,sg=0:
206187 GWT:RFC:C=0,MSG=255;102;3;0;4;2
206233 ?TSF:MSG:SEND,0-0-255-255,s=102,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
207760 TSF:MSG:READ,255-255-0,s=102,c=3,t=3,pt=0,l=0,sg=0:
207826 GWT:RFC:C=0,MSG=255;102;3;0;4;2
207872 ?TSF:MSG:SEND,0-0-255-255,s=102,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
209399 TSF:MSG:READ,255-255-0,s=102,c=3,t=3,pt=0,l=0,sg=0:
209467 GWT:RFC:C=0,MSG=255;102;3;0;4;2
209512 ?TSF:MSG:SEND,0-0-255-255,s=102,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
211041 TSF:MSG:READ,255-255-0,s=102,c=3,t=3,pt=0,l=0,sg=0:
211108 GWT:RFC:C=0,MSG=255;102;3;0;4;2
211153 ?TSF:MSG:SEND,0-0-255-255,s=102,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
229260 TSF:MSG:READ,255-255-0,s=4,c=3,t=3,pt=0,l=0,sg=0:
229325 GWT:RFC:C=0,MSG=255;4;3;0;4;2
229369 ?TSF:MSG:SEND,0-0-255-255,s=4,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
230903 TSF:MSG:READ,255-255-0,s=4,c=3,t=3,pt=0,l=0,sg=0:
230968 GWT:RFC:C=0,MSG=255;4;3;0;4;2
231012 ?TSF:MSG:SEND,0-0-255-255,s=4,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
232543 TSF:MSG:READ,255-255-0,s=4,c=3,t=3,pt=0,l=0,sg=0:
232608 GWT:RFC:C=0,MSG=255;4;3;0;4;2
232652 ?TSF:MSG:SEND,0-0-255-255,s=4,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
234183 TSF:MSG:READ,255-255-0,s=4,c=3,t=3,pt=0,l=0,sg=0:
234250 GWT:RFC:C=0,MSG=255;4;3;0;4;2
234294 ?TSF:MSG:SEND,0-0-255-255,s=4,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
235823 TSF:MSG:READ,255-255-0,s=4,c=3,t=3,pt=0,l=0,sg=0:
235890 GWT:RFC:C=0,MSG=255;4;3;0;4;2
235934 ?TSF:MSG:SEND,0-0-255-255,s=4,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
237463 TSF:MSG:READ,255-255-0,s=4,c=3,t=3,pt=0,l=0,sg=0:
237530 GWT:RFC:C=0,MSG=255;4;3;0;4;2
237573 ?TSF:MSG:SEND,0-0-255-255,s=4,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
255671 TSF:MSG:READ,255-255-0,s=163,c=3,t=3,pt=0,l=0,sg=0:
255740 GWT:RFC:C=0,MSG=255;163;3;0;4;2
255786 ?TSF:MSG:SEND,0-0-255-255,s=163,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
257312 TSF:MSG:READ,255-255-0,s=163,c=3,t=3,pt=0,l=0,sg=0:
257379 GWT:RFC:C=0,MSG=255;163;3;0;4;2
257425 ?TSF:MSG:SEND,0-0-255-255,s=163,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
258952 TSF:MSG:READ,255-255-0,s=163,c=3,t=3,pt=0,l=0,sg=0:
259022 GWT:RFC:C=0,MSG=255;163;3;0;4;2
259067 ?TSF:MSG:SEND,0-0-255-255,s=163,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
260592 TSF:MSG:READ,255-255-0,s=163,c=3,t=3,pt=0,l=0,sg=0:
260660 GWT:RFC:C=0,MSG=255;163;3;0;4;2
260705 ?TSF:MSG:SEND,0-0-255-255,s=163,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
262234 TSF:MSG:READ,255-255-0,s=163,c=3,t=3,pt=0,l=0,sg=0:
262301 GWT:RFC:C=0,MSG=255;163;3;0;4;2
262346 ?TSF:MSG:SEND,0-0-255-255,s=163,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
263875 TSF:MSG:READ,255-255-0,s=163,c=3,t=3,pt=0,l=0,sg=0:
263944 GWT:RFC:C=0,MSG=255;163;3;0;4;2
263990 ?TSF:MSG:SEND,0-0-255-255,s=163,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
282098 TSF:MSG:READ,255-255-0,s=67,c=3,t=3,pt=0,l=0,sg=0:
282165 GWT:RFC:C=0,MSG=255;67;3;0;4;2
282210 ?TSF:MSG:SEND,0-0-255-255,s=67,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
283735 TSF:MSG:READ,255-255-0,s=67,c=3,t=3,pt=0,l=0,sg=0:
283803 GWT:RFC:C=0,MSG=255;67;3;0;4;2
283848 ?TSF:MSG:SEND,0-0-255-255,s=67,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
285377 TSF:MSG:READ,255-255-0,s=67,c=3,t=3,pt=0,l=0,sg=0:
285443 GWT:RFC:C=0,MSG=255;67;3;0;4;2
285488 ?TSF:MSG:SEND,0-0-255-255,s=67,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
287018 TSF:MSG:READ,255-255-0,s=67,c=3,t=3,pt=0,l=0,sg=0:
287085 GWT:RFC:C=0,MSG=255;67;3;0;4;2
287129 ?TSF:MSG:SEND,0-0-255-255,s=67,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
288659 TSF:MSG:READ,255-255-0,s=67,c=3,t=3,pt=0,l=0,sg=0:
288725 GWT:RFC:C=0,MSG=255;67;3;0;4;2
288770 ?TSF:MSG:SEND,0-0-255-255,s=67,c=3,t=4,pt=0,l=1,sg=0,ft=0,st=OK:2
290300 TSF:MSG:READ,255-255-0,s=67,c=3,t=3,pt=0,l=0,sg=0:
290366 GWT:RFC:C=0,MSG=255;67;3;0;4;2

If I set the node ID in sketch, it seems to play "ping-pong" all the time... I don't understand why...

953628 TSF:MSG:READ,10-10-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
953689 TSF:MSG:PINGED,ID=10,HP=1
954954 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
955267 TSF:MSG:READ,10-10-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
955328 TSF:MSG:PINGED,ID=10,HP=1
956593 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
956906 TSF:MSG:READ,10-10-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
956967 TSF:MSG:PINGED,ID=10,HP=1
958232 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
958545 TSF:MSG:READ,10-10-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
958607 TSF:MSG:PINGED,ID=10,HP=1
959871 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
976723 TSF:MSG:READ,10-10-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
976784 TSF:MSG:PINGED,ID=10,HP=1
978048 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1
978361 TSF:MSG:READ,10-10-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
978423 TSF:MSG:PINGED,ID=10,HP=1
979687 !TSF:MSG:SEND,0-0-10-10,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=NACK:1

@SuperNinja you only need #define MY_SECURITY_SIMPLE_PASSWD "testpass". The other one would be needed for encryption wih personalization (so keys saved in eeprom or atsha-chip)

@Anticimex is there a way to give the SIMPLE_PASSWD in hex? As far as I understand the AES key in the personalizer sketch is a hex and the password in sketch would be ASCII. Therefor even if looking identical they would not match. Or do I have to create a password first and convert that to hex to be used in personalization...

wow... to be honest I didn't expected it to be so easy... what flags are those "under the hood" settings?

@Anticimex is there a way to use both methods in one network? So to personalize nodes with the AES key (0x12; 0x34; 0x56; 0x00;...) and use SIMPLE_PASSWD "123456" (or some other derivativ)?

@mfalkvidd I mean the two options #define MY_ENCRYPTION_SIMPLE_PASSWD and #define MY_RFM69_ENABLE_ENCRYPTION (with personalization before)

@Anticimex thank you for your answer. In my case I want to implement OTA with the online version with DualOptibootloader. This way, the node will be able to decrypt and store the new firmware in external flash. With the MYS Bootloader that would not be possible as far as I understood the thing...

@TRS-80 signing will also be added. But I want to be able to send messages unseen from the 'public' to my nodes... some of them are text-based and I don't want to be sniffed...

Hey there,

is there any significant difference between the two options for encryption? Does the simple one consumes more flash? Is it safe to use with OTA updates (should be, as all communication is encrypted)? Why should you bother with personalization in the first place or is it only the 'old grown' method?

Thanks for any contribution in advance,
Anduril

Just in the rare case I want to use it later (and I have encryption enabled in the whole mysensors network) I could theoretically write a sketch inspired by the personalizer to read the serial and send this as a payload to the gateway without anyone out there able to read.

I understand that. Two questions:
what about updating via OTA with whitelisting enabled? Everyone could sniff the new hexfile and read the serial of the whitelisted node, correct?
what about activating encryption? Would that prevent both of these cases? No one could read the hexfile or the send serial without knowing the AES key before.

that's sad.
Maybe it would be possible to write a sketch to read out the atsha serial and transmit it via mysensors... I will be looking into this further when in need of whitelisting. Until then I will just leave it as it is and only use signing and maybe encryption.

@Anticimex still the question: is there a way to find out a nodes whitelist serial later?