💬 Building a Raspberry Pi Gateway

[Anticimex]

@pepson signing is radio agnostic. It has nothing to do with the radio.

[sineverba]

@anticimex @wes Can I please ask how to update? I mean, the right command to type.
I have the folder "MySensors" on documents of my user in Pi:

/home/sineverba/MySensors

Of course I have all installed and perfectly working now (I'm on the 2.2.0 rc2).

I need also to relaunch the ./config command?

Thank you to both and all!

[Anticimex]

@sineverba https://www.mysensors.org/download

[Syna]

Hello, I configure the raspberry gateway to use MQTT. I set mosquitto as the broker. The problem that I encounter is that when I subscribe to test if the gateway publish on the broker, I have empty message. So my first guess is that there is an issue somewhere which cause that only empty message are sent.

Here is my arduino code : https://pastebin.com/YKi4EAad
The RasperryPI3 config & logs : https://pastebin.com/Kjn8CC8A
The MQTT Client logs : https://pastebin.com/ZP8GrkTj

[Sergio Rius]

Regarding the communication issues described in the instructions page with the 2.2 stable version, is that still valid and still recommended to use the development branch?

[gohan]

Go for stable now, I need to remove that line from the page

[Sergio Rius]

@gohan Thank you verys muchos. :+1:

[marceloaqno]

@syna It is empty because it's a message of type I_ID_REQUEST that your node is sending. You need to set up a controller to distribute IDs or you can set it manually by adding this to your node's sketch:

#define MY_NODE_ID X

where X is a unique number from 1 to 254.

[sineverba]

Hi to all,
tonight I made update from 2.2.0 RC2 to 2.2.0 (stable) on my Raspberry PI3.
It is a live system (my heater control).

By the way the update is very simple.

First of all, backup or better CLONE your PI.

1 - Disable the daemon with

sudo systemctl stop mysgw.service && sudo systemctl disable mysgw.service

2 - Make a copy of the MySensors folder ( I made a copy with the name of version coming, so...)

cp -r MySensors MySensorsX.X.X(rc2)/

(the slash at the end means "It's a folder!"

3 - Remove the MySensors folder

sudo rm -r MySensors

4 - Git the "new" MySensors folder && configure it as usual. Remember to activate the daemon and see on Domoticz (for example) the gateway with new version :)

[otto001]

Hi,

I am running the current version (2.2.0) on a RPi 1.
I noticed that sometimes the cpu usage of the service is increasing dramatically (around 90% and more) - and then the service stops working.
As I am not a C-Pro, I wrote a little python-script, which is called every minute by cron and restarts the service, if it uses more than 50% cpu.
Maybe someone will find it useful:

# -*- coding: utf-8 -*-
import psutil, sys, os, datetime

PY3 = sys.version_info[0] == 2
LOOKFOR = u"mysgw"
for proc in psutil.process_iter():
    if proc.name() == "mysgw":
        dt = str(datetime.datetime.now()).split('.')[0]
        #print(proc)
        cpu = proc.cpu_percent(interval=1)
        #print(cpu)
        #print(proc.cpu_times())
        if cpu > 50:
                print(dt + " high CPU-usage! --> restarting service")
                os.system("/bin/systemctl restart mysgw.service")
        else:
                if datetime.datetime.now().strftime('%M') == "45":
                        print(dt + " everything OK, cpu: " + str(cpu))

and the crontab-entry (as root):

* * * * * /home/pi/pstest.sh >> /var/log/mysgw-logger.log

Cheers,
Pula

[Nick Willis]

@otto001 Thanks for that! I'm also getting this annoying service failure on 2.2 on a RPi 2. It seems to happen at random at night when nothing much is going on in the house. It probably happens once every 1 to 2 weeks.
CPU use is almost 100% and the service stops working.
Are there any logs I can check? I'd prefer to know what's wrong although I'll go with the auto restart on high cpu use to prevent the house from ceasing to function at random!

[alowhum]

I once noticed this too, on a pi zero system with domoticz beta.

[otto001]

@Nick-Willis:
I do run the gateway in debug mode, but I could not see anything special.
Yesterday the service was auto-restarted by my script:

2018-02-27 13:31:03 high CPU-usage! --> restarting service```

On the same time in the "normal" mysgw.log (debugging enabled) (should be syslog normally, but I changed the logfile location for better investigation):

Feb 27 13:30:36 raspiez mysgw: TSF:MSG:READ,14-14-0,s=1,c=1,t=23,pt=7,l=5,sg=0:0.11
Feb 27 13:30:36 raspiez mysgw: TSF:MSG:READ,14-14-0,s=3,c=1,t=0,pt=7,l=5,sg=0:21.9
Feb 27 13:30:36 raspiez mysgw: TSF:MSG:READ,14-14-0,s=4,c=1,t=1,pt=7,l=5,sg=0:31.4
Feb 27 13:30:38 raspiez mysgw: New connection from 192.168.1.11 <-- fhem re-connects
Feb 27 13:30:38 raspiez mysgw: GWT:TSA:C=1,CONNECTED
Feb 27 13:31:04 raspiez mysgw: Received SIGTERM <-- AUTO-Restart

The only thing that is a little bit unusual is the re-connect of my controller (fhem) - but this happens every 30 minutes for stability reasons.
This should not happen, but I can not find out what the problem is.

Maybe you could also enable debugging by changing the following file (maybe we can find a pattern why this is happening):

/etc/systemd/system/mysgw.service

from

ExecStart=/usr/local/bin/mysgw

to

ExecStart=/usr/local/bin/mysgw -d

Please do not forget to issue a

sudo systemctl daemon-reload 

followed by

sudo systemctl restart mysgw.service

to enable the change.

My restarting-script might help until someone with better knowledge finds a solution...
I also will have an eye on the logs for findig out how often this is happening...

Cheers,
Otto

[marceloaqno]

Please, could all of you who experienced this issue post the configuration options you used to build the gateway?
This would help to investigate the problem.

[otto001]

@marceloaqno : of course, thanks for the hint!

I had the following configure:

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

(The high CPU problem also occured before I connected PIN 15 to IRQ without the corresponding config option. I hoped to solve the Problem using IRQ, but this did not help. And I have a second GW with default port 5003 in my network. This is running an ancient version of Raspi GW Software and this is working fine -but slower). I am using current fhem as controller and I have it connecting every 30 minutes to the gateways due to stability issues in the past. There are only about 6 nodes (just motion, humidity & temp and lux) connected to this gateway.

In addition to that I changed the default channel in MyConfig.h (because I have two different MySensor networks):

#ifndef MY_RF24_CHANNEL
#define MY_RF24_CHANNEL (82)
#endif

I am pretty sure, that this is not important, but I also set up rsyslog to write gw logs to an own file instead of syslog....

Maybe this helps.

Cheers,
Otto

[marceloaqno]

@otto001 I think I found the problem. I wrote a fix for it:
https://github.com/marceloaqno/MySensors/commit/ca8865d8e1fe1b08195943fae1640d5fddb81924

[otto001]

@marceloaqno : Wow, you are fast! Thanks!
Just applied the patch and recompiled. I will report in a couple of days while my monitoring-script is still running (and logging)...

Cheers,
Otto

[mvader]

@marceloaqno I am also recompiling and testing.
thanks for the (hopeful) fix
I will report back with my status in a few days

[otto001]

@marceloaqno :

At first, THANKS for your help. CPU usage does not rise anymore.
But unfortunately no more node READs after the same situation:

Mar  4 07:00:09 raspiez mysgw: TSF:MSG:READ,14-14-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
Mar  4 07:00:09 raspiez mysgw: TSF:MSG:READ,12-12-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
Mar  4 07:00:09 raspiez mysgw: GWT:RFC:C=1,MSG=14;255;3;0;6;M
Mar  4 07:00:09 raspiez mysgw: !TSF:MSG:SEND,0-0-14-14,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=NACK:M
Mar  4 07:00:09 raspiez mysgw: TSF:MSG:READ,11-11-0,s=255,c=0,t=18,pt=0,l=3,sg=0:1.5
Mar  4 07:00:09 raspiez mysgw: GWT:RFC:C=1,MSG=12;255;3;0;6;M
Mar  4 07:00:09 raspiez mysgw: TSF:MSG:SEND,0-0-12-12,s=255,c=3,t=6,pt=0,l=1,sg=0,ft=0,st=OK:M
Mar  4 07:00:13 raspiez mysgw: TSM:READY:NWD REQ
Mar  4 07:00:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar  4 07:00:13 raspiez mysgw: TSF:SRT:OK
Mar  4 07:00:13 raspiez mysgw: TSF:SAN:OK
Mar  4 07:00:37 raspiez mysgw: Ethernet client disconnected.
Mar  4 07:00:37 raspiez mysgw: New connection from 192.168.1.11
Mar  4 07:00:37 raspiez mysgw: GWT:TSA:C=0,CONNECTED
Mar  4 07:00:37 raspiez mysgw: GWT:TSA:C=1,DISCONNECTED

After this point (again after a reconnect from the controller) no more messages from any node PLUS the cpu usage stayed normal (what makes it even worse at this moment, as I would have to create a script which monitors the logfile and restarts the mysgw service in this situation). As soon as the service is restarted, everything is working fine again.

What happens after this point in the log:

Mar  4 07:00:37 raspiez mysgw: GWT:RFC:C=0,MSG=0;0;3;0;2;
Mar  4 07:15:13 raspiez mysgw: TSF:SAN:OK
Mar  4 07:20:13 raspiez mysgw: TSM:READY:NWD REQ
Mar  4 07:20:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar  4 07:30:13 raspiez mysgw: TSF:SRT:OK
Mar  4 07:30:13 raspiez mysgw: TSF:SAN:OK
Mar  4 07:30:37 raspiez mysgw: GWT:TSA:C=0,DISCONNECTED
Mar  4 07:30:37 raspiez mysgw: Ethernet client disconnected.
Mar  4 07:30:37 raspiez mysgw: New connection from 192.168.1.11
Mar  4 07:30:37 raspiez mysgw: GWT:TSA:C=0,CONNECTED
Mar  4 07:30:37 raspiez mysgw: GWT:RFC:C=0,MSG=0;0;3;0;2;
Mar  4 07:40:13 raspiez mysgw: TSM:READY:NWD REQ
Mar  4 07:40:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar  4 07:45:13 raspiez mysgw: TSF:SAN:OK
Mar  4 08:00:13 raspiez mysgw: TSM:READY:NWD REQ
Mar  4 08:00:13 raspiez mysgw: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
Mar  4 08:00:13 raspiez mysgw: TSF:SRT:OK
Mar  4 08:00:13 raspiez mysgw: TSF:SAN:OK
Mar  4 08:00:37 raspiez mysgw: GWT:TSA:C=0,DISCONNECTED
Mar  4 08:00:37 raspiez mysgw: Ethernet client disconnected.
Mar  4 08:00:37 raspiez mysgw: New connection from 192.168.1.11
Mar  4 08:00:37 raspiez mysgw: GWT:TSA:C=0,CONNECTED

and so on....

It seems that the increasing cpu usage is only a symptom for the real problem.
As I am using this in production I will dis-apply the patch and use the daemon as before (beacuse using the python script for cpu-usage-monitoring makes the situation somehow controllable for me).
Maybe you could have an additional eye on this please? Could I help you with further information? Maybe I could add some additional logging somewhere in the code?

Thanks again and cheers,
Otto

[marceloaqno]

@otto001 I'm trying to reproduce this problem, but so far I've got nothing beyond the normal behavior of mysgw.
I tried with a RPi1 and RPi3 using the fhem controller with the latest raspbian.