💬 Building a Raspberry Pi Gateway

[gohan]

@marceloaqno you forgot just a little little insignificant detail 😂

[marceloaqno]

@gohan @ftw64 sorry for all the trouble

[gohan]

It's OK, don't worry. We need to update the guide with the new instructions 😀

[marceloaqno]

@gohan Done!

[ftw64]

@marceloaqno Thanks! That indeed does the trick! And no worries, it is my own decision to play with beta(!) code (and it was a fun weekend troubleshooting it - I learned a lot about the structure of the MySensors code)!

Only 'bad' thing is that 2.2.0 is not compatible with my existing nodes :-).

I appreciate all the work that has been put into MySensors.

[Fat Fly]

This is really stupid. :D RFM69 radio need powered separately ?

[gohan]

They shouldn't, but it's always a matter trying 😀

[Oliver Acevedo]

This post is deleted!

[Richard van der Plas]

How will this work with HASS running on the same pi ?

[gohan]

It's the same as it was running on separate hw, you will only set ip address of the gateway in hass

[Richard van der Plas]

so i can attach the NRF24L01+ to the pi running HA, make it a Ethernet Gateway and point to his own ip adress ?, will this be a long job with converting from a USB connected GW (Arduino with local sensors ? )

[gohan]

That's pretty much it. I don't know what is your current setup and what sensors you have, but is should not be a long job. Anyway you can install the ethernet gateway and when you are done you take care of the sensors

[Richard van der Plas]

excellent, will the cpu utilisation be much higher that with a usb connected gw ?

[gohan]

No, it uses very few cpu

[manul]

@Richard van der Plas: I strongly recommend to use MQTT instead of Ethernet gateway, as it is a standard way for 2 processes to communicate, and platform-agnostic.
HASS comes with an embed MQTT broker taht works out of the box.
Plus:

• you can easily mock either your sensors network or your controller
• it does support secure communication
• you can add other clients to observe the event, e.g. to log what is coming from/what is sent to the gateway

[gohan]

I suggested ethernet because it's easier to setup and configure, mqtt is the next step.

[pettib]

Hi
I also have problem to get the NRF24L01+ chip to work with the RPi3.

I find that the masterbranch don't recognize the board as RPi3 and sets SoC and Type as unknown.
But if i take development branch it´s detecting RPi3 and seems to work correct.

This is result from development Branch configure:
[SECTION] Detecting target machine.
[OK] machine detected: SoC=BCM2837, Type=rpi3, 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.

This is result from Master Branch configure:
[SECTION] Detecting target machine.
[OK] machine detected: SoC=unknown, Type=unknown, CPU=armv7l.
[SECTION] Checking GPIO Sysfs.
[OK] /sys/class/gpio/export found
[SECTION] Detecting SPI driver.
[OK] SPI driver detected:SPIDEV.
[SECTION] Detecting init system.
[OK] init system detected: systemd.
[SECTION] Saving configuration.
[SECTION] Cleaning previous builds.
[OK] Finished.

This is the result from cat /proc/cpuinfo:

Hardware : BCM2835
Revision : a02082

//Peter

[gohan]

That's odd, I have the 2.1.1 compiled on mine rpi 3

[marceloaqno]

@pettib @gohan There have been some changes in /proc/cpuinfo in newer versions of kernels which leads to a wrong detection.
The problem was fix in #827 and will be available in the master branch in the next mysensor release.

[gohan]

I'm using dietpi and I compiled it like 2 weeks ago..