💬 Building a Raspberry Pi Gateway

[pjeran]

@PhracturedBlue

Thanks for the link and the work, I will give this a shot.

Paul

[Reza]

This post is deleted!

[Mihai]

@eyesoft
As far as I understand, MySensors relay on PubSubClient for MQTT and it does not allow to publish messages with QOS=1 or 2, only 0.
Retain is different that QOS, it offers the possibility to recover the state for a device that loose connection for a while (e.g. after a restart). I find it very usefull. For example I have to restart the controller. When come back I got all states to their real values if retain=true. Otherwise they goes to the default, usually 0.
I have now 6 nodes, each with several sensors and relays.

[Reza]

please help :(
every time after reboot i have to run this code

sudo ./bin/mysgw -d

so built a virtual usb but after reboot ....

how put this code in startup ? :( please help thank you

[marceloaqno]

@Reza

From the Building a Raspberry Pi Gateway article:

If you wish to install:

sudo make install

The last command will provide instructions for your system on how to start the gateway on every boot.

[Reza]

@marceloaqno
i do it but after reboot serial lost again :(
just with command work again

sudo ./bin/mysgw -d

[Reza]

@marceloaqno
i'm sorry
after sudo make install i must run this lines:

 sudo systemctl enable mysgw.service
 sudo systemctl start mysgw.service

sorry thank you

[Reza]

@marceloaqno can you build a rs485 gateway on raspberry pi ?

[eyesoft]

@Mihai yes you are right

[Shantanu Mhapankar]

This data that I get when I run ./mysgw --d , where is it stored and how can I get it to push it on cloud? Please help.

[Tag]

@Shantanu-Mhapankar

Data is not stored... to store the data and do something usefull with it (or not) you need a controller. I use mycontroller, and from this software you can "push" data to an external server.
I use my controller, but i am sure that other controller software also has this feature.

[Shantanu Mhapankar]

@Tag , The controller must be using something to get the data right? How can we do it directly without using the controller?

[pete1450]

@hek It looks like development is the default branch in the repository. I was following the build instructions and couldn't figure out why I kept getting "connection refused". Just typing up a troubleshooting post when I saw my log said 2.2.0-beta. Sure enough when I grabbed master(2.1.0) instead it ran fine. Should probably add a checkout in the instructions.

[mfalkvidd]

@pete1450 could you clarify which instructions should be updated?

The instructions at https://www.mysensors.org/about/arduino recommend using the Arduino IDE Board manager, which will get the latest stable version.

Edit: Now I see. The link in the first post in this thread. It doesn't mention the master branch because up until Dec 25th the development branch was required. But now that 2.1 has been released the instructions should indeed use the stable version. I've updated the instructions. Thanks for noticing!

[Tag]

@Shantanu-Mhapankar

This is also new for me since i do not send data into any cloud... but i can imagine that you can use MQTT. (see https://www.mysensors.org/build/mqtt_gateway for more details) is important that the receiving side supports MQTT. in this case google is your friend ;)

if you do a ./configure --help you will find you can build the mysensors gateway with MQTT support

./configure --help 
...
    --my-gateway=[ethernet|serial|mqtt]
                                Gateway type, set to none to disable gateway feature. [ethernet]
    --my-node-id=<ID>           Disable gateway feature and run as a node with given id.
    --my-controller-url-address=<URL>
                                Controller or MQTT broker url.
    --my-controller-ip-address=<IP>
                                Controller or MQTT broker ip.
    --my-port=<PORT>            The port to keep open on gateway mode.
                                If gateway is set to mqtt, it sets the broker port.
...

[LaMB95]

ran sudo ./bin/mysgw -d
I keep getting mysgw: accept: Bad File Descriptor.
Any possible cause ?

[marceltrapman]

I am trying to get the raspi ethernet gateway running but on both my pi 3 (also running openHAB) and the pi B (pretty basic install).

Unfortunately I get the same error on both.

Any ideas what could be going on here?

I am running the latest gateway and the latest raspbian.

mysgw: Starting gateway...
mysgw: Protocol version - 2.1.0
mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.1.0
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: connect: Connection refused
mysgw: failed to connect
mysgw: Eth: connect
mysgw: connect: Connection refused
mysgw: failed to connect
mysgw: Eth: connect

[LaMB95]

@marceltrapman

I am using a Rasp Pi 3 as well.
I can't even proceed further in the tutorial cause of this error cause nothing works after it.

[marceloaqno]

@marceltrapman @LaMB95
Could you post the complete ./configure command used to configure the gateway?

[marceltrapman]

@marceloaqno Sure, forgot it :)

sudo ./configure \
    --my-gateway=ethernet \
    --my-controller-ip-address=192.168.1.xx \
    --my-port=5003 \
    --my-transport=nrf24