💬 Building a Raspberry Pi Gateway

[mfalkvidd]

@Patrik-Söderström said:

Can I attach one or more DallasTemp sensors on the Raspberry Pi gateway?

I haven't seen anyone doing anything similar so it might require some work. But almost anything is possible given enough work :)

[jerseyguy1996]

Has anyone else had an issue with getting a sensor node to reconnect after a lost connection? I can see it attempting to reconnect but even though it is back within range of the gateway it won't reestablish the connection. If I reset the node it re-establishes the connection without any problem. This is the cycle that it gets stuck in:

TSM:FPAR
TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 0-0-3 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=3)
TSM:UPL
TSP:PING:SEND (dest=0)
!TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=fail:1
TSP:CHKUPL:FAIL (hops=255)
!TSM:UPL:FAIL
TSM:FPAR
TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
TSM:FPAR
TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 0-0-3 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=3)
TSM:UPL
TSP:PING:SEND (dest=0)
!TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=fail:1
TSP:CHKUPL:FAIL (hops=255)
!TSM:UPL:FAIL
TSM:FPAR
TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR
!TSP:SEND:TNR```

[alexsh1]

@Christian-Simonsen multimeter will not detect issues with the power feed (noise or unstable). It just says that you voltage under zero load is 3.3V.

[carlyler]

Appears things are changing, please update wiki:
Warning: --my-radio is deprecated, please use --my-transport

[Patrik Söderström]

@mfalkvidd Alright :) The thing is that I have my Raspberry Pi as a Gateway today near my server rack and would like to measure the temperatur. Maybe I just get a Nano to do the work for me. Just would have been great to use the Raspberry.

[mfalkvidd]

@Patrik-Söderström You can probably connect a temperature sensor to the gpio pins and have your controller read the sensor (without using MySensors)

[marceloaqno]

@carlyler Thanks for pointing that out.

[marceloaqno]

@jerseyguy1996 Are you using a decoupling capacitor?

[jerseyguy1996]

@marceloaqno Yes its 220 uF. It was all I had handy. I read somewhere that this may be a problem specific to the arduino nano. I may give it a try with the pro mini. Although I'm not sure what that may have to do with it.

Edit: I tried the same sketch on an arduino pro mini and it worked fine. When I simulated a loss of connection by walking out of range of the gateway it immediately reestablished the connection when I got back within range. The only difference is that the pro mini is running at 8 mhz whereas the nano runs at 16 mhz. Not sure how that affects things.

[Velo17]

Hello everyone. Is there a way to reduce the number of Heartbeat messages the gateway produces by itself? Using MYSController to analyze the data traffic, I see every 10 seconds a Heartbeat - would like to reduce this once everything is working as expected to maybe every 5 or 10 minutes...

[hek]

@Velo17

Just sleep longer. It sends one heartbeat every time the node wakes up.

[dopeeye]

@Christian-Simonsen

I have exactly the same error

mysGateway: !TSF:MSG:LEN,0!=7

Have you been able to resolve that problem yet? I have tried multiple radios with different capacitors and powersources grounded to the Raspberry Pi.

thanks

[Christian Simonsen]

@dopeeye

Sadly not. I ended up creating an serial gateway (arduino with NRF24L01 and a USB connector) and connected this to the Raspberry Pi, rather than connecting the NRF24L01 directly to the GPIO pins. This worked perfectly straight away.

[dopeeye]

@Christian-Simonsen

Too stubborn to give up, yet.
If i find a resolution I will let you know

[Graham]

I would like to try this, but my pins19-23 are already used by other hardware. Has anyone tried using the SPI1 Pins?

[carlyler]

@dopeeye I had this issue and unfortunately changed several things at once and got rid of it. However, one thing I noticed was I had different versions of mySensors in my library directory since I downloaded the examples package. Therefore the sensor was likely compiling on a different version than the Gateway. You might want to check that.

If you could post more of your logs (sensor and gateway) it might help.

[ericvdb]

@marceloaqno

When running as a service, is there a way to watch the debug log?

[Patrik Söderström]

Any ETA on support for RFM69 ? Need to extend my coverage :)

[alesc]

Done:

1. git clone https://github.com/mysensors/MySensors.git
2. ./configure --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
3. make.
   Got error:
   In file included from ./MySensors.h:287:0,
   from examples_linux/mysGateway.cpp:70:
   ./drivers/RF24/RF24.cpp: In function âuint8_t RF24_spiMultiByteTransfer(uint8_t, uint8_t*, uint8_t, bool)â:
   ./drivers/RF24/RF24.cpp:65:22: error: âNOPâ was not declared in this scope
   *ptx++ = NOP ;
   ^
   Makefile:46: recipe for target 'examples_linux/mysGateway.o' failed
   make: *** [examples_linux/mysGateway.o] Error 1
   Any idea?

[mfalkvidd]

@alesc looks like this commit in the development branch broke the code.

Do

git checkout master

before running configure should get the code to the latest stable release.

EDIT: Sorry, that won't work because the Raspberry Pi stuff didn't exist when MySensors 2.0 was released. You'll have to do git pull instead, to get tekka's fix.