Navigation

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

    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
    • RE: Getting started with Wemos d1 mini & RFM69HW

      I'm going to take a stab in the dark that the issue is with the pi node since the wemos received and sent and I don't see any message on the pi for anything being received.

      With the debuging enabled on the client I get:

      
       __  __       ____
      |  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
      | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
      | |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
      |_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
              |___/                      2.3.1
      
      12703 MCO:BGN:INIT NODE,CP=RPNNE---,REL=255,VER=2.3.1
      12893 TSM:INIT
      12908 TSF:WUR:MS=0
      12928 RFM69:INIT
      12946 RFM69:INIT:PIN,CS=15,IQP=5,IQN=5
      12988 RFM69:PTX:LEVEL=5 dBm
      13017 RFM69:DUMP:Registers Address | HEX value 
      13067 RFM69:DUMP:REG=0x01 Value=0x04
      13106 RFM69:DUMP:REG=0x02 Value=0x00
      13145 RFM69:DUMP:REG=0x03 Value=0x02
      13183 RFM69:DUMP:REG=0x04 Value=0x40
      13222 RFM69:DUMP:REG=0x05 Value=0x03
      13261 RFM69:DUMP:REG=0x06 Value=0x33
      13300 RFM69:DUMP:REG=0x07 Value=0xe4
      13338 RFM69:DUMP:REG=0x08 Value=0xc0
      13377 RFM69:DUMP:REG=0x09 Value=0x00
      13416 RFM69:DUMP:REG=0x0a Value=0x41
      13454 RFM69:DUMP:REG=0x0b Value=0x00
      13493 RFM69:DUMP:REG=0x0c Value=0x02
      13532 RFM69:DUMP:REG=0x0d Value=0x92
      13570 RFM69:DUMP:REG=0x0e Value=0xf5
      13609 RFM69:DUMP:REG=0x0f Value=0x20
      13648 RFM69:DUMP:REG=0x10 Value=0x24
      13687 RFM69:DUMP:REG=0x11 Value=0x57
      13725 RFM69:DUMP:REG=0x12 Value=0x09
      13764 RFM69:DUMP:REG=0x13 Value=0x1a
      13803 RFM69:DUMP:REG=0x14 Value=0x40
      13841 RFM69:DUMP:REG=0x15 Value=0xb0
      13880 RFM69:DUMP:REG=0x16 Value=0x7b
      13919 RFM69:DUMP:REG=0x17 Value=0x9b
      13958 RFM69:DUMP:REG=0x18 Value=0x88
      13996 RFM69:DUMP:REG=0x19 Value=0xe2
      14035 RFM69:DUMP:REG=0x1a Value=0xe2
      14074 RFM69:DUMP:REG=0x1b Value=0x40
      14112 RFM69:DUMP:REG=0x1c Value=0x80
      14151 RFM69:DUMP:REG=0x1d Value=0x06
      14190 RFM69:DUMP:REG=0x1e Value=0x10
      14229 RFM69:DUMP:REG=0x1f Value=0x00
      14267 RFM69:DUMP:REG=0x20 Value=0x00
      14306 RFM69:DUMP:REG=0x21 Value=0x00
      14345 RFM69:DUMP:REG=0x22 Value=0x00
      14383 RFM69:DUMP:REG=0x23 Value=0x02
      14422 RFM69:DUMP:REG=0x24 Value=0xff
      14461 RFM69:DUMP:REG=0x25 Value=0x40
      14499 RFM69:DUMP:REG=0x26 Value=0x07
      14538 RFM69:DUMP:REG=0x27 Value=0x80
      14577 RFM69:DUMP:REG=0x28 Value=0x00
      14616 RFM69:DUMP:REG=0x29 Value=0xe4
      14654 RFM69:DUMP:REG=0x2a Value=0x00
      14693 RFM69:DUMP:REG=0x2b Value=0x00
      14732 RFM69:DUMP:REG=0x2c Value=0x00
      14770 RFM69:DUMP:REG=0x2d Value=0x03
      14809 RFM69:DUMP:REG=0x2e Value=0x88
      14848 RFM69:DUMP:REG=0x2f Value=0x2d
      14886 RFM69:DUMP:REG=0x30 Value=0x64
      14925 RFM69:DUMP:REG=0x31 Value=0x00
      14964 RFM69:DUMP:REG=0x32 Value=0x00
      15003 RFM69:DUMP:REG=0x33 Value=0x00
      15041 RFM69:DUMP:REG=0x34 Value=0x00
      15080 RFM69:DUMP:REG=0x35 Value=0x00
      15119 RFM69:DUMP:REG=0x36 Value=0x00
      15157 RFM69:DUMP:REG=0x37 Value=0xd4
      15196 RFM69:DUMP:REG=0x38 Value=0x40
      15235 RFM69:DUMP:REG=0x39 Value=0xff
      15274 RFM69:DUMP:REG=0x3a Value=0xff
      15312 RFM69:DUMP:REG=0x3b Value=0x00
      15351 RFM69:DUMP:REG=0x3c Value=0x05
      15390 RFM69:DUMP:REG=0x3d Value=0x10
      15428 RFM69:DUMP:REG=0x3e Value=0x00
      15467 RFM69:DUMP:REG=0x3f Value=0x00
      15506 RFM69:DUMP:REG=0x40 Value=0x00
      15544 RFM69:DUMP:REG=0x41 Value=0x00
      15583 RFM69:DUMP:REG=0x42 Value=0x00
      15622 RFM69:DUMP:REG=0x43 Value=0x00
      15661 RFM69:DUMP:REG=0x44 Value=0x00
      15699 RFM69:DUMP:REG=0x45 Value=0x00
      15738 RFM69:DUMP:REG=0x46 Value=0x00
      15777 RFM69:DUMP:REG=0x47 Value=0x00
      15815 RFM69:DUMP:REG=0x48 Value=0x00
      15854 RFM69:DUMP:REG=0x49 Value=0x00
      15893 RFM69:DUMP:REG=0x4a Value=0x00
      15931 RFM69:DUMP:REG=0x4b Value=0x00
      15970 RFM69:DUMP:REG=0x4c Value=0x00
      16009 RFM69:DUMP:REG=0x4d Value=0x00
      16048 RFM69:DUMP:REG=0x4e Value=0x01
      16086 RFM69:DUMP:REG=0x4f Value=0x00
      16125 TSM:INIT:TSP OK
      16148 TSM:FPAR
      16164 RFM69:SWR:SEND,TO=255,SEQ=0,RETRY=0
      16209 RFM69:CSMA:RSSI=-36
      16236 RFM69:CSMA:RSSI=-36
      16264 RFM69:CSMA:RSSI=-36
      16291 RFM69:CSMA:RSSI=-36
      16318 RFM69:CSMA:RSSI=-36
      16345 RFM69:CSMA:RSSI=-36
      16373 RFM69:CSMA:RSSI=-36
      16400 RFM69:CSMA:RSSI=-36
      16427 RFM69:CSMA:RSSI=-36
      16454 RFM69:CSMA:RSSI=-36
      16482 RFM69:CSMA:RSSI=-36
      16509 RFM69:CSMA:RSSI=-36
      16536 RFM69:CSMA:RSSI=-36
      16564 RFM69:CSMA:RSSI=-36
      16591 RFM69:CSMA:RSSI=-36
      16618 RFM69:CSMA:RSSI=-36
      16645 RFM69:CSMA:RSSI=-36
      16673 RFM69:CSMA:RSSI=-36
      16700 RFM69:CSMA:RSSI=-36
      16730 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      18810 !TSM:FPAR:NO REPLY
      18836 TSM:FPAR
      18851 RFM69:SWR:SEND,TO=255,SEQ=1,RETRY=0
      18897 RFM69:CSMA:RSSI=-36
      18924 RFM69:CSMA:RSSI=-36
      18951 RFM69:CSMA:RSSI=-36
      18978 RFM69:CSMA:RSSI=-36
      19006 RFM69:CSMA:RSSI=-36
      19033 RFM69:CSMA:RSSI=-36
      19060 RFM69:CSMA:RSSI=-36
      19087 RFM69:CSMA:RSSI=-36
      19115 RFM69:CSMA:RSSI=-36
      19142 RFM69:CSMA:RSSI=-36
      19169 RFM69:CSMA:RSSI=-36
      19196 RFM69:CSMA:RSSI=-36
      19224 RFM69:CSMA:RSSI=-36
      19251 RFM69:CSMA:RSSI=-36
      19278 RFM69:CSMA:RSSI=-36
      19305 RFM69:CSMA:RSSI=-36
      19333 RFM69:CSMA:RSSI=-36
      19360 RFM69:CSMA:RSSI=-36
      19387 RFM69:CSMA:RSSI=-36
      19418 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      20911 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
      21497 !TSM:FPAR:NO REPLY
      21523 TSM:FPAR
      21538 RFM69:SWR:SEND,TO=255,SEQ=2,RETRY=0
      21584 RFM69:CSMA:RSSI=-36
      21611 RFM69:CSMA:RSSI=-36
      21638 RFM69:CSMA:RSSI=-36
      21665 RFM69:CSMA:RSSI=-36
      21693 RFM69:CSMA:RSSI=-36
      21720 RFM69:CSMA:RSSI=-36
      21747 RFM69:CSMA:RSSI=-36
      21774 RFM69:CSMA:RSSI=-36
      21802 RFM69:CSMA:RSSI=-36
      21829 RFM69:CSMA:RSSI=-36
      21856 RFM69:CSMA:RSSI=-36
      21883 RFM69:CSMA:RSSI=-36
      21911 RFM69:CSMA:RSSI=-36
      21938 RFM69:CSMA:RSSI=-36
      21965 RFM69:CSMA:RSSI=-36
      21992 RFM69:CSMA:RSSI=-36
      22020 RFM69:CSMA:RSSI=-36
      22047 RFM69:CSMA:RSSI=-36
      22074 RFM69:CSMA:RSSI=-36
      22105 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      24184 !TSM:FPAR:NO REPLY
      24210 TSM:FPAR
      24225 RFM69:SWR:SEND,TO=255,SEQ=3,RETRY=0
      24271 RFM69:CSMA:RSSI=-36
      24298 RFM69:CSMA:RSSI=-36
      24325 RFM69:CSMA:RSSI=-36
      24352 RFM69:CSMA:RSSI=-36
      24380 RFM69:CSMA:RSSI=-36
      24407 RFM69:CSMA:RSSI=-36
      24434 RFM69:CSMA:RSSI=-36
      24461 RFM69:CSMA:RSSI=-36
      24489 RFM69:CSMA:RSSI=-36
      24516 RFM69:CSMA:RSSI=-36
      24543 RFM69:CSMA:RSSI=-36
      24570 RFM69:CSMA:RSSI=-36
      24598 RFM69:CSMA:RSSI=-36
      24625 RFM69:CSMA:RSSI=-36
      24652 RFM69:CSMA:RSSI=-36
      24679 RFM69:CSMA:RSSI=-36
      24707 RFM69:CSMA:RSSI=-36
      24734 RFM69:CSMA:RSSI=-36
      24761 RFM69:CSMA:RSSI=-36
      24792 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      26871 !TSM:FPAR:FAIL
      26893 TSM:FAIL:CNT=1
      26915 TSM:FAIL:DIS
      26934 TSF:TDI:TSL
      26953 RFM69:RSL
      

      On the pi, in /etc/mysensors.conf it has
      verbose=debug
      Not sure if it needs to be set elsewhere.

      Always produces this initialization, 1 sent message and just sits there.

      Jul 30 16:51:25 INFO  Starting gateway...
      Jul 30 16:51:25 INFO  Protocol version - 2.3.2-beta
      Jul 30 16:51:25 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,FQ=NA,REL=6,VER=2.3.2-beta
      Jul 30 16:51:25 DEBUG TSF:LRT:OK
      Jul 30 16:51:25 DEBUG TSM:INIT
      Jul 30 16:51:25 DEBUG TSF:WUR:MS=0
      Jul 30 16:51:25 DEBUG TSM:INIT:TSP OK
      Jul 30 16:51:25 DEBUG TSM:INIT:GW MODE
      Jul 30 16:51:25 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
      Jul 30 16:51:25 DEBUG MCO:REG:NOT NEEDED
      Jul 30 16:51:25 DEBUG MCO:BGN:STP
      Jul 30 16:51:25 DEBUG MCO:BGN:INIT OK,TSP=1
      Jul 30 16:51:25 DEBUG GWT:RMQ:CONNECTING...
      Jul 30 16:51:25 DEBUG connected to 127.0.0.1
      Jul 30 16:51:25 DEBUG GWT:RMQ:OK
      Jul 30 16:51:25 DEBUG GWT:TPS:TOPIC=mysensors-out/0/255/0/0/18,MSG SENT
      Jul 30 16:51:25 DEBUG TSM:READY:NWD REQ
      Jul 30 16:51:27 DEBUG ?TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      
      posted in Troubleshooting
      Les
      Les
    • RE: Getting started with Wemos d1 mini & RFM69HW

      also worth noting I am manually running sudo bin/mysgw not as a service. As the instructions sound like it can be tested this way to make sure it is working.

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

      @mfalkvidd I figured it had something to do with the network ID, but from what I understand there is no way to specify it on the PI. However in my case I don't need an ID I was just under the impression it was required. So I've removed it. And 1/2 success.

      The Pi when starting mysgw still produces the same startup and sends 1 msg out.

      On the wemos serial output I see it gets 1 msg from the pi but doesn't progress.

      32566 TSM:INIT
      32568 TSM:INIT:TSP OK
      32570 TSM:FPAR
      33075 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      33814 TSF:MSG:READ,0-0-255,s=255,c=3,t=20,pt=0,l=0,sg=0:
      35082 !TSM:FPAR:NO REPLY
      35084 TSM:FPAR
      35589 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
      37596 !TSM:FPAR:NO REPLY
      37598 TSM:FPAR 
      

      Is there some extra steps required to pair them or get the two to communicate?

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

      Got some good news. Adding the #define MY_RFM69_NEW_DRIVER and now it doesn't crash! Thanks evb and mfalkvidd for the tips.

      So, now that the wemos with radio is has the above sketch, just a simple send of a number running.

      On the pi I download the main branch, ran:

      ./configure --my-transport=rfm69 --my-rfm69-irq-pin=22 --my-rfm69-cs-pin=24 --my-rfm69-frequency=915 --my-is-rfm69hw
      --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out
      --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mysgw1  --my-mqtt-user=UID
      --my-mqtt-password=password 
      

      then

      make
      sudo ./bin/mysgw
      

      The output is the same as post 1. They both say they are sending, but neither receive anything. Did I miss some settings? I know in the sketch I specified a network id which I didn't see the option for in the gateway on pi.

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

      Using a very simple sketch (trying to test after all)

      // Enable debug prints
      #define MY_DEBUG
      
      #define MY_RADIO_RFM69
      #define MY_RFM69_FREQUENCY  RFM69_915MHZ  
      #define MY_IS_RFM69HW // Omit if your RFM is not "H"
      #define MY_RFM69_IRQ_PIN D1
      #define MY_RFM69_IRQ_NUM MY_RFM69_IRQ_PIN
      #define MY_RFM69_CS_PIN D8 // NSS. Use MY_RFM69_SPI_CS for older versions (before 2.2.0)
      #define MY_RFM69_NETWORKID  99
      
      #define MY_BAUD_RATE  115200
      
      #include <MySensors.h>
      
      #define CHILD_ID 1   // Id of the sensor child
      int counter =0;
      
      // Initialize motion message
      MyMessage msg(CHILD_ID, V_TEMP);
      
      void setup()
      {
        Serial.println("Setup completed");
      }
      
      void presentation()
      {
      	// Send the sketch version information to the gateway and Controller
      	sendSketchInfo("Test Sensor", "1.0");
      
      	// Register all sensors to gw (they will be created as child devices)
      	present(CHILD_ID, S_TEMP);
      }
      
      void loop()
      {
        Serial.println("Looped");
      
      //	send(msg.set(tripped?"1":"0"));  // Send tripped value to gw
      
      	send(msg.set(counter, 1));
      	counter=counter+1;
        sleep(2000);
      }
      

      If I disconnect the 3v, it doesn't crash just gives the fail message since it can't communicate with the rfm69. As soon as reconnect it crashes 😞

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

      Tried D1 & D2, no luck. Using a similar board, requires jumper wires to connect but allows future expansion of the antenna.

      0_1564427377546_rfm69.jpg

      Found: https://www.openhardware.io/view/601/NRF24-to-RFM69-adapter

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

      Hi everyone!

      I've tried connecting a wemos d1 mini to a RFM69HW. I have a PCB with headers, connect the pins from the RFM69 to the wemos in the following configuration:
      GND GND
      3.3V VCC
      D1 DIO0
      D5 SCK
      D6 MISO
      D7 MOSI
      D8 NSS

      It repetitively shows the following on the serial output:

       __  __       ____
      |  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
      | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
      | |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
      |_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
              |___/                      2.3.1
      
      58 MCO:BGN:INIT NODE,CP=RRNNE---,REL=255,VER=2.3.1
      73 TSM:INIT
      74 TSF:WUR:MS=0
      78 TSM:INIT:TSP OK
      79 TSM:FPAR``````
      
      

      Therefor I believe the board and rfm to be ok. As for sketches I've tried the ping pong sketch

      Then crashes and restarts.

      So I thought there could be a problem with the RFM or PCB. So I connected to a Raspberry pi (compiled in mqtt gw mode.) and get this.

      Jul 29 13:08:41 INFO  Starting gateway...
      Jul 29 13:08:41 INFO  Protocol version - 2.3.1
      Jul 29 13:08:41 DEBUG MCO:BGN:INIT GW,CP=RPNGL---,REL=255,VER=2.3.1
      Jul 29 13:08:41 DEBUG TSF:LRT:OK
      Jul 29 13:08:41 DEBUG TSM:INIT
      Jul 29 13:08:41 DEBUG TSF:WUR:MS=0
      Jul 29 13:08:41 DEBUG TSM:INIT:TSP OK
      Jul 29 13:08:41 DEBUG TSM:INIT:GW MODE
      Jul 29 13:08:41 DEBUG TSM:READY:ID=0,PAR=0,DIS=0
      Jul 29 13:08:41 DEBUG MCO:REG:NOT NEEDED
      Jul 29 13:08:41 DEBUG MCO:BGN:STP
      Jul 29 13:08:41 DEBUG MCO:BGN:INIT OK,TSP=1
      Jul 29 13:08:41 DEBUG GWT:RMQ:MQTT RECONNECT
      Jul 29 13:08:41 DEBUG connected to 10.0.0.56
      Jul 29 13:08:41 DEBUG GWT:RMQ:MQTT CONNECTED
      Jul 29 13:08:41 DEBUG GWT:TPS:TOPIC=mysensors-out/0/255/0/0/18,MSG SENT
      Jul 29 13:08:41 DEBUG TSM:READY:NWD REQ
      Jul 29 13:08:43 DEBUG TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
      Jul 29 13:23:41 DEBUG TSF:SAN:OK
      

      I believe that means it is ok, which rules out the RFM69 or the PCB.

      So unless someone has an idea what is wrong, any suggestion on how I can connect another rfm69 to another raspberry pi and communicate with the mysensor gateway? Sorry I haven't seen any code for pi as non-gateway. And I only have extra raspberry pi, Wemos d1 mini and an arduino uno clone.

      On a side note - could there be insufficient power for the rfm69?

      posted in Troubleshooting
      Les
      Les