💬 Building a Raspberry Pi Gateway
-
I can run
mysgw. But what can I use it for? I want to make it control my light with 2.4G RF. But I don't know what to do next. Please advice Thank you. -
@ccy
You need to provide some more details about your hw and general setup, what have you done so far, log messages, etc. -
Do you mean your light has already 2.4G RF or do you need to make a relay node with NRF24 that can switch on and of that light? But this is going a little OT in this thread.
-
@gohan Yes. I want to do that. I am sure my LED controller is 2.4G RF. But I can't detect any signal yet from my nrf24l01+ on raspberry pi. I am not sure what's wrong. Still trying now...
@ccy
Being 2.4G RF doesn't mean it is NRF24L01 compatible also without knowing what channel is using will make it even more difficult. So, unless you want to make a Mysensors LED Controller, I think you are out of luck if you want to directly control your existing one with a RPI and the mysensors gateway. Either way this is OT. -
@ccy
Being 2.4G RF doesn't mean it is NRF24L01 compatible also without knowing what channel is using will make it even more difficult. So, unless you want to make a Mysensors LED Controller, I think you are out of luck if you want to directly control your existing one with a RPI and the mysensors gateway. Either way this is OT. -
Hello everyone!
I'm using a Rasp2 (with the 40 pins GPIO header)
Has anyone experience with using the NRF module on different pins than default? I'm asking because I wonder if I can connect a GPIO-connected touch TFT (which would use the 2 CE lines for the touch and display interfaces) together with the NRF - by hooking the MISO/MOSI/SCLK to the default pins (and thus sharing them between the TFT and NRF) and defining free pins for the CE and CS lines in the ./configure script when compiling the gateway code...?!
Or maybe using the SPI1 by first enabling it as laid out in this blog post - but how to proceed from there? (How to tell the gateway code to use SPI1?)
-
./configure --spi-driver=SPIDEV --spi-spidev-device=/dev/spidev1.0(replace the /dev/spidev1.0 with the one you enabled in /boot/config.txt)
-
Hello Masters,
Could you please help me with setting up virtual serial port?
I can't see the interface created under /dev.
I'm using the instructions and finish with the setup with the following command:pi@raspberrypi:/tmp/MySensors $ ./configure --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttyMySensorsGateway [SECTION] Detecting target machine. [OK] machine detected: SoC=BCM2836, Type=Rpi2, CPU=armv7l. [SECTION] Detecting SPI driver. [OK] SPI driver detected:BCM. [SECTION] Detecting init system. [OK] init system detected: systemd. [SECTION] Saving configuration. [SECTION] Cleaning previous builds. [OK] Finished.pi@raspberrypi:/ $ sudo /usr/local/bin/mysgw -d mysgw: Starting gateway... mysgw: Protocol version - 2.1.1 mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.1.1 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: Listening for connections on 0.0.0.0:5003 mysgw: MCO:BGN:STP mysgw: MCO:BGN:INIT OK,TSP=1Everything seems to be OK. However, when I check /dev directory, the interface is not created.
What could be an issue?
Thank you in advacne! -
@gohan I'm sorry, MQTT is not supported by OpenHab MySensors binding. Ethernet Gateway is not supported on Raspberry PI.
@engy OpenHab2 supports mysensors serial and ethernet gateways:
https://github.com/tobof/openhab2-addons/wikiMaybe the build guide may have given you that impression, but ethernet Gateway is supported on Raspberry PI:
./configure --my-gateway=ethernet -
@keldandorin just add a capacitor between vcc and gnd on the radio module as I suggested above.
@gohan Solved the problem with radio...Thx
-
@engy OpenHab2 supports mysensors serial and ethernet gateways:
https://github.com/tobof/openhab2-addons/wikiMaybe the build guide may have given you that impression, but ethernet Gateway is supported on Raspberry PI:
./configure --my-gateway=ethernet -
Hi
Is anyone else having this same problem on Rpi3?: Gateway works ok after "sudo make install" with openHAB. With "sudo ./bin/mysgw -d" I can get debug log visible and log works ok.
But if I run "sudo systemctl enable mysgw.service" after "sudo make install", debug log start showing endlessly "mysgw: accept: Bad file descriptor". So debug log function gets destroyed and it can't be used anymore. I have made several clean installations and every time this same happens.
Br
Tommi -
Hi
Is anyone else having this same problem on Rpi3?: Gateway works ok after "sudo make install" with openHAB. With "sudo ./bin/mysgw -d" I can get debug log visible and log works ok.
But if I run "sudo systemctl enable mysgw.service" after "sudo make install", debug log start showing endlessly "mysgw: accept: Bad file descriptor". So debug log function gets destroyed and it can't be used anymore. I have made several clean installations and every time this same happens.
Br
Tommi@TommiP What I think is happening is that you are running two instances of the gateway.
If you need to get the debug logs, first stop the mysgw service:sudo systemctl stop mysgw.service -
@TommiP What I think is happening is that you are running two instances of the gateway.
If you need to get the debug logs, first stop the mysgw service:sudo systemctl stop mysgw.service@marceloaqno
Ok, now I understand what happened, thanks.
