💬 Building a Raspberry Pi Gateway

[Damian]

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.

[gohan]

What radio are you using?

[Damian]

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

[gohan]

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

[joaoabs]

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.

Thanks

[Damian]

@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.

[gohan]

also look for a channel outside the WiFi range

[kberck3]

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?

[gohan]

@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.

[mfalkvidd]

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

[kberck3]

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

[Mark Swift]

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!

[gohan]

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

[mirodin]

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,
mirodin

[tbowmo]

@mirodin

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?

[mirodin]

@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 :D

EDIT:
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

[gohan]

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

[mirodin]

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.

[gohan]

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

[tbowmo]

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..