💬 Building a Raspberry Pi Gateway

[marceloaqno]

@gieljnssns The fixes I mentioned above haven't yet been applied to the development branch. Eventually they will be, but I'm still doing some testing.

[otto001]

@marceloaqno :
Thank you!!! Should this patch be applied together with your first patch?
Interesting:
After some days without problems on the newest raspbian packages the gw hung again, but WITHOUT high cpu usage (and WITHOUT your first patch applied). There were just no more reads from the sensors in the log, only the re-connects of fhem. After restarting the service, everything is fine again.
Unfortunately I did see your post after that :-(
But I checked the log and could not find the words "too" or "Too" in the log (running service with -d).
Some minutes after restarting I checked how many open files there were with the command you supplied: 21

In the meantime I have created a small udp listening service which restarts the service if a certain string is received, so I can restart the service by double-clicking one of my switches without the need of login to the gw (also for the wife)....

@gieljnssns : I think you are experiencing exactly the same problem we are discussing :-)

Thanks again!
Cheers,
Otto

[gohan]

I'm using dietpi and I am not having big issues even running 2 gateway instances with 2 different radios

[marceloaqno]

@otto001 The second patch can be applied without the first one.

[otto001]

@gohan :
dietpi looks interesting! did not know about this yet.
what hardware are you using? and what version of mysgw?

[otto001]

@marceloaqno :
THANKS! Just applied your patch.
I will report in a few days when I can see if the problem is solved...
Cheers,
Otto

[A Former User]

Can someone tell me how to apply this patch?

[gohan]

@otto001 normal rpi3 and mysgw 2.2

[MasMat]

I need help with my Rpi mqtt-gw.
I tried to get dev-branch working but changed now to stable. All the install routines run without problems. The service just doesn't seem to work and I can't figure out why.

1. Rpi W, Raspbian wheezy, nRF24-PA, MQTT-gw, Mosquitto and Openhab2 on same board
   Mosquitto-log:

1521010232: New connection from 127.0.0.1 on port 1883.
1521010232: New client connected from 127.0.0.1 as mygateway1 (c1, k15, u'xxxx').
1521010232: Socket error on client mygateway1, disconnecting.

syslog:

Mar 14 08:51:02 GwMqOH2 systemd[1]: Starting MySensors Gateway daemon...
Mar 14 08:51:02 GwMqOH2 systemd[1]: Started MySensors Gateway daemon.
Mar 14 08:51:03 GwMqOH2 mysgw: Starting gateway...
Mar 14 08:51:03 GwMqOH2 mysgw: Protocol version - 2.2.0
Mar 14 08:51:03 GwMqOH2 mysgw: MCO:BGN:INIT GW,CP=RNNGLSQX,VER=2.2.0
Mar 14 08:51:03 GwMqOH2 mysgw: TSF:LRT:OK
Mar 14 08:51:03 GwMqOH2 mysgw: TSM:INIT
Mar 14 08:51:03 GwMqOH2 mysgw: TSF:WUR:MS=0
Mar 14 08:51:03 GwMqOH2 mysgw: TSM:INIT:TSP OK
Mar 14 08:51:03 GwMqOH2 mysgw: TSM:INIT:GW MODE
Mar 14 08:51:03 GwMqOH2 mysgw: TSM:READY:ID=0,PAR=0,DIS=0
Mar 14 08:51:03 GwMqOH2 mysgw: MCO:REG:NOT NEEDED
Mar 14 08:51:03 GwMqOH2 mysgw: MCO:BGN:STP
Mar 14 08:51:03 GwMqOH2 mysgw: MCO:BGN:INIT OK,TSP=1
Mar 14 08:51:03 GwMqOH2 mysgw: GWT:RMQ:MQTT RECONNECT
Mar 14 08:51:03 GwMqOH2 mysgw: connected to 127.0.0.1
Mar 14 08:51:03 GwMqOH2 mysgw: GWT:RMQ:MQTT CONNECTED
Mar 14 08:51:03 GwMqOH2 mysgw: GWT:TPS:TOPIC=mysensors-out/0/255/0/0/18,MSG SENT
Mar 14 08:51:03 GwMqOH2 systemd[1]: mysgw.service: main process exited, code=killed, status=11/SEGV
Mar 14 08:51:03 GwMqOH2 systemd[1]: Unit mysgw.service entered failed state```



GW configure-line:

./configure --my-transport=nrf24 --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-rf24-irq-pin=15 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18 --my-mqtt-user=xxxx --my-mqtt-password=yyyyy --my-signing=password --my-signing-password=zzzzzz```

I have checked mosquitto has correct user-pw combination, but what should I check next? Help!

[gohan]

@masmat said in 💬 Building a Raspberry Pi Gateway:

--my-mqtt-client-id=mygateway1

Do you have another client named mygateway1 connecting to mqtt? Try changing it to a different name just to play safe

[MasMat]

@gohan Can I just edit mysgw.cpp and do "daemon-reload"?
I have just this one gw. And openHab2 but that has a different id.

[gohan]

No, you need to recompile it again in case you make that change. Have you ever tried dietpi for RPI?

[MasMat]

@gohan OK. I did that, the same socket error remains in Mosquitto just under new id.
Is my syntax correct or am I somehow having problems with mosquitto user-pw...?

Haven't tried DietPi. Would Mys+Mosquitto+Openhab2 have trouble running on it? Or why should I change to it?

[gohan]

have you tried connecting with another mqtt client like mqttfx to see if everything is working?

[marceloaqno]

@masmat What is the mqtt broker / version you are using?

[marceloaqno]

@gieljnssns One way is to replace the changed files, in this case EthernetServer.cpp for the first patch and EthernetClient.cpp for the second patch.

You can download from:
https://raw.githubusercontent.com/marceloaqno/MySensors/linux-fix-stability/drivers/Linux/EthernetServer.cpp
https://raw.githubusercontent.com/marceloaqno/MySensors/linux-fix-stability/drivers/Linux/EthernetClient.cpp

Here is a step-by-step:

git clone https://github.com/mysensors/MySensors.git
cd MySensors
curl https://raw.githubusercontent.com/marceloaqno/MySensors/linux-fix-stability/drivers/Linux/EthernetServer.cpp -o drivers/Linux/EthernetServer.cpp
curl https://raw.githubusercontent.com/marceloaqno/MySensors/linux-fix-stability/drivers/Linux/EthernetClient.cpp -o drivers/Linux/EthernetClient.cpp

from here just run ./configure with your options and then make

[MasMat]

@marceloaqno Mosquitto v1.4.14.
The broker is working, at least sending & receiving command line (_sub & _pub) messages.

[A Former User]

@gohan

Can you provide some installation instructions for dietpi?
I will try this...

[gohan]

just download the image and do the same as a Raspian image. I haven't tried mqtt gateway yet, so I don't know if it may be a gateway bug or else.

[otto001]

@marceloaqno :
Hi, unfortunately the latest patch did not work for me.
Still the gw stops receiving, but without high cpu usage :-(
Fortunately I can restart the gw now using a button and this udp-scripts :-)

Of cource I could give dietpi a try, but I would think, that a general solution would be better (for other users as well)

cheers,
Otto