Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. Les
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Les

    @Les

    2
    Reputation
    19
    Posts
    135
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    Les Follow

    Best posts made by Les

    • Encryption with RFM69 [solved]

      Hey Everyone. I'm using the example sketch from Mysensors MQTT Gateway and node.
      I've added the standard RFM69HW items and the node sends data to the gateway.

      It would be nice to use signing/encryption so looking through the forums I found:

      #define MY_SECURITY_SIMPLE_PASSWD "123456789"
      #define MY_SIGNING_SOFT_RANDOMSEED_PIN A0
      

      Using A0 since it is the only analogue pin I have on the Wemos D1 mini.

      I pasted the same string to both the node and the gw and while I see they are trying to communicate but get SIGN FAIL.

      So I would like to ask if someone has seen a tutorial or knows what needs to be enable for encryption?

      posted in Troubleshooting
      Les
      Les
    • RE: Encryption with RFM69 [solved]

      @anticimex according to the documentation

      MY_SECURITY_SIMPLE_PASSWD Enables security (signing and encryption) without the need for personalization
      

      So the connection should be encrypted and signed without anything else (other than putting the same define statement on all nodes with the same password).

      posted in Troubleshooting
      Les
      Les

    Latest posts made by Les

    • RE: Neighbor kicking me off my own mysensor network?

      Or if there is at least a way to check if there is no network connection to force a reconnect. (rfm69)

      posted in Troubleshooting
      Les
      Les
    • Neighbor kicking me off my own mysensor network?

      As I am still new to mysensors I'm still testing. And I have an mysensors mqtt gateway and 1 node that sends a counter every second. I let it run and after a few minutes it stopped. Looking at the serial log on the gateway I see nothing strange. So I reset the node and watched the node's output. After a few minutes I saw this:

      155152 SGN:SKP:MSG CMD=3,TYPE=16
      155221 TSF:MSG:SEND,8-8-0-0,s=1,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK:
      155227 SGN:SGN:NCE REQ,TO=0
      155465 TSF:MSG:READ,209-71-52,s=165,c=2,t=50,pt=6,l=25,sg=1:9978A2FCDC377E7B58EE3EAE3CFE73C9691DF39531837A3FF0000000
      155475 !TSF:MSG:REL MSG,NREP
      155675 TSF:MSG:READ,0-0-8,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE>
      155680 SGN:SKP:MSG CMD=3,TYPE=17
      155683 SGN:NCE:FROM=0
      155685 SGN:BND:NONCE=C9C51E6F68377E7B58EE3EAE3CFE73C9691DF39531837A3FF0AAAAAAAAAAAAAA
      155694 SGN:BND:HMAC=C4012E67EE6AF3CAB7FFA958EBA46DF1D2DEC47B2C75C489925A34683F4B8D00
      155701 SGN:SGN:SGN
      155769 TSF:MSG:SEND,8-8-0-0,s=1,c=1,t=16,pt=4,l=4,sg=1,ft=0,st=OK:92
      156775 !MCO:SND:NODE NOT REG
      157778 !MCO:SND:NODE NOT REG
      

      Putting that in the parser it looks like another node (not mine) sent a msg which caused it to disconnect from my gateway.

      So I changed my network id and then got a similar result:

      421032 SGN:SKP:MSG CMD=3,TYPE=16
      421101 TSF:MSG:SEND,8-8-0-0,s=2,c=3,t=16,pt=0,l=0,sg=1,ft=0,st=OK:
      421107 SGN:SGN:NCE REQ,TO=0
      421331 TSF:MSG:READ,156-176-216,s=108,c=1,t=29,pt=6,l=25,sg=1:75C28949816EF1D6D27FD99A4D5303D67DA46283A7DE8171F5000000
      421342 !TSF:MSG:PVER,3!=2
      421548 TSF:MSG:READ,0-0-8,s=255,c=3,t=17,pt=6,l=25,sg=1:<NONCE>
      421554 SGN:SKP:MSG CMD=3,TYPE=17
      421557 SGN:NCE:FROM=0
      421559 SGN:BND:NONCE=F3E9E79AB06EF1D6D27FD99A4D5303D67DA46283A7DE8171F5AAAAAAAAAAAAAA
      421567 SGN:BND:HMAC=6AC3B09CFFC889990700C30211E3B02F63CEE0B2D5B401CDB85E51FB055B985C
      421575 SGN:SGN:SGN
      421642 TSF:MSG:SEND,8-8-0-0,s=2,c=1,t=3,pt=4,l=4,sg=1,ft=0,st=OK:250
      422648 !MCO:SND:NODE NOT REG
      423651 !MCO:SND:NODE NOT REG
      

      So I guess my question is this a neighboring node that I'm picking up and can I force my node to only communicate with my gateway?

      For reference I did enable MY_SECURITY_SIMPLE_PASSWD so it should have been encrypted and signed.

      posted in Troubleshooting
      Les
      Les
    • RE: Encryption with RFM69 [solved]

      I added the following to the top of my code:
      #define MY_DEBUG
      #define MY_DEBUG_VERBOSE_SIGNING
      #define MY_SECURITY_SIMPLE_PASSWD "testpass"

      And it works now....not sure if having the Security above the radio information helped, but it does work now 🙂

      posted in Troubleshooting
      Les
      Les
    • RE: Encryption with RFM69 [solved]

      @kimot Ok, thanks for that info, I thought with MY_SECURITY_SIMPLE_PASSWD you didn't need to personalize. If I'm reading the instruction properly flash securitypersonal.ino to device, copy out the key and then paste to all nodes. Which sounds simple. Have I missed anything?

      posted in Troubleshooting
      Les
      Les
    • RE: Encryption with RFM69 [solved]

      @anticimex said in Encryption with RFM69:

      roubleshooting section in the docs regarding signibg iss

      I see that now, will give it a shot.

      posted in Troubleshooting
      Les
      Les
    • RE: Encryption with RFM69 [solved]

      @anticimex according to the documentation

      MY_SECURITY_SIMPLE_PASSWD Enables security (signing and encryption) without the need for personalization
      

      So the connection should be encrypted and signed without anything else (other than putting the same define statement on all nodes with the same password).

      posted in Troubleshooting
      Les
      Les
    • RE: Encryption with RFM69 [solved]

      @anticimex Thanks for the tips. I did review those pages and based on that it seems that #define MY_SECURITY_SIMPLE_PASSWD "yourpassword" is all that would be required unless you would like to personalize. I would like to keep it simple though.

      posted in Troubleshooting
      Les
      Les
    • Encryption with RFM69 [solved]

      Hey Everyone. I'm using the example sketch from Mysensors MQTT Gateway and node.
      I've added the standard RFM69HW items and the node sends data to the gateway.

      It would be nice to use signing/encryption so looking through the forums I found:

      #define MY_SECURITY_SIMPLE_PASSWD "123456789"
      #define MY_SIGNING_SOFT_RANDOMSEED_PIN A0
      

      Using A0 since it is the only analogue pin I have on the Wemos D1 mini.

      I pasted the same string to both the node and the gw and while I see they are trying to communicate but get SIGN FAIL.

      So I would like to ask if someone has seen a tutorial or knows what needs to be enable for encryption?

      posted in Troubleshooting
      Les
      Les
    • RE: Getting started with Wemos d1 mini & RFM69HW

      Yes D8 = pin 15 🙂

      So any ideas on why the raspberry pi isn't sending parent information or "listening/responding" to the wemos?

      As a side sanity check I will try a different raspberry pi. Can someone confirm the pins on Pi2/3?
      Power - 1
      Mosi -19
      Miso -21
      DIO - 22
      Clk - 23
      NSS - 24
      GND - 25

      posted in Troubleshooting
      Les
      Les
    • RE: Getting started with Wemos d1 mini & RFM69HW

      Also I should mention I saw in the posts it says that some version of raspbian don't play with MySensors, so I've used main branch 2.3.1 and development 2.3.2 beta on Pi. Same results.

      posted in Troubleshooting
      Les
      Les