💬 Building a Raspberry Pi Gateway

  • Contest Winner

    @masmat check that the version you are using (release or beta) match your use of the simple flags, as they differ at the moment.

  • @anticimex Both Arduino IDE is 2.2 and Rpi is compiled with 2.2 stable.
    I'm seeing !TSF:MSG:SIGN FAIL in the serial monitor so something is not compatible... I will try making password >8 characters next (currently 6).

    I will also add those parameters to see if that makes a difference before reuploading arduino code

  • Contest Winner

    @masmat if you add the signing debug flag and use the log parser on the homepage it should become clear what the problem is. You can also use the troubleshooting guide in the signing documentation.

  • @anticimex This is what's happening in the gw:


    The parser didn't really help much: more baffled than before....and I came away from the troubleshooting guide feeling really stupid 🙂

  • Contest Winner

    @masmat looks to me that your gateway is not set up for signing

  • Mod

    @anticimex I think he didn't use all the parameters for the configure, right?

  • Contest Winner

    @gohan the simple flags should not need more args, but I don't use a rPi as gw so I honestly am not sure exactly the args to use. The beta documentation has clear instructions for rPi signing, but those are specifically for beta branch and probably don't map exactly to the release yet.

  • @gohan The whole configure-line:

    sudo ./configure --my-transport=nrf24 --my-rf24-irq-pin=15 --my-signing=software --my-signing-request-signatures --my-signing-weak_security --my-signing-debug --my-signing=password --my-signing-password=ZZZZZZ --my-gateway=mqtt --my-controller-ip-address= --my-mqtt-user=XXXX --my-mqtt-password=YYYYY --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18

    If anyone can tell what's missing or if there's a typo?

  • Contest Winner

  • Contest Winner

    @masmat you have redundant flags. The password option require no other signing flags. Only if you select software as signing backend you need other options (and none of the simple flags)

    And remember that if you use software signing and not password signing, you need to personalize the GW and/or node.

  • @anticimex I thought so too, but I'm grasping at straws to get the signing to work.
    To clarify, is the following enough for simple signing: --my-signing-debug --my-signing=password --my-signing-password=ZZZZZZ

    And the arduino code #define MY_SIGNING_SIMPLE_PASSWD = "ZZZZZZ"
    Any difference where it's placed in the code? Anything else to check for?

  • Contest Winner

    @masmat it needs to be defined prior to the inclusion of mysensors.h. That should be it. (on the arduino node that is).

  • Plugin Developer

    While on the subject: what would be the flags needed for setting the gateway to only use the simple encryption but not the (simple) signing feature?

    I looked in the documentation and the node commands aren't mirrored for the gateway. I was hoping for something like:


  • Mod

    It's actually not needed since you can still set signing as optional on gateway

  • Contest Winner

    @alowhum that feature is still only available for beta and is documented here: https://www.mysensors.org/apidocs-beta/group__SecuritySettingGrpPub.html

    EDIT: not yet for rPi

    Pull requests are welcome. I don't have time for this at the moment.

  • Plugin Developer

    Right. So is this correct?

    NODES (arduino nano)
    On all my nodes I will update them to have this code at the top:

    #define MY_ENCRYPTION_SIMPLE_PASSWD spiderman41 // unfortunately Nano hardware doesn't really have enough memory for signing.
    #define MY_RF24_CHANNEL 100 // in EU the default channel 76 overlaps with wifi.
    #define MY_RF24_DATARATE RF24_1MBPS // slower datarate makes the network more stable?

    GATEWAY (Raspberry Pi Zero W)
    On my gateway I will use this configure code:


  • Contest Winner

    @alowhum you will need to enable weak security as well as that will enable both signing and encryption with signature requirements from all nodes on the gw

  • Plugin Developer

    @Anticimex thanks!

    as that will enable both signing and encryption with signature requirements from all nodes on the gw
    But I don't want signing? Or do you mean that it will remove that requirement?

    I only need to set that on the gateway, right?
    I've also added a slower datarate, thinking that will also create a more stable connection. I am in a busy urban environment with lots of RF noise. Is that smart?

  • Contest Winner

    @alowhum I thought you did not want signing: "but not the (simple) signing feature?"

  • Plugin Developer

    Yes, I don't want signing. But what you wrote said that it wil ENABLE signing. Check your sentence. Probably a typo, but I wanted to make sure 🙂

  • Contest Winner

    @alowhum the simple security flag enables signing yes.

  • Plugin Developer

    @alowhum said in 💬 Building a Raspberry Pi Gateway:


    But does the "--my-signing-weak_security" enable signing?

    I want to disable signing completely. What flags do I need to use when building a gateway that only uses encryption?

  • Contest Winner

    @alowhum just don't use any flags mentioning signing, personalize the gw according to the documentation and pick the appropriate encryption flag.

  • @anticimex I've built a new node, DHT11 that sends temp&hum data. I reconfigured Rpi with this:

    sudo ./configure --my-transport=nrf24 --my-rf24-irq-pin=15 --my-signing-debug --my-signing=password --my-signing-password=XXXXXX --my-gateway=mqtt --my-controller-ip-address= --my-mqtt-user=YYYY --my-mqtt-password=ZZZZZ --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18

    This is what I get in gw syslog:

    Apr  2 22:53:11 DietPi mysgw: Starting gateway...
    Apr  2 22:53:11 DietPi mysgw: Protocol version - 2.2.0
    Apr  2 22:53:11 DietPi mysgw: MCO:BGN:INIT GW,CP=RNNGLSQX,VER=2.2.0
    Apr  2 22:53:11 DietPi mysgw: !SGN:BND:PWD<8
    Apr  2 22:53:11 DietPi mysgw: !SGN:INI:BND FAIL
    Apr  2 22:53:11 DietPi mysgw: TSF:LRT:OK
    Apr  2 22:53:11 DietPi mysgw: TSM:INIT
    Apr  2 22:53:11 DietPi mysgw: TSF:WUR:MS=0
    Apr  2 22:53:11 DietPi mysgw: TSM:INIT:TSP OK
    Apr  2 22:53:11 DietPi mysgw: TSM:INIT:GW MODE
    Apr  2 22:53:11 DietPi mysgw: TSM:READY:ID=0,PAR=0,DIS=0
    Apr  2 22:53:11 DietPi mysgw: MCO:REG:NOT NEEDED
    Apr  2 22:53:11 DietPi mysgw: MCO:BGN:STP
    Apr  2 22:53:11 DietPi mysgw: MCO:BGN:INIT OK,TSP=1
    Apr  2 22:53:11 DietPi mysgw: GWT:RMQ:MQTT RECONNECT
    Apr  2 22:53:11 DietPi mysgw: connected to
    Apr  2 22:53:11 DietPi mysgw: GWT:RMQ:MQTT CONNECTED
    Apr  2 22:53:11 DietPi mysgw: GWT:TPS:TOPIC=mysensors-out/0/255/0/0/18,MSG SENT
    Apr  2 22:53:23 DietPi mysgw: TSF:MSG:READ,99-99-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
    Apr  2 22:53:23 DietPi mysgw: TSF:MSG:BC
    Apr  2 22:53:23 DietPi mysgw: TSF:MSG:FPAR REQ,ID=99
    Apr  2 22:53:23 DietPi mysgw: TSF:PNG:SEND,TO=0
    Apr  2 22:53:23 DietPi mysgw: TSF:CKU:OK
    Apr  2 22:53:23 DietPi mysgw: TSF:MSG:GWL OK
    Apr  2 22:53:23 DietPi mysgw: SGN:SKP:MSG CMD=3,TYPE=8
    Apr  2 22:53:23 DietPi mysgw: TSF:MSG:SEND,0-0-99-99,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
    Apr  2 22:53:25 DietPi mysgw: TSF:MSG:READ,99-99-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
    Apr  2 22:53:25 DietPi mysgw: SGN:SKP:MSG CMD=3,TYPE=24
    Apr  2 22:53:25 DietPi mysgw: TSF:MSG:PINGED,ID=99,HP=1
    Apr  2 22:53:25 DietPi mysgw: SGN:SKP:MSG CMD=3,TYPE=25
    Apr  2 22:53:25 DietPi mysgw: TSF:MSG:SEND,0-0-99-99,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
    Apr  2 22:54:18 DietPi mysgw: TSF:MSG:READ,99-99-0,s=1,c=3,t=16,pt=0,l=0,sg=0:
    Apr  2 22:54:18 DietPi mysgw: SGN:SKP:MSG CMD=3,TYPE=16
    Apr  2 22:54:18 DietPi mysgw: !SGN:NCE:GEN
    Apr  2 22:54:23 DietPi mysgw: TSF:MSG:READ,99-99-0,s=0,c=3,t=16,pt=0,l=0,sg=0:
    Apr  2 22:54:23 DietPi mysgw: SGN:SKP:MSG CMD=3,TYPE=16
    Apr  2 22:54:23 DietPi mysgw: !SGN:NCE:GEN

    This is kicking my butt... I cant understand that last part about the nonce 😞
    I will add the code from the node as soon as possible.

  • Mod

    @masmat according to the log parser

    mysgw: !SGN:BND:PWD<8

    means the password is too short.

  • Contest Winner

    @masmat and this


    Means the signing backend failed to initialize. So you need to make the password longer.

  • @mfalkvidd Made the password 10 characters. From looks of the logs, it's working now.
    I cant believe I skipped the step of making the password longer... Just got too fixated on the password I came up with.

  • Contest Winner

    @masmat the nonce failures is because the backend never initialized so basically any call to the backend that can fail will fail.

  • Plugin Developer

    I just discovered these USB-to-NRF24 devices. Would it be possible to use that instead of connecting to the GPIO pins?


  • Mod

    @alowhum not with the existing code. Is there a datasheet that describes how these modules work?

    One of the reviews says "have no idea wath software to use with this" so documentation might be hard to come by.

  • Hardware Contributor

    Background: I use signing software on some nodes + whitelisting on a node (of course only PI serial is on the whitelist).

    With current --development branch (I think 2.3.0alpha) I cannot anymore set my previous personalized flags on gateway RPI3.

    In detail, with current master (2.2.0) I can do:

    sudo mysgw --set-soft-hmac-key=F618D4[...]848992B
    sudo mysgw --set-soft-serial-key=26[...]9
    sudo mysgw --set-aes-key=EC7[...]CEB4

    WIth development I did see only the --get[...] flags and cannot set anymore. Can you confirm?

    How can I set my previous values for signing?

  • Contest Winner

  • I'm currently compiling the code for connecting the NRF24l01+ directly to the Raspberry PI. Since I'm running the controller (on this case OpenHab) on the same Raspberry PI, would it be recommended the Ethernet or the serial flavor of it?
    In the case of ethernet, can I place the own machine IP ( This way, if I need to change the IP address of the PI it wouldn't affect the communication between the controller and the MySensors code, right?
    --my-gateway=ethernet --my-controller-url-address=

    And by the way, for the signing configuration, it is mentioned in the documentation "Update the gateway config file with the generated keys/valeus", what file is that (name, path)?

    I should be able to re-use the keys I have defined before, right? So I just go to step 2 (no need to generate new keys).
    I'm refering to this link.


  • Mod

    --my-controller-url-address= is not needed for ethernet

  • I found that the configuration file is /etc/mysensors.conf but " The first time you start the gateway the configuration file will be created if it does not already exist.", so that's why I wasn't finding it.

    Anyway, the file states that:
    "Note: The gateway must have been built with signing support to use the options below."

    What flags should I include to have signing support?

    OK, found it: just run ./configure -h and there is a list of options. Leaving it here just for future reference

  • Mod

    @joaoabs said in 💬 Building a Raspberry Pi Gateway:

    ust run ./configure -h and there is a list of options. Leaving it here just for future reference

    it is already written in the article

  • Contest Winner

  • Thanks for the replies.

    I've changed the PI from a PI1 to a PI3 and was able to make it working with signing. Its running smoothly, I guess the GW is chosen :).

    I'll now focus on the nodes, specially the SenseBender micros that are 2xAA battery powered and are consuming ~3% bat per day, but that will be for another post...


  • Hi, is there any way to check the current gateway operating parameters? My purpose is to check the radio channel and power level set before compilation but I would be glad if I could check other configurable parameters. I looked at Makefile.inc and found some flags set, but not the information I was looking for (does it mean that the default values are set)? Debug logs neither provide these informations.

  • Mod

    What radio are you using?

  • @gohan nrf24, one deployment pa+lna version with external antenna and the other standard with build-in "zig-zag" antenna.

  • Mod

    I always set gw to max power if the radio is shielded

  • Hi,

    Is it normal to have frequently these errors in the RPI GW?

    May 11 00:43:54 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:43:54 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:43:56 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:43:56 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:43:58 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:43:58 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:44:00 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.
    May 11 00:44:00 nettemp mysgw: RF24: Recovered from a bad interrupt trigger.


  • @gohan Well, that is not an answer to my question apparently 🙂 I suppose that max power lever is the default setting according to the configure script's help.

  • Mod

    also look for a channel outside the WiFi range

  • Openhab2 on pi3b+ using nrf24 radios and mqtt. I can follow the wiring diagram, but the commands are a bit confusing and seem to jump around randomly. Do I put all the --my-blah-blah together after the ./configure to build a file? Should I do development version? Do the nfr improvements go together with everything else?

  • Mod

    @kberck3 said in 💬 Building a Raspberry Pi Gateway:

    Do I put all the --my-blah-blah together after the ./configure to build a file?

    From the article "Note: All options must be added to the same line, after ./configure"

    Leave the development version for now, the stable works fine.

  • Mod

    @gohan to be fair, I added that note this morning so kberck3 might not have seen it 🙂

  • Appreciate the reply mfalkvidd and gohan! Service is running, will report back if I run into other issues.

  • Hi Guys,

    Is anyone here using the Pi with OTA updates? I'm finding them painfully slow (1-2 stream messages every few seconds). It's taking 1 hour per OTA update compared with 2-3 minutes when using the Arduino gateway!

  • Mod

    I did some tests on pi3 and I found slow ota too. Tekka has an open issue on github about this.

  • Hey guys,

    I tried to setup my Raspberry running Node-RED and serial gateway but I got stuck halfway. I followed the serial gateway compilation above and got it up and running, however using the serial nodes an Node-RED I could not manage to get them to connect tho the gateway.

    First I tried to connect to /dev/ttyMySensorsGateway which did not work due to permissions (owned by root). When checking out /dev/ttyMySensorsGateway I found it links to /dev/pts/1
    which belongs to root and the tty group. But I could not connect to this as the tty group only has write privileges. I think I miss some crucial point connecting those two together so I hope somebody can save the day by pointing me in the right direction.

    Thanks in advance,

  • Admin


    So you run a separate arduino board as a mysensors gateway, connected with serial (USB) to your raspberry pi? Or do you mean that you are using the rpi directly with radio, and then run the rpi variant of the mysensors gateway code?

  • @tbowmo I run the gateway on my Pi directly with the radio is connected to the Pi's GPIOs. Compilation and gateway do just fine I, if only I could convince my Pi to let Node-RED talk to the device 😄

    This is my output:

    dietpi@buddy:~ $ ll /dev/ttMySensorsGateway 
    lrwxrwxrwx 1 root root 10 Jun 18 14:38 /dev/ttMySensorsGateway -> /dev/pts/2
    dietpi@buddy:~ $ ll /dev/pts/
    total 0
    crw--w---- 1 dietpi tty  136, 0 Jun 18 14:38 0
    crw--w---- 1 dietpi tty  136, 1 Jun 18 14:38 1
    crw--w---- 1 root   tty  136, 2 Jun 18 14:38 2
    crw--w---- 1 dietpi tty  136, 3 Jun 18 14:38 3
    c--------- 1 root   root   5, 2 Nov  3  2016 ptmx

  • Mod

    wasn't it the problem of the missing permission on the dialup group?

  • Unfortunately adding my nodered user to dialout did not bring the hoped success. I still get premission denied messages after a reboot of my raspberry.

    As my console print above shows the /dev/pts device belongs to tty but adding nodered to tty did not work out either (since the group only has write privileg). I have no idea how to fix this other then chowning the port to nodered but that feels wrong for me after years using linux based systems.

  • Mod

    it is not a solution, but you could switch to ethernet GW and you will avoid all the permissions problems.

  • Admin

    My 5 cents:
    Run it as a MQTT gateway, if possible. It makes things so much easier, when you interact with the data in node-red. Even integrating other controllers is easier, as you have the MQTT as standard backbone bus between everything.

    You need to have a MQTT broker (mosquitto) running as well.. But it's worth it..

  • Yes I came to the conclusion that this might be my only option even if it sucks as I have to subscribe to all events from MySensors, process them with Node-RED and republish again which screws my logging a bit. Right now I have another flow subscribed to "#" and write every event into my DB.

    Since I have everything talking to mosquitto setup to follow Homie Convention I was hoping for only having my MQTT broker bombarded with compliant messages and have Node-RED convert everything (assign device names, etc. using a SQLite DB) from serial so the rather cryptic MySensors topics do not show up there.

  • Mod

    @mirodin you actually need only mysensors-in and mysensors-out topics and their subtopics

  • @gohan Yes I know but now I can no longer just wildcard-dump every event on my mosquitto instance into my DB as I need to filter out the mysensor-in and -out topics.

  • Mod

    Or meanwhile just use the ethernet gw

  • Well... I think I fixed it, let's hear it for documentation. Just when I had MQTT setup half way I got struck by the idea that there was some group flag for configure. And indeed there is, setting --my-serial-groupname=nodered did the trick making /dev/pts/X owned by group nodered and let Node-RED connect to it, writing and reading works just fine now.

    Thanks @gohan for your input I think I would have gone the ethernet route in the end if this last test had failed.

  • I am currently trying to update to 2.3
    Have stopped service and deleted the file (systemctl status mysgw -> Unit mysgw.service could not be found.)
    Also renamed the config file /etc/mysensors.dat
    Renamed the old folder, then copied new files.
    Checked readme.md in MySensors-folder: MySensors Library v2.3.0
    Then I configured the radio and -> make, no errors
    However, changing to bin folder and executing mysgw shows: Protocol 2.2.0
    What am I missing?

  • @inso Did you sudo make install after building it? This command copies the service file and mysgw to their respective locations.

  • Mod

    @inso remember to unregister the service and then make a new make install of the new gw

  • Mod

    @gohan how is the unregistration done? I didn’t know that was needed. We should probably add upgrade instructions to the build page.

  • @mirodin
    make install before testing did the trick, now it is 2.3.0 . 😃
    Was just going step by step through tutorial, there it´s make -> test -> make install. Didn´t realized it would use old parts if it´s not first install ☺

    thought stop, disable and remove the service would be enough to ensure the service is completely "uninstalled" - could you give me a hint what I´ve missed? 😅

  • Hi,
    I try to access log info from my gateway installed on my domoticz raspberry pi, but I get no success..
    First, I can't find the mysensors.conf file : nothing in the /etc folder. I tried to use "find / -name 'mysensors.conf' 2>/dev/null" command, but it finds nothing.
    I tried creating such a file (then it's found by the fond command above) and in which I have the lines


    as instructed above.
    I restarted the wole Raspberry PI, then tried the command cat /tmp/mysgw.pipe but error message:

    cat: /tmp/mysgw.pipe: Aucun fichier ou dossier de ce type

    (= no file or folder like that)
    I then tried this: sudo mysgw -c /etc/mysensors.conf and I got also error message:

    mysgw: invalid option -- 'c'

    I installed the Mysensor gateway on 17th October 2017 and my raspberry pi is working on Wheezy. In Domoticz, I see the Mysensor gateway has version 2.1.1.
    MY gateway seems working fine, communicating properly with sensors (both ways). I'm trying to find log because I face an issue with a new sensor which works properly when powered with external FTDI 3.3V and only 1 way (sensor to gateway only) when powered on battery (I raised question in another post, where I was suggested to check log fil on gtw side..)

    Any idea of what I should do (except "reinstall whole raspberry pi with latest OS..) ?
    Thanks a lot,

  • Mod

    @ricorico94 there seems to have been some major changes in the raspberry pi gateway, without vorresponding updates to the documentation.

    I have not been able to locate the exact changes though. @marceloaqno might know.

  • Mod

  • @mfalkvidd : thanks a lot ! I had searched for such version history and couldn't find it.
    Indeed it seems introduction of the switches for log files was introduced in February, so I should probably update my install.

    Precisely, talking about upgrade process: I read in previous posts that we should uninstall/unregister the install/service. WHat would be commands to do so ? Should it be:

    sudo systemctl disable mysgw.service

    and executed before anything else ? So upgrade process would be:

    sudo systemctl disable mysgw.service
    sudo make install
    sudo systemctl enable mysgw.service

    (and maybe test the gateway before the "systemctl enable..")
    Is there anyfile to remove manually ? or any other command to apply before or after ?

  • Plugin Developer

    Would someone be willing to create a post that lists each step required to set up the simple encryption+signing option? I understand I have to add a password line to the arduino sketch. But how exactly one sets up the server side is still a bit of a mystery to me. It would rock if there was a similar simple command to give during the make process.

  • Contest Winner

    @alowhum https://www.mysensors.org/apidocs/group__RaspberryPiGateway.html
    That is straight from the documentation. Which in the case of Linux ports is also what you get if you issue ./configure --help
    I believe.

  • @alowhum
    I also need this info...

  • Code Contributor

    @ricorico94 to update your install run:

    sudo make install
    sudo systemctl restart mysgw.service

  • Thank you for the clarification !

  • Plugin Developer

    @anticimex said in 💬 Building a Raspberry Pi Gateway:


    @Anticimex Thanks, but a documentation page (which I have checked before) is not the same as an easy to use guide for beginners.

    In my ideal world it would be this:

    1. Add the MY_SIMPLE_PASSWORD line to your Arduino sketch.
    2. Compile the gateway with --MY_SIMPLE_PASSWORD="yabadabad000!"
    3. Done

  • Contest Winner

    @alowhum it is not easy to have simple guides tailored for specific usecases when there are so many options.
    Those tend to not follow implementation and our documentation is made to live with the implementation to ensure it is always up to date. Maintaining a simple guide for every conceivable use case is simply not feasible. The signing and security documentation does have a step by step guide for setting up security.

  • Plugin Developer

    @Anticimex: I understand, but:

    • Currently even the outline of the steps eludes me. Seeing the steps for usecase #14 or #385 would already help me understand the scope, and to see what ballpark of difficulty it's in. It's easier to mod a guide when there is something to go on.
    • Secondly, there must be a common use case? The defaults that MySensors uses already suggests a lot of these: a Raspberry Pi with the default settings of the software (ethernet), with the nRF24 radio.

  • Contest Winner

    @alowhum ok, well first of all, I don't have a rPi setup to test on, secondly I don't have time to look into that (this) environment.
    But, this is a open source project so anyone is free to contribute with both code and documentation (which in our case lives in the same repositories) so if there are guides missing enyone is welcome to contribute with experiences and guides to help others out.
    It is just important to understand that the guides need to be maintained in order to remain valid.
    I don't mind guides at all. But it makes little sense for me to write guides for an environment which I am not familiar with nor can test on.

  • Plugin Developer

    @Anticimex: Sure, that's totally understandable. There are other people on the forum 🙂 Can anyone help me and @pepson out?

    And it is exactly my goal to create a more elaborate guide after someone points out the basic steps.

  • I have designed a 3D printable enclosure for this and the design/STL files are available here: https://www.thingiverse.com/thing:3072244

  • Admin

    @John-Oliva, nice! Added it to the MySensors collection:

  • @korleone HI
    I have same error
    Can you write that rigth do you ser to folder ?

  • @cadet I just remove /usr/local/bin/mysgw and compile again
    And I have one question - why is it happened?
    MysGW work fine about 3 months.

  • Mod

    what problem did you have?

  • @gohan mysgw: ERROR accept: Bad file descriptor - today morning

  • Mod

    I get that when another instance of the process is already running

  • @gohan I was try to find it with ps -ef, but nothing found. Reload RPI.
    @korleone was write about this
    "Hello, it seems I found the problem: Complete newbie thing: 🔰
    sudo ./bin/mysgw -h worked, but /usr/local/bin/mysgw didn't
    I just gave the right to the folder, and now it's working."

    But what right hi gave ?

  • Mod

    sudo ./bin/mysgw -h could work, it only depends in which folder you are running the command from

  • FYI looks like on the 2.3.1 beta the transport has been changed to rf24 instead of nrf24

  • Is the rasberry pi serving as a gateway and a server in this project? Or do you have to have a separate pi to host something like openhab and another pi for your gateway?

  • Mod

    Hi @magjef29, welcome to the MySensors forum!

    You can run your controller(s) on the same Raspberry Pi.

    Depending on what tou mean by ”server”, the gateway can be a server, but the gateway is not a controller.

    If you haven’t already, see the getting started guide for information about the different parts.

  • Hi! Does anybody test Cubieboard as Gateway? I have a cubieboard runing archlinux with spi enabled in kernel. How i define pins for nrf24 gateway connection? Or i need to make big changes in code to star work with different bord than Rpi?
    Best regards

  • This is my old dream to connect directly nrf to Cubieboard GPIOs. Few years ago i try to do this without success using this lib - https://github.com/bearpawmaxim/librf24-sunxi

  • Mod

    Hi @артем-тихонович, welcome to the MySensors forum!

    For the NRF24, the same defines as for normal sketches are used. Documentation: https://www.mysensors.org/apidocs/group__RF24SettingGrpPub.html
    The defines can be added to the Raspberry Pi gateway by following the instructions on https://www.mysensors.org/build/raspberry#advanced

    I have not heard about anyone using the Cubieboard but hopefully someone else has. The information provided on https://www.mysensors.org/build/orange might be useful if the Cubieboard is similar to the Orange Pie.

    oh, and in case you haven't already, see the ./configure --help text about the most common NRF24 defines; you might not need the advanced build options.

  • Thank you, @mfalkvidd. Ihave a little troubles with correct defining gpios from Cubie. In fex file the gpios defines is:
    gpio_used = 1
    gpio_num = 2
    gpio_pin_1 = port:PH07<0><default><default><default>
    gpio_pin_2 = port:PH15<6><default><default><default>
    in sys/gpio:
    [root@Archey boot]# ls -ls /sys/class/gpio/
    total 0
    0 --w------- 1 root root 4096 Nov 21 11:58 export
    0 lrwxrwxrwx 1 root root 0 Nov 18 17:01 gpio1_ph7 -> ../../devices/platform/gpio-sunxi/gpio/gpio1_ph7
    0 lrwxrwxrwx 1 root root 0 Nov 21 11:54 gpio2_ph15 -> ../../devices/platform/gpio-sunxi/gpio/gpio2_ph15
    0 lrwxrwxrwx 1 root root 0 Nov 18 10:45 gpiochip1 -> ../../devices/platform/gpio-sunxi/gpio/gpiochip1
    0 --w------- 1 root root 4096 Nov 18 16:52 unexport

    When i define in configure: --my-rf24-ce-pin=1 --my-rf24-cs-pin=2 build is ok, but test failed with error:
    Nov 21 11:58:15 ERROR Could not open /sys/class/gpio/gpio1/direction[root@Archey MySensors]#
    when i define --my-transport=nrf24 --my-rf24-ce-pin=gpio1_ph7 the build failed wirh error:
    ./drivers/RF24/RF24.cpp: In function 'void RF24_ce(bool)':
    <command-line>:0:16: error: 'gpio1_ph7' was not declared in this scope
    ./drivers/RF24/RF24.cpp:52:17: note: in expansion of macro 'MY_RF24_CE_PIN'
    hwDigitalWrite(MY_RF24_CE_PIN, level);

    How can i resolve this problem? Please help.

  • I just see for another app using nrf24 on cubieboard
    and funcrtion to use nrf24 have GPIO defining is RF24 radio(SUNXI_GPB(10), SUNXI_GPB(11), "/dev/spidev0.0");
    GPIO set using this style: SUNXI_GPB(10), this type of gpio defined in #include "gpio_sun4i.h" file. Maybe this specific defining in ARCHLINUX ARM distro.

  • Plugin Developer

    I hereby donate these images:

    4_1542918057729_step1.png 3_1542918057729_step2.png 2_1542918057728_step3.png 1_1542918057727_step4.png 0_1542918057727_step5.png


Suggested Topics