💬 Building a Raspberry Pi Gateway

[manul]

@Richard van der Plas: I strongly recommend to use MQTT instead of Ethernet gateway, as it is a standard way for 2 processes to communicate, and platform-agnostic.
HASS comes with an embed MQTT broker taht works out of the box.
Plus:

• you can easily mock either your sensors network or your controller
• it does support secure communication
• you can add other clients to observe the event, e.g. to log what is coming from/what is sent to the gateway

[gohan]

I suggested ethernet because it's easier to setup and configure, mqtt is the next step.

[pettib]

Hi
I also have problem to get the NRF24L01+ chip to work with the RPi3.

I find that the masterbranch don't recognize the board as RPi3 and sets SoC and Type as unknown.
But if i take development branch it´s detecting RPi3 and seems to work correct.

This is result from development Branch configure:
[SECTION] Detecting target machine.
[OK] machine detected: SoC=BCM2837, Type=rpi3, CPU=armv7l.
[SECTION] Detecting SPI driver.
[OK] SPI driver detected:BCM.
[SECTION] Detecting init system.
[OK] init system detected: systemd.
[SECTION] Saving configuration.
[SECTION] Cleaning previous builds.
[OK] Finished.

This is result from Master Branch configure:
[SECTION] Detecting target machine.
[OK] machine detected: SoC=unknown, Type=unknown, CPU=armv7l.
[SECTION] Checking GPIO Sysfs.
[OK] /sys/class/gpio/export found
[SECTION] Detecting SPI driver.
[OK] SPI driver detected:SPIDEV.
[SECTION] Detecting init system.
[OK] init system detected: systemd.
[SECTION] Saving configuration.
[SECTION] Cleaning previous builds.
[OK] Finished.

This is the result from cat /proc/cpuinfo:

Hardware : BCM2835
Revision : a02082

//Peter

[gohan]

That's odd, I have the 2.1.1 compiled on mine rpi 3

[marceloaqno]

@pettib @gohan There have been some changes in /proc/cpuinfo in newer versions of kernels which leads to a wrong detection.
The problem was fix in #827 and will be available in the master branch in the next mysensor release.

[gohan]

I'm using dietpi and I compiled it like 2 weeks ago..

[Fat Fly]

@Richard-van-der-Plas what is this: HASS ?

[Richard van der Plas]

Ok, i am standig on a crossroad it seems, i have to build a new gateway but i am also interested in the MQTT option, this is between mysensors & HomeASSistant i presume? i have some ESP's lying around unused, but i have 0 knowledge of mqtt (i dont think my hass has it running by default)

[gohan]

Just go with ethernet first that is easier, get used to it then take your time to learn MQTT. Of course MQTT is more advanced has authentication and encryption but it adds complexity to initial setup.

[Richard van der Plas]

Damn, just connected as in manual, but gives an error : mysgw: !TSM:INIT:TSP FAIL
Double checked the GPIO pins (except 15 cannot find that one) but seems ok

[Richard van der Plas]

NM, used GPIO numbers instead of Pin numbers RTFM :)

[A Former User]

I always have a mysgw: accept: Bad file descriptor error when I launch a new ./bin/mysgw -d Exact problem is the following:

mysgw: bind: Address already in use
mysgw: Failed to bind!

And I always need to kill the process first. Is this normal ? (I'm in LAN GW)

Thanks!

[gohan]

If you already installed mysgw as service to start at boot, it is normal that you can not run another process in debug mode and it conflicts

[A Former User]

@gohan said in 💬 Building a Raspberry Pi Gateway:

lready installed mysgw as service to start at boot, it is normal that you can not run another process in debug mode and it conflicts

Oh, Ok. Thanks.
Another thing is that when i close PuTTY, the gateway doesn't retrieve anymore the data...

[gohan]

You need to install it as service so it always runs in background

[A Former User]

Is it this process :

1421 ?        Rs    40:25 /usr/local/bin/mysgw

Seems it runs for 40 minutes, but no the gateway sees no data...

[gohan]

what gateway did you compile? What option in ./configure did you use?

[A Former User]

First of all : thanks for helping !

I compiled an Ethernet gateway
The options are the following:

./configure --my-gateway=ethernet --my-port=5003 --my-rf24-irq-pin=15 --my-transport=nrf24

The only way I make the GW working is through the debug mode (by switching off the service process)

[A Former User]

Hello, it seems I found the problem: Complete newbie thing: :beginner:
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.
Thanks for taking time to help beginners !

[sillicius]

@Richard van der Plas : i was have the same error with my raspberry zero. I have succed with the devellopement branch version...