💬 Building a Raspberry Pi Gateway

[mfalkvidd]

@Sergio-Rius it would be great if you could contribute to making that a reality.
An earlier discussion on the same topic: https://forum.mysensors.org/topic/4151/nrf24l01-and-rfm69-on-one-gw/

So far, people have found it easier to add a separate gateway for each transport.

[Sergio Rius]

@mfalkvidd thanks for guiding me on the starting point. Perhaps the raspberry can break the doble transport limitation.
I'll investigate in how to install two services at once. But it'll would be nice any advice on the device virtualization part.

[mfalkvidd]

Another thread: https://forum.mysensors.org/topic/2331/gateway-with-both-rfm69-and-nrf24l01/

[mfalkvidd]

Maybe it could be as simple as running two instances of mysgw, using different pins for the nrf and the rfm?

[Sergio Rius]

@mfalkvidd Maybe. I'm programmer, but not for Linux. My concern is the part of the service that creates the virtual device colliding between the instances.
I'll do a test in a virtual machine as soon as I have some time.
It should be something easy to test.

[mfalkvidd]

@Sergio-Rius by "virtual device", do you mean the com port? If that's the caee, it can be specified with --my-serial-pty=

Ot let one gateway be serial and the other ethernet.

[Sergio Rius]

@mfalkvidd yes. Should work. I admit I've not taken a look at the code nor I don't know how to install the service two times.
I'm used to having problems with programs that use static resources allocation. But I don't know if that's the case.

[gohan]

maybe you could also consider making 2 ethernet gateway one on port 5003 and the other on port 5004 so that you can use myscontroller to debug from remote.

[Matt]

Hi guys couple of questions, apologies if they have been covered elsewhere.
I am running latest dev branches of domoticz and MYS on a pi2.
At random times it seems the NRF24L01+ LNA/PA goes down, or MYS goes down and domotics stops receiving signals from all of the nodes at the same time. I have the interrupt feature enabled.
I have set the option under domoticz/hardware/data timeout to restart if no data received in five minutes but I dont think this is an ideal solution, and have yet to find out if this domoticz feature actually works in my scenario.
Any idea what causes this? I found an old thread over on the domoticz/mysensors forum but no answers there. I am using a new sd card class 10.
What I want to do is try out the different MYS builds on domoticz ie MQTT and SERIAL as well as ethernet which I am currently running. However I'm not sure how to stop the current MYS service and completely clean up the current build to start from scratch... I have tried just re entering the ./configure commands then 'make' but this does not seem to work.
Many thanks,
Matt

[mfalkvidd]

@Matt log files for the time where the problem occurred will be essential for troubleshooting.

make uninstall will stop the service and uninstall
make cleanconfig will remove previous ./configure settings
make clean will remove compiled code

[enlo]

@ccy that correction to the detect_machine function was necessary on my Rpi 3 too (I took the latest version from master). I got it working with that addition.
Soooo I guess that would be worth adding to the code / opening an issue on github, wouldn't it?

[Sergio Rius]

I'm just now testing the two instances installation. I was going to just alter the flag --prefix but now I see in options that there's also the install dir:

Installation options:
    --prefix=<PREFIX>           Installation prefix path. [/usr/local]
    --gateway-dir=<DIR>         Gateway files installation directory. [PREFIX/bin]

What do you think should be the preferred way for installing two instances, only changing --gateway-dir?

[Matt]

@mfalkvidd OK thanks for your reply.
Have set up the -d parameter in mysgw.servie and am waiting for it to fall over again.
If I catch it I will post syslog.
Thanks,
Matt

[Sergio Rius]

Seems that I'll need some help for getting this properly done.
I can't launch two instances of the service.

What I've done is following the guide instructions with the following configuration:

./configure \
 --my-transport=nrf24 \
 --my-rf24-irq-pin=18 \
 --my-gateway=ethernet --my-port=5003 \
 --prefix=/opt/mysgw-nrf

Then manually executed it, and it run ok and get one test node connected and Domoticz saw it all.

Then I duplicated the MySensors folder and in there made the build with the following configuration:

./configure \
 --my-transport=nrf24 \
 --my-rf24-channel=82 \
 --my-rf24-ce-pin=37 \
 --my-rf24-cs-pin=36 \
 --my-rf24-irq-pin=33 \
 --my-gateway=ethernet --my-port=5004 \
 --prefix=/opt/mysgw-rfm

Even when it says rfm, i connected a second NRF with the following pinout (blue=first NRF, green=second):

*IRQ on pin 33 as config says, and power from 1.

Then I tried to make and run and I get this output:

pi@domo_testing:~/MySGW_RFM $ sudo ./bin/mysgw -d
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
 __  __       ____
|  \/  |_   _/ ___|  ___ _ __  ___  ___  _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| |  | | |_| |___| |  __/ | | \__ \  _  | |  \__ \
|_|  |_|\__, |____/ \___|_| |_|___/\___/|_|  |___/
        |___/                      2.2.0-beta

mysgw: MCO:BGN:INIT CP=RNNG--Q-
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: pinMode: invalid pin: 33
mysgw: pinMode: invalid pin: 37
mysgw: pinMode: invalid pin: 36
mysgw: digitalWrite: invalid pin: 37
mysgw: digitalWrite: invalid pin: 36
mysgw: You need root privilege to use SPI.

Is that I have to connect MOSI and MISO to the same pins that the first NRF?

[mfalkvidd]

@Sergio-Rius see https://forum.mysensors.org/post/72145 and https://github.com/mysensors/MySensors/issues/895

[Sergio Rius]

@mfalkvidd That was the culprit. Thanks.
But now... seems that the radio that is using channel 76 also get connections from nodes on channel 83, and the second radio, the 83 one doesn't pick anything.

Is there a way to confirm that gw and nodes are using one channel or other during the bootup?

[gohan]

@Sergio-Rius try increasing the distance between channels to at least 10 or more

[Sergio Rius]

@gohan Done. I've just burnt the node with channel 125 and it seems to have no effect. It registers on the 76 radio.

Does the #define MY_RF24_CHANNEL 125 has to be before or after the include of mysensors.h? I have it before.

[Sergio Rius]

Well, I've changed the channel for the 1st radio to 83 and left the second at 125.
If I burn the testing node for ch125 it doesn't receives reply from the gw. If I then burn it on ch83, it registers and comunicates with the first radio.

So I think the second radio does not work on the Raspberry Pi. The service communicates with the controller but does nothing for the network side.
Also on the second radio:

mysgw: Client 0: 0;0;3;0;18;PING
mysgw: Client 0: 0;0;3;0;18;PING
mysgw: Client 0: 0;0;3;0;18;PING
mysgw: !TSF:SAN:FAIL
mysgw: TSM:FAIL:CNT=1
mysgw: TSM:FAIL:DIS
mysgw: TSF:TDI:TSL
mysgw: Client 0: 0;0;3;0;18;PING
mysgw: TSM:FAIL:RE-INIT
mysgw: TSM:INIT
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: Client 0: 0;0;3;0;18;PING
mysgw: Client 0: 0;0;3;0;18;PING

[mfalkvidd]

@Sergio-Rius if you shut down mysgw for the first radio and restart mysgw for the second radio, does the second radio start to work?
And do you get the same debug output? The SPI message looks bad. Maybe the two gateways are conflicting.