💬 Building a Raspberry Pi Gateway

[MasMat]

@marceloaqno OK, I will look into that once I have an extra sensor feeding my gw (the one I built is a little complex and could be buggy).

Another question: I configured mysgw without "simple password" to sort out problems.
Now to reconfigure mysgw I have to run the "./configure --blah --blahblah..." command and "make", but do I also have to do "make install"? And do I have to re-start & enable the service? Should I stop it first also? Anybody got a step-by-step for this?

[gohan]

You could also make a simple node running mock mysensors sketch that can simulate a working sensor, if you need some data running through the gateway. When I recompile the gateway I usually stop the service, uninstall the mysgw service and do the make and make install. I don't really know if it is actually required but I like to keep things clean

[marceloaqno]

The two patches to fix ethernet stability have been merger into the development branch, and also some changes to the gateway logging. I updated the build instructions to reflect the changes.

[MasMat]

@gohan I made a sensor that sends DHT11 temp+hum. This is the output (some of it..) from mosquitto_sub to topic mysensors-out. So I appear to have a something working. OpenHab2 is not finding any items still...

pi@DietPi:~ $ mosquitto_sub  -u XXXXXX -P YYYYYY -v -t 'mysensors-out/#'
mysensors-out/99/1/1/0/0 14.0
mysensors-out/99/0/1/0/1 46.0
mysensors-out/99/1/1/0/0 15.0
mysensors-out/99/0/1/0/1 45.0
mysensors-out/99/1/1/0/0 15.0
mysensors-out/99/0/1/0/1 45.0
mysensors-out/99/0/1/0/1 44.0
mysensors-out/99/0/1/0/1 45.0
mysensors-out/99/0/1/0/1 44.0
mysensors-out/99/1/1/0/0 15.0
mysensors-out/99/0/1/0/1 45.0
mysensors-out/99/1/1/0/0 15.0
mysensors-out/99/0/1/0/1 44.0
mysensors-out/99/0/1/0/1 45.0
mysensors-out/99/0/1/0/1 44.0
mysensors-out/99/1/1/0/0 15.0
mysensors-out/99/0/1/0/1 44.0
mysensors-out/99/1/1/0/0 15.0

Once I changed the config to include simple password, it's not showing anything anymore in mosquitto_sub
It would appear that something is missing from my setup or there's a bug in the configure-line. Can someone tell if there's a bug here somewhere:

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

[gohan]

Look also in node log, that's the first place to look at

[MasMat]

@gohan I did, I will post it (but it appears to send normally). But the only things I changed was:

1. Rpi configure added: --my-signing=password --my-signing-password=ZZZZZZ
2. In the nodes code: #define MY_SIGNING_SIMPLE_PASSWD = "ZZZZZZ"

[gohan]

I use also these parameters with the normal signing

--my-signing=software --my-signing-request-signatures --my-signing-weak_security --my-signing-debug

of course the debug parameter is there only for debug reasons

[Anticimex]

@masmat check that the version you are using (release or beta) match your use of the simple flags, as they differ at the moment.

[MasMat]

@anticimex Both Arduino IDE is 2.2 and Rpi is compiled with 2.2 stable.
I'm seeing !TSF:MSG:SIGN FAIL in the serial monitor so something is not compatible... I will try making password >8 characters next (currently 6).

I will also add those parameters to see if that makes a difference before reuploading arduino code

[Anticimex]

@masmat if you add the signing debug flag and use the log parser on the homepage it should become clear what the problem is. You can also use the troubleshooting guide in the signing documentation.

[MasMat]

@anticimex This is what's happening in the gw:

TSF:MSG:READ,36-192-15,s=69,c=0,t=81,pt=1,l=21,sg=0:221
!TSF:MSG:LEN,16!=28
TSF:MSG:READ,75-68-77,s=48,c=1,t=110,pt=1,l=25,sg=1:249
!TSF:MSG:LEN,16!=32

The parser didn't really help much: more baffled than before....and I came away from the troubleshooting guide feeling really stupid :)

[Anticimex]

@masmat looks to me that your gateway is not set up for signing

[gohan]

@anticimex I think he didn't use all the parameters for the configure, right?

[Anticimex]

@gohan the simple flags should not need more args, but I don't use a rPi as gw so I honestly am not sure exactly the args to use. The beta documentation has clear instructions for rPi signing, but those are specifically for beta branch and probably don't map exactly to the release yet.

[MasMat]

@gohan The whole configure-line:

sudo ./configure --my-transport=nrf24 --my-rf24-irq-pin=15 --my-signing=software --my-signing-request-signatures --my-signing-weak_security --my-signing-debug --my-signing=password --my-signing-password=ZZZZZZ --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-user=XXXX --my-mqtt-password=YYYYY --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18

If anyone can tell what's missing or if there's a typo?

[Anticimex]

@masmat https://www.mysensors.org/apidocs/group__RaspberryPiGateway.html

[Anticimex]

@masmat you have redundant flags. The password option require no other signing flags. Only if you select software as signing backend you need other options (and none of the simple flags)

And remember that if you use software signing and not password signing, you need to personalize the GW and/or node.

[MasMat]

@anticimex I thought so too, but I'm grasping at straws to get the signing to work.
To clarify, is the following enough for simple signing: --my-signing-debug --my-signing=password --my-signing-password=ZZZZZZ

And the arduino code #define MY_SIGNING_SIMPLE_PASSWD = "ZZZZZZ"
Any difference where it's placed in the code? Anything else to check for?

[Anticimex]

@masmat it needs to be defined prior to the inclusion of mysensors.h. That should be it. (on the arduino node that is).

[alowhum]

While on the subject: what would be the flags needed for setting the gateway to only use the simple encryption but not the (simple) signing feature?

I looked in the documentation and the node commands aren't mirrored for the gateway. I was hoping for something like:

--MY_SIGNING_SIMPLE_PASSWD=flowerpot77
--MY_ENCRYPTION_SIMPLE_PASSWD=spiderman41